[00:03] <StevenK> wgrant: http://pastebin.ubuntu.com/5785377/ is the last failure, but the tests are very strange
[00:05] <wgrant> StevenK: Which test is that?
[00:06] <StevenK> lp.testing.tests.test_layers_functional.LaunchpadTestCase.testLibrarianWorking
[00:06] <wgrant> But anyway, the problem is fairly clear
[00:06] <wgrant> It expects an AttributeError or ComponentLookupError when the ZCA is not loaded
[00:06] <wgrant> But now it gets a TypeError
[00:54] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/bug-1193157/+merge/170722
[00:57] <StevenK> wgrant: Looks good, r=me
[10:49] <cjwatson> StevenK: Ooh, just noticed bug 1188034.  Excellent.  Do you have client code already or should I write one for ubuntu-archive-tools?
[10:49] <_mup_> Bug #1188034: Should be possible to upload chroots over the API <distributions> <lp-soyuz> <qa-ok> <soyuz-ftpmaster-tools> <Launchpad itself:Fix Released by stevenk> <https://launchpad.net/bugs/1188034>
[10:49] <cjwatson> (I'm happy to do so)
[10:51] <cjwatson> StevenK: Archive owner is an interesting choice for the permission.  You didn't consider launchpad-buildd-admins instead, which I think was what infinity and I were expecting to use?
[12:18] <StevenK> cjwatson: infinity requested archive owner
[12:19] <StevenK> cjwatson: My client code was a horrible hack, so please write a better one
[12:19] <cjwatson> OK :)
[12:19] <cjwatson> Do we want an equivalent of 'manage-chroot.py remove'?
[12:21] <cjwatson> I think that's the only piece missing to be able to kill that script
[12:23] <cjwatson> BTW I have a test now that exercises the case of copies into private archives owned by private teams causing /builders to 403, so hope to be able to push up a branch fixing that soon
[12:24] <StevenK> cjwatson: Hmmm
[12:25] <StevenK> cjwatson: data=None, perhaps? I suspect it will need a small code change
[12:27] <cjwatson> It might be clearer as a separate method
[12:27] <cjwatson> Particularly since sha1sum is a weird thing to have to pass with None
[12:27] <cjwatson> But just for clarity in general
[12:27] <StevenK> Hmmm, indeed
[12:29] <StevenK> cjwatson: The QA with that method wasn't exactly smooth on qas, so I'd like to see a test against prod with someone who doesn't suffer from Australian internet
[12:35] <cjwatson> Maybe infinity fancies doing a chroot refresh
[12:37] <StevenK> I'd rather something like hardy i386 or something known just in case it does go pear shaped, TBH, but your call
[17:19] <cjwatson> EC2 gave a few errors for one of my recent branches, most of which I've fixed; they were unreliable tests rather than anything I'd caused, I think.  I don't understand http://paste.ubuntu.com/5787381/ though - is that one that's known to be unreliable?
[23:52] <wgrant> cjwatson: Yeah, that one's known to be unreliable.
[23:53] <wgrant> You might have also run into two ddeb failures that I think are arch-dependent but I haven't bothered to fix yet.