00:05:03  * jenkins-monitorquit (Remote host closed the connection)
00:05:11  * jenkins-monitorjoined
02:52:08  * rmgjoined
02:52:11  <rvagg>mhdawson: you here? I'm trying to figure out how I can run the coverage stuff over an arbitrary commit from Node, but I can't see how it's done, looks like it might be happening on a personal machine of yours so I don't know what the scripts are to run it
02:56:56  * rmgquit (Ping timeout: 260 seconds)
04:13:43  * rmgjoined
04:18:08  * rmgquit (Ping timeout: 260 seconds)
05:20:02  * node-ghjoined
05:20:03  * node-ghpart
05:20:34  * node-ghjoined
05:20:34  * node-ghpart
05:38:07  * node-ghjoined
05:38:07  * node-ghpart
07:22:59  * rmgjoined
07:28:03  * rmgquit (Ping timeout: 260 seconds)
07:50:32  * rmgjoined
07:55:07  * rmgquit (Ping timeout: 260 seconds)
08:17:36  * rmgjoined
08:22:12  * rmgquit (Ping timeout: 260 seconds)
11:14:11  * not-an-aardvarkquit (Quit: Connection closed for inactivity)
11:17:43  * italoacasasjoined
11:25:09  * thealphanerdquit (Quit: farewell for now)
11:25:40  * thealphanerdjoined
11:27:10  * rmgjoined
11:31:40  * rmgquit (Ping timeout: 260 seconds)
11:54:16  * rmgjoined
11:58:44  * rmgquit (Ping timeout: 260 seconds)
12:21:32  * rmgjoined
12:26:15  * rmgquit (Ping timeout: 260 seconds)
15:30:42  * rmgjoined
15:35:44  * rmgquit (Ping timeout: 260 seconds)
15:58:14  * rmgjoined
16:01:46  * mhdawsonquit (*.net *.split)
16:02:48  * rmgquit (Ping timeout: 260 seconds)
16:05:59  * mhdawsonjoined
16:06:14  * evanlucasjoined
16:10:45  * evanlucasquit (Ping timeout: 248 seconds)
16:25:12  * rmgjoined
16:29:52  * rmgquit (Ping timeout: 260 seconds)
16:34:31  * node-ghjoined
16:34:31  * node-ghpart
16:34:39  * node-ghjoined
16:34:39  * node-ghpart
16:52:21  * rmgjoined
16:56:56  * rmgquit (Ping timeout: 260 seconds)
16:58:59  * rmgjoined
17:33:11  <ofrobots>Trott: we are seeing a test in the test/known_issues directory failing in the V8 + node integration CI. Should we be running test-ci instead of test in that build?
17:56:08  <Trott>Either should work, I would think.
17:56:56  <Trott>There's no chance this version of V8 fixed the issue described in the known issues test, is there?
17:57:41  <Trott>(Known issues tests are expected to fail because they're written for bugs that haven't been fixed yet.)
18:02:07  <ofrobots>Trott: the test (test-vm-function-redefinition) is failing now but used to pass: https://build.chromium.org/p/client.v8.fyi/builders/V8%20-%20node.js%20integration%20-%20lkgr/builds/2359/steps/build%20and%20test%20node.js%20-%20baseline/logs/stdio
18:02:19  <ofrobots>I'll take a look at what it does.
18:02:56  <ofrobots>we have some cascading build breaks over the last week (and the long weekend didn't help). I am trying to figure out how to get the build back to green.
18:04:20  <jbergstroem>hello. no austin for me; its final :'( toss a beer in the fire for me
18:31:31  <Trott>ofrobots: cjihrig wrote that test so maybe ping him? But it sure looks like a straightforward test. If it's "failing", that's probably good. Means the bug has been fixed. If so, test can be moved to test/parallel.
18:56:20  * sgimenoquit (Quit: Leaving)
19:14:50  * chorrelljoined
19:37:05  * not-an-aardvarkjoined
20:08:16  * chorrellquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
20:08:39  * chorrelljoined
20:09:05  * chorrellquit (Client Quit)
20:09:32  * chorrelljoined
20:09:53  * chorrellquit (Client Quit)
20:10:21  * chorrelljoined
20:10:42  * chorrellquit (Client Quit)
20:11:03  * chorrelljoined
20:11:29  * chorrellquit (Client Quit)
20:11:52  * chorrelljoined
20:12:19  * chorrellquit (Client Quit)
20:43:50  * jenkins-monitorquit (Remote host closed the connection)
20:44:03  * jenkins-monitorjoined
21:17:27  * node-ghjoined
21:17:27  * node-ghpart
21:31:23  * jenkins-monitorquit (Remote host closed the connection)
21:31:37  * jenkins-monitorjoined
21:47:23  * chorrelljoined
22:23:43  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
22:39:06  * lanceballchanged nick to lance|afk
23:54:12  * not-an-aardvarkquit (Quit: Connection closed for inactivity)