09:10:20  * node-ghjoined
09:10:20  * node-ghpart
09:10:44  * seishunjoined
10:25:08  * mylesborinsquit (Quit: farewell for now)
10:25:39  * mylesborinsjoined
11:26:11  * evanlucasjoined
11:34:02  * evanlucasquit (Remote host closed the connection)
11:45:35  * seishunquit (Ping timeout: 248 seconds)
12:07:55  * seishunjoined
15:28:41  * seishunquit (Ping timeout: 240 seconds)
15:46:00  * node-ghjoined
15:46:00  * node-ghpart
15:46:02  * seishunjoined
17:47:31  * node-ghjoined
17:47:31  * node-ghpart
19:03:31  * node-ghjoined
19:03:31  * node-ghpart
20:02:45  * node-ghjoined
20:02:45  * node-ghpart
20:21:00  * seishunquit (Ping timeout: 240 seconds)
20:45:53  * seishunjoined
21:00:01  * node-ghjoined
21:00:01  * node-ghpart
21:10:25  * seishunquit (Ping timeout: 248 seconds)
21:31:10  <Trott>Uh oh, looks like I might need to tell people at Collab Summit to slow their roll on launching CI jobs from Code + Learn right now.
21:32:07  <refack>Yep. We're at 13
21:32:52  <Trott>Walked over to whisper with bridgear about it but he already knew. "Yes, we're at 13, which is why I stopped." :-D
21:33:17  <refack>my 2cent again, run https://ci.nodejs.org/job/node-test-linter/build & https://ci.nodejs.org/job/node-test-commit-linuxone/build
21:33:30  <refack>For the tests only PRs
21:34:42  <Trott>👍
21:34:59  <Trott>(I mean, as a first pass. Then run with everything if that comes back green.)
21:37:46  <refack>Personally I wouldn't be that stringent. Worse case we roll back one or two commits.
21:38:48  <refack>another option, batch land on a side-branch, and full CI it
21:39:15  <refack>We're not even at the 10% mark, so we need to find a way to scale this up
21:54:55  <Trott>You make good points.
22:24:53  * node-ghjoined
22:24:53  * node-ghpart
22:46:36  * node-ghjoined
22:46:36  * node-ghpart
23:26:28  * node-ghjoined
23:26:28  * node-ghpart