[05:10] <robru> apologies for the noise, that should be good now
[08:45] <sil2100> jibel, davmor2, Mirv: I'll most probably have to skip today's morning LT meeting, need to drive my girlfriend to the train station
[08:45] <jibel> sil2100, works for me
[09:02] <Mirv> sil2100: ok
[09:48] <pstolowski> sil2100, hey, any idea why silo 24 suddenyl fails on libunity-scopes-dev >=1.0.1 dependency in xenial (which has 1.0.2)?
[09:50] <pstolowski> sil2100, same problem with silo 54
[09:54] <pstolowski> sil2100, uh, and similar issue in silo 45, but there it fails on libunity-scopes-dev (>= 0.6.16)
[09:54] <pstolowski> sil2100, all that built fine last Friday and we haven't landed anything since
[10:12] <Saviq> trainguards, is that a known issue? http://pastebin.ubuntu.com/14992475/ silos can't install ofono so e.g. unity8 builds fail
[10:13] <Saviq> not sure what changed recently, but doesn't seem like it's ofono, rather something that ofono uses in its postinst scripts
[10:15] <Mirv> Saviq: that somehow looks familiar (maybe from some autopkgtests), but no it's not known as in having an idea what causes it
[10:16] <Saviq> Mirv, yeah I think I saw it somewhere before, too
[10:16] <pstolowski> Mirv, hey, any idea about the issues i asked above?
[10:17] <Saviq> hmm I wonder where is ofono's code on LP :/
[10:18] <robru> Saviq: is that log from ci-train.ubuntu.com or from the PPA build log?
[10:18] <Saviq> robru, PPA
[10:19] <Saviq> robru, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-057/+sourcepub/6052290/+listing-archive-extra
[10:19] <robru> Saviq: hmmmmm dunno then. could be an issue in the buildds
[10:21] <Mirv> pstolowski: hmm, no, I just managed to install libunity-scopes-dev fine on xenial-proposed myself
[10:21] <Saviq> Mirv, robru https://launchpad.net/ubuntu/+source/init-system-helpers
[10:21] <Mirv> pstolowski: I was thinking something would have been broken in proposed
[10:22] <Mirv> pstolowski: hmm W: The repository 'file:/«BUILDDIR»/resolver-xuZgwz/apt_archive ./ Release' is not signed.
[10:23] <Mirv> maybe that's nothing
[10:24] <Mirv> also sudo apt-get build-dep unity-scopes-shell works fine on xenial-proposed
[10:26] <pete-woods> hi folks, I'm looking for some assistance in landing (https://code.launchpad.net/~pete-woods/ubuntu/xenial/libgcrypt20/disable-arm-asm-rijndael) into xenial+vivid overlay. it's not a train-managed package, so I don't know how to land it
[10:27] <pete-woods> it seems to upset citrain when I tried to use that
[10:28] <pstolowski> Mirv, yes, that's weird
[10:28] <Mirv> pete-woods: get a silo with it in Source package names, run 'bzr bd -S -- sa' and put the resulting files into your private-fileshare for a trainguard to fetch them
[10:34] <pete-woods> Mirv: thanks, will get on with that :)
[10:43] <pete-woods> Mirv: https://requests.ci-train.ubuntu.com/#/ticket/978 does that look about right?
[10:44] <Mirv> pete-woods: well I don't remember how the manual download url:s work :) morphis always just gave me an url and I downloaded them myself from there. otherwise looks good if you have both xenial and vivid patches source.
[10:45] <pete-woods> Mirv: right, so I need to create separate source build for xenial and vivid then?
[10:45] <pete-woods> will also get on with that
[10:45] <Mirv> pete-woods: the changelog entry needs to have "vivid" or "xenial" instead of UNRELEASED. and probably based on a different release for both, as xenial has 1.6.4-5 and vivid 1.6.2-4ubuntu2
[10:46] <Mirv> pete-woods: yes. and since xenial is a direct sync from Debian, run 'update-maintainer' tool from ubuntu-dev-tools
[10:47] <pete-woods> Mirv: okay, will fix all that, too (manual release noob here) :)
[11:21] <pete-woods> Mirv: okay, I've updated that silo to just be for vivid for the moment (as I don't know if the xenial version is broken anyway), and I *think* I've got all the packaging correct now
[11:29] <Mirv> pete-woods: does it build? :)
[11:30] <Mirv> pete-woods: let's try assigning
[11:30] <Mirv> let's try building
[11:30] <pete-woods> Mirv: okay, pretty sure it builds locally (I've tried it on the phone)
[11:30] <Mirv> pete-woods: yeah, just the manual download url thing
[11:30] <pete-woods> ah, right
[11:31] <pete-woods> yeah, I've just stuffed all the source build stuff in there
[11:31] <pete-woods> hopefully that's what it wants?
[11:31] <Mirv> pete-woods: I'll just grab them and upload like I usually do
[11:31] <Mirv> since the build did not work out
[11:31] <pete-woods> ah
[11:35] <Mirv> pete-woods: the train generated diff looks good to me https://ci-train.ubuntu.com/job/ubuntu-landing-070-1-build/lastSuccessfulBuild/artifact/libgcrypt20_vivid_content.diff
[11:36] <pete-woods> Mirv: yeah, looks reasonable to me :)
[12:07] <Saviq> trainguards, can you please retry the failed unity8 builds in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-057 - https://launchpad.net/ubuntu/+source/init-system-helpers/1.28ubuntu2 is there to fix the issue
[12:07] <sil2100> Saviq: on it
[12:10] <sil2100> Should be rebuilding
[12:14] <Mirv> sil2100: do you have any ideas regarding pstolowski's issue?
[12:15] <sil2100> Mirv: let me take a look at the backlog to get some context
[12:15] <Saviq> sil2100, crap, too early ;)
[12:16] <Mirv> Saviq: I can do it now
[12:16] <sil2100> Saviq: didn't build yet?
[12:16] <sil2100> ;)
[12:16] <Saviq> sil2100, it did build, but didn't get to ftpmaster yet
[12:17] <Saviq> let's see if Mirv has better luck ;)
[12:17] <Mirv> Saviq: there might be delay of 10-20 mins even
[12:17] <Mirv> restarted amd64 now
[12:19] <Mirv> Saviq: any idea about these unity8 autopkgtests failures, do they require something from you? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-023/xenial/amd64/u/unity8/20160208_100006@/log.gz
[12:19] <sil2100> Mirv, pstolowski: let me investigate those two silos issue
[12:21] <Saviq> Mirv, never saw those, what's the trigger?
[12:22] <Mirv> Saviq: my qtdeclarative silo (that changes alt-tab behavior so nothing related) https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-023/excuses.html
[12:22] <pstolowski> sil2100, Mirv thanks
[12:23] <Saviq> Mirv, owait, when there's a FAIL, that we know - silo 57 will fix a flaky test (you can grep for "fail!", if it's tst_LazyImage, a retry will help)
[12:24] <Saviq> Mirv, but dependency issues look more real
[12:24] <Saviq> Mirv, and armhf not stable yet (hence Always failed)
[12:25] <Saviq> Mirv, it's weird that it's only -gles that triggers the dependency issues
[12:25] <Saviq> the non-gles show our flaky test (sorries)
[12:26] <Mirv> Saviq: right, ok. not sure what's the gles then about.
[12:27] <Saviq> Mirv, I can't even parse the pkgProblemResolver output...
[13:23] <sil2100> Interresting
[13:30] <Mirv> Saviq: ok rerun got https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-023/excuses.html to fail the test also on gles, but the flakiness seems pretty persistent since both archs triggered by both packages are failing with LazyImage::test_lazyimage(Unbound Wide)
[13:36] <sil2100> pstolowski: found the reason
[13:36] <pstolowski> sil2100, oh, what is that?
[13:36] <sil2100> pstolowski: sorry it took so long but had a different firefight
[13:37] <pstolowski> np
[13:37] <sil2100> pstolowski: so, basically nothing wrong on your side, but some action is required - you'll have to do a no-change rebuild of unity-scopes-api for 24 at least (didn't check the other silo but it might be the same case)
[13:38] <sil2100> pstolowski: someone synced libjsoncpp from Debian, it's stuck in -proposed now
[13:38] <pstolowski> sil2100, ah
[13:38] <sil2100> pstolowski: this introduced libjsoncpp1 while -api is still depping on libjsoncpp0v5
[13:40] <Mirv> sil2100: weird that I didn't see any install problems on xenial-proposed
[13:40] <Mirv> sil2100: thanks for looking into it!
[13:41] <sil2100> Mirv: I tried using chdist but actually couldn't reliably reproduce it ther
[13:41] <sil2100> *there
[13:41] <sil2100> But on the chroot I was able to see the issue
[13:42] <sil2100> pstolowski: anyway, I suppose a no-change rebuild would help - really bad practice for anyone that did the sync from Debian though, he should have taken care of the no-change rebuilds himself
[13:43] <pstolowski> sil2100, ok, trying. thanks for investigating!
[13:43] <sil2100> pstolowski: for 45 it seems to be the same case, so once you release one silo it should be good - we could of course simply dput a no-change rebuild straight into the archive if you want
[13:43] <pstolowski> sil2100, ack
[13:44] <sil2100> pstolowski: so just poke me if you want that no-change upload and I'll do it
[13:45] <Saviq> Mirv, yeah, sorry about that, I'm just about to test silo with the fix
[13:45] <pstolowski> sil2100, ok
[13:49] <Mirv> Saviq: the problem is it's preventing my silo from getting to QA queue and me being able to start on the next OTA-10 landing. although as soon as the "running" results would be complete otherwise, I'll reping QA if they could take it into queue manually
[13:51] <Mirv> sil2100: you'll need to blame Mr. Robot since the package doesn't have Ubuntu changes so was auto-synced
[13:51] <sil2100> Bad mr Robot
[13:56] <Saviq> Mirv, you can ask jibel to force it QA ready
[13:56] <Saviq> referring to our MP for this
[13:58] <Mirv> jibel: davmor2: yes so I asked for getting it into Trello last week too, but could you get https://requests.ci-train.ubuntu.com/#/ticket/944 manually to the queue? it was already passing once, now unity8 test fails because of what Saviq says. https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-023/excuses.html is the full results, see also overrides for all the other known failures.
[13:59] <Mirv> I'm not really sure why it's rerunning tests again though, but they were green before and nothing has changed in the silo.
[14:00] <Saviq> trainguards, noticed that landing descriptions disappeared?
[14:00] <Mirv> jibel: davmor2: what I mean "it was passing" was that it was passing last week but the overrides were not supported. now I got that bug fixed via Robert ad pitti, but now unity8 started failing and some reruns seem possibly stuck. but if the autopkgtest fixes would have been in last week, the silo would be in Trello automatically
[14:00] <Mirv> Saviq: not for me? in bileto?
[14:01] <Saviq> Mirv, yeah
[14:01] <Saviq> Mirv, can you see a desc here https://requests.ci-train.ubuntu.com/#/ticket/963 ?
[14:01] <Mirv> Saviq: probably something in the contents of your 963
[14:01] <Saviq> Mirv, same in https://requests.ci-train.ubuntu.com/#/ticket/938
[14:01] <Mirv> Saviq: you're probably throwing robru's sanitizer into troubles :)
[14:01] <Saviq> both were working before
[14:02] <Saviq> Mirv, yeah looks like it
[14:02] <Mirv> it's not the #:s
[14:02] <Mirv> hard to think of anything else
[14:02] <Mirv> Saviq: correction, it is probably the #:s, now shown at https://requests.ci-train.ubuntu.com/#/ticket/938
[14:03] <Saviq> Mirv, well, yeah, but no links :P
[14:03] <Mirv> Saviq: yeah.
[14:03] <Mirv> robru: if description has #:s (like bug #1541388), the description isn't shown anymore on the bileto page
[14:03] <ubot5`> bug 1541388 in qtmir (Ubuntu) "Icons in launcher sometimes refuse to launch application" [Critical,In progress] https://launchpad.net/bugs/1541388
[14:03] <Saviq> robru!!
[14:04] <davmor2> Mirv: Of course it's Saviq s fault I should of known :P
[14:39] <rvr> charles: Hi
[14:39] <rvr> charles: On silo 12, tapping on "Location settings" opens and closes System Settings.
[14:41] <charles> rvr, hi!
[14:43] <charles> rvr, I think silo 12 is not ready for QA yet on the 'System settings' issue, it needs a system-settings patch from jgdx who is handling the systems-settings component of this bug.
[14:44] <rvr> charles: Err
[14:45] <rvr> charles: It appeared in the QA queue
[14:45] <rvr> charles: Anyway, it's clear that is not  ready. I'll wait for it :)
[14:46] <charles> rvr, I think that's my error, QA was not doing testing the silo when another indicator-location bug for OTA 10 came along so I reused the silo. I should have used a second silo or noted in the QA card
[15:34] <pstolowski> sil2100, uh, unfortunately unity-scopes-api fails on our ABI check now with the no-change rebuild in xenial :(
[15:35] <sil2100> pstolowski: uh oh, oh noes
[15:35] <sil2100> Eh, we'll have to update those as well, looks like the jsoncpp ABI changes leak to the scopes-api...
[16:27] <rvr> popey: Is popey.mooo.com down?
[16:27] <popey> rvr: what IP do you get for it?
[16:27] <popey> (it could be dynamic dns not updating)
[16:28] <rvr> popey: popey.mooo.com has address 82.16.62.66
[16:28] <popey> ok, ah, I know, I had to update my router, and lost all the port forwarding
[16:28] <popey> lemme fix
[16:40] <rvr> popey: Thanks :)
[16:40] <popey> np
[16:41] <rvr> popey: There is a test that requires to download an older version and it uses your archives
[16:43] <popey> haha
[16:45] <popey> rvr: perhaps that test could be modified to have a copy of the click on people.canonical.com or something, in case my thing is down :)
[16:46] <rvr> popey: No, no, no... you must available 24/7 and send warnings for maintenance with 48H of prior notice ;D
[16:47] <ogra_> and describe the length of the outage window in minutes !
[16:49] <popey> :)
[17:53] <jdstrand> sil2100: hey, how can I verify that libxml2, bind9 and curl are in the candidate images? I know you said that it shouldn't be a problem, but I'd like to verify since they aren't in stable-snapshot
[18:35] <sil2100> jdstrand: hey! We don't really have a solid candidate image besides rc-proposed, which uses those packages from -updates and -security
[18:35] <sil2100> jdstrand: OTA-9.5 development is currently basically rc-proposed ;)
[18:36] <jdstrand> sil2100: ok. I thought that rc-proposed was going to be ota 10 and 9.5 something different
[18:36] <jdstrand> sil2100: in that case, I can just check the changes files
[18:36] <sil2100> jdstrand: yes, basically it will, but currently not yet - all fixes in the overlay-ppa are OTA-9.5 wanted ;)
[18:38] <sil2100> jdstrand: but since we had one OTA-9.5-wannabe-rc image built from the snapshot, I removed bind9, xml2 and curl packages from the snapshot so that it pulls them from the archive
[18:38] <sil2100> So even for the case when we decide to switch to snapshot building, we're safe ;)
[18:52] <sil2100> slangasek, robru: we have the internal meeting today?
[18:52] <robru> sil2100: I guess so
[18:53] <sil2100> Ok, good, since in the e-mail you said you'll be on IRC, didn't know if you'll be working normally
[18:56] <slangasek> ah
[18:56] <slangasek> robru: why are you coming in for a meeting on your day off? :)
[18:56] <robru> slangasek: well we missed it last week
[18:56] <robru> also I'm putting out fires
[18:56] <robru> so i'm here anyway
[19:01] <ChrisTownsend> How long does it take for autopkg tests to queue up after I approve the lander signoff?  I approved https://requests.ci-train.ubuntu.com/#/ticket/982 well over an hour ago and I still don't see it in http://autopkgtest.ubuntu.com/running.shtml.
[19:01] <ChrisTownsend> trainguards ^^^^
[19:02] <robru> ChrisTownsend: in meeting, sorry
[19:02] <ChrisTownsend> robru: Ok, no worries.  Just not sure if something is stuck.
[19:05] <robru> ChrisTownsend: oh god there's been an explosion of silos which means britney now takes an hour to run instead of half an hour, so yeah, it'll get picked up in the next run
[19:05] <ChrisTownsend> robru: Oh, ok.  That explains it.  Thanks
[19:36] <dobey> ci train must not like releasing locks
[19:47] <robru> dobey: that doesn't explain why this is the only branch in the history of ever to ever have this problem
[19:47] <robru> dobey: also I force-broke the lock and it's still doing this
[19:48] <robru> dobey: also you can reproduce this locally: bzr missing --show-ids --directory lp:~didrocks/unity/dep-session-shorcuts lp:unity --theirs-only
[19:48] <dobey> oh
[19:48] <robru> dobey: so not really a train issue at all, but I'm trying to work around it
[19:48] <dobey> has didrocks tried to force-break the lock?
[19:49] <robru> dobey: no I didn't contact him
[19:49] <robru> dobey: although the weird this is if you actually run the command, it works in spite of not being able to get the lock. train is just exploding because it sees stderr, doesn't notice that stdout has stuff in it
[19:51] <dobey> fun
[19:51] <robru> dobey: also this only happens if you say --theirs-only
[19:52] <robru> https://www.irccloud.com/pastebin/3mhyYiQB/
[19:53] <dobey> hmm
[21:17] <Trevinho> dobey: yes he tried to break the lock
[21:18] <Trevinho> dobey: but that was a broken lightweight branch that , well caused some troubles to lp:unity too
[21:18] <dobey> oh
[21:19] <dobey> robru: that same command gets run on all MP branches in silos?
[21:30] <robru> dobey: yep, every 15 minutes the train runs 'bzr missing' on all branches in all silos, looking for new commits
[21:31] <robru> dobey: as a workaround I made it just ignore stderr when stdout has some value and it seems to be working. there were a few other cases also where bzr was having some non-fatal error on stderr that the train was treating as fatal
[21:32] <dobey> robru: yeah, it should be checking the exit code anyway
[21:33] <dobey> treating possibly normal output as fatal errors is dumb :)
[21:34] <robru> dobey: well when originally written it wasn't anticipated that 'bzr missing' command would output anything to stderr during a success.
[21:37] <Saviq> jibel, did you not pick up silo 57 yet? can't see it in QA trello?
[21:43] <jibel> Saviq, is it ready?
[21:44] <Saviq> jibel, yeah, I thought we cleared up the Regressions situation earlier - anyway we've restarted the only remaining regression so we should get a PASS from britney on it soon
[21:45] <robru> Saviq: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-057/excuses.html regression
[21:45] <robru> oh ok nm
[21:45] <robru> heh
[21:45] <Saviq> robru, ;)
[21:45]  * robru reads good
[21:45] <Saviq> bug #1532358
[21:45] <ubot5`> bug 1532358 in unity-scope-click (Ubuntu) "flaky autopkgtests cause migration issues" [High,In progress] https://launchpad.net/bugs/1532358
[21:45] <Saviq> and bug #1541854
[21:45] <ubot5`> bug 1541854 in QtMir "SharedWakelock test unstable" [High,In progress] https://launchpad.net/bugs/1541854
[21:45] <robru> Saviq: britney is under high load right now, each run takes about an hour, so by the time you fix the regression it'll probably take britney 2 hours to notice.
[21:46] <jibel> alesage, ^ can you take silo 57?
[21:46] <Saviq> robru, is it http://autopkgtest.ubuntu.com/running.shtml ?
[21:46] <robru> Saviq: yeah I can see it at the very bottom there
[21:46] <robru> Saviq: so however long that takes, + an extra hour for the britney run to notice it
[21:46] <jibel> alesage, create a card temporarily on the trello board until britney finishes its things
[21:47] <Saviq> robru, ack
[21:48] <dobey> exit
[21:48] <dobey> doh
[21:49] <robru> heh
[21:51] <dobey> now why is unity-scopes-api failing abi check on xenial :(
[21:55] <alesage> jibel, ack willdo