00:12:06  * node-ghjoined
00:12:06  * node-ghpart
00:26:00  * BridgeAR1quit (Remote host closed the connection)
00:29:09  * gabrielschulhofquit (Ping timeout: 256 seconds)
01:52:39  * gabrielschulhofjoined
03:00:57  * qbitquit (Ping timeout: 264 seconds)
03:00:57  * cxregquit (Ping timeout: 264 seconds)
03:02:29  * cxregjoined
03:06:54  * qbitjoined
04:06:58  <Trott>Jenkins is doing that thing a lot lately where it feels like the website is blocking on a single thread somehow. Like, click something and it spin spins spins, so open another tab to look at something else on Jenkins, and it spins spins spins, repeat two more times, then all four tabs suddenly all load at once.
04:08:02  <Trott>At least it's not giving 504 (or whatever the code was) errors like it used to. So that's definitely an improvement. I'm not really complaining. Just observing in case anyone knows what it is and/or is interested in investigating. It would be cooler if the wait-wait-wait didn't happen, but I can totally live with it.
05:37:42  * gabrielschulhofquit (Ping timeout: 260 seconds)
07:46:20  * seishunjoined
10:25:09  * mylesborinsquit (Quit: farewell for now)
10:25:40  * mylesborinsjoined
12:30:50  * BridgeAR1joined
13:02:38  * BridgeAR1quit (Ping timeout: 276 seconds)
13:04:42  * BridgeAR1joined
13:11:53  * targosjoined
13:20:37  <targos>joyee: hi
13:23:06  <targos>joyee: do you know if someone is working on error codes for errors thrown in `node.cc`?
13:24:05  * gabrielschulhofjoined
13:26:05  <joyee>targos: I don't think so
13:26:17  <joyee>targos: also are we in the wrong channel? :P
13:28:59  * BridgeAR1quit (Remote host closed the connection)
14:53:15  <targos>oops
16:28:30  <Trott>test-rackspace-win2008r2-x64-6 is perma-failing https://ci.nodejs.org/computer/test-rackspace-win2008r2-x64-6/builds Marking it as offline.
16:28:31  <Trott>Problem is a stale index.lock file. Should be easy for someone to fix if they can log in....
16:28:31  <Trott>rvagg joaocgreis refack
16:32:05  <refack>@Trott, cleared it's workspace. now watching
16:32:38  <Trott>Thanks. Maybe at the Collaborators Summit, someone else from Build can shame me into learning how to log into Windows machines in CI again.
16:33:00  <refack>This task can be done via Jenkins GUI
16:37:05  <Trott>🤦 Even easier to use social pressure to require me to learn then. :-D
16:37:30  <Trott>So just clear the workspace and that's it? I think I should be able to handle that...
16:37:51  <refack>As a first-aid attempt
16:49:52  * srl295quit (Quit: Connection closed for inactivity)
17:00:45  * Ashwijoined
17:03:44  * Ashwiquit (Client Quit)
17:04:48  * Ash_joined
17:06:36  * Ash_quit (Client Quit)
17:17:49  * seishunquit (Ping timeout: 256 seconds)
17:25:15  * seishunjoined
18:59:09  * gabrielschulhofquit (Ping timeout: 264 seconds)
19:51:20  * gabrielschulhofjoined
20:34:27  * seishunquit (Ping timeout: 256 seconds)
21:26:57  * gabrielschulhofquit (Ping timeout: 240 seconds)