[00:15] <wgrant> cjwatson: My suspicion about the broken Maverick armel builds was correct. We've had some more show up and a LOSA confirmed that the queue record is missing.
[00:15] <wgrant> So I'm not completely insane.
[00:15] <ScottK> wgrant: Correction: That's not evidence of you being completely insane.
[00:16] <wgrant> True.
[04:01] <cody-somerville> Is there something wrong with hpijs-ppds in Maverick?
[09:16] <jml> cjwatson: the thing to create the branches was kicked off overnight. Once I finish interviewing this candidate I'll check on the status and get back to you.
[09:27] <doko> cjwatson: ok to promote llvm-2.8 (used by openjdk-6) and python3.2 (used by python3-stdlib-extensions)? new upstream versions
[09:28] <cjwatson> yep
[10:43] <apw> doko, ok the initial kernel is finialised and in the accept queue
[10:43] <apw> cjwatson, i've pushed the initial kernel for natty, i believe doko wants that built to bootstrap the toolchain
[10:48] <cjwatson> apw: looks like somebody beat me to accepting it :)
[10:51] <apw> cjwatson, :)  thanks anyway
[11:06] <doko> cjwatson: I did :-/
[11:06] <doko> I won't interfer anymore after the initial bootstrap
[11:09] <doko> security hits the buildds hard ...
[11:14] <cjwatson> I didn't consider it interfering
[11:23] <cjwatson> jml: ooh.  I spy a bunch of branches.
[11:23] <jml> cjwatson: yes. the script is still running[1] afaik
[11:24] <jml> [1] Where "running" means one of: actually running; stopping; waiting for someone to restart it
[12:02] <doko> apw: how long do the kernel builds usually take?
[12:06] <cjwatson> doko: are you still intending to upload python2.7?
[12:07] <doko> cjwatson: hmm, no
[12:10] <doko> cjwatson: so when the kernel headers are there, we could open natty
[12:13] <jml> cjwatson: the branching process is done. some branches failed. we'll look into it, but not as an issue of critical importance.
[12:16] <cjwatson> doko: last linux build was 2h on amd64, 15h on armel, 7h on i386, 4h45m on powerpc
[12:17] <cjwatson> jml: great, thanks - I think that's good enough to open with
[12:17] <cjwatson> doko: I'd like to run through at least one compiled package with the new linux, so that we won't get the situation where we open the floodgates and find that everything fails to build
[12:17] <jml> cjwatson: cool. let me know if there's anything else I can do to help.
[12:17] <cjwatson> *nod*
[12:18] <cjwatson> doko: (there are plenty of random merges in the queue we could use)
[12:18] <doko> cjwatson: yes, makes sense
[12:54] <doko> xvfb still broken, no jtreg test results for openjdk-6, but at least the build doesn't take that long
[13:15] <doko> again, firefox security uploads ... we'll never open this week with powerpc lagging that behind :-/
[13:17] <cjwatson> we'll still be ahead of historical schedule for opening, I think
[13:17] <cjwatson> depending on whether you count in calendar days or working days
[13:17] <cjwatson> (I think calendar days are slightly more realistic for this purpose since much of the time is spent waiting around for computers)
[13:28] <cjwatson> doko: I've scored up linux/powerpc, not that it will help hugely (UI says start in 7 hours)
[13:28] <cjwatson> actually, that will have it finishing around the same time as linux/armel finishes, so that might be OK
[14:25] <apw> doko, cjwatson the build will be about 6-7 hours total, armel is only one flavour right now
[14:26] <cjwatson> ah, so powerpc will be the last one after all then
[15:06] <apw> cjwatson, yeah i see, damnable security
[22:56] <doko> apw, cjwatson: http://launchpadlibrarian.net/57569441/buildlog_ubuntu-natty-powerpc.linux_2.6.36-0.1_FAILEDTOBUILD.txt.gz should we ignore this, or fix it before opening natty?
[22:57] <apw> doko, well its probabally an easy fix
[22:58] <doko> apw: ok, I'll be awake for about 30min, let me know if you could prepare another upload
[23:00] <apw> doko, i'll know shortly if its easy
[23:00] <doko> thanks