/srv/irclogs.ubuntu.com/2016/05/11/#ubuntu-ci-eng.txt

robruBloody hell06:25
=== chihchun_afk is now known as chihchun
Saviqjibel, sil2100, morning, we've got a fix for bug #1578665 - what's the process of getting it in as a blocker fix these days?08:55
ubot5bug 1578665 in qtmir (Ubuntu) "no trust prompt appearing in clock or weather app after images on the 4th of may" [Critical,In progress] https://launchpad.net/bugs/157866508:55
jibelSaviq, it's already in the list08:59
jibelSaviq, now we need a silo with the fix08:59
jibelSaviq, blockers are tagged lt-blocker and targeted to OTA1109:00
sil2100Saviq: just prepare a normal silo, we still didn't snapshot or anything09:03
sil2100So trunk is OTA-1109:03
Saviqack09:06
=== greyback is now known as greyback|away
Mirvmorphis: https://requests.ci-train.ubuntu.com/#/ticket/1351 claims there should be urfkilld in addition to urfkill, but only urfkill is there. is it ok to publish urfkill only?11:29
morphisMirv: ah, package urfkill includes urfkilld binary, so yeah11:30
morphissorry for the mis-wording :-)11:30
Mirvmorphis: ok, I'll fix the train and publish11:30
kdubsil2100, seems ota didn't open yet, would it be possible to copy the packages in silo 31 into silo 69 to unblock mir building and testing?11:34
sil2100kdub: hey! Indeed, ok, let's maybe do it differently - just add a dependency to the PPA on the other silo PPA, this should just work (with a big warning not to forget removing that depenendency)11:34
kdubsil2100, alright, I will remind you to remove the dep, and then rebuild the packages before landing 6911:36
kdubthanks!11:36
sil2100kdub: done - you could try rebuilding I suppose11:43
kdubthanks sil210011:44
=== greyback|away is now known as greyback
=== iahmad is now known as iahmad_
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== marcusto_ is now known as marcustomlinson
=== _salem is now known as salem_
=== chihchun is now known as chihchun_afk
jdstrandsil2100: hi! what is the status of the emulator with xenial overlay?14:44
jdstrandsil2100: actually, I'm curious about vivid too14:45
sil2100jdstrand: hey! We didn't check xenial recently, so not sure14:45
sil2100jdstrand: the vivid emualtor got promoted to stable, at least the one for OTA-10.114:45
sil2100There should be an emulator for OTA-11 as well14:45
jdstrandsil2100: oh nice! :)14:45
sil2100jdstrand: look into the stable/ubuntu channel, you should find it there :)14:46
jdstrandI'll give the xenial one a go and report back14:46
jdstrandhmm, actually I don't know how to generate a xenial image14:50
sil2100jdstrand: use the staging channel14:50
jdstrandsil2100: what channel should I use for xenial emulator?14:50
jdstrandok14:50
jdstrandthanks14:50
sil2100https://system-image.ubuntu.com/ubuntu-touch/staging/ubuntu/ for instance14:50
* jdstrand uses ubuntu-touch/staging/ubuntu14:50
jdstrandperfect, thanks!14:51
sil2100Yeah ;)14:51
sil2100Thanks for looking into that!14:51
jdstrandwell, that was fast14:52
jdstrandDevice generic_x86 not found on server https://system-image.ubuntu.com channel ubuntu-touch/staging/ubuntu14:52
jdstrandI just used: ubuntu-emulator create touch.xenial --arch=i386 --channel=ubuntu-touch/staging/ubuntu --password=000014:53
=== pat_ is now known as pmcgowan
rvrsil2100: Payment screen is still un-translated16:44
rvrsil2100: So I guess my fears where right. Payment screen is not using pay-service as context.16:45
rvrThe pay-service.mo files are in the image and contain the strings.16:46
sil2100rvr: really? We didn't have a new image with the new langpack yet16:56
sil2100rvr: I mean, we had the exports yesterday but I did a langpack run only today in the afternoon16:56
sil2100So in theory the latest image should not have pay-service.mo16:57
sil2100rvr: what image are you using?16:57
sil2100Maybe someone kicked a new one in the meantime..?16:57
rvrOh wait16:57
rvrI was checking my phone with stable16:58
rvrETOOMANYDEVICESINMYDESKTOP16:58
sil2100rvr: ;) If you have a free device for testing, you could try updating the -es langpack from the overlay and check real quick16:58
sil2100This would be faster I suppose than kicking a new image and waiting for it to build16:58
rvrsil2100: Ah, cool, I'll check16:59
sil2100rvr: thanks!16:59
rvrmarcustomlinson: jibel: Silo 56 approved17:04
marcustomlinsonrvr: awesome thanks!17:04
dbarthjibel: o/ silo 76 coming your way with oxide 1.14.8 with security fixes AND a nice DGU bug fix as well17:07
dbarth1.14.8 is a stable release, same as 1.14.7 and previous which have been in use for a while17:08
jdstrandsil2100: ok, trying to test silo 15's xenial packages. I reflashed a mako with staging (xenial) but I can't set the passcode ('Could not set security display hint'), so I can't enable developer mode. I also can't enter a wifi password19:29
jdstrandsil2100: is this known?19:29
jdstrandjibel: ^19:29
sil2100jdstrand: possibly related to the policykit-unity8 landing that happened19:29
sil2100jdstrand: it's a known thing, we had the same regression in vivid but reverted, we're busy with OTA-11 so we didn't work on this in xenial yet19:30
jdstrandsil2100: that is what I was thinking. is there something I can do on the device to undo that? can a flash with a different rev?19:30
sil2100Yeah, let me quickly find you the rev that should be free of this change19:30
jdstrandsil2100: I'm asking cause pmcgowan ask that I try to get bug #1569582 in by friday19:31
ubot5bug 1569582 in Canonical System Image "Add Bluetooth apparmor policy" [High,Confirmed] https://launchpad.net/bugs/156958219:31
jdstrand(for vivid overlay)19:31
sil2100jdstrand: https://system-image.ubuntu.com/ubuntu-touch/staging/ubuntu/mako/version-7.json <- try this version maybe19:31
sil2100The rootfs was built before the seed change happened, so I guess it should be okay19:31
jdstrandbut we obviously need it for xenial, so I prepared those packages, but I can't claim I tested the silo if I haven't done xenial19:32
jdstrandok, thanks19:32
sil2100jdstrand: thanks for looking into that!19:32
sil2100+1 on checking xenial, it's our big thing for the nearest days19:32
jdstrandhrmm, I can't flash cause I don't have adb19:32
* jdstrand wonders if 'passwd' in a terminal will do what I need19:34
* jdstrand is flashing19:35
ToyKeepersil2100, robru: Do you see anything here which would keep it from showing up in the QA queue?  https://requests.ci-train.ubuntu.com/#/ticket/139620:24
sil2100ToyKeeper: automated sign-off20:25
sil2100The autopkgtests are probably still running20:25
ToyKeeperawe seems to be EOD'd but he didn't get it quite far enough for QA before leaving.20:25
* sil2100 goes EOD20:25
ToyKeeper:)20:25
davmor2ToyKeeper: he might of hit the trigger on the silos but then autopackage test not finished their run20:26
robruToyKeeper: yeah you only approved it 20 minutes ago, takes usually an hour for automated signoff to happen, plus however long it takes for the autopkgtests if any20:26
ToyKeeperHe did all his tests then started a rebuild to change the version number, and left.  :(20:27
ToyKeeperI assume those tests still apply, but it caused the ticket status to revert.20:27
ToyKeeperAnyway, thanks.  :)20:28
pat_ToyKeeper, from earlier...20:29
pat_once we finish testing and I kick off the silo rebuild ( to strip the ~testX suffix from the version ),20:29
pat_from awe20:29
pat_I forwarded email20:30
ToyKeeperpat_: That's why I kicked it manually.  :)20:30
pat_excellent20:31
ToyKeeper(wasn't sure what it was waiting on after that though)20:31
ogra_"kicked manually" ... sounds quite contradicting :)20:31
pat_heh20:35
robruToyKeeper: strictly speaking the tes manual testing happens on the binary package and so a rebuild invalidates all the testing, however we don't usually require a complete retest on a simple version number change, just a smoke test to make sure nothing exploded during the build20:39
robruToyKeeper: it's one of those things where, IN THEORY changing the version number can't break anything but in practice builds sometimes fail subtly, so it's best to double check20:40
ToyKeeperogra_: ... kicked pedually?20:40
ToyKeeperrobru: That's why I'm a little grumpy.  Usually it's build-then-test, not test-then-build.20:41
robruToyKeeper: indeed20:42
ToyKeeperOTOH, it's also a blocker which needs to land ASAP.20:42
ToyKeeper... and it looks like it worked.  Krillin standby went back down by 90%.  :)20:43
ogra_ToyKeeper, hah !20:45
pat_ToyKeeper, thats great, my arale has died every night this past week21:00
ToyKeeperpat_: Arale doesn't benefit as much.  Standby should at least double, but it won't go up by 10X like on krillin.21:00
pat_ToyKeeper, still goodness, why so much more on krillin?21:01
ToyKeeper(arale's standby w/ wifi has always been a bit power-hungry)21:01
pat_ah21:01
pat_but I usually got 3-4 days and now not 1 so will see21:01
ToyKeeperSeems to be an upstream kernel issue, I think.  Arale doesn't sleep well with wifi on.21:01
robruToyKeeper: good news: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-077/excuses.html your autopkgtests have started21:30
ToyKeeper:)21:30
=== salem_ is now known as _salem
=== cwayne_ is now known as cwayne
ToyKeeperWow, it really does take a while for the automated parts to run.23:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!