/srv/irclogs.ubuntu.com/2016/05/23/#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
oSoMoNSaviq, Mirv: ever seen regressions similar to those at http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#webbrowser-app (qmluitests.sh failing at the dh_auto_configure phase, Checking for module 'unity-shell-application=14')?08:28
oSoMoNMirv, and would re-running those tests make them pass (i.e. was it a transient failure)?08:28
MirvoSoMoN: not familiar, maybe there's a real unity8 FTBFS in yakkety at the moment?08:29
SaviqoSoMoN, Mirv, needs a re-run with --all-proposed08:29
Saviqbecause that's old unity8 trying to test with new unity-api08:30
Mirvno such switch in that UI08:30
SaviqMirv, oSoMoN, no - need to ask pitti for that atm08:30
Saviqunless Mirv you got access to snakefruit https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Re-running_tests08:30
oSoMoNMirv, in the meantime, would you mind merging https://requests.ci-train.ubuntu.com/#/ticket/1387 on my behalf? this will allow rebuilding other webbrowser-app silos08:34
* Saviq thinks we should ignore britney results for yakkety for now08:40
Mirvsorry, on hangout08:41
MirvSaviq: no snakefruit08:41
MirvoSoMoN: ok08:42
oSoMoNthanks08:42
Mirvthere might be yakkety Qt build problem now anyway because qtchooser got autosynced 3h ago... I uploaded new qtbase 30mins ago08:42
Saviqpstolowski, ↑↑ Mirv's already on it08:43
pstolowskiSaviq, great, thanks08:43
=== vrruiz_ is now known as rvr
Saviqjibel, I think we need to ignore yakkety britney results for a few days, wdyt?08:44
jibelSaviq, for which packages?08:47
Saviqjibel, well, for one, unity8 won't pass for anyone in yakkety until a new unity8 goes into the release pocket08:48
jibelSaviq, okay then, it seems we don't have a choice08:51
Saviqjibel, https://requests.ci-train.ubuntu.com/#/silo/58 is failed because it's uninstallable on yakkety https://requests.ci-train.ubuntu.com/static/britney/yakkety/landing-058/excuses.html until http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-scopes-shell releases, and that one is waiting for http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-scopes-api08:52
Saviqjibel, so yeah, I'd be obliged if you made silo 58 QA Ready - it's only failed because of the dependency chain08:57
Mirvsil2100: so in short they moved a couple of files from qtbase-opensource-src and qt4-x11 to qtchooser. so now absolutely about everything trying to install Qt 5 or Qt 4 fails due to conflicts since only qtchooser was updated in Ubuntu...09:09
Mirvnew qtbase https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.5.1+dfsg-17ubuntu1 and qt4-x11 are building in archives https://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.7+dfsg-5ubuntu509:09
sil2100:|09:09
jin_davmor2: buddy, thank you09:16
jin_davmor2: I know the ticket is under testing by you09:16
jin_davmor2: anything please let me know, cool!09:16
davmor2jin_: yeap I took it as I knew what it was about :)09:16
davmor2jin_: will do09:16
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== alex-abreu is now known as alex-abreu|off
Saviqsil2100, can you please ♻ http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-scopes-api - it's failed because of Qt being uninstallable but that should be good again now https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.5.1+dfsg-17ubuntu110:25
Saviqhmm or not yet10:26
Saviqneed to wait for the arm builds to complete10:26
sil2100Saviq: oh, ok10:46
Saviqsil2100, you could rerun them now - amd64 and i386 of qt is published now10:48
MirvQt always surprises like today. You start with a plan in the morning and then it gets completely thrown out in favor of something that needs to be done first :)11:24
Mirvon the plus side I managed do to necessary SIM card roulette with my secondary operator and can now officially devote my krilling for development while the necessary SIMs are in my turbo11:25
pstolowskiMirv, any idea about libubuntu-location-service-dev in Y? https://launchpadlibrarian.net/261192027/buildlog_ubuntu-yakkety-s390x.unity-scopes-shell_0.5.7+16.10.20160523.2-0ubuntu1_BUILDING.txt.gz11:25
Saviqpstolowski, at least x86 installs build-dep for u-s-shell fine now11:33
Saviqpstolowski, so I'd say that's temporary11:33
Mirvpstolowski: tested in container, I don't see problem installing it even with yakkety-proposed11:36
SaviqMirv, could be a temporary s390x issue11:37
Saviqsil2100, did you ♻ http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-scopes-api after all?11:38
MirvSaviq: oh, s390x, yes I don't have container for s390x :)11:38
MirvSaviq: pstolowski: uh oh it's waiting for s390x platform-api https://launchpad.net/ubuntu/+source/location-service/3.0.0+16.04.20160405-0ubuntu4/+build/965805111:39
sil2100Saviq: now I did, didn't see your last message ;)11:39
Mirvbut why, err, it's even trying https://launchpad.net/ubuntu/+source/platform-api/3.0.1+16.10.20160523-0ubuntu111:39
SaviqMirv, but papi is waiting for location-service...11:40
Saviqhttps://launchpad.net/ubuntu/+source/platform-api/3.0.1+16.10.20160523-0ubuntu1/+build/979174311:40
Saviqsounds like a circular build dep :-S11:40
Mirvlol11:41
Mirvsil2100: ^11:41
* sil2100 stopped caring about yakkety after being so busy with vivid and xenial11:41
Mirvoh, what a mess, with the Qt thrown into it too11:41
sil2100uh oh11:41
sil2100Ok, just kidding, will look into that later11:42
Mirvsil2100: I can feel you :)11:42
Saviqsil2100, thanks, let's see if that completes - we needed a --all-proposed before, not sure if that sticks11:42
MirvSaviq: well the platform-api FTBFS also in general on all archs, so it would not even help if there wasn't a circular dependency to location...11:43
Mirvhttps://launchpad.net/ubuntu/+source/unity-scopes-shell/0.5.7+16.04.20160505-0ubuntu211:43
SaviqMirv, https://launchpad.net/ubuntu/+source/platform-api/3.0.1+16.10.20160523-0ubuntu1 hmm?11:43
MirvSaviq: oh right sorry I meant the scopes ftbfs11:44
Saviqright, that's new11:44
Mirv"scope-uri.cpp:35:46: error: ‘vector’ does not name a type" etc11:44
* Saviq pings api folk11:45
pstolowskiMirv, on it11:49
pstolowskiMirv, ok to add the fix to existing silo?11:50
Saviqpstolowski, depending on the fix we could maybe skip QA and unblock things quicker11:53
pstolowskiSaviq, ack11:53
Mirvpstolowski: sure12:06
Mirvwhatever suites best12:06
pstolowskiMirv, Saviq her eyou go https://code.launchpad.net/~stolowski/unity-scopes-shell/fix-yakkety-ftbfs/+merge/295459 , build here in Y chroot12:07
pstolowskiMirv, it's a trivial fix.. so yeah let's land directly12:07
Saviqok /me pops a silo12:08
pstolowskik12:08
Saviqjibel, agreed ↑↑ can skip QA?12:09
Saviqit's just new gcc being stricter with includes12:09
kenvandineanyone know why xenial packages are going to the unapproved queue instead of the overlay PPA?12:11
jibelSaviq, +112:12
Saviqkenvandine, because you didn't trio-ify your silo?12:27
Saviqkenvandine, if you had a vivid+xenial silo, it will be a SRU since last week12:28
kenvandineah... i had read that12:28
kenvandinebut didn't catch the part about it being an SRU12:29
abeatosil2100, hey, tarballs generated in the usual places: http://people.canonical.com/~abeato/avila/ubuntu/device_frieza-20160523.0.tar.xz and http://people.canonical.com/~abeato/avila/cooler/ubuntu/device_cooler-20160523.0.tar.xz12:29
kenvandinei manually copied it to yakkety12:29
Mirvkenvandine: what I've done with the remaining dual silos is copy-package the built packages manually to overlay and then the xenial package without binaries to yakkety12:36
kenvandineMirv, that's what i did12:37
kenvandinei just hadn't realized the xenial build would be an SRU, must have missed that part12:37
kenvandineMirv, i took care of it :)12:37
kenvandinethx12:37
Mirvkenvandine: oh right and you'll need manual merge reportedly12:41
kenvandineMirv, done :)12:44
kenvandineugh... yakkety fails to build because of depends12:45
Mirvkenvandine: yes, qtchooser autosynced from Debian in the morning since it doesn't have Ubuntu changes. I've had a "couple" of pings related to that :) I think your armhf might just have missed the publishing of qtbase armhf https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.5.1+dfsg-17ubuntu112:50
Mirvit moved files around so everything Qt 5 or Qt 4 broke12:50
Mirvbecause of conflicting files when installing build deps12:51
kenvandineMirv, ah...12:53
kenvandineMirv, so if i wait a bit and retry i might be good?12:53
SaviqMirv, kenvandine, it's still not in proposed for armhf indeed12:53
Saviq libqt5core5a | 5.5.1+dfsg-16ubuntu11  | yakkety-proposed | armhf12:53
Saviq libqt5core5a | 5.5.1+dfsg-17ubuntu1   | yakkety-proposed | amd64, arm64, i386, powerpc, ppc64el, s390x12:53
Mirvkenvandine: yes12:56
=== _salem is now known as salem_
Mirvpublisher seems slowish, the armhf is still not published while the build was finished >1h ago13:18
rvrkdub: ping13:30
kdubhello rvr13:30
rvrkdub: Hi13:30
rvrkdub: I'm testing silo 6913:30
rvrkdub: There is a problem in frieza. When I launch a X11 app on desktop mode, it only starts when I click the window to set it to full screen mode.13:31
rvrIt only happens with the silo installed13:31
kdubrvr, thanks, sounds like something to fix13:32
jhodappsil2100, ping13:33
rvrkdub: I am failing the silo. Ping me the silo is ready for QA again.13:33
kdubrvr, sure13:33
Saviqkenvandine, Mirv libqt5core5a | 5.5.1+dfsg-17ubuntu1   | yakkety-proposed | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x13:33
kenvandineSaviq, thx!13:34
Saviqmterry, can you please retry this build https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-077/+build/979277013:34
mterrySaviq, done13:34
MirvSaviq: \o/13:37
Saviqmterry, thanks, that will get us just a bit closer to unblocking things (currently waiting to see results from a unity8 --all-proposed run in excuses, should make all the unity8 reds out)13:37
Saviqs/out/go away/13:37
=== chihchun is now known as chihchun_afk
* Saviq cries a little14:04
Trevinhosil2100: hey, since we're stuck in landing unity in yakkety because a s390x build-dep (upstart is  not built there), can we just proceed with a forced landing and then we'll remove unity7 from that arch at all?14:32
Trevinhorobru: (maybe) too ^14:32
sil2100Trevinho: hey! We could consider force-merging that if needed, but from what I heard foundations wanted to have unity7 available on the s390x just-in-case14:40
sil2100But it was a few weeks ago when I heard this14:40
Trevinhosil2100: we were discussing this in -devel with seb128 and pitti, and they agree on removing it14:40
Saviqtrainguards, help please https://requests.ci-train.ubuntu.com/#/ticket/1450 ?14:42
tedgSaviq: Not sure, but is it because your s390 buildx are depwait?14:43
Saviqtedg, it was always depwait on s390x14:43
tedgAh, okay.14:44
* tedg will be curious to see what that error is14:44
sil2100hmm14:44
Saviqit's as if something uploaded to yakkety that the train didn't expect?14:44
Saviqbut it would've complained when building, wouldn't it14:45
SaviqI could IGNORE_VERSIONDESTINATION14:45
Saviqjust not sure I wanna without understanding what the issue is14:46
sil2100Strange, I don't see any uploads14:46
sil2100Let me just check the queue real quick14:46
sil2100No, nothing, hm14:47
sil2100I guess let's ignore dest version, since this seems to be not an issue14:48
Saviqsil2100, will publish with ↑↑ then14:48
sil2100I suppose it's the train getting confused14:48
sil2100Saviq: ACK14:48
Saviqsuccess14:49
Saviqoh well14:49
robruSaviq: sil2100: tedg: manual upload: https://launchpad.net/ubuntu/+source/unity-scopes-shell/0.5.7+16.04.20160505-0ubuntu214:57
Saviqrobru, yeah, but shouldn't the train complain when it was building?14:57
Saviqrobru, that upload is from last week, and that silo was only created a few hours ago14:57
robruSaviq: yeah, it should, hm14:58
robruSaviq: anyway that upload is not on trunk, so that's definitely what it was complaining about.15:00
Saviqrobru, ack15:00
dobeySaviq: doesn't matter how old a manual upload is, if nobody ever noticed and merged the changes back to trunk15:01
Saviqdobey, sure, I just meant that I would've "expected" that error if the upload happened between build and publish15:01
robrusil2100: I'm not sure where you were looking that you didn't see your own upload and realize that's what it was complaining about15:02
Saviqso basically the train should've complained when building (as it usually did in that case) that there's a version in Ubuntu that isn't in trunk15:02
Saviqrobru, is it looking at proposed?15:02
robruSaviq: yes15:02
robruSaviq: yeah I'll have to look why it didn't complain during build, but the publish check is correct15:03
dobeyit never complains during build15:03
robrudobey: no there's definitely a "dest version missing from changelog"check that fails, which is why there's a force option.15:04
dobeythe source packages build and upload to the PPA just fine. but then when a build fails, or the builds are completed, the status will say something about dest version missing from trunk, iirc15:04
dobeyat least, that's my experience15:06
sil2100robru: but it was there when the silo got built, so it's not an unexpected upload IMO15:07
sil2100robru: unexpected upload for me is a situation when you built a silo and then someone uploaded15:07
robrusil2100: well your wrong.15:07
sil2100robru: in this case, the silo was assigned today, and built today15:07
sil2100Probably, I don't give a fuck15:08
dobeyany upload that happened outside the silo is an "unexpected upload" i would think15:08
robrusil2100: and the build did not include the last upload in proposed15:08
robruYes15:08
Saviqrobru, it could mention which upload was unexpected, would be easier to grok what's wrong15:13
robruSaviq: file a bug please15:13
Saviqwill do15:18
Saviqgrr grr how long before it shows up in proposed :/15:37
robruSaviq: 29 minutes ago15:49
Saviqrobru, where?15:53
Saviqnow it's there15:53
robruYeah15:54
Saviqgaah16:07
SaviqMirv,  qdbus : Depends: qtchooser (>= 55-gc9562a1-1~) but it is not going to be installed16:07
Saviq qtchooser : Breaks: libqtcore4 (< 4:4.8.7+dfsg-7~) but 4:4.8.7+dfsg-5ubuntu5 is to be installed16:08
MirvSaviq: yep, qt4 is not fixed yet, including qdbus (vs qdbus-qt5)16:23
MirvSaviq: so this is the real deal for Qt 4 users https://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.7+dfsg-7ubuntu116:24
Mirvshouldn't everything be ported to Qt 5 already though, Qt 4 reached end of support in December :)16:24
dobeymterry, sil2100, kenvandine: can someone restart this test please? https://autopkgtest.ubuntu.com/request.cgi?release=vivid&arch=amd64&package=unity8&trigger=pay-service%2F15.10%2B15.04.20160520-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-05616:52
sil2100dobey: on it16:53
dobeythanks16:53
sil2100hm, I get an error16:53
sil2100Oh, ok16:53
sil2100Now it's good16:53
dobeygreat, thanks16:55
dobeyoh good, at least autopkgtests queue isn't completely insane any more16:55
dobeyi wonder how much longer the molasses migration of yakkety is going to take16:56
sil2100Mirv: looking into why platform-api is not migrating from -proposed right now... looks like the dependency chain somewhere seems to lead to qtchooser17:48
sil2100Mirv: it's just a first look of mine, but it looks like it's not any of our actual newly pushed touch stuff, just the Qt madness you mentioned earlier17:49
jhodappsil2100, does this require an SRU? https://requests.ci-train.ubuntu.com/#/ticket/143617:56
sil2100jhodapp: let me take a look17:56
sil2100hmm, I guess it could but, considering that all our touch packages for xenial are in the xenial-overlay anyway, I guess that would be the best place to start17:57
sil2100jhodapp: just in case, wouldn't this change be good to land to all 3 series?17:58
sil2100jhodapp: like, it looks like it would work on vivid as well17:59
sil2100jhodapp: you wouldn't have to create a separate xenial trunk then, just include it in a normal triple landing silo17:59
sil2100jhodapp: that way the same change would be in xenial and also in the latest devel series, so yakkety17:59
jhodappsil2100, it will merge the package change for all 3 (merged into trunk for qtubuntu-media) but it wouldn't only copy over the package for xenial18:00
sil2100Wouldn't it be better to keep all distros in sync?18:01
jhodappsil2100, but it fails to compile on vivid and yakkety18:01
sil2100hm18:01
jhodappfor arm6418:01
jhodappno platform-api packages for arm64 on those18:01
sil2100Well, it was always failing for arm64 on vivid, right?18:01
jhodappyup18:01
sil2100So releasing this change would have no effect18:01
sil2100But at least all 3 would be in sync18:02
jhodappso just keep it triple landing then?18:02
sil2100Yeah, I would say that's the best option, we don't want to get confused by different versions on different serieses18:02
davmor2sil2100: ha you foolish mortal ;)18:02
jhodappsil2100, cool, I'll do that and then hand over to QA18:02
jhodappdavmor2, does your team have an arm64 device to test on?18:02
sil2100jhodapp: thanks! It should be basically a no-op for QA so not much trouble18:02
jhodappyeah18:03
davmor2sil2100: I have every faith in jhodapp ability to break the universe in new and interesting ways ;)18:03
davmor2jhodapp: nope18:03
jhodappdavmor2, thanks for believing in me!18:03
sil2100;)18:03
jhodappdavmor2, alright18:03
=== boiko_ is now known as boiko
Mirvsil2100: ok. Qt should be fixed now but all migration is now intertwined so lots of autopkgtest kicking would probably needed. I'm on my Meizu now so I won't check at this hour but I will in the morning.19:39
sil2100Mirv: thanks!19:45
sil2100Excellent :)19:45
=== rpadovani_ is now known as rpadovani

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