[01:16] <Trevinho> robru: I removed (commented) two MPs but I still get them merged at build time...
[01:16] <Trevinho> robru: also, why build-all now happens also if the packages have been built in the past and there are no new commits?
[01:17] <robru> Trevinho: you talking about https://requests.ci-train.ubuntu.com/#/ticket/1481 ? I don't see any commented MPs
[01:17] <Trevinho> robru: eh, yeah... I've just removed them to try if that was the problem
[01:17] <Trevinho> robru: it included
[01:17] <Trevinho> #https://code.launchpad.net/~smspillaz/compiz/compiz.animationaddon-returns/+merge/295497
[01:17] <Trevinho> #https://code.launchpad.net/~smspillaz/compiz/compiz.animationsjc-returns/+merge/295534
[01:17] <Trevinho> too
[01:17] <robru> Trevinho: the code that checks for commits is stuck back in jenkins for a moment so the new thing that's doing the building doesn't have the ability to check for new commits first. I'll be porting that over next so hopefully this regression doesn't last too long.
[01:18] <robru> Trevinho: compare https://requests.ci-train.ubuntu.com/log/1481/build/8 and https://requests.ci-train.ubuntu.com/log/1481/build/9, they have different MP lists being merged
[01:19] <robru> and #10 too
[01:20] <Trevinho> robru: they do, but the resulting src seemed wrong here (it failed in ppa)
[01:20] <robru> Trevinho: not sure what to tell you, build 9 definitely does not merge any smspillaz branches.
[01:21] <Trevinho> robru: yeah, so it seems, but then check the resulting pkg (and changelog) https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-012/+sourcepub/6479663/+listing-archive-extra
[01:22] <robru> Trevinho: I think you're crazy: https://requests.ci-train.ubuntu.com/#/ticket/1492 https://requests.ci-train.ubuntu.com/log/1492/build/latest
[01:23] <robru> Trevinho: (build fails because there are no uncommented mps so nothing to build)
[01:23] <robru> definitely not including commented MPs
[01:24] <Trevinho> robru: well, I don't know what to say... You can see how build 9 log doesn't mention anything, but the built source has smspillaz stuff in it
[01:25] <robru> Trevinho: that build only has 1 smspillaz in it, are you sure that's not from build 8 which shows one smspillaz? I think maybe you were just too impatient waiting for the packages from build 9.
[01:26] <robru> Trevinho: try putting the branches back with comments and try again
[01:26] <Trevinho> ok, i will... Mine was just an hypothesis though... Since yeah, I could have been too fast.
[01:29] <Trevinho> ok, things seem fine now... Couldn't be something caused by some caching or... I don't know.. I just mentioned this because maybe there was something weird going on. And... Well, I want to make sure I report any oddity
[01:31] <Trevinho> although the thing that build 8 doesn't mention anything in the log, but the generated .deb has a different changelog is weird, isn't it?
[01:58] <robru> Trevinho: yeah, I'm not convinced that the changelog doesn't match the build, I think you're looking at the build from one and the log from another. That code literally iterates over the merges to merge them, builds a dict of authors->commit messages, and then dumps that dict into the changelog. There is no way that something that wasn't merged can get into
[01:58] <robru> the changelog.
[01:59] <Trevinho> robru: ah, ok... well, then ther's something else... because the debian version matched between the two
[01:59] <robru> Trevinho: the only caching would be the log file you're looking at
[02:01] <robru> Trevinho: I think you built them so close together that v...2.1 wasn't even fully accepted into the PPA yet, so build 9 didn't see that to bump the version number. build 8 and 9 are both uploading v...2.1
[02:08] <robru> Trevinho: yeah builds 8 and 9 are literally 66 seconds apart, the new upload from 8 wouldn't have even shown up in the ppa yet, so 9 picked the same version
[02:09] <Trevinho> ok I see the thing then :)
[02:09] <robru> Trevinho: I'll implement a timeout so you have to wait 5 minutes between builds :-P
[02:10] <Trevinho> robru: can't be they be cancelled now?
[02:11] <robru> Trevinho: nah that's not implemented yet, will do that soon
[02:12] <robru> Trevinho: i figured the builds were so fast that you couldn't cancel it anyway;-)
[09:50] <pstolowski> trainguards hey, i started getting http://pastebin.ubuntu.com/16917087/ today in silo 65 and am not sure what happened
[09:52] <sil2100> pstolowski: when trying to build the silo?
[09:52] <pstolowski> sil2100, yes
[09:53] <Mirv> hmm, this is certainly new rollout outputs
[09:54]  * sil2100 really needs to allocate one day of his time to familiarize with the new train bits
[09:54] <pstolowski> we triple-landed last week, so all should be in sync
[09:56] <sil2100> hm, yeah, it looks more like an issue with checking the previous version in the PPA when a rebuild happens
[09:56] <sil2100> ANyway, I see the packages are building anyway?
[09:56] <sil2100> Might be worth filling in a bug for robru to take a look
[10:00] <pstolowski> sil2100, where do i file the bug?
[10:02] <sil2100> pstolowski: I would say http://bugs.launchpad.net/cupstream2distro/
[10:05] <pstolowski> sil2100, https://bugs.launchpad.net/cupstream2distro/+bug/1588265
[14:42] <ChrisTownsend> trainguards: Hi!  Is there anything to be concerned about when it says "Diff missing" for https://requests.ci-train.ubuntu.com/#/ticket/1490 ?
[14:46] <tedg> ChrisTownsend: I'm not certain, but that's been discussed a lot in the backlog.
[14:46] <tedg> ChrisTownsend: I think it's an issue with the upgrade.
[14:46] <ChrisTownsend> tedg: Ok, I'll ignore it for now.
[14:46] <ChrisTownsend> tedg: Thanks
[14:48] <robru> ChrisTownsend: tedg: if you're still working on the silo and anticipate needing to build more, then ignore it, diffs will be generated next time you build. if you don't anticipate any more builds, run the 'diff' job to generate diffs.
[14:49] <ChrisTownsend> robru: Ok, thanks!
[14:49] <robru> ChrisTownsend: you're welcome
[15:03] <ChrisTownsend> robru: I ran the Diff job and https://requests.ci-train.ubuntu.com/#/ticket/1490 still shows missing diffs.  Does it take some time for it to see that I ran the job?
[15:03] <robru> ChrisTownsend: yes, the status is only updated every 15 minutes.
[15:04] <ChrisTownsend> robru: Ok, patience is a virtue, right?;-)
[15:04] <ChrisTownsend> Thanks
[15:04] <robru> ChrisTownsend: also there seems to be some unrelated issue where it sometimes fails to find the diffs, if you see the scrollback there's a huge pile of "diff missing" and then right away they go back to "successfully built" or whatever.
[15:04] <robru> you're welcome
[15:26] <kdub> trainguards, can I get a selective rebuild of a package? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-069/+build/9849658
[15:26] <robru> kdub: on it
[15:26] <kdub> thanks robru !
[15:27] <robru> kdub: done. you're welcome!
[15:27] <kdub> thanks robru, is that something I can do myself and should learn how to do?
[15:27] <robru> kdub: nope, you need special powers for that
[15:27] <robru> kdub: one day I'll write a train feature that allows you to do it but that's a ways off
[15:28] <kdub> robru, ack, just making sure I wasn't being needlessly annoying ^_^
[15:28] <robru> kdub: nope, all good. happy to rebuild when needed
[17:29] <ChrisTownsend> trainguards: Any ideas on why https://requests.ci-train.ubuntu.com/#/ticket/1490 is complaining that https://code.launchpad.net/~townsend/libertine-scope/release-1.2/+merge/296255 has merge conflicts?  I don't see any and doing a local merge works fine.
[17:29] <robru> ChrisTownsend: why are you using the old build job?
[17:30] <ChrisTownsend> robru: Because the new build job didn't rebuild.
[17:30] <ChrisTownsend> robru: Some complaint about PPA/bzr version mismatch (libertine-scope/yakkety)
[17:30] <ChrisTownsend> robru: Which I don't understand what that means.
[17:31] <robru> ChrisTownsend: so what the build job does is builds a source package and pushes one copy of it to a bzr branch on lp, and one copy into the ppa.
[17:31] <robru> ChrisTownsend: then there's a status job that checks that everything's good, but sometimes it finds those are out of sync.
[17:32] <robru> ChrisTownsend: sometimes it means there was a failure to upload to the ppa (unfortunately ppa uploads are async so if they fail we won't know until after the job is done running)
[17:32] <robru> ChrisTownsend: sometimes it just means "wait a minute because the ppa upload is a bit slower than the bzr push"
[17:33] <ChrisTownsend> robru: Ok, that makes sense.  Thanks for explaining that.  So try it again?
[17:33] <robru> ChrisTownsend: maybe just wait? the build log in the new system looks fine to me
[17:35] <robru> ChrisTownsend: ugh, something is goofy here actaully, this doesn't match what's in the ppa http://bazaar.launchpad.net/~ci-train-bot/libertine-scope/libertine-scope-ubuntu-yakkety-landing-072/revision/38#debian/changelog
[17:35] <robru> it doesn't even match it's own commit message, so, uh...
[17:36] <robru> ChrisTownsend: oh hrm, it's not forcing the version number with dch
[17:37] <robru> ChrisTownsend: I guess you saw my email about not using a Commit Message? this is a bug in that
[17:37] <robru> ChrisTownsend: one sec
[17:47] <robru> ChrisTownsend: ok I've pushed a fix, it will take some time to hit production, please try again in 15 minutes.
[17:47] <robru> ChrisTownsend: with the new job
[17:55] <robru> kenvandine: why are you using the old build job
[17:56] <kenvandine> robru, dunno... i just clicked build :)
[17:56] <robru> kenvandine: can you reload the ticket page?  you're apparently using a week-old copy of it (and it's supposed to auto-reload on rollouts, sigh)
[17:57] <robru> kenvandine: you should see a new button "diff" right next to "build" on the new ticket page
[17:57] <kenvandine> i had to shift-reload to get it
[17:57]  * kenvandine hates browsers :)
[17:58] <robru> kenvandine: you got some hardcore caching going on there.
[17:58] <kenvandine> robru, i've even rebooted twice today!
[17:58] <kenvandine> so it's not like an old tab
[17:58] <robru> kenvandine: ok anyway, that build will *probably* be fine, but do be sure not to use jenkins for future builds, I'll take that job away soon
[17:59] <robru> kenvandine: if the new build job does something wrong let me know asap.
[17:59] <robru> kenvandine: right now I'm just ironing out some bugs with changelog generation
[17:59] <kenvandine> robru, will do
[18:01] <robru> ChrisTownsend: you around? I'll run the build for you now
[18:05] <robru> ChrisTownsend: ok, looks good now: http://bazaar.launchpad.net/~ci-train-bot/libertine-scope/libertine-scope-ubuntu-yakkety-landing-072/revision/38#debian/changelog please ask me before using the old job in future, I need to fix whatever is preventing the new job from working.
[18:07] <ChrisTownsend> robru: Sorry, had to take a phone call.
[18:08] <ChrisTownsend> robru: Ok, and sorry for using the old job when I didn't understand what was going on.
[18:10] <ChrisTownsend> robru: And thanks for fixing this!
[18:18] <robru> ChrisTownsend: no worries, the old job is left in place specifically to unblock people who are having trouble with the new job, I just need to know who's using it and why, that's all
[18:18] <robru> ChrisTownsend: feel free to rebuild if you want your name in the changelog instead of mine
[18:22] <dobey> poor jenkins
[21:34] <robru> dobey: any luck getting SSO to force @canonical? I'm seeing some people using gmail addresses for their SSO, and thus that's getting into changelogs.