[08:59] <bzoltan> sil2100: robru: may i get a kick on this https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-014/excuses.html
[08:59] <sil2100> bzoltan: looking
[08:59] <sil2100> Oh, that one again
[08:59] <sil2100> Kicked
[09:02] <sil2100> dbarth: hey! This silo needs to be switched to a triple landing and re-built for yakkety: https://requests.ci-train.ubuntu.com/#/ticket/1344
[09:02] <sil2100> dbarth, jibel: ^ I suppose such action shouldn't require any re-testing?
[09:29] <oSoMoN> ubuntu-qa: hi guys, any chance silo 3 will be validated today?
[09:33] <rvr> oSoMoN: Yes
[09:33] <oSoMoN> great!
[09:49] <pstolowski> uh, no silos available..
[09:52] <pstolowski> robru, hey, it would be nice to display a 'no silos avail' message in the Status of the silo, it stays at 'New' if Assign fails
[10:53] <sil2100> dbarth: ping
[11:10] <bzoltan> sil2100:  may I ask for an other kick - https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-014/excuses.html
[11:15] <sil2100> Done o/
[11:17] <bzoltan> sil2100:  thank you, this time the unity8 was acting up :)
[11:55] <dbarth> sil2100: pong
[11:58] <sil2100> dbarth: did you see my message above about the silo?
[12:01] <dbarth> sil2100: hmm, nope, just automated queuebot messages; what's up ?
[12:02] <sil2100> dbarth: so https://requests.ci-train.ubuntu.com/#/ticket/1344 this would need to be converted to a triple-landing silo
[12:02] <sil2100> SInce I can't release it as it is now
[12:02] <sil2100> So changed to a trio-landing and the yakkety packages built (with a re-build)
[12:02] <sil2100> This *shouldn't* require a QA re-test I would expect
[12:07] <dbarth> sil2100: ah ok, i will do the change and rebuild
[12:15] <sil2100> dbarth: thanks
[12:21] <ChrisTownsend> sil2100: Are you able to kick stuck britney jobs?  The i386 job for https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-051/excuses.html has already been re-tried once, so I'm not sure what is going on.
[12:24] <ChrisTownsend> sil2100: Also, when it comes time to land that silo, we will need coordinate deprecating the ubuntu-pocket-desktop metapackage and the -pd channel in general.  We will need to see python3-libertine-chroot in the ubuntu image at that time.  But that landing will remove the libertine-demo package.
[12:24] <ChrisTownsend> /s/see/seed
[12:24] <sil2100> ChrisTownsend: ok, I have powers to re-try, not sure if I can do anything else
[12:25] <ChrisTownsend> sil2100: ok, thanks
[12:25] <ChrisTownsend> sil2100: Also, about -pd, ubuntu-app-launch already pulls in xmir, so that is already in the main ubuntu channel.
[12:25] <sil2100> ChrisTownsend: as for PD - ok, in case I miss the silo landing, could you poke me as well once everything is ready for the ubuntu-pd channel deprecation?
[12:25] <ChrisTownsend> sil2100: Absolutely!
[12:25] <sil2100> Yeah, saw that last time I checked
[12:25] <sil2100> THanks :)
[12:25] <ChrisTownsend> sil2100: k, cool
[12:26] <ChrisTownsend> sil2100: thank you too!
[12:42] <ChrisTownsend> sil2100: Sorry to bother you again, but have you tried to kick https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-051/excuses.html ?  I ask because I have to see it show up in http://autopkgtest.ubuntu.com/running.shtml.
[13:00] <sil2100> ChrisTownsend: I couldn't deal with it myself, didn't manage to find a way of doing that, but pitti re-scheduled it just now
[13:09] <ChrisTownsend> sil2100: Ok, thank you
[13:19] <bzoltan> sil2100:  I am not sure if the previous attempt has finished already or it is a new flakiness -> https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-014/excuses.html
[13:46] <sil2100> bzoltan: *sigh* I would expect it to be a new thing already
[13:46] <sil2100> Let me retry once more
[14:16] <rvr> oSoMoN: ping
[14:17] <oSoMoN> rvr, hey, I just saw your comment on silo 3, testing again, I’m pretty sure it was working for me when I tested with a bt keyboard
[14:17] <rvr> oSoMoN: I also tried with an USB keyboard with the same result
[14:24] <oSoMoN> rvr, just tested on arale with a bt keyboard, and Ctrl+- and Ctrl+0 work, Ctrl++ doesn’t because the + is on the second level of the key (shift), but I suspect that’s a bug somewhere else in the stack
[14:29] <rvr> oSoMoN: With my USB keyboard, none work: +, - and 0
[14:30] <oSoMoN> rvr, and with your bt keyboard?
[14:31] <rvr> oSoMoN: Neither
[14:33] <oSoMoN> rvr, mmm… it would be interesting to see if those shortcuts work in a simple QML scene
[14:33] <oSoMoN> rvr, if I send you a simple test app, can you test in on your device?
[14:33] <rvr> oSoMoN: of course
[14:34] <oSoMoN> rvr, okay, give me a moment, I’ll create that for you
[15:24] <oSoMoN> rvr, it’s taking me longer to create that test app than I expected, but I’m on it
[15:26] <rvr> oSoMoN: Ack
[16:20] <awe> ping trainguards, need some assistance with https://requests.ci-train.ubuntu.com/#/ticket/1462
[16:21] <robru> awe:  hi
[16:21] <awe> hey...  it's me again
[16:21] <awe> ;D
[16:21] <robru> awe: what's up?
[16:21] <awe> I seem to be in a rock in a hard place, whenever it comes to landing NM
[16:22] <awe> so, the silo is marked for triple landing
[16:22] <awe> however I've only uploaded vivid and xenial versions to the silo
[16:22] <awe> for reasons previously described, I can't triple land the same code in all three places
[16:22] <robru> awe: ok
[16:23] <awe> ( and note, this will need to be discussed in the context of our PPA becoming a "generic" stable overlay PPA
[16:23] <awe> but that's another conversation I'll pickup on the UES ml
[16:23] <robru> awe: what?
[16:24] <robru> awe: I'm not sure what you're needing help with but as far as I can see on the ticket, you need to get britney & qa approval, then I can copy those packages into the overlay ppa.
[16:24] <awe> so just trying to figure out how to get britney approval
[16:25] <awe> davmor2 is waiting to test
[16:26] <awe> robru, I wasn't sure whether or not the lack of a y package, would cause the britney approval to stall; also this is one part of the landing process that I don't fully grok
[16:27] <robru> awe: yeah I'm not sure how a missing yakkety package will affect britney. I think it'll just look at yakkety, see there's nothing there, and approve it because it's a no-op.
[16:28] <robru> awe: so the thing about britney is that it iterates over each ticket in series, which is quite slow. last run took an 72 minutes. but that finished 20 minute ago, which means the new run should have picked up your ticket.
[16:28] <awe> davmor2 ^^
[16:28] <robru> awe: davmor2: so at some point in the next 50 minutes it should pop up with a result
[16:29] <awe> ty
[16:29] <davmor2> awesome news
[16:29] <robru> awe: davmor2: however if there are autopkgtests, that means it'll only just have *started* the autopkgtests.
[16:30] <awe> davmor2, guess I should've approved it last night!  That said, I wanted to ensure I had the Y mp submitted first.  hindsight...
[16:30] <robru> awe: davmor2: https://requests.ci-train.ubuntu.com/static/britney/log_20160608_161001.txt here's the log if you want to watch it live, eventually you should see -077 in there.
[16:30] <awe> cool
[16:31] <davmor2> awe: hindsight is always 20/20 vision :)
[16:31] <awe> indeed
[16:33] <bzoltan> sil2100:  I know it is annoying... flaky tests are horrible. Would it be possible to kick only the vivid and yakketi tests?
[16:33] <bzoltan> https://requests.ci-train.ubuntu.com/static/britney/yakkety/landing-014/excuses.html
[16:33] <bzoltan> https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-014/excuses.html
[16:33] <bzoltan> xenial is now clean... and now the other two are acting up
[16:41] <dobey> robru: hrmm, seems like the new build stuff only takes the first line of commit messages now?
[16:41] <robru> dobey: yes, wasn't it always like that?
[16:42] <dobey> i don't think so
[16:42] <robru> dobey: there was a build time option for "TAKE_WHOLE_COMMIT_MESSAGE" but the default thing was to truncate. I guess it truncated at the first blank line rather than just the first line.
[16:43] <robru> dobey: anyway that value gets passed in to dch which forcibly re-wraps it, so passing in multiple lines probably isn't what you want.
[16:43] <robru> or rather, probably won't do what you want
[16:44] <dobey> well what i want/expect is for each line to be a new "* foo" line in the changelog.
[16:44] <robru> dobey: hmmm
[16:44] <dobey> well, non-blank line starting after each newline or something
[16:45] <dobey> not sure how feasilble that is, given the tooling
[16:45] <robru> dobey: well I mean I could iterate over the lines of that field rather than just truncating to the first line, I'm just wondering if your expectations match everybody else's though, that behavior might be quite a surprise to everybody else.
[16:47] <robru> dobey: oh, no, that won't work, because it scans the source branch for linked bugs, and it would have no way to know which linked bug goes with which line of the commit message field. so you'd get "* foo (LP: #1)\n* bar (LP: #1)\n* grill (LP: #1)" in your changelog
[16:48] <dobey> robru: well, it could only add it to the first line or something
[16:48] <robru> dobey: if you're wanting tighter control of how your changelog comes out, you're better off just writing it yourself and leaving the commit message field blank. then it'll use debcommit so the bzr commit message matches what you wrote in the changelog
[16:49] <dobey> robru: on the other hand, there's another issue where if the commit message has (LP: #foo) in it already, train still adds it to the end :)
[16:49] <robru> yeah, so stop writing (LP: #foo) in your commit message field :-P
[16:49] <dobey> well, i didn't
[16:49] <dobey> i just noticed that, when someone else did
[16:50] <dobey> i have long been an advocate of not duplicating that data in the commit message, since bzr has meatadata for storing it in the history
[16:50] <robru> yeah
[16:51] <dobey> oh well
[17:38] <robru> awe: yeah, so autopkgtests are running now https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-077/excuses.html
[17:39] <robru> awe: the blank yakkety result shouldn't interfere with the overall outcome.
[17:40] <awe> thanks robru; been keeping an eye on it too
[17:41] <robru> awe: you're welcome.
[17:42] <robru> awe: sorry if I didn't explain it well before, when I said "you should see a result within 50 minutes", that includes "autopkgtests have started running" as "a result"
[17:42] <robru> awe: not that it would be *completed* within those 50 minutes
[19:55] <robru> heh
[22:18] <jhodapp> robru, koza could use a hand in figuring this issue out with his silo: https://requests.ci-train.ubuntu.com/#/ticket/1376
[22:18] <robru> jhodapp: you mean destination version missing?
[22:18] <robru> jhodapp: or the britney failure?
[22:19] <jhodapp> britney failure
[22:19] <jhodapp> I just gave it a quick glance, so maybe it's something simple
[22:19] <jhodapp> he's newer to the landing process though
[22:19] <robru> jhodapp: so what it's saying there is that the destination version is newer than the silo version.
[22:20] <robru> jhodapp: so this upload was published from a different silo but hasn't merged yet: https://launchpad.net/ubuntu/+source/ubuntu-system-settings/0.4+16.10.20160606-0ubuntu1
[22:20] <robru> jhodapp: you'll need to wait for that to merge and then rebuild
[22:21] <jhodapp> robru, cool thanks, I'll pass along the info
[22:21] <robru> jhodapp: once it merges the silo status will say "needs rebuild due to new commits"
[22:21] <jhodapp> yeah makes sense
[22:21] <jhodapp> thanks robru
[22:21] <robru> jhodapp: you're welcome. yeah here's the ticket that was just published: https://requests.ci-train.ubuntu.com/#/ticket/1507
[22:21] <jhodapp> thanks