[04:52] <marcustomlinson> robru: Hey Rob. Following up from Friday's discussion: https://answers.launchpad.net/launchpad/+question/295413
[04:54] <marcustomlinson> (so LP guys' believe CI Train should be marking no change MPs as Merged when landed)
[04:59] <robru> marcustomlinson: ok, file a bug against lp:bileto pls
[05:00] <marcustomlinson> robru: sure? Not against lp?
[05:03] <marcustomlinson> robru: https://bugs.launchpad.net/bileto/+bug/1594248
[05:03] <ubot5> Launchpad bug 1594248 in Launchpad itself "no-change MPs not marked as Merged when landed" [Undecided,New]
[05:04] <robru> marcustomlinson: mark it against lp:bileto if you want it fixed this decade.
[05:04] <marcustomlinson> robru: ok, sorry man
[05:04] <robru> (they're not going to care about MPs with no commits, it's a weird corner case to them)
[05:04] <robru> marcustomlinson: no worries.
[05:05] <robru> marcustomlinson: I would have thought that when I do the merge commit that would have some record of which branch was merged even when there were no revisions (like a git commit with two parents) but I guess bzr doesn't do that so it would be pretty hard to fix on their end
[05:06] <marcustomlinson> robru: yeah, seems like a fundamental flaw
[05:06] <robru> marcustomlinson: one q though, are you sure you actually want this fixed? Seems to me if no-commit MPs aren't marked as merged you could just re-use them whenever whenever you need a no-change rebuild, rather than making a new one each time
[05:07] <marcustomlinson> robru: well, I can reuse it either way really
[05:08] <marcustomlinson> robru: it just seems wrong that it doesn't merge. I think it technically is a bug, so it should probably be fixed
[05:08] <robru> marcustomlinson: ah, a make-work project, ok :-P
[05:09] <marcustomlinson> robru: but hey, not critical. If you want to put it on the backburner we have the bug to remind us
[05:09] <robru> marcustomlinson: yeah, commented on the bug with some details
=== robru changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? Use JenkaaS: http://bit.ly/jenkins-docs | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known issues: robru vacationing in Athens, forward trainguard requests to kenvandine / tedg.
[05:10] <marcustomlinson> robru: cool, thanks!
[05:10] <robru> marcustomlinson: you're welcome
=== chihchun_afk is now known as chihchun
[09:37] <pstolowski> hi trainguards, can somebody re-trigger autopkg tests in silo 1? (it failed on a flaky unity8 test on one arch)
[10:35] <t1mp> jibel: hello. What do you need for the UITK landing to pass (w.r.t. the red outlines around the telegram-app header)? I have an MR ready, and it will be reviewed and tested, but do you have deadlines for that or is it enough if we tell you that the fixes will land soon?
[10:38] <jibel> t1mp, I'd need a click of telegram with the fix.
[10:39] <jibel> t1mp, no necessarily in the store, but a build to confirm that we will have a fix for this ota
[10:39] <t1mp> jibel: ok, cool. Working on that.
[11:04] <robru> sil2100: lol @ https://requests.ci-train.ubuntu.com/log/1568/build/1/info/
[11:08] <sil2100> robru: yeah, my excellent test run, just make it end gracefuly in such a case! ;)
[11:09] <sil2100> robru: even saying: "Nothing to build man, chill out"
[11:09] <robru> sil2100: you were so excited to try it you just couldn't wait for a real landing ;-)
[11:12] <sil2100> robru: yeah, I saw your e-mail and I was like: "huh, what about manual landings? Lemme check that" and WHAM
[11:12] <t1mp> jibel: I have the click package for telegram-app (thanks cimi!), shall I send it to you by e-mail?
[11:12] <sil2100> robru: ;)
[11:12] <robru> sil2100: oh yeah, manuals will just have to click build first and then upload to the chosen PPA, indeed.
[11:30] <pstolowski> sil2100, hey, can you re-trigger tests in silo 1?
[11:34] <pstolowski> sil2100, hey, can you re-trigger tests in silo 1?
[11:37] <sil2100> pstolowski: sure! Let me try find that request
[11:38] <sil2100> pstolowski: retried
[11:47] <pstolowski> sil2100, ty!
[11:47] <sil2100> yw!
[12:14] <robru> hmmmm
=== sil2100_ is now known as sil2100
[12:37] <jibel> t1mp, ^
[12:42] <t1mp> jibel: great, thank you :)
[13:33] <Saviq> sil2100, hey, you've no commit logs for turbo?
=== chihchun is now known as chihchun_afk
[16:06] <rvr> pstolowski: Silo 65 approved
[16:06] <pstolowski> rvr, great, thanks!
[16:11] <alecu> pstolowski: rvr: yay!
[16:14] <pstolowski> rvr, there is a very similar change to my photos scope, but i think it doesn't go via citrain (it's going to the custom tarball); penk or gary wang should clarify this soon hopefuly
[16:37] <renato___> trainguards, I having problems to assign this silo: https://requests.ci-train.ubuntu.com/#/ticket/1577
[16:37] <renato___> it says invalid URL
[16:37] <renato___> kenvandine, tedg ^^
[16:38] <robru> renato___: just build
[16:38] <renato___> robru, thanks
[16:38] <robru> renato___: I sent an email explaining changes
[16:38] <robru> You're welcome
[16:39] <renato___> sorry I did not see the e-mail, I will re-check
[16:40] <tedg> On-the-fly-assignment is a cool feature.
[16:43] <dobey> tedg: and literally when we start running builds on drones
[16:43] <dobey> and literal, even
[16:45] <robru> renato___: assign button will disappear if you reload
[16:47] <dobey> robru: what about silos that need to manually assign, for manual uploads?
[16:48] <robru> dobey: just run build first then put packages in the PPA after
[16:49] <robru> dobey: basically assign and build are the same now
[16:54] <dobey> ah ok
[17:21] <mterry> sil2100, your ubuntu-touch commitlogs don't seem to be including the debian/changelog contents of late