01:52:35  * evanlucas1quit (Ping timeout: 240 seconds)
02:38:23  * chorrelljoined
03:12:41  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
08:37:56  * seishunjoined
10:25:10  * mylesborinsquit (Quit: farewell for now)
10:25:41  * mylesborinsjoined
11:25:29  * seishunquit (Ping timeout: 258 seconds)
11:42:42  * seishunjoined
11:50:11  * addaleaxjoined
11:51:23  <addaleax>Hi everyone! I’m seeing this in CI:
11:51:25  <addaleax>https://ci.nodejs.org/job/node-test-binary-arm/8743/RUN_SUBSET=addons,label=pi2-raspbian-wheezy/console
11:51:26  <addaleax>ccache: error: Failed to create temporary file for /tmp/addon.stdout: Input/output error
11:51:28  <addaleax>addon.target.mk:91: recipe for target 'Release/obj.target/addon/addon.o' failed
12:55:29  * refackquit
13:11:52  * node-ghjoined
13:11:52  * node-ghpart
13:40:39  * refackjoined
13:51:35  * refackquit (Ping timeout: 240 seconds)
15:01:10  * seishunquit (Ping timeout: 240 seconds)
15:18:36  * refackjoined
15:27:08  * refackquit (Ping timeout: 255 seconds)
15:52:39  * addaleaxquit (Quit: ChatZilla 0.9.93 [Firefox 54.0/20170612122018])
16:16:25  * seishunjoined
16:53:06  * node-ghjoined
16:53:06  * node-ghpart
16:59:57  * seishunquit (Ping timeout: 240 seconds)
17:05:19  * seishunjoined
17:07:26  * node-ghjoined
17:07:26  * node-ghpart
18:39:21  <joaocgreis>seishun: I don't think so. Windows should be obvious from the jenkins labels, for others you can check the ansible scripts in the build repo but there have been issues to update compilers and I'm not sure if the scripts were updated as well. If you want to know a specific machine, I can check
18:40:41  <seishun>it seems most of them use gcc 4.8. I'm now trying to figure out how ansible works
18:48:50  * benglquit (*.net *.split)
18:48:52  * othiym23quit (*.net *.split)
18:48:52  * rvaggquit (*.net *.split)
18:48:52  * phillipjquit (*.net *.split)
18:48:52  * zkatquit (*.net *.split)
18:48:52  * orangemochaquit (*.net *.split)
18:49:24  <seishun>joaocgreis: gibfahn mentioned that you haven't moved over to the new scripts completely, is there a list of boxes that already use the new scripts?
18:49:33  * othiym23joined
18:49:37  * orangemochajoined
18:49:49  * rvaggjoined
18:49:55  * phillipjjoined
18:49:56  * bengljoined
18:50:21  * zkatjoined
18:52:59  <joaocgreis>seishun: no. I believe the new scripts already support most simple test runners (at least windows excluded). It's mostly other servers that are missing (www, backup, ci master). I don't know what has and hasn't been redeployed with the new scripts
18:53:36  <seishun>so if I want to make modifications I should look at the new scripts right?
19:05:18  <joaocgreis>seishun: yes, for test servers it should be mostly done. Let us know if you find something off
19:07:59  * node-ghjoined
19:07:59  * node-ghpart
19:16:13  * refackjoined
20:44:33  <seishun>joaocgreis: would this guide still work for testing new scripts? https://github.com/nodejs/build/blob/master/setup/TESTING_LOCALLY.md
20:53:01  * node-ghjoined
20:53:01  * node-ghpart
21:03:12  * seishunquit (Read error: Connection reset by peer)
21:11:41  * seishunjoined
21:21:51  * node-ghjoined
21:21:51  * node-ghpart
22:08:32  * seishunquit (Read error: Connection reset by peer)
22:21:36  * node-ghjoined
22:21:36  * node-ghpart
23:01:25  * chorrelljoined
23:06:52  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)