01:40:04  * node-ghjoined
01:40:04  * node-ghpart
01:46:35  * Fishrock123joined
01:55:27  <rvagg>thealphanerd: any chance there's a cleanup going on in the job that's doing so prematurely? I can't think of what else it might be
04:03:43  <Trott>https://ci.nodejs.org/job/node-test-commit-arm-fanned/2636/ doesn't seem to want to take YES for an answer. All sub-jobs are green but it's been spinning for some time....
04:31:07  <jbergstroem>ill hvae a look
04:31:13  <jbergstroem>says green though?
04:47:31  <Trott>Fixed itself, I guess. Took a looong time. /shrug
04:56:35  <rvagg>you just need patience grasshopper
05:02:27  * Fishrock123quit (Quit: Leaving...)
05:16:04  * evanlucasquit (Remote host closed the connection)
05:29:19  * rmgquit (Remote host closed the connection)
05:29:52  * rmgjoined
05:34:12  * rmgquit (Ping timeout: 246 seconds)
05:37:03  <Trott>Looks like the stress tests aren't working. They seem to build and then not run the tests. It looks like their parameters are not being passed. See, for example, https://ci.nodejs.org/job/node-stress-single-test/717/nodes=centos7-64/parameters/ which only has four parameters but there are a handful more in the form you fill out to launch the job, including
05:37:03  <Trott>one that specifies the test you want to run and another that specifies how many times to run it.
05:39:58  <thealphanerd>jbergstroem ^^^
05:40:05  <thealphanerd>Trott this was a known bug with the security update
05:40:11  <thealphanerd>env vars need to be whitelisted
05:41:56  <Trott>I'm aware of the env vars part. I'm not sure what you mean by "known bug".
05:44:48  <Trott>(Are you just speaking loosely and mean something more like "Yeah, there was a high probability that there were some missed env vars in there somewhere...")
05:44:57  <jbergstroem>will check
05:45:42  <jbergstroem>RUN_TESTS, RUN_TIMES, RUN_TESTS are missing. adding
05:45:51  <Trott>🎉
05:46:19  <Trott>'cause let me tell ya...that test-preload.js failure is GOING DOWN!!!!
05:46:22  <jbergstroem>just gotta wait for the queue to ru nout
05:46:26  <jbergstroem>run out
05:47:08  <Trott>Heh, they're probably all my jobs.
05:47:23  <Trott>But yeah, there's one in there that I would definitely like to let finish...
05:47:27  <jbergstroem>cancel if you want
05:47:33  <jbergstroem>i've told jenkins to go into shutdown mode
05:58:26  <jbergstroem>gonna be a bit longer. windows/arm
06:01:06  <Trott>My Windows/ARM job is done.
06:05:00  <jbergstroem>Trott: restarted.
06:05:01  * jenkins-monitor1quit (Remote host closed the connection)
06:05:01  * jenkins-monitorquit (Remote host closed the connection)
06:05:10  * jenkins-monitor1joined
06:05:10  * jenkins-monitorjoined
06:05:43  <Trott>
06:06:21  <jbergstroem>i reckon we should be good now then
06:06:28  <jbergstroem>there might be other jobs but just ping someone in here
06:06:28  <Trott>OK, now to fire up those two stress tests again and see the magic....
06:06:53  <jbergstroem>rvagg: thoughts on killing fedora21?
06:10:54  <jbergstroem>Trott: gotta agree though! TOTAL makes all the difference: + echo '181 OK: 181 NOT OK: 0 TOTAL: 9999'
06:11:18  <jbergstroem>i guess its irrelevant for you seeing how you create all of them :)
06:14:15  * evanlucasjoined
06:14:31  <jbergstroem>phillipj: how would i get hold of log files from the gh bot if i wanted to start debugging? also, could we do a flag where we perhaps don't update github or should i just change endpoint forn ow?
06:15:08  <jbergstroem>requestb.in or smth
06:17:06  <phillipj>jbergstroem: log files in production?
06:17:21  <jbergstroem>phillipj: i think i'll play aroudn with requestb.in for a bit to make sure we get sha right
06:17:31  <phillipj>okey
06:17:56  <jbergstroem>lets aim at having something working over the weekend (i'm talking to myself here)
06:19:09  <phillipj>atm I'm the only one who has access to logs, which is why this PR was opened -> https://github.com/nodejs-github-bot/github-bot/pull/42
06:19:26  <phillipj>I could ofc give you a dump when you need it
06:21:34  <phillipj>on not updating github... locally or in production?
06:22:18  <Trott>The POST_STATUS_TO_PR checkbox does nothing right now, right? At least, I'm not seeing anything. No harm in checking it or not checking it either way?
06:30:24  * rmgjoined
06:33:29  <jbergstroem>Trott: i intentionally changed it to avoid any issues with the security update
06:33:35  <jbergstroem>i will update it again over the weekend and start testing
06:33:56  <jbergstroem>likely against requestb.in 'til i figure out the issues me/phillipj found
06:34:18  <Trott>👍
06:35:13  * rmgquit (Ping timeout: 252 seconds)
06:47:35  <jbergstroem>🤒
07:09:39  <thealphanerd>jbergstroem let me know if there is anything I can do tomorrow to help
07:09:57  <jbergstroem>sure!
09:31:53  * rmgjoined
09:36:43  * rmgquit (Ping timeout: 252 seconds)
10:44:27  * thealphanerdquit (Quit: farewell for now)
10:44:57  * thealphanerdjoined
13:33:59  * chorrelljoined
13:40:47  * chorrellquit (Quit: My Mac has gone to sleep. ZZZzzz…)
13:58:04  * Fishrock123joined
14:19:50  * sgimenoquit (Quit: Leaving)
14:26:24  * rmgjoined
14:45:10  * chorrelljoined
14:49:20  * chorrellquit (Client Quit)
15:16:24  * chorrelljoined
15:39:23  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
16:30:05  * chorrelljoined
16:41:49  * chorrell_joined
16:45:02  * chorrellquit (Ping timeout: 260 seconds)
16:54:20  * chorrell_quit (Quit: Textual IRC Client: www.textualapp.com)
16:56:23  * orangemochaquit (Remote host closed the connection)
16:56:23  * zkatquit (Remote host closed the connection)
16:56:23  * starefossenquit (Remote host closed the connection)
16:56:24  * michael___quit (Remote host closed the connection)
16:56:25  * joaocgreisquit (Remote host closed the connection)
17:18:42  * zkatjoined
17:29:26  * joaocgreisjoined
17:31:47  * michael___joined
17:32:52  * starefossenjoined
17:33:55  * orangemochajoined
19:50:56  * Fishrock123quit (Remote host closed the connection)
19:54:44  * Fishrock123joined
20:19:46  * node-ghjoined
20:19:47  * node-ghpart
21:51:34  * node-ghjoined
21:51:35  * node-ghpart
22:11:14  <Trott>In our test code, we have common.localhostIPv4. It looks like the sole purpose of that code is to allow FreeBSD jails to send something other than `127.0.01` as the value for the localhost IP. Offhand, does anyone know what we use for FreeBSD jails? Is it still within 127.0.0.0/8? Asking for a friend.
22:11:24  <Trott>jbergstroem ^^^^
22:11:49  <jbergstroem>we used to run from freebsd jails
22:11:58  <Trott>Wait, what? No more?
22:12:33  <Trott>There's a lot of FreeBSD jail workaround code that arguably can go, at least in the tests and stuff, if that's the case.
23:14:18  * Fishrock123quit (Remote host closed the connection)
23:41:54  <jbergstroem>Trott: I don't think freebsd jails will go away though. It'd be nice to have a way for freebsd users to have tests pass?
23:57:58  * Fishrock123joined