[00:45] wgrant/StevenK: did the recipe builds change recently to append ~ubuntuNN instead of ~series? [00:47] bigjools: Yes [00:47] Ubuntu's used the version number for backports for a while, and we need to switch before u-series [00:47] wgrant: ok. you broke juju-core folks. haha :) [00:47] Why are they depending on the version number? [00:47] s/version number/structure of the version number/ [00:47] That's pretty broken [00:47] stupidity I think :) [00:47] Still [00:48] That recipe is already pretty broken [00:48] I'm going to close that tab and pretend I never saw it. [00:48] heh [04:00] wgrant: The next branches for buildd-manager are due RSN? [04:00] Indeed === tasdomas_afk is now known as tasdomas [07:44] StevenK: https://code.launchpad.net/~wgrant/launchpad/buildd-manager-inlineCallbacks/+merge/183578 [07:55] wgrant: I'm wary of the the commit in the manager code [07:57] StevenK: It's committing after it comes back from a Deferred [07:57] Which doesn't make much sense. [07:58] Though I'm surprised you noticed that in the merged diff. [07:59] It's five lines into a green diff [07:59] In fact, you couldn't have noticed. Which commit are you talking bout? [07:59] 455 + # Commit the changes done while possibly rescuing jobs, to [07:59] 456 + # avoid holding table locks. [07:59] 457 + transaction.commit() [07:59] That's not new [08:00] And it shouldn't do anything, but it's there to ensure that builder.currentjob is as up to date as possible. [08:00] Oh, it's just moved from other twisted garbage [08:00] I didn't change any code except for removing two xmlrpc.Fault wrappers. [08:00] And I guess that is one of the commits that is not long for this world? [08:01] Correct. [08:01] We can't afford to calculate currentjob there. [08:01] It will be precalculated, and that method won't touch the DB until further down. [08:02] So thanks to a day of JavaScript and Twisted, my brain is now leaking out of my ears [08:05] wgrant: r=me [08:05] wgrant: Sorry, I got distracted [08:07] Thanks [09:01] wgrant: Your buildd-manager-inlineCallbacks branch and my destroy-builder-aborted branch clash. Which would you prefer to have landed first? [09:06] cjwatson: I was deliberately waiting for yours to land, sorry. [09:07] OK, landing [09:08] During the refactoring I discvoered something that I thought was just a production glitch a few months ago. [09:08] A manualled, disabled builder won't get its current build terminated. [09:09] Probably missed originally because of the convoluted callbacks. It makes no sense otherwise. [09:16] cjwatson: test_binarypackagebuildbehavior still references AbortedSlave [09:18] what. I grepped. [09:19] one moment :( [09:19] Oh, I must have only grepped buildmaster, damn [09:19] Ah, yeah [09:21] Very confused by what buildbot just did [09:21] It successfully ran no tests [09:22] It doesn't check the exit code due to an old lxc-start-ephemeral bug [09:22] The testrunner probably died badly due to the import. [09:29] wgrant: https://code.launchpad.net/~cjwatson/launchpad/testfix-destroy-builder-aborted/+merge/183598 [09:33] cjwatson: r=me [09:34] landing [09:57] Anyone up for a Swift branch review? More /srv and /srv2 juggling underway it seems. [10:02] I really should get to that eventually [10:02] But the /srv and /srv2 juggling can't stop for at least a few months after we start using Swift === tasdomas is now known as tasdomas_afk