00:15:43  * Fishrock123joined
00:30:19  * Fishrock123quit (Quit: Leaving...)
00:44:30  <jbergstroem>rvagg: i stuck around for 15; was getting late (11:15pm our time) then went offline, got an email 11:18 :(
00:45:43  <jbergstroem>i'll find other times
00:45:48  <jbergstroem>and do a proper cal inv
01:20:32  <rvagg>mm, that would help
01:20:42  <rvagg>for those of us who live and die by our calendars
01:20:45  * rvaggsobs
03:55:03  <rvagg>pi1p-5 might be buggered, even with a fresh image the kernel borks on a hung task while trying to boot up
04:16:21  <jbergstroem>:(
04:16:25  <jbergstroem>what task
04:43:54  <thealphanerd>rvagg I ran into reconbot at maker faire and he is very interested in getting some tessel's into the ci environment
04:44:31  <rvagg>thealphanerd: we have a t2 that they donated to us but they are just too slow to do anything in CI
04:44:42  <thealphanerd>fair enough :D
04:44:47  <rvagg>perhaps reconbot has some ideas on how we can manage it, both jbergstroem and i have discussed this
04:45:04  <rvagg>would love to figure something out but it'd doubtful we'll get anything close to fast enough for inclusion in general CI runs
04:45:26  <thealphanerd>that's a good piece of info to know
04:54:47  <Trott>POST_STATUS_TO_PR isn't yet working and we can either check it or not, right?
05:03:50  <jbergstroem>nope
06:36:14  <jbergstroem>its not working ; just skip for now. I need to do environment passing for it to work
06:36:51  <jbergstroem>thealphanerd: it would take a day to finish a test suite if even on the tessel 2
06:37:00  <jbergstroem>i focused on the toolchain and investigated patches instead
06:37:05  <jbergstroem>its a nice piece of hardware though
06:42:26  * node-ghjoined
06:42:27  * node-ghpart
10:49:45  * thealphanerdquit (Quit: farewell for now)
10:50:16  * thealphanerdjoined
11:50:01  * jenkins-monitor1quit (Remote host closed the connection)
11:50:02  * jenkins-monitorquit (Remote host closed the connection)
11:50:11  * jenkins-monitor1joined
11:50:11  * jenkins-monitorjoined
11:55:02  * jenkins-monitor1quit (Remote host closed the connection)
11:55:02  * jenkins-monitorquit (Remote host closed the connection)
11:55:11  * jenkins-monitor1joined
11:55:11  * jenkins-monitorjoined
12:00:01  * jenkins-monitorquit (Remote host closed the connection)
12:00:01  * jenkins-monitor1quit (Remote host closed the connection)
12:00:11  * jenkins-monitor1joined
12:00:12  * jenkins-monitorjoined
12:00:24  * bnoordhuisjoined
12:01:19  <bnoordhuis>i'm getting 502 bad gateway errors for https://ci.nodejs.org/job/libuv-test-commit/ and https://ci.nodejs.org/job/node-test-pull-request/
12:02:05  <bnoordhuis>also, hi =)
12:02:12  <bnoordhuis>(i forget my manners sometimes)
12:05:02  * jenkins-monitorquit (Remote host closed the connection)
12:05:02  * jenkins-monitor1quit (Read error: Connection reset by peer)
12:05:11  * jenkins-monitorjoined
12:05:12  * jenkins-monitor1joined
12:10:01  * jenkins-monitorquit (Remote host closed the connection)
12:10:01  * jenkins-monitor1quit (Remote host closed the connection)
12:10:11  * jenkins-monitor1joined
12:10:11  * jenkins-monitorjoined
12:13:05  * rmgquit (Remote host closed the connection)
12:13:41  * rmgjoined
12:15:02  * jenkins-monitorquit (Remote host closed the connection)
12:15:04  * jenkins-monitor1quit (Remote host closed the connection)
12:15:09  * jenkins-monitorjoined
12:15:11  * jenkins-monitor1joined
12:18:25  * rmgquit (Ping timeout: 260 seconds)
12:20:01  * jenkins-monitorquit (Remote host closed the connection)
12:20:01  * jenkins-monitor1quit (Remote host closed the connection)
12:20:11  * jenkins-monitor1joined
12:20:11  * jenkins-monitorjoined
12:25:01  * jenkins-monitor1quit (Remote host closed the connection)
12:25:03  * jenkins-monitorquit (Remote host closed the connection)
12:25:09  * jenkins-monitor1joined
12:25:11  * jenkins-monitorjoined
12:28:20  * bnoordhuisquit (Quit: leaving)
12:30:01  * jenkins-monitor1quit (Remote host closed the connection)
12:30:02  * jenkins-monitorquit (Remote host closed the connection)
12:30:10  * jenkins-monitorjoined
12:30:11  * jenkins-monitor1joined
12:35:01  * jenkins-monitorquit (Remote host closed the connection)
12:35:01  * jenkins-monitor1quit (Remote host closed the connection)
12:35:10  * jenkins-monitorjoined
12:35:11  * jenkins-monitor1joined
12:37:42  <rvagg>eeek!
12:44:16  <rvagg>should be back up and good to go
12:59:22  <rvagg>jbergstroem: ^ rebooted jenkins server and those two failed to come up in iptables, added them and `/etc/init.d/iptables-persist save` but it's obviously not happening automatically
13:14:07  * rmgjoined
13:18:57  * rmgquit (Ping timeout: 258 seconds)
13:40:35  <jbergstroem>rvagg: according to the description it is supposed to run save on reboot :(
13:40:38  <jbergstroem>rvagg: lets cronjob it
14:50:34  * Fishrock123joined
15:03:09  * rmgjoined
15:18:25  <Fishrock123>I love when jobs fail for no apparent reason at all: https://ci.nodejs.org/job/node-test-binary-arm/2259/RUN_SUBSET=4,label=pi1-raspbian-wheezy/console
16:09:19  * jbergstroemquit (Ping timeout: 260 seconds)
16:33:42  * jbergstroemjoined
16:45:41  * Fishrock123quit (Remote host closed the connection)
16:50:27  * Fishrock123joined
16:54:53  * jbergstroemquit (Quit: bye)
16:55:41  * jbergstroemjoined
16:58:47  <jbergstroem>rvagg: added service iptables-persistent save to both jenkins's cron.hourly
17:10:00  * Fishrock123quit (Remote host closed the connection)
17:17:56  * Fishrock123joined
17:21:58  * Fishrock123quit (Remote host closed the connection)
17:30:17  * Fishrock123joined
17:30:39  * Fishrock123quit (Remote host closed the connection)
17:42:16  <Trott>Fishrock123: There is this line, just in case you missed it: /tmp/hudson5673170787785044551.sh: line 41: 14802 Bus error
17:43:02  <Trott>Of course, if that's what you're referring to as "no apparent reason", yeah, I don't know what to tell you on that one... I think I ran into it once before and jbergstroem or joaocgreis explained that there wasn't really anyway to know what was in the .sh file. But I might be misremembering....
17:43:18  <jbergstroem>.sh is generated as part of a build step in jenkins
17:43:29  <jbergstroem>and its likely just the `make test` stuff
17:43:42  <jbergstroem>bus error can be a bit of everything
17:43:52  <jbergstroem>i'd re-run on the same machine
17:51:36  * Fishrock123joined
19:12:00  * Fishrock123quit (Remote host closed the connection)
19:50:23  * Fishrock123joined
20:36:40  <Trott>Raspberry Pi 1 devices are blowing up with Java errors pretty much every CI run. :-(
20:43:03  <Trott>ppcbe-ubuntu1404 seems to be having problems too... https://ci.nodejs.org/job/node-test-commit-plinux/2614/nodes=ppcbe-ubuntu1404/console https://ci.nodejs.org/job/node-test-commit-plinux/2615/nodes=ppcbe-ubuntu1404/console https://ci.nodejs.org/job/node-test-commit-plinux/2616/nodes=ppcbe-ubuntu1404/console
21:03:55  <Trott>^^^^ rvagg on the Raspberry Pi stuff, I guess...
21:05:01  <Trott>Is jbergstroem still traveling?
21:05:33  <rvagg>don't think so but he's in a very different TZ now
21:05:43  <rvagg>probably asleep now, or partying
21:05:45  <jbergstroem>Trott: almost there; 24h
21:07:28  <jbergstroem>haven't seen that tb before :/
21:07:42  <jbergstroem>michael___: see above ppc issue; any clues?
21:09:04  <rvagg>gonna killall java on the pi's and let them restart
22:34:42  * Fishrock123quit (Remote host closed the connection)
22:37:43  <rvagg>woo! that's pi1p-5 coming back online after a long absence .. turned out to be a borked microsd card
22:39:01  <Trott>woot
22:57:57  * Fishrock123joined
23:01:34  * Fishrock123quit (Remote host closed the connection)
23:16:43  <ofrobots>folks, any idea what happened on this freebsd build bot: https://ci.nodejs.org/job/node-test-commit-freebsd/2640/console
23:17:11  * Fishrock123joined