[00:43] <robru> awesome
[03:13] <veebers> robru: you're not still around are you?
[10:19] <pstolowski> sil2100, hey, can we consider silo 80 for the 9.1 hotfix release?
[10:22] <jibel> pstolowski, no, 9.1 is closed
[10:22] <pstolowski> jibel, ah, ok
[11:35] <greyback> trainguards: hey, can someone please remove the unity8 packages from https://requests.ci-train.ubuntu.com/#/ticket/957 (silo 74)
[11:36] <Mirv> greyback: ok
[11:36] <greyback> Mirv: thanks
[11:36] <Mirv> done
[11:36] <greyback> heers
[11:36] <greyback> +c
[11:36] <sil2100> o/
[11:37] <sil2100> Mirv is fast!
[11:37] <greyback> indeed
[11:41] <Mirv> just lucky, 30mins+ without checking IRC
[11:50] <greyback> darn
[12:15] <Mirv> jibel: the silo 023 has been now been upstream tested for three weeks, could it be moved up in silo testing priority? multiple OTA-10 targetted bugs can't be started to be fixed in UITK before 023 is in.
[12:29] <Saviq> trainguards, Icanhasrebuild of unity8 and qtmir (only amd64, armhf, i386) in here https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-064? thanks
[12:29] <sil2100> Saviq: on it
[12:29] <Saviq> sil2100, owait
[12:29]  * sil2100 owaits
[12:29] <Saviq> sil2100, actually, nowait
[12:30] <Mirv> Saviq: you're making it a bit confusing :)
[12:30] <Saviq> looks like armhf actually waited long enough
[12:30] <Saviq> Mirv, sorry, LP is making me confused ;P
[12:30] <sil2100> Yeah, we can just kick it anyway
[12:30] <sil2100> ;)
[12:30] <Saviq> hiding failed builds because some others are building is ¿?
[12:32] <sil2100> Saviq: ok, I hope I rebuilt all that you needed
[12:34] <Saviq> sil2100, thanks
[12:57] <mardy> trainguards: anyone can help me understand what's wrong here? https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-036/excuses.html
[12:58] <Mirv> mardy: there's nothing wrong in there, that's why https://requests.ci-train.ubuntu.com/#/silo/036 says "Approved" for Automated Signonff
[13:03] <mardy> Mirv: ah, cool, thanks :-)
[13:31] <Saviq> Mirv, hey, we're getting qmenumodel FTBFS (tests, actually) in xenial https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-064/+packages – I've a strong feeling it's a regression somewhere in Xenial, could you please upload no-change qmenumodel rebuilds to https://requests.ci-train.ubuntu.com/#/ticket/1006
[13:33] <rvr> oSoMoN: Hi
[13:34] <oSoMoN> hi rvr
[13:34] <rvr> oSoMoN: I'm testing silo 42
[13:35] <rvr> oSoMoN: I still don't see previews on frieza, either in narrow or wide mode
[13:35] <rvr> oSoMoN: I wait until the page is loaded to open a new tab
[13:35] <oSoMoN> rvr, for previews to be generated, you need to visit the corresponding page at least once, I assume you did that, right?
[13:36] <rvr> oSoMoN: Right
[13:36] <oSoMoN> rvr, so no preview at all, for all top sites?
[13:36] <rvr> oSoMoN: Right
[13:37] <rvr> oSoMoN: In which device did you test the silo?
[13:37] <oSoMoN> rvr, flo and arale
[13:37] <oSoMoN> I received a frieza yesterday, but it’s not operational yet
[13:38] <oSoMoN> rvr, can you confirm the issue on another different device?
[13:38] <rvr> oSoMoN: I'll check in krillin
[13:38] <oSoMoN> thanks
[13:39] <oSoMoN> it would be weird if it was a frieza-specific issue, but that wouldn’t be the first time a new device has specific issues
[13:41] <rvr> oSoMoN: I think so
[13:41] <rvr> oSoMoN: I opened a private bug about that last week
[13:42] <oSoMoN> rvr, haven’t seen it, can you share the link with me?
[13:42] <rvr> oSoMoN: Just checked krillin, and it displays the previews in rc-proposed, without the silo
[13:43] <oSoMoN> rvr, can you check with the silo, just to make double-sure that the silo doesn’t introduce a regression (I don’t think it does, I tested it myself on two devices, but you never know)
[14:02] <oSoMoN> rvr, if the issue is confirmed to be frieza-specific, this shouldn’t prevent the silo from landing
[14:34] <Saviq> trainguards, can someone please source-copy qmenumodel from xenial to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-007, I've a feeling something regressed and causes test failures on arm64
[14:35] <sil2100> Saviq: just the xenial to xenial, yes?
[14:35] <Saviq> sil2100, it can have the same version between xenial and PPA, right?
[14:35] <Saviq> sil2100, and yeah, we only get failures on xenial/arm64
[14:36] <sil2100> hmm, I suppose we'd need to append ~overlay just in case if we're supposed to rebuild it
[14:37] <sil2100> Saviq: wait, so you want to do a rebuild of qmenumodel for release to xenial archives?
[14:38] <sil2100> A no-change rebuild in xenial?
[14:40] <rvr> oSoMoN: Sure
[14:44] <dobey> cjwatson: hi. can i get you to please retry the unity8 autopkgtests triggered by pay-service on vivid for https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-041/excuses.html ?
[14:44] <Mirv> Saviq: yeah sorry busy + phone call + busy, didn't check hilights for a little while
[14:46] <Saviq> mrnw
[14:46] <Saviq> ↑ that was "Mirv, nvm"
[14:46] <Saviq> sil2100, not "for release"
[14:47] <Saviq> sil2100, rather to confirm that it FTBFS because of something that changed in xenial, not because of code changes in qmenumodel itself
[14:47] <sil2100> Saviq: just for testing? Ok, let me copy it with a rebuild tag then, one moment
[14:50] <cjwatson> dobey: sure, done
[14:52] <sil2100> Saviq: should be building soon
[14:53] <Saviq> sil2100, tx
[14:55] <dobey> cjwatson: great, thanks!
[15:39] <rvr> oSoMoN: Approving the silo
[15:51] <Saviq> trainguards, please drop qmenumodel from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-064/+packages thanks!
[15:51] <Mirv> Saviq: ok
[15:51] <sil2100> Wow
[15:51] <sil2100> ;)
[15:54] <Saviq> sil2100, shall we force merge https://requests.ci-train.ubuntu.com/#/ticket/1001 ?
[15:55] <sil2100> Saviq: leave it as is for now
[15:55] <Saviq> sil2100, ack, we might still need stuff in there
[15:55] <sil2100> Saviq: I want the silo to stay in case QA finds some regression in unity8 or any other component
[15:55] <Saviq> yup
[15:55] <sil2100> Would be a nice emergency silo
[15:58] <oSoMoN> rvr, thanks!
[16:06] <oSoMoN> trainguards: can silo 42 be published? the status says there’s new commits and it needs rebuilding, but the one additional commit is highly optional and the silo’s been validated by QA, so I’d rather land it as is
[16:28] <sil2100> oSoMoN: could you revert that commit from the branch? I suppose it's the one from https://code.launchpad.net/~osomon/webbrowser-app/topsites-previews/+merge/285697 , right?
[16:30] <oSoMoN> sil2100, yes, I can revert the change for sure, do you mean you want me to push an extra commit that reverts it, or overwrite the history to remove entirely the last commit?
[16:30] <sil2100> oSoMoN: I think the best way is overwriting it with --overwrite
[16:30] <sil2100> oSoMoN: then LP won't have any issues once the merges are merged
[16:30] <oSoMoN> sil2100, ok, doing that now
[16:30] <sil2100> oSoMoN: thanks! Poke me once it's done and I'll publish
[16:31] <oSoMoN> sil2100, done
[16:33] <sil2100> oSoMoN: hm, let's wait a moment for the status job to kick in
[16:53] <Saviq> robru, I know it's a paper cut, but maybe, if comment has newlines, it should be put on a new line https://requests.ci-train.ubuntu.com/#/ticket/959 ?
[17:44] <robru> train needs to be taken offline briefly for maintenance, anybody working on urgent stuff that can't wait an hour?
[18:15] <salem_> rvr, hey, how is it going with silo 30?
[18:17] <salem_> rvr, just to let you know that this morning boiko and I found an issue with messaging-app on rc-proposed and that's not related to silo 30: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1546094
[18:17] <ubot5`> Launchpad bug 1546094 in messaging-app (Ubuntu) "messaging-app apparmor profile deny reading dconf files" [Undecided,New]
[18:18] <rvr> salem_: I was re-flashing frieza to install the silo
[18:19] <rvr> salem_: Does the bug impact testing?
[18:22] <salem_> rvr, it does now because I changed the test plan to cover that case.
[18:22] <rvr> salem_: Ok
[18:25] <Trevinho> trainguards, any idea why this is failing https://requests.ci-train.ubuntu.com/#/ticket/999?
[18:26] <robru> Trevinho: looking
[18:26] <Trevinho> I dontt see anythig special in the excuses file (https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-040/excuses.html ) a parta a failure on s390x which is quite known
[18:27] <robru> Trevinho: well that's exactly the issue, I'm not sure what you mean by "quite known" but britney thinks it's a problem.
[18:27] <Trevinho> robru: unity has never been built in that arch
[18:27] <Trevinho> robru: so... When it happens with unity itself it just doesn't care about that
[18:27] <Trevinho> robru: since... nux doesn't compile either there
[18:28] <robru> Trevinho: well for some reason britney thinks that you're supposed to build on that arch.
[18:28] <Trevinho> Well, it's all about tests I think
[18:28] <Trevinho> robru: what can be done to teach it?
[18:28] <Trevinho> (or her? :-))
[18:29] <robru> Trevinho: I guess what you'd want to do is adjust your packaging to not build on that arch? strangely the build succeeded on s390x, I guess unity is just a runtime dependency and not a build time dependency?
[18:29] <robru> Trevinho: you should check with people in #ubuntu-release (paste them the link to the excuses file), they'll know better what to do about it.
[18:29] <Trevinho> yeah, it depends for some icons..
[18:29] <Trevinho> ok thanks
[18:30] <robru> Trevinho: what'll probably happen is, if you stop building on that arch, it'll be seen as a regression, so you'll need to get them to delete all the historical builds on that arch to make it go through.
[18:32] <Trevinho> robru: I don't think there have been ever builds on that arch...
[18:33] <robru> Trevinho: says s390x build passed right here: https://launchpad.net/ubuntu/+source/unity-lens-applications/7.1.0+15.10.20151002-0ubuntu1
[18:34] <robru> Trevinho: maybe a better solution than hard-coding not to build on s390x would be to just build-depend on unity so that it doesn't build on the same arches unity doesn't build on
[18:34] <robru> more future-proof that way
[18:37] <robru> Saviq: need help with https://ci-train.ubuntu.com/view/1.%20Build/job/ubuntu-landing-010-1-build/78/consoleFull ?
[18:49] <Saviq> robru, nah, forgot to bump -gles
[18:49] <rvr> salem_: Side panel works, but the message is misleading, as it keeps suggesting to swipe
[18:53] <robru> Saviq: ah ok, just saw the failure
[18:56] <dobey> hmm, seems my silo is still tagged "next milestone" and still being ignored in the qa trello
[18:56] <salem_> rvr, yeah, that might probably need some input from design, since the side panel will also be used on tablets.
[19:05]  * dobey wonders if he should just change it
[19:09] <boiko> rvr: sorry, went for a coffee break, back now, so, the messaging is indeed wrong, good catch
[19:10] <boiko> rvr: can you proceed with the test plan? I can change the string and trigger a rebuild (as it is only a string change it won't invalidate your current tests)
[20:23] <robru> bzoltan_: hey you using the train? we need to take it offline for maybe ~1hr for maintenance
[20:25] <robru> dobey: ^
[20:26] <dobey> robru: well, i was using the train, but launchpad seems to be hella borked
[20:26] <robru> dobey: I saw some timeout issues but seems to be resolved now. what are you seeing?
[20:27] <dobey> oh, is it back now?
[20:27] <robru> dobey: hmmm, seems spotty. there's at least one job where I saw the timeout but then it succeeded on a second try
[20:29] <dobey> ssl connection failures
[20:29] <dobey> anyway
[20:29] <robru> dobey: yeah, let me do some maintenance and then hopefully that'll sort itself out in a bit.
[20:29] <dobey> yeah i was trying to get a silo built
[20:29] <dobey> but anyway
[22:12] <Saviq> robru, train "about to shut down" for over an hour now?
[22:12] <robru> Saviq: yeah, sorry, we're taking it offline for maintenance right now, just a bit distracted with fires.
[22:13] <Saviq> robru, ack, wfm
[22:21] <alecu> hi trainguards: there seems to be a regression in the frameworks installed in the rc-proposed image
[22:22] <alecu> r259 lacks the 15.04.4 frameworks
[22:22] <alecu> r255 has them: http://paste.ubuntu.com/15096536/
[22:22] <alecu> here's 259: http://paste.ubuntu.com/15096526/
[22:31] <alecu> oh, I see: "the necessary features did not
[22:31] <alecu> +    land so its introduction does not make any sense."
[22:32] <robru> alecu: no idea, sorry
[22:33] <alecu> robru: no problem, I think I figured it out.
[22:34] <alecu> I found it in the package's changes file.
[22:39] <popey> ahhh
[22:44] <robru> Saviq: dobey: ok sorry for that interruption, we're back online if you want to do more builds now