03:25:27  * jenkins-monitorquit (Ping timeout: 276 seconds)
03:28:21  * jenkins-monitorjoined
03:31:27  * rmgjoined
03:36:30  * rmgquit (Ping timeout: 276 seconds)
07:32:32  * Fishrock123joined
09:33:28  * rmgjoined
09:37:59  * rmgquit (Ping timeout: 260 seconds)
10:30:35  * thealphanerdquit (Quit: farewell for now)
10:31:06  * thealphanerdjoined
10:35:19  * node-ghjoined
10:35:19  * node-ghpart
10:57:23  * node-ghjoined
10:57:24  * node-ghpart
11:34:12  * rmgjoined
11:38:31  * rmgquit (Ping timeout: 240 seconds)
12:35:26  * lance|afkchanged nick to lanceball
13:10:11  * chorrelljoined
14:08:30  * evanlucasquit (Remote host closed the connection)
14:55:28  * Fishrock123quit (Quit: Leaving...)
14:58:10  * targosjoined
15:19:34  * rmgjoined
16:08:13  * chorrellquit (Quit: Textual IRC Client: www.textualapp.com)
17:07:25  * node-ghjoined
17:07:25  * node-ghpart
17:08:01  * node-ghjoined
17:08:01  * node-ghpart
18:39:35  <Trott>Does this failure have a known cause? https://ci.nodejs.org/job/node-test-binary-arm/2632/RUN_SUBSET=4,label=pi3-raspbian-jessie/console I'm guessing not and I'm guessing it's non-trivial to get to the bottom of, but just in case....
18:39:43  <Trott>rvagg__ ^^^^
19:30:27  * Fishrock123joined
19:38:19  <jbergstroem>phillipj: here?
19:39:16  <jbergstroem>Fishrock123: here?
19:39:34  <Fishrock123>jbergstroem: yeah
19:39:46  <jbergstroem>the config is now running @ nodejs.org
19:39:59  <jbergstroem>not sure which pages i should check, but /it/docs seems to be english but kr is 404ing
19:40:30  <Fishrock123>jbergstroem: should be ko?
19:40:39  <Fishrock123>./ko/?
19:40:47  <jbergstroem>:-D
19:40:56  <jbergstroem>that works
19:41:06  <Fishrock123>https://nodejs.org/it/daaa
19:41:08  <Fishrock123>404 works
19:41:15  <Fishrock123>https://nodejs.org/en/daaa
19:41:22  <Fishrock123>https://nodejs.org/ko/daaa
19:41:26  <jbergstroem>yep
19:42:51  <Fishrock123>not really sure what else to tests
19:42:54  <jbergstroem>ok i've tested what I have to and the rest seems to work
19:43:05  <jbergstroem>so now we wait for twitter ?
19:43:09  <Fishrock123>I guess just need to wait and see if people start complaing to the nodejs twitter
19:43:13  <Fishrock123>ayup
19:43:44  <jbergstroem>ok
19:43:51  <jbergstroem>how about we run this until i sign off
19:43:51  <jbergstroem>revert
19:43:57  <jbergstroem>then again tomorow?
19:44:08  <jbergstroem>(just to be safe if no one from infra is around)
19:47:22  <phillipj>yo! so it didnt explode? wow, got lucky there ;)
19:56:49  * Fishrock123quit (Remote host closed the connection)
19:56:50  <phillipj>cant see any issues so far
19:58:57  <phillipj>fallbacks seems to be working nicely
20:00:30  <phillipj>zh-cn is the one with the most complete translation so far, even has the download page almost done
20:01:01  <phillipj>the other locales only has only done the frontpage more or less
20:01:04  <phillipj>https://github.com/nodejs/nodejs.org/tree/master/locale
20:02:26  <phillipj>jbergstroem: sure, you could revert just to be certain it works while you're away, but I'm pretty confident there's no explotion waiting to happen
20:02:34  <phillipj>...famous last words
20:02:45  <jbergstroem>load up
20:02:48  <jbergstroem>~10%
20:03:12  <jbergstroem>but negligible
20:03:25  <jbergstroem>I have a few optimisations in mind in general
20:05:43  <phillipj>has there been discussions around verifying the site/nginx conf after changes like theese?
20:06:33  * Fishrock123joined
20:07:45  <phillipj>would have been nice to be able to do what ever we want, then trigger some checks which verifies it still working as expected
20:09:41  <jbergstroem>we could do a curl suite
20:09:47  <jbergstroem>but we seldom do intrusive stuff
20:10:05  <jbergstroem>so i can't say I've up to now seen a strong need; it's prdy mouch been 0/1 tests (add headers, locations, etc)
20:10:22  <jbergstroem>i have a local setup and i reckon the others that have done changes likely also does
20:12:12  <jbergstroem>im sorry for this taking so long for me to verify, its just that when it comes to nginx logic (ifs are evil bla bla and / matches) it can affect a lot of stuff. we have 500mbit+ at any given day
20:18:00  <jbergstroem>just had another look; should be ok to keep up
20:25:27  <phillipj>awesome
20:25:50  <phillipj>thanks for getting it live!
20:30:15  <phillipj>bed time here, cya
20:46:50  <Fishrock123>jbergstroem: hmmm we should probably check some sort of server stats for it then
20:46:56  <Fishrock123>do we have cpu usage graphs and stuff?
20:47:18  <jbergstroem>Fishrock123: poor stuff through DO, i just look at average load
20:47:39  <jbergstroem>1/5/15
20:48:41  <jbergstroem>Fishrock123: we're still <1 avg though so it doesn't really matter
20:54:34  <Fishrock123>k, well, going offline
20:54:47  <Fishrock123>jbergstroem: cheers for all the work on this :D
20:54:52  * Fishrock123quit (Quit: Leaving...)
20:55:15  <jbergstroem>not sure if sarcasm :)
20:55:22  <jbergstroem>still, progress!
21:45:16  * lanceballchanged nick to lance|afk
21:48:13  * node-ghjoined
21:48:14  * node-ghpart
22:22:39  <rvagg__>Trott: that error is the same one that joaocgreis was trying to resolve with an alternate JVM - joaocgreis do you recall what node you did that upgrade on so we can work out whether it made a difference?
22:23:11  <rvagg__>Trott, joaocgreis: the best response I have is to restart the slave process on that machine but I don't even know if that actually does anything!