03:45:00  * node-ghjoined
03:45:01  * node-ghpart
05:23:57  <joyee>test-digitalocean-freebsd10-x64-1 has been constantly timing out...cannot make much out of the logs https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd10-64/18652/console
05:32:02  <joyee>I restarted the machine
05:55:30  <joyee>Weird, I cannot start any job manually from https://ci.nodejs.org/job/node-test-commit-freebsd/nodes=freebsd10-64/ ...
05:55:57  <joyee>There is not the "Build" button
07:24:53  * richardlaujoined
07:27:21  * richardlau_quit (Ping timeout: 240 seconds)
07:34:19  * Steve_pquit (Ping timeout: 260 seconds)
07:47:21  <lucalanziani>joyee I think you are inside the configuration for the node, the build button is on the job https://ci.nodejs.org/job/node-test-commit-freebsd/
08:12:46  * BridgeARjoined
09:07:43  <joyee>lucalanziani: ahh thanks
09:08:27  <joyee>:( the job is still timing out
09:12:03  <joyee>It's always compiling openssl before timing out. Maybe there's something wrong with the compiler
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
10:40:27  * thefourtheyejoined
11:18:28  * seishunjoined
13:10:07  * thefourtheyequit (Quit: Connection closed for inactivity)
13:19:29  * node-ghjoined
13:19:29  * node-ghpart
13:20:14  * node-ghjoined
13:20:14  * node-ghpart
13:21:19  * node-ghjoined
13:21:19  * node-ghpart
13:22:57  * seishunquit (Ping timeout: 240 seconds)
13:41:47  * seishunjoined
14:02:21  <maclover7>joyee: maybe try running the jenkins worker create playbook to restore the machine?
14:05:09  <refack>maclover7: you have been keeping changing the live job with an reviewed code - https://ci.nodejs.org/job/node-test-commit-freebsd/jobConfigHistory/showDiffFiles?timestamp1=2018-06-21_18-07-42&timestamp2=2018-06-22_14-59-39
14:05:26  <refack>I'm suspending your previliges
14:13:29  <maclover7>refack: that seems a bit extreme
14:13:45  <maclover7>to be honest, the reason why I haven't opened up a PR yet is because the last time I did, you kind of jumped on my code and ran with it
14:13:59  <maclover7>and I didn't really want to deal with that until I knew the script was working properly
14:14:16  <maclover7>Also, everything is in git version control, and you can see the job config history to see what it is I am doing with the job
14:14:37  <refack>You are defient, refuse to comunicate, and are causing regressions and wasting other colaborators time.
14:15:29  <refack>I've commented about that, asked you not to proceed without further review, and you choose to unilateraly play with the organization's resources.
14:15:31  <maclover7>How am I wasting other collaborator's time? If anything combining the scripts makes them much easier to maintain over the long run, given how much code is shared
14:15:38  <refack>You've lost my trust
14:55:03  <refack>After I've reverted the job's configuration conmpilation seems to finish:
14:55:04  <refack>https://ci.nodejs.org/job/node-test-commit-freebsd/18659/nodes=freebsd10-64/console ( test-joyent-freebsd10-x64-1 )
14:55:04  <refack>https://ci.nodejs.org/job/node-test-commit-freebsd/18658/nodes=freebsd10-64/console ( test-digitalocean-freebsd10-x64-1 )
16:07:46  * seishunquit (Ping timeout: 260 seconds)
17:42:23  * seishunjoined
19:38:44  * BridgeARquit (Ping timeout: 276 seconds)
20:16:12  * BridgeARjoined
20:20:21  * seishunquit (Ping timeout: 240 seconds)
21:33:52  * seishunjoined
22:54:35  * seishunquit (Ping timeout: 240 seconds)
23:55:51  * BridgeARquit (Ping timeout: 256 seconds)