00:32:48  * node-ghjoined
00:32:48  * node-ghpart
00:34:34  * gabrielschulhofquit (Ping timeout: 264 seconds)
01:30:26  * gabrielschulhofjoined
02:36:24  * mmarchiniquit (Ping timeout: 256 seconds)
02:36:32  * mmarchinijoined
02:47:37  * node-ghjoined
02:47:37  * node-ghpart
03:48:34  * apapirovskijoined
04:05:42  * apapirovskiquit (Remote host closed the connection)
04:53:55  * node-ghjoined
04:53:56  * node-ghpart
05:46:13  * apapirovskijoined
05:55:33  * apapirovskiquit (Remote host closed the connection)
06:19:56  * seishunjoined
06:44:44  <ryzokuken>cannot manage to trigger a rebuild. link: https://ci.nodejs.org/job/node-test-commit-linux/19550/rebuild/parameterized
06:45:03  <ryzokuken>clicking on "rebuild" just takes me to the status page.
06:46:26  <ryzokuken>okay, I cannot build a new one either
07:28:45  * seishunquit (Ping timeout: 260 seconds)
08:20:40  * gabrielschulhofquit (Ping timeout: 260 seconds)
09:11:48  * node-ghjoined
09:11:48  * node-ghpart
09:57:26  * lucalanzianiquit (Quit: ZNC 1.7.0 - https://znc.in)
10:25:28  * mylesborinsquit (Quit: farewell for now)
10:25:58  * mylesborinsjoined
10:39:12  * lucalanzianijoined
10:43:50  * lucalanzianiquit (Read error: Connection reset by peer)
10:44:00  * lucalanzianijoined
11:18:55  * BridgeAR1joined
11:34:57  <maclover7>joyee: can you remove kunalspathak from nodejs-private/build
12:11:49  * victoralencarjoined
12:37:32  * node-ghjoined
12:37:32  * node-ghpart
12:37:47  * node-ghjoined
12:37:47  * node-ghpart
12:43:07  * BridgeAR1quit (Ping timeout: 245 seconds)
12:55:35  * Steve_pjoined
13:07:46  * node-ghjoined
13:07:46  * node-ghpart
13:09:20  * victoralencarquit (Quit: Page closed)
13:15:53  * node-ghjoined
13:15:53  * node-ghpart
13:19:20  <Steve_p>So, I ran into y'all this morning, and I'm interested in helping out.
13:19:46  <Steve_p>I'm going through your docs on github and will be taking a stroll though the issues there as well.
13:20:11  <Steve_p>Is there any where else I should be taking a look before I try to dig into anything?
13:29:41  <maclover7>Steve_p: nope, github issues and the docs are the best places to get started
13:29:51  <maclover7>and to see where things stand with the working group
13:49:28  <refack>take a look at https://github.com/nodejs/build/issues/1330, also yesterday's meeting from https://youtu.be/juQ53qvh1l8?t=618
14:01:16  * apapirovskijoined
14:01:39  <Steve_p>Thanks, I'll take a look at that meeting
14:07:53  * apapirovskiquit (Quit: Leaving...)
14:38:48  * node-ghjoined
14:38:48  * node-ghpart
14:46:15  * node-ghjoined
14:46:15  * node-ghpart
14:46:37  * node-ghjoined
14:46:37  * node-ghpart
14:47:40  * node-ghjoined
14:47:40  * node-ghpart
14:56:58  * Guest29713joined
14:58:04  <Guest29713>Hello! I'm interested in participating in the build group.
14:58:25  * Fishrock123joined
14:59:55  <refack>Hello Guest29713, you can take a look at some comments from a few minutes ago at: http://logs.libuv.org/node-build/latest#13:19:20.118
15:01:26  <refack>P.S. It would be nice if you authenticated your account and introduced yourself
15:01:33  <Guest29713>Perfect. I'll go through those resources. I look forward to submitting my first PR.
15:01:37  <Guest29713>Oh, sure.
15:01:41  * sxajoined
15:02:08  * Guest29713quit (Quit: Leaving)
15:02:14  * sxaquit (Client Quit)
15:02:48  * node-ghjoined
15:02:48  * node-ghpart
15:05:13  * cody__joined
15:06:00  <cody__>Hi, I'm back. I was in here as a gust a few moments ago.
15:06:44  <cody__>Anyways, my name is Cody Heimberger and I'm an Ops engineer at printerlogic.com
15:06:56  <cody__>Looking forward to helping out on this project.
15:08:49  <cody__>Oh, and my github is www.github.com/certifiedloud
15:08:54  <cody__>Oh, and my github is https://www.github.com/certifiedloud
15:12:27  * node-ghjoined
15:12:27  * node-ghpart
15:23:02  <refack>Hello cody__
15:23:12  <lucalanziani>if we get all in and up to speed maclover7 and refack might be able to relax a bit :D
15:26:31  * node-ghjoined
15:26:31  * node-ghpart
15:28:26  * sxajoined
15:34:26  * BridgeAR1joined
15:37:59  * node-ghjoined
15:37:59  * node-ghpart
15:53:34  <joyee>Something wrong with test-azure_msft-win2016-x64-4, it's been bugging the last CI runs
15:53:38  <joyee>https://ci.nodejs.org/job/node-test-binary-windows/18004/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console
15:54:04  <refack>`stderr: fatal: Unable to create 'c:/workspace/node-test-binary-windows/.git/index.lock': File exists.`
15:54:37  <joyee>Are the windows machine SSH-able?
15:55:08  <refack>what to do:
15:55:08  <refack>remove the job ID from the URL (and the /console) to get
15:55:08  <refack>https://ci.nodejs.org/job/node-test-binary-windows/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/
15:55:08  <refack>click workspace
15:55:08  <refack>click "Wipe Out Current Workspace"
15:56:01  <refack>RE SSH; not yet, you need to RDP
15:57:07  <joyee>OK, I've wiped it out
15:57:59  <joyee>hmm, I only have host for test-azure_msft-ubuntu1404-x64-1 although that probably does not matter..
15:59:08  <joyee>If anyone is interested, I've mined the CI failures of the last 100 CI runs https://gist.github.com/joyeecheung/c40ef984af4b17f6171efa754fddae3b
15:59:45  <refack>joyee: did you see mmarchini's https://nodejs-ci-health.mmarchini.me/
16:00:10  <joyee>Yep, although you'll need to parse stuff to get the reasons
16:01:32  <refack>So your `"reason": "..."` is a parsed outcome? it seems quite focused
16:02:40  <joyee>https://gist.github.com/joyeecheung/2d189d9cbbfa146827f31716c5837590
16:02:51  <joyee>This is the original data, I just picked the first line
16:03:21  <joyee>It's a bit dumb, apparently, e.g. the true reason in the previous case is the existence of lock file
16:03:35  <joyee>But good enough for aggregation
16:03:43  <refack>It's gold
16:05:58  <joyee>https://github.com/nodejs/node-core-utils/pull/254 PR is here
16:07:55  * juggernaut451joined
16:08:53  * node-ghjoined
16:08:54  * node-ghpart
16:13:00  * node-ghjoined
16:13:00  * node-ghpart
16:13:35  * node-ghjoined
16:13:35  * node-ghpart
16:13:48  * node-ghjoined
16:13:49  * node-ghpart
16:15:10  * juggernaut451quit (Remote host closed the connection)
16:15:46  <Trott>I wonder if there's something wrong with our .status file parsing. https://ci.nodejs.org/job/node-test-commit-freebsd/18476/nodes=freebsd10-64/console is yellow but it should be red AFAICT.
16:15:47  * BridgeAR1quit (Remote host closed the connection)
16:16:04  * cody__quit (Quit: Leaving)
16:23:38  * seishunjoined
16:31:11  * juggernaut451joined
16:45:30  * node-ghjoined
16:45:30  * node-ghpart
16:45:58  <Trott>Oh, i see if I edit a build repo comment, it reposts it here. Guess I'll try to edit less....
17:14:02  * juggernaut451quit (Remote host closed the connection)
17:21:17  * node-ghjoined
17:21:17  * node-ghpart
17:23:41  <refack>Trott: yeah it's a bug. At least at the CI job level. I'm trying to figure out if it's also a bug at the make or test.py level
17:25:44  * juggernaut451joined
17:41:25  * BridgeAR1joined
17:46:23  * juggernaut451quit (Remote host closed the connection)
17:46:30  * node-ghjoined
17:46:30  * node-ghpart
17:47:18  <refack>maclover7: See ^^^^ there's a bug in `node-test-commit-test.sh` on freebsd
17:54:27  * Fishrock123quit (Remote host closed the connection)
17:59:31  * Fishrock123joined
18:14:26  * sxaquit (Ping timeout: 265 seconds)
18:34:20  * seishunquit (Ping timeout: 260 seconds)
18:40:55  * seishunjoined
18:50:59  * seishunquit (Ping timeout: 255 seconds)
19:00:08  * node-ghjoined
19:00:08  * node-ghpart
19:15:42  * node-ghjoined
19:15:42  * node-ghpart
19:21:35  <refack>a bit of noise in CI ATM, transitioning job structure
19:23:10  * Fishrock123quit (Remote host closed the connection)
19:33:31  * Fishrock123joined
19:35:52  * seishunjoined
19:45:54  * node-ghjoined
19:45:54  * node-ghpart
19:47:17  <maclover7>refack: what changes are you making?
19:48:38  <maclover7>I had been editing a few jobs, things look different now
19:48:47  <refack>the node-test-commit-test.sh was swallowing test failures, so I rolled back the configs of the live job
19:49:07  <refack>s
19:49:34  <maclover7>Hmm what do you mean swallowing the failures
19:49:41  <maclover7>They weren't printing in the console output?
19:50:17  <refack>you called it without -xe so `make test` errors didn't propogate
19:50:44  <refack>They were printing, and the `text-finder` found them but only marked the job as unstable
19:51:01  <maclover7>Ah ok
19:51:03  <refack>see https://ci.nodejs.org/job/node-test-commit-freebsd/18476/nodes=freebsd10-64/console
19:51:08  <maclover7>Did you update the jobs to use -xe then?
19:51:22  <refack>Anyway I'm working on a single job https://ci.nodejs.org/job/node-test-commit-unified
19:51:41  <maclover7>Idk about a single job
19:51:48  <refack>No, I use the 'config history' to go back to 6-11-2018
19:51:48  <maclover7>I'm sticking with refactoring what we've got now
19:52:00  <maclover7>and then will slowly move to pipelines once we're in a single script
19:52:05  <refack>anyway lets test this some more
19:52:14  <maclover7>A single job is likely too much for someone to fully view
19:52:19  <refack>I have https://ci.nodejs.org/job/refack-test-commit & https://ci.nodejs.org/job/node-test-commit-unified
19:52:23  <maclover7>Yeah I've been slowly testing out my PR
19:53:40  <refack>Then I'd we have a single point to flip the switch, maybe just change the named in the stages of https://ci.nodejs.org/job/node-test-commit
19:53:56  <maclover7>refack: looks like a lot of the post-build-status-update blocks are missing now
19:53:57  <refack>So that will be the only place we can turn this on/off
19:54:02  <maclover7>I'm adding them back in there
19:54:22  <refack>That's strage, point me to where.
19:54:54  <refack>I was hoping that "Restore old config" button will be safe
19:57:47  <maclover7>Not really sure what happened, just trying to fix it
20:02:12  * node-ghjoined
20:02:12  * node-ghpart
20:04:12  * node-ghjoined
20:04:12  * node-ghpart
20:12:14  * node-ghjoined
20:12:14  * node-ghpart
20:26:49  * node-ghjoined
20:26:49  * node-ghpart
21:05:01  * Steve_pquit (Quit: Page closed)
21:06:24  * node-ghjoined
21:06:24  * node-ghpart
21:17:46  * node-ghjoined
21:17:46  * node-ghpart
21:25:42  * node-ghjoined
21:25:42  * node-ghpart
21:31:05  * seishunquit (Ping timeout: 260 seconds)
21:31:06  * node-ghjoined
21:31:06  * node-ghpart
21:35:55  * node-ghjoined
21:35:55  * node-ghpart
21:48:03  * Fishrock123quit (Remote host closed the connection)
22:00:11  * Fishrock123joined
22:04:06  <ofrobots>mhdawson_: any idea why ppcle and s390x are failing on the V8 CI for me: https://ci.nodejs.org/view/All/job/node-test-commit-v8-linux/1426/
22:04:48  <ofrobots>I have had this status on a bunch of backports.. is it possible that these jobs are no longer working for 8.x?
22:06:32  * node-ghjoined
22:06:32  * node-ghpart
22:06:55  * node-ghjoined
22:06:55  * node-ghpart
22:11:24  * node-ghjoined
22:11:24  * node-ghpart
22:15:19  * node-ghjoined
22:15:19  * node-ghpart
22:16:20  * node-ghjoined
22:16:21  * node-ghpart
22:17:22  * node-ghjoined
22:17:22  * node-ghpart
22:19:00  * node-ghjoined
22:19:00  * node-ghpart
22:25:57  * node-ghjoined
22:25:57  * node-ghpart
22:26:05  * node-ghjoined
22:26:06  * node-ghpart
22:27:45  * node-ghjoined
22:27:45  * node-ghpart
22:38:55  * node-ghjoined
22:38:55  * node-ghpart
22:39:46  <refack>mmarchini: if this works we can move all that voodoo into the script in the repo
22:41:51  * Fishrock123quit (Quit: Leaving...)
22:42:18  <mmarchini>in theory we only need one Build Step, right? `curl https://raw.githubusercontent.com/nodejs/build/master/jenkins/scripts/node-test-v8-updates.sh | bash bash -ex`
22:42:49  <mmarchini>(trying to understand how Jenkins jobs are setup)
22:42:59  <refack>yes and no
22:43:46  <refack>it's sufficient but then we lose other jenkins features like we have in https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/
22:44:17  <refack>But yeah we could just lump everything up into a single step
22:45:55  <mmarchini>the script needs to be hardcoded in the step for https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/ to work?
22:46:33  <mmarchini>or https://ci.nodejs.org/job/node-test-pull-request-lite-pipeline/ relies on the first/third steps (pre and diagnostics)?
22:46:57  <refack>No, but Jenkins doesn't understand bash
22:47:30  <refack>So the idea of moving everything into a single bash is to minimize the amount of setup that is locked within Jenkins
22:49:29  <refack>But Jenkins understand to DSLs, pipelines and job DSL. So optimaly after everything works we could refactor to something like:
22:49:29  <refack>https://github.com/nodejs/build/blob/master/jenkins/pipelines/node-test-pull-request-lite-pipeline.jenkinsfile
22:50:29  <refack>*to DSLs => two DSLs
22:53:48  * jasnelljoined
23:39:02  * jasnellquit
23:42:37  * node-ghjoined
23:42:37  * node-ghpart
23:46:16  * node-ghjoined
23:46:16  * node-ghpart
23:46:42  * node-ghjoined
23:46:42  * node-ghpart
23:48:16  * node-ghjoined
23:48:16  * node-ghpart
23:48:22  * node-ghjoined
23:48:22  * node-ghpart
23:49:57  * node-ghjoined
23:49:57  * node-ghpart
23:52:06  * BridgeAR1quit (Ping timeout: 256 seconds)
23:56:03  * node-ghjoined
23:56:03  * node-ghpart
23:57:06  * node-ghjoined
23:57:06  * node-ghpart