01:16:23  * node-ghjoined
01:16:23  * node-ghpart
03:02:09  * qbitquit (*.net *.split)
03:03:04  * qbitjoined
03:04:54  * qbitchanged nick to Guest55816
07:02:15  * lucalanzianijoined
07:06:39  * lucalanziani_joined
07:08:22  * lucalanzianiquit (Ping timeout: 272 seconds)
10:49:38  * sxajoined
11:06:54  * debsan7joined
11:07:38  * debsan7quit (Remote host closed the connection)
11:17:44  * evil_steve12joined
11:18:29  * evil_steve12quit (Remote host closed the connection)
11:37:59  * richardlauquit (Read error: Connection reset by peer)
12:03:01  * purplepod28joined
12:07:47  * purplepod28quit (Remote host closed the connection)
12:12:13  * kfunk10joined
12:14:25  * kfunk10quit (K-Lined)
12:57:29  * bathtub_shark4joined
13:02:11  * bathtub_shark4quit (Remote host closed the connection)
13:14:34  * Guest55816quit (Quit: WeeChat 2.2)
13:25:33  * node-ghjoined
13:25:33  * node-ghpart
14:04:07  <tniessen>I am getting a lot of java exceptions... "java.net.SocketException: Socket closed" caused by "Caused: java.net.SocketTimeoutException: timeout"
14:04:37  <tniessen>I can barely use jenkins
14:21:33  * qbitjoined
14:21:57  * qbitchanged nick to Guest14725
14:23:46  * Guest14725changed nick to qbit
15:00:08  <tniessen>What's going on here? https://ci.nodejs.org/job/node-test-commit-windows-fanned/20700/
15:00:41  <tniessen>Both subtasks are done but node-test-commit-windows-fanned doesn't stop.
15:00:57  <tniessen>And Jenkins is waaaaay too slow, I can't even look at the console
15:35:34  * node-ghjoined
15:35:34  * node-ghpart
16:08:34  * Guest88481joined
16:11:23  * Guest88481quit (Remote host closed the connection)
16:31:03  <joaocgreis>tniessen: we're not sure what's happening, but Jenkins has been quite bad for a few days.. https://github.com/nodejs/build/issues/1495
16:31:54  <joaocgreis>for the most part, I can use it. Takes a few seconds to open anything, but I got only one 504 today
16:32:54  <joaocgreis>looks like the jobs not quitting issue was not only on win2016
16:37:32  * node-ghjoined
16:37:32  * node-ghpart
16:50:48  * node-ghjoined
16:50:48  * node-ghpart
17:19:44  * node-ghjoined
17:19:44  * node-ghpart
17:53:26  <tniessen>joaocgreis: I am seeing a lot of these stacktraces: https://pastebin.com/raw/GqVfincP
17:54:36  <node-slack-bot>[trott] tniessen: On Windows only? Or on all sorts of things?
17:58:16  <refack>joaocgreis: it seems to be almost always `https://api.github.com/user`. Since it should only be for when we call the GUI, I think it's a symptom of the CPU @ 100%, and the auth failing to complete
17:59:47  <refack>We could increase the HTTP session timeout so Jenkins will make less call to GitHub (https://stackoverflow.com/a/31809977/27955)
18:00:30  * gauge19joined
18:00:44  * node-ghjoined
18:00:44  * node-ghpart
18:01:10  * gauge19quit (Remote host closed the connection)
18:04:40  * sxaquit (Ping timeout: 244 seconds)
18:06:26  <refack>FTR: is you see that crash, click "login"
18:24:18  <tniessen>refack: session timeout might be a good idea
18:24:20  <tniessen>refack: thanks
18:25:47  <tniessen>Last CI passed but GH is not updating, this seems to be happening quite often lately: https://github.com/nodejs/node/pull/22660
18:27:14  <refack>tniessen: it's related. When Jenkins get's to 100% cpu and timesout, it isn't able to run the post-status-update jobs
18:27:25  <tniessen>oh okay
19:03:19  * node-ghjoined
19:03:19  * node-ghpart
19:16:22  * darkling13joined
19:19:09  * darkling13quit (Remote host closed the connection)
20:16:59  * node-ghjoined
20:16:59  * node-ghpart
21:00:43  * roylez21joined
21:08:03  * roylez21quit (Ping timeout: 252 seconds)
21:58:39  * delacroix28joined
21:59:25  * delacroix28quit (Remote host closed the connection)
22:50:41  * node-ghjoined
22:50:41  * node-ghpart
23:47:52  * ryan_fordjoined
23:57:05  * ryan_fordquit (Remote host closed the connection)