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

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
Mirvjhodapp: pong04:35
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
bzoltanMirv:  are you doing someting with that silo?10:23
bzoltanMirv:  Ahh, I see your comment.10:30
Mirvbzoltan: that10:55
Mirvbzoltan: I'll click Approved again once it has built, although because of the yakkety s390x problem it's currently not going to QA queue automatically still10:56
Mirvthere must be a boatload of people wanting to fix upstart s390x problem in yakkety10:56
bzoltanMirv:  it did not fail last time I have built the silo... what changed since?10:57
Mirvbzoltan: it built fine this time too https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-029/+packages - but as you know, you had the yakkety excuses problem regarding the auto approval tests10:58
Mirvand that remains unless answering my suggestion on #otherchannel :)10:58
bzoltanMirv:  i see, thanks... is there a way to land that silo anyway?10:59
Mirvbzoltan: by asking qa nicely to get it into their queue, yes. but then it won't migrate from yakkety-proposed to release pocket10:59
Mirvbzoltan: although that wouldn't be a new thing since the current UITK in yakkety-proposed isn't migrating either...11:00
bzoltanMirv:  right11:00
bzoltanjibel:  would you please? Pretty please :)11:00
Mirvjibel: so bzoltan is asking QA Signoff Ready for https://requests.ci-train.ubuntu.com/#/ticket/1443 because of remaining yakkety problems that will be solved .. in time11:01
Mirvright now, as mentioned, no-one probably is jumping to fix upstart s390x11:02
Mirvwell of course unless it's something really easy, there's unrelated upload just done11:03
Mirvanyway, with yakkety there will be some amount of unresolved issues that won't be immediately solved11:03
jibelMirv, bzoltan done11:07
=== _salem is now known as salem_
=== chihchun is now known as chihchun_afk
mardy_Mirv: our tests are failing in Xenial and Yakkety due to a mesa error: https://launchpadlibrarian.net/261581280/buildlog_ubuntu-yakkety-arm64.ubuntu-system-settings-online-accounts_0.7+16.10.20160525.1-0ubuntu1_BUILDING.txt.gz13:57
mardy_Mirv: any idea on what's wrong? They used to pass13:57
Saviqplars, krillin-07 seems gone https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/171/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/console14:03
=== chihchun_afk is now known as chihchun
plarsSaviq: weird, it's getting unauthorized14:18
plarsSaviq: we should not still be seeing that14:18
plarsSaviq: has something changed with the way you deploy it?14:18
plarsSaviq: should be able to recover it, but I don't see how that can happen right now14:20
plarsand none of the other devices seem to be in that state14:21
Saviqplars, no, nothing new14:41
sil2100pstolowski: hey! How far are you guys with silo silo 47?14:42
plarsSaviq: I can try recovering it, but I'm not sure how it could have ended up in that state - or if your job runs recover from lifeboat, then it should also do the same14:42
sil2100pstolowski: I'm asking since I would like to back-port the arm64 enablement from yakkety and I wouldn't want to break your work14:42
Saviqplars, yeah that output is from recover, see 13:08:1314:43
plarslet me try it here14:43
pstolowskisil2100, all built ok, looks ok & approved by me; waiting for autopkg tests to finish14:43
sil2100pstolowski: excellent, I see arm64 binaries are also built now so the change is included - thanks, we'll be waiting for this to land14:45
sil2100:)14:45
=== johnlage_ is now known as johnlage
pstolowskisil2100, the previous run of autpkg tests on yakkety failed on unity8, probably a flaky test but need Saviq to confirm14:46
Saviqpstolowski, got link?14:47
Saviqah 4714:47
Saviqhmm not sure if I can get back to that test14:47
pstolowskiSaviq, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-047/yakkety/i386/u/unity8/20160524_215652@/log.gz14:48
pstolowskiSaviq, FAIL!  : qmltestrunner::Wizard::test_passwdPasscode()14:50
Saviqpstolowski, ah yeah, that's fixed in the u8 released last night14:51
Saviqso the new run will be fine14:51
pstolowskicool14:51
plarsSaviq: it seems to have recovered fine when I tried it - give it a try14:54
Saviqplars, ack, thanks14:54
=== charles_ is now known as charles
charleskenvandine, wrt silo 50, be my guest15:02
kenvandinecharles, someone already published it :)15:07
Mirvmardy_: arm64 Qt switched to OpenGL ES today (same as armhf), looks like fallout from that since you're using mesa software rendering instead of real hardware and maybe not too many people in the world are using arm64 mesa software rendering... you may need to skip the test on arm64 (and we should test on real accelerated hw)15:10
Mirvof course we don't have such phone hw either yet though :)15:11
Mirvmardy_: it might be useful to file against mesa about the issue anyhow15:14
mardy_Mirv: OK, I will15:16
mardy_Mirv: about disabling tests, what's the best way? set DEB_BUILD_OPTIONS=nocheck15:16
mardy_Mirv: set the env variable above at the beginning of debian/rules, depending on the value returned by dpkg-architecture?15:17
Mirvmardy_: see eg http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/debian/rules - lines 10,11,14,23,2915:17
mardy_Mirv: excellent, thanks!15:19
pstolowskisil2100, hmm silo 47 autopkg tests failed, but there are not regressions reported?15:33
pstolowskiMirv, hey, any idea about silo 47? ^15:54
bschaefertrainguards, hello. I need a silo for getting a ppa into vivid + overlay15:58
bschaeferits maliit-framework and maliit-inputcontext-gtk2/315:59
bschaeferppa: https://launchpad.net/~brandontschaefer/+archive/ubuntu/maliit15:59
bschaefertested working on the phone15:59
robrubschaefer: hiya. I guess you need permissions to create the ticket?16:02
bschaeferrobru, i ... think so, since it will require someone here to upload the ppa to the16:02
* bschaefer looks16:02
Mirvpstolowski: vivid dependency problem, but I can't reach my computer to debug more properly right now (I'm outside spending the evening)16:03
bschaeferrobru, i can create a new request16:03
pstolowskiMirv, ah..16:03
robrubschaefer: OK create the request and assign it, I'll copy the package over16:04
Mirvpstolowski: the arm64 enablement is done on xenial/yakkety so I can't really guess what would be causing a vivid problem... maybe that enablement related regardless, from some triple landing16:04
robruJust need some breakfast first, brb16:04
bschaeferrobru, cool, (as do i!) (its being assigned now but taking for ever)16:05
bschaeferrobru, https://requests.ci-train.ubuntu.com/#/ticket/146616:06
bschaeferthanks!16:06
pstolowskirobru, sil2100 can either of you help with silo 47 (see Mirv's comments above)?16:07
Saviqpstolowski, Mirv, on vivid: unity-scope-click/arm64 unsatisfiable Depends: ubuntu-sdk-libs16:09
SaviqNot considered16:09
Saviqpstolowski, you want uitk as a build dep to never build for arm64 if it's not available there16:09
Saviqpstolowski, in the mean time someone needs to delete your vivid arm64 binaries for this to go green16:10
Saviq*or* we need uitk to build for arm64 in vivid overlay16:10
Saviqoh hum16:11
Saviqwhat's ubuntu-sdk-libs? virtual?16:11
Saviqah d'oh16:11
Saviqit's from ubuntu-touch-meta16:12
robrupstolowski: yeah, that ^16:12
robrubschaefer: ok, copied16:13
Saviqpstolowski, ok so to avoid this unity-scope-click needs to B-D on ubuntu-sdk-libs, so it's never built for arm64 unless that is available (and we need to discuss with archive people how to do this, it's been a problem a few times already)16:14
pstolowskiSaviq, ok, preparing MP.. why didn't we see it before in vivid?16:15
robruSaviq: what do you need to know how to do? build-dep on something that has the correct arches sounds like the right solution to me16:15
robrupstolowski: because arm64 has only just been enabled for some packages, apparently16:16
pstolowskiah16:16
bschaeferrobru, awesome thanks!16:23
robrubschaefer: you're welcome16:23
dobeyrobru: why doesn't someone just make the same change to ubuntu-touch-meta in vivid, that was made in yakkety/xenial?16:33
robrudobey: I have no idea. I guess we don't care about arm64 in vivid?16:34
robruwhich would make sense since we're trying to update to xenial16:34
dobeywell, but we aren't updating all devices to xenial16:35
robruungh16:36
dobeyand the frameworks files in ubuntu-sdk-libs are a lie on xenial/yakkety anyway, because the ABI is broken16:38
dobeycest la vie16:38
MirvSaviq: robru: so there is certainly some new vivid-overlay problem that needs to be fixed other than starting to undepend on ubuntu-sdk-libs16:49
robruMirv: undepend? they were talking about adding a dep on that so it'll follow its arches16:50
MirvI'd guess some arm64 enablement targeting xenial/yakkety was triple landed and somehow wonderously causes now a new vivid related problem simply regarding installing the touch packages16:50
Mirvrobru: ah right sorry, now I finally could look into the problem so right this is I guess about pstolowski instead working on arm64 enablement and he has added a new dep on ubuntu-sdk-libs. ok that makes sense and you probably indeed already suggested the correct way to fix it.16:51
MirvI just try to do things in haste when running from place to place but I'm glad it seems relatively clear to you at least :)16:51
Mirvif it seems hard to do vivid only exception for not depending on arm64 meta package, we may still enable ubuntu-sdk-libs for arm64 for these purposes (even though arm64 won't be enabled for real on vivid)16:53
Mirvok I'll really go now, it's better to focus on these things during working hours16:53
robruMirv: goodnight16:56
=== chihchun is now known as chihchun_afk
rvrMirv: Hi18:34
rvrMirv: Silo 918:35
rvrMirv: I killed the music app using the spread. Now, music app stucks after start.18:36
rvrMirv: I have rebooted, but the application remains in the same state after starting it.18:36
rvrMirv: Not sure whether it is related to the silo changes.18:37
rvrmzanetti: ^18:37
rvrThis is the log of music app http://paste.ubuntu.com/16690390/18:37
rvrI manually removed the lock file, and the app works again18:45
rvrIt's documented in the silo card18:45
rvrAnd yes, the silo packages are installed.18:46
dobeyoh, well ubuntu-sdk-libs isn't installable on xenial arm64 either. yay18:47
dobeya bit surprised it does install in y18:48
mzanettirvr, still here?20:17
mzanettiand still in that state?20:17
dobeyrobru: if britney has "old binaries left" listed for the silo autopkgtests, we need to someone to delete those binaries?21:14
robrudobey: yep, what silo?21:14
dobeyrobru: 4721:16
dobeyrobru: click scope arm64 binaries on xenial/vivid21:17
robrudobey: ok, deleted. will take 1-2 hours for britney to notice21:18
dobeyan eternity by any other name21:18
dobeyrobru: thanks21:20
robrudobey: you're welcome!21:20
=== salem_ is now known as _salem
=== johnlage is now known as Cipher
=== Cipher is now known as johnlage_bots
=== johnlage_bots is now known as cipher
=== cipher is now known as Cipher
=== Cipher is now known as johnlage_bots
=== johnlage_bots is now known as Cipher
=== Cipher is now known as johnlage

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