[08:40] <pstolowski> trainguards hello, may i ask for publishing of silo 65? i'm not authorized
[08:40] <sil2100> pstolowski: hey! Let me take a look
[08:41] <sil2100> pstolowski: so this one's autopkgtest failure is known and unrelated, yes? Just confirming
[08:43] <pstolowski> sil2100, yes, known, unstable unity8 tests, there is a fix coming separately https://code.launchpad.net/~aacid/unity8/fix_unstable_phone_stage_tests/+merge/297294
[08:46] <sil2100> pstolowski: ok, on it, reviewing
[08:48] <sil2100> pstolowski: just one thing - is there a bug filled for the flaky tests on arm64?
[08:49] <pstolowski> sil2100, for unity8?
[08:50] <sil2100> pstolowski: no, for ubuntu-system-settings-online-accounts
[08:50] <sil2100> pstolowski: the ubuntu-system-settings-online-accounts there is disabling arm64 unit-testin
[08:52] <pstolowski> sil2100, ah. dunno
[08:52] <pstolowski> mardy, ^ ?
[08:52] <sil2100> mardy: ping
[08:53]  * mardy reads
[08:53] <sil2100> Since now that arm64 is gaining on importance (for xenial), we need to have this tracked at least so that the test don't stay disabled for too long
[08:53] <sil2100> We need an assigned bug for that
[08:53] <mardy> sil2100: yes, there is, let me find it
[08:54] <mardy> sil2100: bug 1585942
[08:54] <sil2100> mardy: excellent, ok, thanks!
[08:54] <sil2100> Let me publish then
[08:56] <pstolowski> sil2100, uh ^
[08:56] <sil2100> pff
[08:58] <sil2100> Oh
[08:58] <sil2100> hm, funny thing
[08:59] <sil2100> WTH
[08:59] <sil2100> pstolowski: ok, so there was an unity-scopes-shell release happening in the meantime
[08:59] <sil2100> pstolowski: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6544174/+listing-archive-extra
[09:00] <sil2100> pstolowski: which means... you'll have to no-change rebuild unity-scopes-shell now :<
[09:00] <sil2100> pstolowski: but I don't think a re-test will be needed
[09:00] <pstolowski> sil2100, ah, ok..
[09:00] <pstolowski> sil2100, yes, it was a no change rebuild for abi break in location service
[09:06] <pstolowski> sil2100, thanks for investigating! btw, when this lands you may want to mention it in your landing emails, as this is a significant change. plus there are a few known bugs surrounding it; you can find more details in the last section of the updates scopes test plan
[09:07] <sil2100> I know, I was already thinking about that when seeing the silo in testing ;)
[09:07] <pstolowski> sil2100, such as mx4 rebooting.. :/
[09:51] <oSoMoN> trainguards: could you please retry https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022334 and https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022337 for me? they depend on a UITK version that hadn’t migrated to -release yet, rebuilding now should make them succeed
[10:09] <robru> oSoMoN: done. you should bump your Build-Depends to point at the new version so that a) they would depwait instead of fail and b) they would auto-retry periodically
[10:09] <oSoMoN> robru, good point
[10:09] <oSoMoN> and thanks for retrying the failed jobs!
[10:09] <robru> oSoMoN: you're welcome!
[10:11] <oSoMoN> robru, ah, the armhf build would need to be retried too, it suffered from the same problem (but it took longer to fail): https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022336
[10:11] <robru> oSoMoN: done
[10:11] <oSoMoN> cheers
[10:11] <robru> you're welcome
[11:01] <oSoMoN> robru, would you mind retrying the 3 failed builds at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+sourcepub/6544262/+listing-archive-extra again? it seems the builds still didn’t pick up the updated UITK, hopefully now they will
[11:02] <robru> oSoMoN: done. which UITK are you hoping for?
[11:02] <oSoMoN> robru, https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.1995+16.10.20160607.1
[11:02] <oSoMoN> it’s been in the release pocket for > 1 hour, I wonder why it wasn’t picked up previously
[11:03] <robru> oSoMoN: well according to LP it was in release just 1 hour ago and I retried those builds 1hr ago so maybe just a bit racy. we'll see this time
[11:04] <oSoMoN> thanks
[12:06] <rvr> mardy: ping
[12:07] <mardy> rvr: pong
[12:07] <rvr> mardy: Silo 39
[12:07] <mardy> rvr: yes?
[12:08] <rvr> mardy: Without an active U1, I tapped on Cut the Rope price button
[12:08] <rvr> mardy: No prompt is displayed, see the logs here https://trello.com/c/dgYXSQVM/3305-1448-ubuntu-landing-039-ubuntu-system-settings-online-accounts-dbarth
[12:09] <rvr> By "active" I mean, there is no U1 account added
[12:10] <mardy> rvr: how did you get that log?
[12:11] <rvr> mardy: dbus.log
[12:11] <mardy> rvr: ah, ok
[12:11] <mardy> rvr: do you have other applications open?
[12:11] <rvr> mardy: Nope
[12:12] <mardy> rvr: looks like a mir issue, can you try killing unity8?
[12:13] <rvr> mardy: Done, let me see
[12:17] <rvr> mardy: Same result
[12:18] <dbarth> rvr: hmm
[12:18] <mardy> rvr: with about the same logs ("Couldn't setup prompt session")?
[12:19] <rvr> mardy: Yes, same logs
[12:19] <mardy> rvr: last thing, can you please try without the silo?
[12:19] <dbarth> i will re-flash my phone in parallel
[12:19] <rvr> Flashing
[12:19] <dbarth> rvr: you're on latest proposed?
[12:21] <rvr> dbarth: Yes
[12:23] <rvr> dbarth: mardy: 65 didn't land when I installed the silo, could be that?
[12:24] <dbarth> rvr: shouldn't be, it's only for the soundcloud fix
[12:24] <dbarth> rvr: you mean the silo with oxide?
[12:25] <rvr> dbarth: Confinement
[12:25] <mardy> rvr: but it still hasn't landed, has it?
[12:25] <rvr> mardy: Yeah, so I ask whether that is needed/related
[12:26] <mardy> rvr: it's not needed, but it could have an impact indeed
[12:26] <mardy> rvr: better test silo 39 without silo 65
[12:30] <rvr> mardy: Same problem with the silo
[12:30] <rvr> Err
[12:30] <rvr> Without
[12:30] <mardy> rvr: that's "good" ;-)
[12:31] <mardy> rvr: looks like some other landing caused that regression
[12:32] <mardy> rvr: I wonder if it's related to bug 1586219
[12:37] <mardy> rvr: how do you want to proceed? Are you trusting that the silo work, or do you want me to remove that branch from the silo, since you cannot effectively test it?
[12:38] <mardy> rvr: or would it be acceptable to test the silo using an older revision of rc-proposed, where you can test this fix?
[12:45] <rvr> mardy: Meeting, will ping you later
[13:16] <rvr> mardy: I have checked OA prompt, and it is displayed in other scopes, so seems the only thing failing is paid apps
[13:16] <rvr> mardy: I think the best way to proceed is to remove the branch, as it cannot be tested properly
[13:24] <mardy> rvr: OK
[13:29] <mardy> dbarth: I need to take https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/unconfined-req-1582824/+merge/295196 out of the silo; could you please ask another silo for it?
[13:31] <mardy> dbarth: or maybe not, I just saw your discussion with rvr in the other channel :-)
[13:31] <mardy> rvr: you decide :-)
[13:41] <dbarth> mardy: quick chat with rvr; we agreed to proceed with the rest of the validation of this silo
[13:41] <rvr> mardy: Just had a quick hangout with dbarth and clarified the test case for the prompt
[13:41] <rvr> Yup
[13:41] <dobey> hmm
[13:45] <rvr> mardy: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592829
[13:47] <dobey> rvr: that is a regression. definitely shouldn't land a silo that is causing that
[13:48] <rvr> dobey: The silo is not causing that
[13:48] <rvr> Another silo introduced the regression
[13:48] <dobey> you're saying this happens in current rc-proposed?
[13:48] <rvr> Yes
[13:50] <dobey> rvr: it's opening the login UI here just fine
[13:50] <dobey> well "fine"
[13:50] <dobey> it's opening it _behind_ the pay-ui window
[13:51] <dobey> which is https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586219
[13:51] <dobey> at least, on my mako that i literally just updated less than an hour ago
[13:52] <dobey> so this does indeed seem like the branch mardy mentioned is likely causing this issue
[13:52] <mardy> dobey: nope, because rvr said that the logs where the same without the silo: the trust session couldn't be created
[13:53] <dobey> mardy: but that doesn't make any sense, because it works fine here; so it seems like perhaps something got left around for the "without the silo" case
[13:54] <dobey> and i can't imagine what else would have already landed and caused this
[13:54] <mardy> dobey: given that it works fine there, could you please install the silo and try if it breaks?
[13:54] <dobey> what silo # is it?
[13:54] <mardy> dobey: silo 39
[13:54]  * rvr flashes again his device
[13:55] <dobey> granted, i have been hitting a very weird issue lately on my mako, when installing silos
[13:55] <dobey> but lets see what happens
[14:01] <dobey> mardy, rvr: hrmm, so after installing the silo it's still the same. login ui opens behind pay-ui "just fine"
[14:01] <dobey> really do wish that bug would be fixed though
[14:04] <mardy> dobey: I'm sure that if unity8 were to be reverted to the last working version, the bug would get fixed in no time :-)
[14:05] <dobey> assuming unity8 is the problem
[14:06] <mardy> dobey: sure, but it looks like the reason for the bug has already being identified
[14:08] <dobey> well anyway, that bug is certainly not introduced in this silo
[14:09] <rvr> mardy: Is it unity8?
[14:10] <dobey> the pop-under issue apparently is
[14:11] <dobey> but that's not what you claim to be hitting here
[14:12] <rvr> 2016-06-15 15:11:24,003 - WARNING - RequestAccess failed: QDBusError("com.ubuntu.OnlineAccountsUi.NoPromptSession", "Could not create a prompt session")
[14:12] <rvr> That is without any silo
[14:12] <dobey> weird
[14:12] <rvr> current build number: 104 device name: turbo channel: ubuntu-touch/rc-proposed/meizu.en
[14:12] <dobey> no idea what is causing that then. definitely not happening on my mako :)
[14:16] <sil2100_> pstolowski: did you rebuild silo 65 in the end?
[14:17] <pstolowski> sil2100_, i'm still waiting for that other change to land
[14:17] <sil2100_> Ah, it didn't migrate yet?
[14:17] <sil2100_> Damn
[14:18] <sil2100_> Tests in progress I see
[14:18] <sil2100_> eh
[14:50] <mardy> dbarth: do you need to push some button for https://requests.ci-train.ubuntu.com/#/ticket/1532 to land? QA approved it this morning
[14:58] <dbarth> mardy: generally not, it all goes automatically after that step
[15:00] <mardy> robru: can you please confirm? I just wonder why it's taking so long ^
[15:28] <dobey> mardy: someone with uplooad privs, like a coredev, has to approve the packaging changes and publish the ticket
[15:43] <rvr> oSoMoN: Silo 68 merge proposals need review and approval.
[15:44] <oSoMoN> rvr, darn, forgot about that, I’ll fix that
[15:45] <oSoMoN> rvr, done
[15:46] <pstolowski> sil2100, hey, can you check again if the migration that's blocking silo 65 isn't stuck or someting?
[16:20] <sil2100> pstolowski: I need to go now for dinner
[16:20] <sil2100> Will try to look later
[16:21] <sil2100> o/
[16:30] <rvr> bschaefer: ping
[16:31] <kenvandine> robru, any magic to get a silo built for a new package that has never been in the archive?
[16:35] <kenvandine> robru, does bileto handle native packages?  maybe it's unhappy by the native package version
[16:38] <bschaefer> rvr, pong
[16:38] <rvr> bschaefer: Hi
[16:38] <bschaefer> hello!
[16:38] <rvr> bschaefer: I'm checking silo 70
[16:38] <rvr> bschaefer: but I don't see any OSK appearing
[16:39] <rvr> bschaefer: Can you give me some info about how to test it?
[16:39] <bschaefer> rvr, you'll need a libertine branch as well
[16:39] <bschaefer> yup
[16:39] <bschaefer> rvr, https://code.launchpad.net/~brandontschaefer/libertine/seed-packages-workaround/+merge/297393
[16:39] <bschaefer> rvr, you've libertine + say gedit open?
[16:40] <bschaefer> rvr, you dont need need that branch since you can install whats needed
[16:40] <rvr> bschaefer: What is needed?
[16:40] <bschaefer> libertine-container-manager install-package -p maliit-inputcontext-gtk3
[16:40] <bschaefer> (for gedit)
[16:40] <bschaefer> if you're doing qt youll need
[16:40] <bschaefer> maliit-framework
[16:40] <rvr> Hmm
[16:41] <bschaefer> annnd maliit-inputcontext-gtk2 (on the container)
[16:41] <bschaefer> rvr, soo i should have been more descriptive, where are you testing this?
[16:41] <rvr> bschaefer: On the tablet
[16:41] <rvr> bschaefer: Using latest rc-proposed
[16:41] <rvr> with the silo installed
[16:42] <bschaefer> o ok, yeah that libertine branch was just approved to auto install those packages on your container
[16:42] <bschaefer> but right now they dont get installed by default
[16:42] <rvr> Hmm
[16:42] <bschaefer> rvr, and you cant use puritine since you cant edit the container
[16:42] <bschaefer> for testing you'll have to make your own container, install gedit
[16:42] <bschaefer> and then install the inputcontext
[16:43] <rvr> bschaefer: as phablet user:  Not using locking for read only lock file /var/lib/dpkg/lock
[16:44] <rvr> bschaefer: As root: Please do not run libertine-container-manager using sudo
[16:44] <bschaefer> rvr, yup thats puritine, its read only
[16:44] <bschaefer> (onces those packages get seeded you'll be OK)
[16:44] <bschaefer> for now to test on a R/W container do:
[16:44]  * bschaefer has to find command :)
[16:45] <bschaefer> ChrisTownsend, if you know off the top of your head ^
[16:46] <bschaefer> libertine_container_manager create -t chroot -s cont
[16:46] <bschaefer> (cont is the name of the container)
[16:46] <bschaefer> rvr, ^
[16:46] <ChrisTownsend> rvr: bschaefer: We need to land libertine first that will add the maliit packages automatically upon container creation.
[16:46] <bschaefer> ChrisTownsend, yeah... but for testing he could create his own container right?
[16:46] <ChrisTownsend> rvr: bschaefer: I'm working on a branch for that landing right this very moment.
[16:46] <bschaefer> o ok that makes things easier
[16:46] <bschaefer> rvr, we can just wait then :)
[16:47] <ChrisTownsend> bschaefer: He could and then manually install the maliit packages.
[16:47] <ChrisTownsend> bschaefer: And then he still needs the title bar workaround.
[16:47] <rvr> ChrisTownsend: Are you using the same silo?
[16:47] <ChrisTownsend> rvr: No, it won't be since libertine is a triple landing.
[16:47] <bschaefer> ChrisTownsend, that seed packages MP
[16:47] <bschaefer> has the toolbar workaround
[16:47] <ChrisTownsend> bschaefer: Right, I meant if he manually did it.
[16:47] <bschaefer> ooo right
[16:47] <bschaefer> yeah
[16:48] <rvr> Ok, then I will block this silo and test both at the same time
[16:48] <rvr> ChrisTownsend: ping me when ready
[16:48] <bschaefer> ChrisTownsend, thanks!
[16:48] <ChrisTownsend> rvr: Ok, sounds like a plan:)
[16:48] <bschaefer> rvr, thanks as well!
[16:48] <kenvandine> robru, i think you can disregard my ping now
[17:13] <ChrisTownsend> robru: Hey, I thought I would point out that https://requests.ci-train.ubuntu.com/#/ticket/1542 says "Ready to build" even though packages are building in the silo.  Not sure if that's a bug or something.
[17:42] <ChrisTownsend> robru: nm
[18:37] <bschaefer> wgrant, hello, im fixing the mir FTBFS issue but not hitting it in my pbuilder
[18:37] <bschaefer> would you be able to test this branch fixes it? https://code.launchpad.net/~brandontschaefer/mir/include-missing-header-0.21/+merge/297485
[19:11] <robru> kenvandine: it should handle native packages as long as it's source format 3
[19:31] <dobey> robru, kenvandine: yeah, native packages work, but you need source/format "3.0 (native)"
[19:33] <kenvandine> thx
[19:37] <bzoltan> robru: how can i build only the gles package of my silo?
[19:37] <bzoltan> robru:  I mean rebuild.
[19:38] <bzoltan> robru: I would need to rebuild only this - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008/+build/10024176
[19:39] <dobey> bzoltan: you have to ping robru or someone with access to upload directly to the PPA, to retry the build.
[19:39] <robru> bzoltan: by asking Ken nicely (I'm EOD in Athens)
[19:40] <bzoltan> kenvandine:  would you be able to help me with this?
[19:41] <kenvandine> sure
[19:41] <bzoltan> kenvandine:  thank you!
[19:42] <kenvandine> hmmm...
[19:42] <kenvandine> oh... nm
[19:42] <bzoltan> I have no idea why, but the unit tests are much more flakier in the silo builds than with the jenkins. I am landing MRs what were tested about 14-16 times before they were siloed. Strange.
[19:42] <kenvandine> bzoltan, rebuild kicked
[19:43] <bzoltan> kenvandine: thanks a lot... I was rebuilding this silo like 4th time and always a different package (out of 12) fails for different magical reason.
[20:25] <ChrisTownsend> rvr: I'm sure you're not around, but https://requests.ci-train.ubuntu.com/#/ticket/1542 is ready to go along with silo 70.  I have instructions in that request including a link to the new Puritine click.
[20:41] <tvoss_> robru, am I good to hit merge on https://requests.ci-train.ubuntu.com/#/ticket/1451
[20:42] <robru> tvoss_: no? It's already landed
[20:44] <tvoss_> robru, ah okay, I'm probably confused by the buttons :)
[20:45] <robru> tvoss_: merging is automatic, only forced in special cases