/srv/irclogs.ubuntu.com/2016/03/30/#ubuntu-ci-eng.txt

lpotter++fqvvx01:05
lpottergeez qtbase takes forever to build...03:33
=== 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
=== faenil_ is now known as faenil
mardycjwatson: hi! Is this normal? https://launchpad.net/~mardy/+archive/ubuntu/phablet/+build/941604809:57
mardycjwatson: seems to be stuck there09:57
cjwatsonmardy: no, I presume a compute node is sad, cancelling and retrying09:58
mardycjwatson: thanks10:01
cjwatsonmardy: (done)10:03
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
tvossrobru, ping11:02
tvossrobru, hey there, I have got a build for platform-api consistently failing for xenial whereas it passes reliably on vivid+o. Would you mind having a look? silo 7411:03
tvosssil2100, ^11:03
sil2100In a moment11:15
Mirvtvoss: all the simbackendtests seem to be failinng on xenial11:31
Mirvtvoss: just use "trainguards" is easiest always, it'll higlight me, sil, robert, and others at times11:31
tvossMirv, yeah, wondering why11:31
tvossMirv, ack11:32
tvossMirv, I'm doing a test build locally in a xenial chroot11:32
tvossMirv, let's see11:32
Mirvtvoss: erm. " Actual: 4-byte object <03-00 00-00>, Expected: core::posix::wait::Result::Status::exited"11:32
tvossMirv, that's a result of the backend not being loadable11:32
Mirvtvoss: it's almost two months since last platform-api landing, this could be something changed in xenial. I've been hit by some, including a glibc bug.11:33
=== chihchun is now known as chihchun_afk
tvossMirv, interesting11:36
tvossMirv, the build used to work fine before, though11:36
tvossMirv, silo has been around for some time and actively rebuilding11:36
Mirvtvoss: I see you had a successful build at 2016-03-22. assuming it's not something you changed in platform-api, it could be something change in xenial since then.11:37
tvossMirv, yup11:38
Mirvtvoss: at least this gcc-5 landing happened during the timeframe http://launchpadlibrarian.net/249840962/gcc-5_5.3.1-12ubuntu4_5.3.1-13ubuntu1.diff.gz11:38
Mirvtvoss: and also the whole glibc 2.21 -> 2.23 upgrade https://launchpad.net/ubuntu/+source/glibc/+changelog that broke a single Qt unit test for me which took some hunting to find the culprit11:39
tvossMirv, ack, I will do a deep dive in a local environment then, thanks for investigating11:40
=== alan_g is now known as alan_g|lunch
=== _salem is now known as salem_
popeyjibel: sil2100 is https://trello.com/c/qnhVyg2j/2936-1095-ubuntu-landing-050-ubuntu-ui-toolkit-bzoltan going to make OTA-10? It's blocking an update to music.12:59
ahayzenpopey, not blocking an update to music, it makes the *current* app startup horrible, eg a regression :-)13:00
=== alan_g|lunch is now known as alan_g
popeyoh, yes, you're right!13:05
popey^ jibel sil2100 :)13:05
jibelpopey, it won't land unless bzoltan cherry picks the fix13:07
popeybzoltan: ^13:07
ahayzenit is this bug specifically https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/155489713:07
ubot5`Launchpad bug 1554897 in ubuntu-ui-toolkit (Ubuntu RTM) "App with dark background flickers temporarily to white at startup" [High,Fix committed]13:07
bzoltanpopey:  what UITK rev do you need?13:08
popeyIt causes a problem for "dark" apps like music and podbird13:08
popeymusic is more adversely affected as it takes a while to load, so it is very noticable.13:09
popeyAlso, being a default app we're breaking.13:09
ahayzenbzoltan, we need this fix https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/fasterWindowColor/+merge/28866113:09
popeyta ahayzen13:09
ahayzenrevision 1895 of staging it landed13:09
bzoltanahayzen:  why now? OTA10 is closing.13:10
ahayzenbecause it has been in the queue for ages sortof expected it to be in ota10 :')13:10
popeyit's a regression in ota-1013:10
ahayzenand when it says "Description of landing: OTA10 landing" ... that sortof leads you to think it'll be in ota10...13:10
bzoltanahayzen: popey: an OTA10 tag helps me to put it on our backlogs13:11
ahayzenyeah this one seems to have missed having the usual canonical-devices thing + a milestone13:13
ahayzeni think it was because it was found from the previous UITK silo while testing that13:14
bzoltanahayzen:  I can start pulling it in.. but it does take time.. only siloing and building takes ate least 24h if we are lucky13:14
ahayzenugh :-/13:14
ahayzenbzoltan, what's the reason that this silo isn't landing through QA? https://trello.com/c/qnhVyg2j/2936-1095-ubuntu-landing-050-ubuntu-ui-toolkit-bzoltan13:14
bzoltanjibel:  how much time we have?13:15
bzoltanahayzen:  That is not the same silo :)13:15
ahayzenit includes that fix? no?13:15
ahayzenthat was the one i was assuming was going to land...13:15
bzoltanahayzen:  it is the next landing and it does include that fix ... but it does include a regression too13:15
=== chihchun_afk is now known as chihchun
ahayzenah !13:15
popeySo, pick your regresion or fix both?13:16
ahayzenheh many options :-)13:16
jibelbzoltan, if you can have a silo with just this fix today it can land for OTA1013:16
bzoltanpopey:  Fixing that silo will take a day13:16
popeySo a cherry pick then?13:17
bzoltanjibel:  today? the Automated Signoff will take a day if not two13:17
popeybzoltan: jibel this is what it looks like - from my phone running rc-proposed http://people.canonical.com/~alan/music.mkv13:26
=== chihchun is now known as chihchun_afk
bzoltanpopey: Confirmed13:28
john-mcaleelyjibel, I believe this device landing is needed for adb. Anything needed for it to be 'ready for qa'?13:34
john-mcaleelyjibel, https://requests.ci-train.ubuntu.com/#/ticket/119713:34
john-mcaleelyI think I'm done with it13:34
bzoltanjibel: popey: the silo35 is chewing on it already13:40
popeyheh, thanks.13:40
bzoltanpopey:  andf here comes the gles parade ... Mirv help me :)13:43
rvrtvoss: morphis: Silo 47 approved13:45
Mirvbzoltan: looks like your previous successful landing did not touch changelog at all https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/applauncher-fixes-gles/+merge/28886113:51
Mirvbzoltan: now it seems the train is increasing the number on every build and if you want to keep the changelog change maybe try .2 next...13:52
tvossrvr, thank you13:56
bzoltanMirv: i am running after an escaping number :) It is not going well14:06
pmcgowansil2100, heya do we need a new custom tarball for mako? seems it hasnt been updated with the apps yet14:18
sil2100pmcgowan: you mean the one in the BQ aquaris channel, yes?14:19
sil2100Let me spin that one quickly14:19
AlbertAtrainguards: could somebody retrigger the arm64+armhf builds in the xenial ppa: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/+packages14:27
sil2100AlbertA: on it14:28
rvrmterry: Hi. How can I check the name set in the wizard?14:28
mterryrvr: you mean to confirm it got set correctly?  "cat /var/lib/extrausers/passwd" should show the new name instead of "Ubuntu"14:29
rvrmterry: Ah, it does, great14:30
mterryrvr: or, if you are on a tablet, the greeter will show your name14:30
mterryrvr: awesome14:30
mterryrvr: that was a surprisingly annoying bug to fix  :)14:31
rvrmterry: Because the image partition is usually ro?14:32
ogra_/var/lib/extrausers/passwd is rw ;)14:32
mterryrvr: well the ro partition was part of it, but there were like 3 things that had to be fixed to get that right.  Each time, I'd be like "got it!" and then it still wouldn't work14:32
ogra_(and adduser respects that with the right options)14:33
mterryogra_: but usermod didn't, had to fix it  :-/  But should be good now14:33
ogra_cant you just use adduser instead of usermod ? i think adduser can modify too14:33
ogra_(academic though ... since you fined it :) )14:34
ogra_*fixed14:34
mterryogra_: well this usage was more like passwd -- wants to try /etc/passwd and fallback to extrausers gracefully.  And AccountsService was driving use of usermod, didn't want to hack/patch it to switch14:36
ogra_passwd needs the --extrausers option14:37
ogra_then it shoudl just ignore /etc/passwd14:37
ogra_(for any write operations)14:37
bzoltanjibel: popey: in the silo50 I have a fix to help the flaky builds on Xenuial. I am not going to port that fix to the silo35, so you need to take the silo35 as it is.. or I keep pushing builds as long as it gets OK. But xenial armhf should not be an issue for you.14:40
jibelbzoltan, okay14:41
mterryogra_: no...  My memory is that adduser has an --extrausers option (because it doens't know where you want to add the new user).  I didn't add that though.  I do remember patching passwd (and now usermod) to fallback to checking extrausers if they can't find the provided user in /etc/passwd and extrausers exists (without any arguments, because the callers of14:41
mterrysuch programs rarely know where the user will be ahead of time)14:41
ogra_hmm, i thought adduser simply hands the option through to passwd14:42
ogra_but i might mis-remember that +14:42
mterryogra_: I dunno.  I didn't add the --extrausers support, not sure how that works14:42
ogra_yeah, that was sergiuens14:42
mterryanyway, it should all work fine now14:43
mterryUntil we find another low-level tool that doesn't know about extrausers :)14:43
ogra_chfn doesnt14:46
* ogra_ has that on the TODO to fix for snappy 14:46
AlbertAsil2100: thanks! is there something up with the arm64 builders? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016/+build/941459015:22
AlbertAI don't see a build log...15:22
sil2100Now that's strange15:23
sil2100cjwatson: hey! Could you take a look what happened with the build AlbertA posted above? ^15:24
sil2100We don't see the build-log for that15:24
cjwatsonthat happens if the builder died catsastrophically.  retry15:24
sil2100ACK15:25
sil2100AlbertA: retried again15:25
cjwatsonI have crappy networking right now and it would take ages to check further15:25
AlbertAcjwatson, sil2100: thanks gentleman :)15:25
AlbertAgentlemen even...15:25
bzoltanpopey: jibel: the  vivid UITK  is there in the silo35.15:40
bzoltanpopey: jibel: the gles amd package is acting up.. i rebuild15:40
=== tvoss is now known as tvoss|dinner
robruMirv: you're looking at the input merge. train generates gles changelog for you: http://bazaar.launchpad.net/~phablet-team/ubuntu-ui-toolkit/gles/revision/11116:22
jibelSaviq, mterry 66 approved16:49
bzoltanjibel: popey: the silo35 is ready for you. i can not flip the approved flag because the xenial armhf failed17:00
bzoltanjibel: but if you want to release it the packages are there17:00
jibelbzoltan, thanks, I'll force the flag17:01
jibelah I cannot if the build failed on one target17:02
jibelbzoltan, this will land as part of silo 50 on xenial?17:03
bzoltanjibel:  the silo50 has other fixes... including the build stability17:04
bzoltanjibel:  not easy to cherry pick :)17:04
jibelbzoltan, yes, I mean silo 35 won't be published to xenial?17:04
bzoltanjibel:  I do not need it on xenial17:04
jibelbzoltan, fine, thanks17:04
bzoltanjibel:  I keep the dual landing because of the version clarity17:05
jibelunderstood, not sure how the publication will work17:05
bzoltanjibel: this change would fix the xenial armhf build http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/revision/1913 But it tcan wait with the next real landing17:07
jibelsil2100, ^ will this work? land only on vivid a dual landing silo?17:08
=== alan_g is now known as alan_g|EOD
Saviqjibel, great, thanks17:15
Saviqmterry, can you publish please https://requests.ci-train.ubuntu.com/#/ticket/118617:15
dobeytrainguards: can someone hit https://autopkgtest.ubuntu.com/request.cgi?release=vivid&arch=armhf&package=unity-scope-click&trigger=unity-scope-click%2F0.1.1%2B15.04.20160330-0ubuntu1&ppa=ci-train-ppa-service%2Fstable-phone-overlay&ppa=ci-train-ppa-service%2Flanding-075 please?18:16
dobeyor kenvandine ^^ :)18:16
mterrySaviq: sorry was at gym, looks like it still needs publishing?18:19
robrudobey: sorry, you need somebody with upload rights, train guards have no power there. maybe mterry ^18:20
dobeywell, sil2100 has the power i guess, but yeah18:21
mterryrobru, dobey: done18:21
dobeythanks mterry18:21
robrudobey: right but that's because he's a core dev and not because he's a train guard18:21
dobeysure18:22
dobeybut a motu would be fine here too; i didn't know if you were motu or not (i guess not) :)18:23
=== boiko_ is now known as boiko
robrudobey: yeah I got nuthin18:30
rvrbzoltan: Hi. Silo 35... I still see the menu bar turning white briefly with silo 35 installed https://private-fileshare.canonical.com/~vrruiz/top-bar-white.mp418:33
rvrbzoltan: Although problem is gone for music app18:33
* mterry feeds queuebot a cookie20:11
=== salem_ is now known as _salem
alecuping trainguards21:32
alecuhi! I can't understand what failed here: https://requests.ci-train.ubuntu.com/#/ticket/120421:32
robrualecu: there's a unity8 autopkgtest failure in xenial.21:33
alecuI see a regression for the autopkgtest for unity8, but the revert in the silo should not be causing that21:33
alecurobru: right...21:33
alecurobru: is there a way to retry?21:34
alecushould I just try rebuilding?21:34
robrualecu: no21:35
robruthat is the worst thing you can do, extremely wasteful21:35
robrualecu: I guess there's some problem with unity8's autopkgtests, I don't really understand it, just ask QA nicely to add your silo to the queue21:36
alecurobru: will do, thanks.21:36
robrualecu: assuming you're ready to release I mean21:36
robruyou're welcome21:36
alecuI guess ToyKeeper is the one to ask in this timezone...21:37
robruyeah I think so21:37
ToyKeeperHmm?21:37
alecurobru: we are ready to release, thanks.21:37
ToyKeeperThe silo bot should pick it up soon and add it to the QA queue.21:38
robruToyKeeper: no because britney is hung up on an unrelated unity8 autopkgtest failure, so the whole thing is marked as "failed" and won't get into the queue on it's own. needs to be poked21:40
ToyKeeperI'd have to double-check, but I think the QA silo bot only cares about the "QA Signoff=Ready" flag.21:40
robruToyKeeper: that's what I'm saying, it won't get to ready because the autopkgtests are failed.21:41
ToyKeeperAh, and there it is.21:41
alecuToyKeeper: yes, it just showed up on the Trello board. Thanks!!!21:41
ToyKeeperEr, [15:38:12] -queuebot/#ubuntu-ci-eng- dobey, https://requests.ci-train.ubuntu.com/#/ticket/1204 QA Signoff: Ready21:41
ToyKeeper^^^ That triggered the trello bot to add it.21:42
robruToyKeeper: uh ok, I don't understand how it approved that considering the glaring unity8 autopkgtest failure, this doesn't make any sense.21:42
ToyKeeperI don't know how it got marked as ready, but that's all the trello bot cares about.  It assumes any other details are handled elsewhere.21:43
ToyKeeperIf a human overrides the other bots and marks it as ready, the QA bot will pick it up.21:44
robruoh the unity8 failure went away *just now*, huh21:45
ToyKeeperAnyway, I moved it to the top of the queue and marked it green.21:46
alecuyay, thanks robru, ToyKeeper!21:48
ToyKeeperI helped break it, so I kinda want to get it fixed quickly...21:49
robrualecu: you're welcome21:49
Saviqrobru, can you please force-merge https://requests.ci-train.ubuntu.com/#/ticket/1186 - we need a follow up packaging thing to unstick those from proposed22:26
Saviqhttps://requests.ci-train.ubuntu.com/#/ticket/1206 would be the follow-up (just packaging changes)22:27
robruSaviq: sure. Sorry about the testsuite thing, i tried backporting dpkg from vivid to trusty to fix this but it fails to compile for no discernable reason. Not sure how to proceed other than migrating the train to xenial, which won't happen for a few months yet.22:32
robruSaviq: pitti was saying it needs to be XS-Testsuite because trusty dpkg doesn't support Testsuite at all.22:33
Saviqrobru, that's fine, we shoulda had it explicit in any case22:34
Saviqrobru, ack, lemme fix22:34
Saviqrobru, well, you could build the source packages in a minimal xenial chroot (I know you don't wanna :))22:35
robruSaviq: i just spent weeks ripping all the chroots out :-P22:36
Saviqrobru, I wanna talk to you about one more thing at some point - how do we share code between train and jenkaas - after all a whole lot of what we need in CI train is doing, too22:37
robruSaviq: what kind of code do you want to share?22:37
Saviqrobru, everything up to (and maybe including) building packages22:38
robruSaviq: i don't understand what that even means. All the train does is build packages.22:38
Saviqrobru, yup ;)22:38
Saviqrobru, fetch code from branches, build source packages, build binary packages, run autopkgtests - that's really the extent of what our jenkins instance is doing22:39
Saviqsome teams have a little more built on top22:40
robruSaviq: train does not build binary packages or run autopkgtests, that's all handled remotely.22:40
robruSaviq: i don't really understand what jenkaas is even doing for you, it sounds like you just want more silos.22:41
Saviqrobru, for one, it's triggered on MP changes22:41
Saviqrobru, for two, we have touch devices to run autopilot tests on in there22:42
Saviqrobru, three - we can build much faster than PPAs by cutting corners (ccache, prepopulated chroots etc.)22:42
Saviqrobru, four - report on MPs22:42
Saviqrobru, five - autolanding22:42
Saviqrobru, six - custom things on top22:42
robruSaviq: yeah I'm not sure what to say. I don't see how they could share any code. I'm in the middle of tearing everything apart, no way I'm ready to handle any sort of stable api that other services could consume.22:42
Saviqrobru, which is why I said we ~"have to talk at some point"22:43
robruSaviq: autolanding is the opposite of what the train does. That merges to trunk when branches are approved, doesn't wait for packages to publish.22:43
Saviqrobru, you don't need to explain the differences to me :)22:44
Saviqrobru, I just mean there's a lot of overlap which I'd really like to get rid of22:44
Saviqnothing that needs to happen any time soon22:44
robruSaviq: there's just a huge and bizarre impedance mismatch here, they're different tools that have different work flows and age only superficially similar.22:44
Saviqrobru, I don't want to take the whole of train and shove it into jenkaas22:45
Saviqrobru, but there are discrete work items that both need to do, and those common bits can arguably be abstracted to benefit both22:46
robruSaviq: it sounds like you want jenkaas to create tickets and trigger builds for you.22:46
robruSaviq: one thing i could consider is making silos auto-rebuild when new commits are detected but i worry that might not quite be what people want, eg rebuilding all conflicting silos when one merges.22:47
Saviqrobru, that was an idea at some point, but the latency of train is too big IMO for the MP level - we need as quick turnaround as possible22:47
Saviqrobru, no, train is good as is - I would just like to share the code that has the same result on both sides22:48
robruSaviq: right, I'm working on reducing the latency, parallelism is coming soon so each build will only take a couple minutes22:48
robruSaviq: OK, well think about specifically what features you'd need because i can't even picture really what bits you're wanting.22:49
Saviqrobru, fetch code, build source packages - that at least22:49
Saviqrobru, later, maybe, dealing with ephemeral PPAs where appropriate22:50
robruHmm22:50
robruOnce that code is even written :-P22:50
Saviqrobru, yup :)22:50
Saviqrobru, in the mean time, would you please be so kind as to review the two unreviewed branches in https://requests.ci-train.ubuntu.com/#/ticket/120622:51
robruSaviq: OK well the new paradigm is that everything is a super simple shell script so i might be able to commit to an api in there and you could just invoke the shell script for the steps you need rather than having to have a full train deployment22:51
Saviqrobru, that's my thinking exactly22:52
Saviqrobru, btw, not sure if you saw my twist to inline gles: https://code.launchpad.net/~unity-team/qtmir/inline-gles-quilt/+merge/29006122:52
robruSaviq: you apparently didn't see my review22:54
robru;-)22:54
Saviqrobru, :)22:54
Saviqjust noticed the wrong sed, too22:54
robruSaviq: nice approach though. I wonder if it might make sense to just make the train do the quilt and then let packages supply their patches. From a security perspective it'd be nicer than running arbitrary scripts.22:58
Saviqrobru, https://code.launchpad.net/~unity-team/qtmir/inline-gles-quilt/+merge/290061/comments/74356022:59
Saviqrobru, I don't see a reason why not - the sed on changelog can be automated, too so23:00
Saviqrobru, one disadvantage would be for people to do it locally23:00
Saviqthey'd need to do the sed manually23:01
robruRight23:02
robruHmm23:02
robruSaviq: maybe write some docs about how you generated the patch in the first place? I find quilt strange and fiddly to work with.23:06
Saviqrobru, oh easy, export QUILT_PATCHES=debian/gles-patches; quilt new convert-to-gles.patch; quilt add debian/*; # do your thing; quilt refresh23:09
Saviqrobru, then, when you want to update: quilt push -af; # fix up; quilt refresh; quilt pop -a23:09
Saviqrobru, but yeah, I'll add something to the branch23:10
Saviqespecially on the "how to update" bit23:10
* Saviq found it frustrating that ~/.quiltrc takes precedence over QUILT_PATCHES to be honest23:11
robruSaviq: maybe I'll leave it as a script since I already have the infrastructure for running hooks, and then if somebody can get away with just having a sed, they're not forced to use quilt at all.23:12
robruSaviq: I should probably decouple this gles stuff from the giant monster branch I'm working on...23:12
Saviqrobru, can you change https://requests.ci-train.ubuntu.com/#/ticket/1206 to QA: N/A? it's only dumb packaging changes23:50
robruSaviq: heh, ok23:51
robruSaviq: why are you dropping the testsuite header from qtmir>23:51

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