00:00:54  <rvagg>scaleway machines are all offline, not coming up from reboot
00:01:30  <jbergstroem>ok ill jump onto email
00:01:55  <rvagg>jbergstroem: no, not an email concern, that's mininodes
00:02:09  <rvagg>scaleway is self-serve, I can reprovision new machines if need be or force reboot of these ones
00:02:56  <jbergstroem>I meant for access - I don't recall seeing that in our secrets
00:03:04  <jbergstroem>oh, actually it is. my bad.
00:03:28  <jbergstroem>you want to do it?
00:04:26  <rvagg>I'm trying
00:04:37  <rvagg>yeah, got a hard reboot, will see how that goes
00:05:40  <jbergstroem>i think i've done that once or twice
00:05:49  <jbergstroem>(as in, successfully)
00:06:08  <rvagg>💥 it worked, they are back up
00:06:19  <jbergstroem>great
00:06:23  <rvagg>and test-nodesource_ceejbot-debian7-arm-pi1p-1 should be happy again
00:06:38  <jbergstroem>if you're in there
00:06:40  <jbergstroem>could you rename it?
00:06:47  <jbergstroem>should be: test-nodesource_ceejbot-debian7-arm_pi1p-1
00:06:56  <jbergstroem>arm-pi1p -> arm_pi1p
00:07:06  <jbergstroem>i think its the only one that has the typo
00:07:19  <rvagg>eeek
00:07:45  <jbergstroem>I can rename it
00:07:52  <jbergstroem>if you're logged in just change secret and restart
00:08:53  <jbergstroem>it _is_ correct in jenkins
00:09:17  <jbergstroem>oh, no. sorry. too quick with mouse pointer
00:10:01  <jbergstroem>I must be hallucinating, it's correct too. I wonder if its just readme.md then
00:11:21  <rvagg>so many places to change the name!
00:11:25  <jbergstroem>yep as always, my bad
00:11:39  <rvagg>no, jenkins was wrong, I fixed it too quick for you
00:11:43  <jbergstroem>oh..
00:12:00  <jbergstroem>hey don't put too much air under my wings
00:12:01  <rvagg>everything was wrong, jenkins, the hostname on the machine, my inventory, ssh config, host_vars, nfs exports, nfs export directory
00:12:03  <rvagg>copypasta
00:18:30  <rvagg>and /etc/fstab for the mount
00:18:35  <rvagg>all fixed and running now
00:23:04  <jbergstroem><3
00:26:31  * jenkins-monitorquit (Remote host closed the connection)
00:26:40  * jenkins-monitorjoined
00:26:44  <rvagg>I think I've taken care of the new Odroid-XU machines that are part of armv7-ubuntu1404 now with a `JOBS=4`, doing a test compile on one to confirm
00:27:18  <rvagg>the 1404 ansible setup doesn't have JOBS in it, tho I thought it made a sensible default at some point in the chain
00:28:53  <jbergstroem>how many cores do they have?
00:29:26  <jbergstroem>you have {{ ansible_processor_vcpus }} availble
00:29:27  <jbergstroem>which is pretty reliable
00:29:34  <jbergstroem>(after gather of course)
00:30:08  <jbergstroem>good thing: in newer versions of ansible you can tell gather what to get. we only use a small amount of info from the os so it'll speed things up
00:31:15  <jbergstroem>rvagg: oh and if you want; having a newer openssh on the jump host so we can use -J would be pretty nice ¯\_(ツ)_/¯
00:33:56  <rvagg>https://www.dropbox.com/s/quy6107c83nt5i1/2016-08-29%2011.13.33.jpg?dl=0
00:34:50  <rvagg>unfortunately they are not the same machines, there is 1 Odroid-XU3 and 2 Odroid-XU's there, 8 cores vs 4 cores
00:34:50  <jbergstroem>sweet keep em comin'
00:35:15  <jbergstroem>did you get a ups?
00:36:31  <rvagg>https://www.dropbox.com/s/ih66hzon8mdmqxf/2016-08-29%2023.36.09.jpg?dl=0
00:37:13  <rvagg>Yep, there's a UPS in the mix now tho the armv8 machines are a little too thirsty for it. I'm thinking of getting in to those and removing some fans or replacing with more efficient ones.
00:37:28  <jbergstroem>yeees
00:37:39  <rvagg>Will gave better photos up shortly, just replacing some final messy bits before I take some sharable shots.
00:37:42  <jbergstroem>can we perhaps cpuidle them?
00:38:32  <rvagg>maybe, they are not optimal in their current state
00:39:09  <rvagg>if you look carefully in that last photo you can see test-nodesource-mininodes-debian7-arm_pi1p-1 is offline, I'll let you work out where it is
00:45:49  * jenkins-monitorquit (Remote host closed the connection)
00:45:56  * jenkins-monitorjoined
00:52:33  * node-ghjoined
00:52:33  * node-ghpart
01:24:58  * node-ghjoined
01:24:58  * node-ghpart
04:50:00  * jenkins-monitorquit (Remote host closed the connection)
04:50:09  * jenkins-monitorjoined
07:32:34  * sgimenoquit (Ping timeout: 240 seconds)
08:11:21  * sgimenojoined
08:32:24  * gibfahnjoined
10:44:14  * gibfahnquit (Ping timeout: 264 seconds)
10:47:13  * thealphanerdquit (Quit: farewell for now)
10:47:43  * thealphanerdjoined
11:30:08  <joaocgreis>what is the best way to get in touch with the release team? (cc evanlucas thealphanerd perhaps)
11:42:06  <jbergstroem>joaocgreis: they're pretty responsive on irc so hopefully here :)
11:46:22  <jbergstroem>if someone could help out with hangout/yt links for https://github.com/nodejs/build/issues/474 that'd be cool
12:22:11  <thealphanerd>joaocgreis what's up
12:22:12  <thealphanerd>?
12:23:10  <jbergstroem>thealphanerd: perhaps stalled and https://github.com/nodejs/node/issues/7989#issuecomment-243410541 ?
12:28:21  <joaocgreis>thealphanerd: I'm working on a release jenkins job for v6 onwards, using vs2015 for windows. I'll need a review when it's done (it's a release job, so my eyes should not be the only ones on it perhaps) and I need to notify the release team about it
12:36:56  <thealphanerd>sure thing
12:37:03  <thealphanerd>more than happy to help test
12:37:10  <thealphanerd>I don't know much about the scripting differences
12:37:22  <thealphanerd>but I recently got a windows machine so I can learn more
12:47:26  * lance|afkchanged nick to lanceball
13:10:00  * node-ghjoined
13:10:00  * node-ghpart
13:17:06  * node-ghjoined
13:17:06  * node-ghpart
13:21:22  * node-ghjoined
13:21:22  * node-ghpart
13:23:53  * node-ghjoined
13:23:53  * node-ghpart
13:26:30  * node-ghjoined
13:26:30  * node-ghpart
13:34:35  * node-ghjoined
13:34:35  * node-ghpart
13:43:20  * node-ghjoined
13:43:20  * node-ghpart
13:46:37  <mhdawson>@jbergstroem, @joaocgreis can on of you add the following machines to the firewall
13:46:52  <mhdawson>test-osuosl-ubuntu14-ppc64_le-5/
13:47:04  <mhdawson>test-osuosl-ubuntu14-ppc64_le-6/
13:47:21  <mhdawson>these are on the new production openstack instance replacing the temporary ones we had
13:47:44  <jbergstroem>done
13:49:31  * node-ghjoined
13:49:32  * node-ghpart
13:51:04  * node-ghjoined
13:51:05  * node-ghpart
13:56:27  * node-ghjoined
13:56:27  * node-ghpart
13:56:35  <jbergstroem>could someone lgtm this? https://github.com/nodejs/build/issues/481 (ping mhdawson, someone else that is around)
14:03:32  * node-ghjoined
14:03:32  * node-ghpart
14:04:17  * node-ghjoined
14:04:17  * node-ghpart
14:04:32  * node-ghjoined
14:04:32  * node-ghpart
14:10:22  * node-ghjoined
14:10:22  * node-ghpart
14:16:35  * node-ghjoined
14:16:35  * node-ghpart
14:20:34  * node-ghjoined
14:20:34  * node-ghpart
14:32:39  * node-ghjoined
14:32:39  * node-ghpart
14:33:25  <Trott>test-nodesource_ceejbot-debian7-arm_pi1p-1 is still failing up a storm again. :-| https://ci.nodejs.org/job/node-test-binary-arm/3567/RUN_SUBSET=1,label=pi1-raspbian-wheezy/ https://ci.nodejs.org/job/node-test-binary-arm/3567/RUN_SUBSET=0,label=pi1-raspbian-wheezy/
14:33:25  <Trott>https://ci.nodejs.org/job/node-test-binary-arm/3567/RUN_SUBSET=addons,label=pi1-raspbian-wheezy/
14:33:47  <Trott>rvagg jbergstroem ^^^^ (test-nodesource_ceejbot-debian7-arm_pi1p-1 build failures galore again...)
14:36:43  <jbergstroem>urgh
14:43:46  <mhdawson>As an fyi forcing some adding ppc jobs to check out the new production ppc vms
14:45:37  <mhdawson>fedora24 failed
14:45:47  <mhdawson>wondering if it has an up to date enough toolchain
14:46:22  <mhdawson>Error: Failed to perform requested operation on instance "release-osuosl-ubuntu14-ppc64_le-2", the instance has an error status: Please try again later [Error: Build of instance 31b8261d-7870-4b38-b4a7-81328ef64f81 aborted: Failed to allocate the network(s) with error No fixed IP addresses available for network: a5bd5b53-1dc4-423c-a854-aa1cc9ee5456, not
14:46:22  <mhdawson>rescheduling.].
14:46:40  <mhdawson>wrong pastes
14:46:43  <mhdawson>https://www.irccloud.com/pastebin/ZbIhpXxU/
14:51:47  <jbergstroem>mhdawson: yeah, fixed
14:52:17  <jbergstroem>mhdawson: we're talking about it in #node-dev. Perhaps chip in on how we can avoid using the bundled toolchain? (ref addaleax)
14:59:57  <mhdawson>For the non-ppc, 390 platforms that is the default
15:00:18  <mhdawson>to use their bundled toolchain
15:11:35  <mhdawson>if you open an issue and cc me, I'll see if I can get someobdy to comment on how we might use the local toolcahin instead of the downloaded one
15:29:31  <jbergstroem>mhdawson: ok
15:41:50  * node-ghjoined
15:41:50  * node-ghpart
15:42:21  * node-ghjoined
15:42:21  * node-ghpart
15:43:44  * lanceballchanged nick to lance|afk
15:52:11  * node-ghjoined
15:52:11  * node-ghpart
16:30:22  * node-ghjoined
16:30:22  * node-ghpart
16:46:55  * sgimenoquit (Quit: Leaving)
17:01:54  * node-ghjoined
17:01:54  * node-ghpart
17:56:05  * node-ghjoined
17:56:05  * node-ghpart
17:56:36  * Fishrock123joined
18:30:43  * lance|afkchanged nick to lanceball
18:42:33  <jbergstroem>restarting the arm host (ceejbot pi1)
18:46:43  * node-ghjoined
18:46:43  * node-ghpart
18:48:03  * node-ghjoined
18:48:03  * node-ghpart
18:49:53  * node-ghjoined
18:49:53  * node-ghpart
18:51:16  <jbergstroem>joaocgreis, rvagg, mhdawson: could someone update the issue/gdoc for youtube/hangout links?
18:51:58  * node-ghjoined
18:51:58  * node-ghpart
18:55:55  <jbergstroem>argh almost meeting time and I don't have any links :(
19:00:31  <joaocgreis>jbergstroem: I don't have access. Meeting is in 1h time right?
19:01:01  <jbergstroem>joaocgreis: yeah in 1h
19:57:23  <jbergstroem>ok
19:57:27  <jbergstroem>so what do we do?
19:57:40  <starefossen>good question
19:57:56  <starefossen>I guess one of us should create a Hangout On Air?
19:58:56  <jbergstroem>we need to record and republish/broadcast live
19:59:57  * gibfahnjoined
20:00:04  <starefossen>the recording can be transferred to node yt account after the meeting
20:00:20  <joaocgreis>mhdawson rvagg: I think only you two have access to the foundation account to create the meeting
20:00:30  <jbergstroem>Fishrock123 is probs helping out!
20:00:39  <jbergstroem>🎉
20:01:00  <thealphanerd>jbergstroem do we have a link?
20:01:01  <Fishrock123>I don't know how to create one of those
20:01:09  <jbergstroem>not just yet
20:01:15  <thealphanerd>kk
20:01:20  <jbergstroem>thealphanerd: you has admin?
20:01:24  <jbergstroem>we need to create the links
20:01:26  <thealphanerd>nop
20:01:29  <thealphanerd>mhdawson does
20:01:33  <thealphanerd>I think
20:01:34  <jbergstroem>can't reach him
20:01:39  * node-ghjoined
20:01:39  * node-ghpart
20:01:47  <starefossen>Fishrock123: http://hangouts.google.com/onair
20:02:14  * node-ghjoined
20:02:14  * node-ghpart
20:02:15  <jbergstroem>Fishrock123: you log in with the node.js account and set it up to stream to yt
20:03:26  <jbergstroem>Fishrock123: (don't go live just yet though)
20:03:40  <Fishrock123>That only seems to work from my personal account
20:03:42  <rvagg>ok, I'm up, sorry
20:03:47  <jbergstroem>ah, sweet
20:03:49  <rvagg>lemme set it up
20:04:45  <thealphanerd>:)
20:06:46  <starefossen>jbergstroem: we should have a look at automating hangouts using the bot :D
20:06:58  <jbergstroem>automate all the things :)
20:06:59  <Fishrock123>I've talked about this a lot
20:07:14  <rvagg>http://www.youtube.com/watch?v=p6viQ2HyGqk live feed
20:07:23  <Fishrock123>I think the main issue there was getting info out of (probably) google calandar for meeting times
20:07:24  <rvagg>https://hangouts.google.com/hangouts/_/hoaevent/AP36tYfOUN-VgervByMOkRj9SpukzKndyyCF3SJK1KHSnXFxbYinSw hangout participate
20:07:35  <Fishrock123>but we could do it more manually first probably
20:07:48  <thealphanerd>I'm in
20:08:28  * node-ghjoined
20:08:29  * node-ghpart
20:42:31  * node-ghjoined
20:42:31  * node-ghpart
20:47:08  <phillipj>gotta go, cya
20:49:52  <williamkapke>I do not believe the build group has the authority to claim ownership of any project they choose. If they started the project- sure. But the build group do not start the bot project. I merged my work with Phillips in the spirit of collaboration- but I feel it is being completely take away from me at this point. Infact- it is really odd to be "welcomed" to a
20:49:52  <williamkapke>project I started. :/
20:58:49  <phillipj>Build wg hasn't claimed ownership of if, it just welcomes the project as far as I understood it
21:00:54  <phillipj>Next would probably be a formal vote among the gh-bot members?
21:02:16  <williamkapke>The language being used was leaning that way- so I was just commenting to make sure it wasn't suggested in that fashion
21:04:25  <Fishrock123>I'm not sure why anything other than the deployment would fall under the build wg
21:05:24  <Fishrock123>see: the website
21:11:22  <phillipj>Getting the Jenkins -> gh status integration stable will take some effort
21:13:58  <starefossen>williamkapke: thanks for the comment. I have updated the meting minutes to reflect that Build is not in any way claiming ownership but is positive if the bot wants to be a group under the Build WG
21:14:20  <phillipj>The current Travis CI integration/hack we've got could be seen as build related.. There has even been some thoughts about creating such a CI service on the nodejs infra, which would get even more build wg related
21:15:16  <phillipj>As said in the meeting, the bot is still in its early stages
21:15:57  <starefossen>could we try to set a date / time for a Bot meeting to discuss this?
21:16:22  <williamkapke>starefossen: k thx
21:17:38  <williamkapke>starefossen: A meeting would be great!
21:21:37  <thealphanerd>jbergstroem it just dawned on me that for the tap2junit converter the test suite can convert itself o0o0o0o
21:24:20  <phillipj>starefossen: the group is @nodejs/github-bot (not jus bot), otherwise minutes lgtm 👍
21:24:45  <starefossen>fixed, thanks!
21:31:45  <starefossen>williamkapke phillipj Fishrock123 jbergstroem: Bot Meeting https://github.com/nodejs/github-bot/issues/68
21:32:42  <Fishrock123>starefossen: I think that overlaps with a TSC meeting
21:33:16  <williamkapke>yup- I just left a comment on the issue saying the same
21:33:52  <williamkapke>the TSC meeting is only every-other Thrus though... so we could do another Thurs
21:37:51  * Fishrock123quit (Remote host closed the connection)
21:51:47  * node-ghjoined
21:51:47  * node-ghpart
21:56:50  * gibfahnquit (Ping timeout: 264 seconds)
22:32:11  <thealphanerd>jbergstroem https://github.com/tapjs/tap-mocha-reporter/blob/master/lib/reporters/xunit.js
22:32:23  <thealphanerd>it looks like exactly what we want may already exist in some form inside tap
22:32:40  <thealphanerd>I'm going to run with this as an example
22:36:45  <jbergstroem>thealphanerd: xunit is close enough but not exactly junit
22:37:05  <thealphanerd>yup... I also have the reporter from citgm to base it on
22:37:10  <thealphanerd>which I know works with the jenkins tool
22:37:18  <thealphanerd>I think I should have a POC soon
22:37:35  <thealphanerd>just brushing up on stream apis as I think this will be a good learning opportunity
22:39:03  * Fishrock123joined
22:41:51  <rvagg>woohoo, a stack of SD cards just arrived
22:43:55  * Fishrock123quit (Ping timeout: 265 seconds)
22:47:04  * Fishrock123joined
23:15:27  * Fishrock123quit (Remote host closed the connection)
23:26:39  * Fishrock123joined
23:28:18  * Fishrock123quit (Remote host closed the connection)