[00:00] <camako> robru, sure... But it "remembers" today's build history.. But assigns the next job a number from yesterday I think : https://ci-train.ubuntu.com/job/ubuntu-landing-019-1-build/build
[00:01] <robru> camako: yeah I can't explain that
[00:01] <robru> camako: but your job is running, i think that's the best we can hope for
[00:01] <camako> robru, yeah it seems to be working
[00:01] <camako> thanks
[00:01] <robru> camako: you're welcome! and sorry for the hassle!
[00:46] <robru> camako: ^^ so your status being all "...1125 not in PPA", I'm assuming that's due to stale backups being restored, don't worry about that, I'm working on a fix for that, just leave it for now
[00:47] <camako> robru, yea I was ignoring those
[02:18] <veebers> trainguards Hi all, it's been a while since I've used the train. After creating a request what's my next step? Do I assign it or is that used for something else?
[02:24] <renatu> traingruards, hey I am getting this error: 2015-12-01 21:24:58,594 WARNING Silo name list not found, run setup_citrain.py
[02:24] <renatu> traingruars, on silo 45, https://ci-train.ubuntu.com/job/ubuntu-landing-045-1-build/114/console
[02:26] <veebers> renatu: Hi, you may know :-) After requesting a silo, do I hit the Assign button or something else?
[02:26] <renatu> veebers, yes, and it was building before
[02:27] <veebers> renatu: sorry, I meant for my own silo. It's been a while since I've used it and things have changed
[02:28] <renatu> veebers, yes you need to hit the assign button
[02:28] <renatu> veebers, the silo should change to 'Ready to build"
[02:28] <veebers> renatu: ah I see, awesome thanks for the help :-)
[02:33] <robru> renatu: the train imploded earlier today, how old is that log? Should work if you try again
[02:33] <renatu> robru, I am trying and nothing happens
[02:35] <robru> renatu: what do you mean "nothing happens"? Doesn't look like you ran the job
[02:35] <renatu> robru, I click on build button and the screen refresh without any new job
[02:36] <robru> renatu: one sec
[02:40] <robru> renatu: it's something https://ci-train.ubuntu.com/job/ubuntu-landing-045-1-build/114/console
[02:40] <robru> Brb, eating
[02:49] <dobey> robru: uhm, how are there two tickets assigned to silo 21?
[02:49] <dobey> i just tried to build https://requests.ci-train.ubuntu.com/#/ticket/724 but it is building location-service instead
[02:50] <dobey> which i see is already built in the ppa
[02:58] <robru> dobey: the train experienced a catastrophic failure today and we restored from a backup.
[02:59] <robru> dobey: was one of them landed already?
[02:59] <robru> dobey: what ticket numbers?
[03:01] <dobey> i don't know about location-service
[03:01] <dobey> https://requests.ci-train.ubuntu.com/#/ticket/724 i created earlier today
[03:01] <dobey> just before the implosion
[03:02] <dobey> https://requests.ci-train.ubuntu.com/#/ticket/678 seems to be the one for location-service, and the MPs do say "Merged" on it
[03:08] <robru> dobey: https://ci-train.ubuntu.com/job/ubuntu-landing-023-1-build/176/console you're building in 23 ho
[03:08] <robru> now
[03:08] <dobey> ok
[03:09] <robru> dobey: sorry for the hassle.
[03:16] <renatu> robru, the build started but got a very strange error
[03:17] <renatu> robru, https://requests.ci-train.ubuntu.com/#/ticket/722
[03:17] <robru> renatu: yeah that's because the backup is probably missing address-book-app. If you want to fix that quickly you can rebuild it, or wait some hours as I'm working on a permanent fix.
[03:18] <renatu> robru, ok I will rebuild it, thanks
[03:18] <robru> renatu: ok, sorry
[04:19] <robru> oh fun
[06:21] <robru> here we go!
[07:23] <Mirv> yay for working backups
[07:33] <robru> Mirv: yay even more for pushing branches to lp so that backups aren't even necessary ;-)
[07:33] <Mirv> robru: yeah, I read your e-mail, it sounds good
[07:34] <robru> Mirv: I'm just going through and double checking that the silo states make sense and are consistent with reality. so far it seems good
[07:36] <Mirv> robru: nice. thanks for your hard work.
[07:36] <Mirv> it seems the Qt migration autopkgtests will take a while... this is 18h after the publishing: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src
[07:37] <robru> Mirv: you're welcome. also sorry for breaking everything constantnly
[07:37] <robru> Mirv: yes I've heard that autopkgtest infra is strained
[07:37] <Mirv> robru: well when you break everything in every possible way, you eventually get a really tested and bulletproof system :) and the problems haven't like caused huge, longstanding problems.
[07:38] <robru> Mirv: heh, thanks. once it stabilizes I think I need to take a month off ;-)
[07:39] <Mirv> robru: yes, please eventually have a good, long break and we will also then ban you from IRC this time :)
[07:39] <robru> lol
[07:40] <robru> Mirv: ugh, silo 12 status reporting is broken, which means auto merge is also broken. looking into it.
[07:45] <Mirv> robru: thanks. a working merge / marking as Landed would be nice.
[07:46] <robru> Mirv: this error is very strange though as it seems to be an error in requests library itself.
[07:49] <robru> Mirv: it seems to only happen with qtdoc-opensource-src. do you know anything unusal about that one?
[07:51] <Mirv> robru: it's a package that had Ubuntu changes but now is a sync from Debian, that's the only thing special I can think of
[07:51] <robru> Mirv: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+sourcepub/5736443/+listing-archive-extra hummmm no signer!!! dun dun dun!
[07:51] <Mirv> robru: right, if you do a copy-package from Debian to PPA or archive it doesn't have a signer indeed
[07:52] <robru> Mirv: also no changes file?
[07:52] <Mirv> (or so the LP says in the PPA)
[07:52] <Mirv> robru: I guess it's because it's never uploaded to Ubuntu, it's a LP-made sync directly from Debian
[07:53] <robru> Mirv: what's happening is that the train is trying to download the changes file from the ppa and from ubuntu and confirm that the contents of the changes file from both matches (ie, that the version in proposed is really our version from the ppa and not some other package with the same version number)
[07:53] <Mirv> robru: there would have been many other ones, but the others were already auto-synced from Debian to -proposed and I made a "build1" of them
[08:05] <robru> Mirv: ok, pushed a fix, we'll see how it goes in about 12 minutes.
[08:19] <Mirv> robru: ok!
[08:22] <robru> Mirv: so the train thinks your "pre-merge commit" is a new commit
[08:24] <robru> Mirv: if possible I recommend deleting your commit, and then pushing https://code.launchpad.net/~ci-train-bot/qtubuntu-camera/qtubuntu-camera-ubuntu-xenial-landing-012 to lp:qtubuntu-camera instead. then the train will recognize it's own commit and report correctly that a rebuild is not needed
[08:24] <robru> Mirv: as it stands, this 'new commit' warning will prevent the auto merge.
[08:25] <Mirv> robru: ok, trying out
[08:25] <Mirv> I tried to help Kaleo in working on his silo
[08:26] <Mirv> robru: done
[08:27] <robru> Mirv: ok, let's see if it works ;-)
[08:27] <Mirv> no idea why I thought a manual merge would be a good idea. it was 1 min before leaving for team dinner..
[08:27] <robru> hehe
[08:29] <Mirv> robru: it worked!
[08:29] <robru> Mirv: blam
[08:30] <Mirv> robru: that's nice actually, that train supports this pre-pushing while being able to track the migration still
[08:31] <robru> Mirv: it didn't used to. before it would track tip commit id's and complain if there was any change. I fixed it to use 'bzr missing' and parse the output, so now it's much smarter about if commits are missing or not
[08:32] <Mirv> that's smart indeed
[08:33] <robru> Mirv: did silo 12 used to contain oxide and now it doesn't?
[08:33] <Mirv> robru: correct. I moved the main packages to 059 for sil2100 to publish them.
[08:33] <robru> ok
[08:34] <Mirv> well, more exactly non-train main packages that needed to have a manual upload instead of no-change MP.
[08:35] <Mirv> moved at the very last minute, worked well and thankfully sil2100 got his core dev rights.
[08:36] <robru> Mirv: no worries, just found an old copy of the source tree from the last time oxide was diffed, just cleared it out
[08:36] <robru> Mirv: https://ci-train.ubuntu.com/job/cyphermox-test/24/console how's that for a train full of silos? ;-)
[08:42] <Mirv> robru: sweet! :)
[12:27]  * sil2100 off to lunch
[13:35] <rvr> kenvandine: Silo 14 approved
[14:27] <morphis> Mirv, sil2100: one of you have time for some uploads?
[14:27] <sil2100> morphis: I'm here o/
[14:28] <morphis> awesome
[14:40] <mardy> Mirv: hi! For some reason whenever I build it, it tells me that it needs to be rebuilt: https://requests.ci-train.ubuntu.com/#/ticket/695
[15:04] <Mirv> mardy: funny. the only thing I see is that there's some disparency between your MP branch and the target - like trunk is at 11, the MP says unmerged commits start from 13. so maybe try doing a new MP based on trunk where you apply the diff in a single commit or something (just a guess based on seeing there's some history with the branch)
[15:56] <dobey> slangasek: hi again. can you poke qtpurchasing-opensource-src through the NEW queue in xenial?
[16:00] <dobey> whee netsplits
[16:04] <dobey> it'll unfortunately end up blocked in proposed though, i think, because of qt5.5
[16:33] <slangasek> dobey: if I were reviewing this package in a silo, I would reject it for
[16:34] <slangasek> dobey: if I were reviewing this package in a silo, I would reject it for multiple packaging issues; but since it's in the NEW queue, I guess it's going through...
[16:34] <slangasek> (and Mirv isn't around for me to poke)
[16:36] <dobey> slangasek: hmm, ok. yes, please bug mirv about that, as i'm sure the same issues need to be fixed in the vivid overlay version too
[16:41] <slangasek> dobey: ok, he wasn't in this channel but his irc client is connected so I've braindumped to him and accepted the package
[16:42] <dobey> slangasek: ok, thanks
[16:43] <dobey> seems freenode is having lots of issues today
[17:28] <mterry> robru, sil2100: is there a spare silo I could take for a bit for testing some code changes?
[18:42] <robru> mterry: yeah there's like 15 free. You don't need to ask, generally ;-)
[18:43] <mterry> robru, yeah but there was that email a bit back where you said you folks were full up
[18:43] <mterry> didn't know if we were still hard up
[18:43] <robru> mterry: what? That must have been over a week ago...
[18:44] <mterry> robru, yeah...  :)
[18:44] <mterry> Point is, I'll make  a silo
[18:44] <robru> mterry: it says how many are in use on requests.c.u.c, just subtract from 60 total
[18:44] <mterry> So just 6 free
[18:44] <robru> mterry: OK, you can make a request and assign it yourself, just let me know if there's any trouble
[18:45] <mterry> robru, that total would be interesting data to surface.  like 54 / 60 Assigne
[18:46] <robru> mterry: requests page unfortunately doesn't know how many total there are, unless I hard coded it. Eventually we'll move to a system of unlimited ppas, so it won't even matter
[18:47] <robru> There were 15 free when I went to bed last night, people got greedy in my sleep ;-)
[18:57] <renatu> robru, xenial is having problems with qtdeclarative5-* packages. Do you know what is happening?
[18:57] <renatu> robru, full build log: https://launchpadlibrarian.net/228221248/buildlog_ubuntu-xenial-amd64.address-book-app_0.2%2B16.04.20151202.4-0ubuntu1_BUILDING.txt.gz
[18:57] <robru> renatu: no, what? is there an error log?
[18:57] <mterry> robru, I ruined everything: https://requests.ci-train.ubuntu.com/#/ticket/737
[18:58] <robru> mterry: your merge is superceded: https://code.launchpad.net/~mterry/ubuntu-app-launch/warn-on-xapp/+merge/278497
[18:58] <mterry> robru, ugh right
[18:59] <mterry> robru, oh
[18:59] <mterry> robru, did you see the "fail train" page?
[18:59] <robru> Mirv: you still around? can you help renatu with this qt explosion? ^^
[18:59] <robru> mterry: I *made* the fail train page... what are you seeing now?
[19:00] <mterry> robru, well I was seeing that on that page (737) when I said I ruined everything.  But now I don't see it.  So I dunno
[19:01] <robru> mterry: dunno, could be a transient network error or something. did it say an error code before it disappeared?
[19:01] <mterry> robru, no
[19:01] <robru> then i dunno
[19:02] <mterry> robru, again: http://imgur.com/VuwWyBQ
[19:03] <mterry> Oh, at least queuebot tells me error
[19:03] <ChrisTownsend> Hi, the ppc64el build on Xenial failed earlier today for https://requests.ci-train.ubuntu.com/#/ticket/726 and according to the build log, it looks like python3.5 seg faulted during setup.  Any one know of this issue?
[19:03] <ChrisTownsend> Buildlog: https://launchpadlibrarian.net/228197665/buildlog_ubuntu-xenial-ppc64el.libertine_0.99.6%2B16.04.20151202-0ubuntu1_BUILDING.txt.gz
[19:03] <robru> mterry: uh well if you see {{'s like that it means javascript isn't running to fill out the template. are you running noscript or something?
[19:03] <mterry> robru, not intentionally  :)
[19:05] <mterry> robru, huh.  If I refresh the page, it doesn't go away. But if I press enter in the location bar, it does
[19:06] <robru> mterry: try it in firefox. I think it's a problem on your end, it's fine for me
[19:15] <robru> renatu: so long story short, there's a problem with qt and it'll take some time to fix. are you able to work on something else for a day or two?
[19:16] <robru> ChrisTownsend: first I've heard of it
[19:16] <renatu> robru, can we land it?
[19:16] <ChrisTownsend> robru: Hmm, I'll just do a rebuild and see what happens then.
[19:17] <renatu> robru, we will be able to land it, when  it get approved, or we will need to wait for the fix?
[19:17] <robru> ChrisTownsend: I'd report a python3.5 segfault directly to barry ;-)
[19:17] <robru> renatu: well you can't land a package that won't build, no.
[19:17] <ChrisTownsend> robru: Ok, I'll see if it happens again, and if so, poke him.
[19:18] <renatu> robru, ok
[19:18] <renatu> bfiller, ^^
[19:18] <ChrisTownsend> robru: Thanks
[19:18] <robru> yw
[19:19] <bfiller> renatu: what silo are you talking about
[19:19] <renatu> bfiller, all address-book silos
[19:19] <barry> ChrisTownsend, robru: it's more likely of course that some extension is misbehaving
[19:23] <bfiller> robru: we'll need to get that sorted rather quickly as it will potentially block a lot of silos
[19:23] <bfiller> which I'm sure you already know
[19:23] <dobey> trainguards: for xenial FTBFS fixes on dual landed packages, is it required to go through the full QA process to land a trivial fix?
[19:26] <ChrisTownsend> Hrrm, now all build are failing due to a different reason...
[19:28] <dobey> i'll presume not for now
[19:35] <dobey> heh
[19:35] <robru_hates_irc> mterry: just a note, your qtmir-gles build will fail because you are trying to build qtmir 0.4.7 but qtmir-gles is still 0.4.6. If you're going to bump the upstream version number you have to do it in both branches
[19:35] <mterry> robru_hates_irc, ugh -- I was just trying to avoid the error about not having qtmir-gles
[19:36] <mterry> robru_hates_irc, I didn't want to bother making a real qtmir-gles branch
[19:36] <cjwatson> ChrisTownsend: next time please don't do a full source rebuild for a single-arch failure.  we can retry single architectures
[19:36] <cjwatson> ChrisTownsend: random segfaults on ppc64el are likely a known (but fortunately quite rare) bit of guest memory corruption
[19:36] <robru_hates_irc> mterry: no big deal, just s/0.4.6/0.4.7/ on the first line of the changelog in qtmir-gles
[19:37] <robru_hates_irc> mterry: most of the -gles pain has been automated away
[19:37] <ChrisTownsend> cjwatson: Ok, how do I just do a single arch rebuild?  I don't see any obvious option for that.
[19:37] <robru_hates_irc> ChrisTownsend: you have to ask me and I can do it
[19:38] <cjwatson> ChrisTownsend: anyone with direct upload access to the silo can do it, so anyone in ~ci-train-ppa-service
[19:38] <ChrisTownsend> robru_hates_irc: Hmm, well, now I know
[19:38] <ChrisTownsend> cjwatson: Ok, thanks
[19:39] <robru_hates_irc> ChrisTownsend: there's an open bug about adding a train feature so people can retry ppa builds but it hasn't been a priority unfortunately.
[19:40] <ChrisTownsend> cjwatson: robru_hates_irc: Since I did do the full source rebuild, any ideas why all xenial builds are failing?
[19:40] <dobey> err, xenial archive wonky at the moment?
[19:40] <robru_hates_irc> ChrisTownsend: what silo #? i lost my scrollback
[19:41] <ChrisTownsend> robru_hates_irc: 044
[19:41] <dobey> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/+packages has all build failures on xenial due to unable to install build deps
[19:41] <ChrisTownsend> Yeah, maybe wonky archive.
[19:42] <dobey> i don't know when will be an appropiate time to have someone poke the retries though
[19:42] <cjwatson> haha yeah that was some amusement with archive admin
[19:42] <cjwatson> a certain person deleted qtbase-opensource-src from xenial-proposed
[19:42] <cjwatson> slangasek was just in #launchpad-ops asking for undeletion instructions, which I provided
[19:42] <robru_hates_irc> cjwatson: is anybody working on a fix for that? timo just signed off...
[19:42] <dobey> ah
[19:42] <robru_hates_irc> nice
[19:42] <cjwatson> so it should be back after the next publisher cycle
[19:43] <dobey> fun
[19:43] <robru_hates_irc> cjwatson: how long are publisher cycles?
[19:43] <cjwatson> as long as they take
[19:43] <cjwatson> but typically 15 minutes ish
[19:43] <robru_hates_irc> ah ok
[19:43] <slangasek> yes; fixed on the archive side, and I'm addressing the removal with the responsible AA so that we don't end up in a revert war.
[19:44] <robru_hates_irc> slangasek: I liked Mirv's plan to fix the contested issue in the next upload
[19:44] <robru_hates_irc> rather than breaking the entire world
[19:44] <ChrisTownsend> robru_hates_irc: Well, I'll need a xenial only rebuild for all archs for the silo when this is fixed:)
[19:45] <robru_hates_irc> ChrisTownsend: will do
[19:45] <ChrisTownsend> robru_hates_irc: Thank you!
[19:45] <robru_hates_irc> yw
[19:46] <dobey> i guess a bunch of things will need that :)
[20:07] <cjwatson> ok, I retried that seconds too early, trying again
[20:08] <robru_hates_irc> cjwatson: oh are you doing the retries? thanks
[20:10] <cjwatson> well, some
[20:11] <cjwatson> robru_hates_irc: I've done 10 and 44, but I haven't been keeping an eye on what else might need it
[20:11] <cjwatson> robru_hates_irc: also haven't touched the train (can't remember if that's needed nowadays), just silos
[20:14] <robru_hates_irc> cjwatson: nah these days it'll notice things on it's own
[20:14] <cjwatson> thought so, good
[20:23] <robru_hates_irc> renatu: ok, the issue with qt should be resolved, I've retried your builds
[20:23] <renatu> robru_hates_irc, thanks
[20:23] <renatu> robru_hates_irc, was quick than a day :D
[20:23] <robru_hates_irc> renatu: yeah thanks to slangasek fixing it quickly, I was afraid it would take longer (qt is usually quite slow to move)
[20:34] <robru> there we go
[21:38] <dobey> hmm
[21:38] <ogra_> this channel has turned into a logfile
[21:38] <dobey> i guess i can't do that :-/
[21:42] <dobey> robru: so having upload rights isn't enough to be able to publsih something?
[22:25] <robru> dobey: nope, it published. There's just a race condition between the status updater and the publisher, so it reverted to "successfully built" status temporarily before noticing the publish was successful
[22:27] <dobey> robru: ah, ok
[22:27] <robru> ogra_: yeah i increased the granularity of the status reporting (now reporting per-arch statuses) and the bot went crazy pinging constantly. I'm not sure how to get it under control again
[22:36] <dobey> robru: fix the code to wait until all statuses are either failed or success, until reporting in channel?
[22:36] <dobey> (not sure how hard that would be, of course)
[22:38] <robru> dobey: well the problem with that I'd that i want the first failure reported as early as possible so people can respond to it
[22:39] <robru> I'd have to come up with a regex that ignores statuses that only have some combination of building/built but reports all failures
[22:39] <dobey> well, i mostly ignore the bot anyway
[22:39] <dobey> i should probably just actually /ignore it, so it doesn't even show up for me
[22:39] <robru> dobey: right, it'd be worth paying attention to if it didn't spam constantly ;-)
[22:40] <dobey> well i just pay attention to the PPA page and the requests page
[22:41] <robru> dobey: right but the advantage of the bot is that it's a push notification instead of having to reload the page constantly
[22:42] <robru> Also i personally love the bot because i need to keep an eye on all failures, and investigate ones that are train problems
[22:42] <dobey> robru: implement actual push notifications support, and write a simple app for the phone? :)
[22:43] <robru> dobey: ugh, push notifications ;-) I'd rather use cross platform tech like sending you emails
[22:43] <dobey> robru: there's a W3C proposal for push notifications :)
[22:43] <robru> Ooooh
[22:44] <dobey> of course, i'm sure it's not implemented anywhere useful
[22:45] <robru> I'll add support for w3c push and let the phone adapt to me ;-)