[05:12] <robru> oh god
[06:58] <Mirv> :(
[07:01] <robru> yeah
[07:03] <Mirv> robru: I've noticed that log disappearing before too on restarts, funny that the logs would be there but not shown
[07:03] <robru> Mirv: yeah
[07:05] <robru> Mirv: I just realized that all the diffs are inaccessible too, so I'm trying to get #is to tar them up for us so we can get to them
[07:07] <robru> Mirv: so, WATCH_ONLY is gone, but if you're in a pinch and really need to regenerate diffs on a silo, you can add a phony source package, build that package in PACKAGES_TO_REBUILD, and when it runs the diff phase it diffs everything, then just drop the package from the silo config after that. but hopefully we'll get all the diffs and it won't be necessary
[07:07] <robru> Mirv: or if the silo happens to have a manual source, just put that one in PACKAGES_TO_REBUILD and it'll do it
[07:10] <Mirv> robru: oh right, thanks for the trick.
[07:11] <robru> Mirv: I really don't want to bring back WATCH_ONLY but it seems like I'm going to need to provide some method of just regenerating diffs without rebuilding the packages.
[07:16] <robru> Mirv: no luck from #is, apparently there's too many to feasibly tar them up, and it's difficult to grab just the latest one
[07:29] <Mirv> robru: ok then
[07:30] <robru> Mirv: actually he just made a tarball and it's only 340MBs...
[07:49] <Mirv> ^ that's a first since March when the silo was started for vivid...
[07:49] <Mirv> mostly because no sense to work on the -gles packages before they are really needed
[07:50] <Mirv> but surely there were some months of other build failure too, and then reappearing new build failures with new toolchains etc
[08:02] <robru> Mirv: hmm? what's a first?
[08:07] <Mirv> robru: first time silo 012 was fully and succesfully built
[08:08] <Mirv> all packages that are meant to land from there
[08:09] <robru> Mirv: oooooh
[08:13] <robru> yowza
[08:28] <robru> Mirv: so uh, you gonna land ticket 20 then? Would be great to get that one out the door eh? ;-)
[08:39] <Mirv> robru: possibly next week :) it's starting to be as good as it's going to get at this point
[08:40] <robru> Nice
[09:20] <popey> Mirv, https://requests.ci-train.ubuntu.com/#/ticket/710 is the clock update ticket for QA as requested yesterday.
[09:35] <Mirv> popey: great!
[09:35] <Mirv> popey: what about the dropping letters?
[09:35] <popey> next on my list Mirv
[09:36] <Mirv> thank you
[09:43] <diwic> hi, I click "Create new request" and get an error 401 - what team should I be a part of, and who can make me part of such a team?
[09:55] <john-mcaleely> sil2100, ^ ?
[09:56] <brendand> diwic, it would be ci-train-users
[09:58] <brendand> diwic, ci-train-ppa-service is the admin: https://launchpad.net/~ci-train-ppa-service/+members#active
[09:59] <john-mcaleely> Mirv, does that mean you can help add diwic?
[10:00] <diwic> brendand, thanks, looking
[10:01] <diwic> all core devs are members of that team it seems like
[10:02] <brendand> diwic, yeah should be lots of people who can do it
[10:02] <brendand> diwic, unfortunately not me :(
[10:02] <Mirv> john-mcaleely: yes, diwic should just highlight "trainguards" so that we notice it more easily
[10:03] <john-mcaleely> :-)
[10:03] <popey> Mirv, dropping letters is done
[10:05] <diwic> trainguards: you are hereby highlighted
[10:05] <Mirv> diwic: ok, you're now part of the ci-train-users team
[10:05] <Mirv> diwic: try again
[10:05] <Mirv> popey: \o/
[10:05] <robru> diwic: log out and log back in though
[10:05] <Mirv> diwic: \o/
[10:05] <diwic> Mirv, thanks, working now
[10:06] <robru> diwic: https://wiki.ubuntu.com/citrain/LandingProcess documentation is here
[10:07] <diwic> robru, thanks, I'll try to follow it
[10:08] <robru> diwic: you're welcome!
[10:19] <rvr> jgdx: ping
[10:23] <jgdx> rvr, pong
[12:19]  * sil2100 off to lunch
[12:46] <Elleo> sil2100 / robru: any idea what's causing the "not in PPA" errors for some (but not all) packages in silo 17?
[13:12] <Saviq> rvr, hey, just ACKed the two branches, silo 5 should be good for testing
[13:13] <rvr> Saviq: Ah, good
[13:13] <Saviq> they were just missing top-ack after some tweaks
[13:14] <rvr> Saviq: I already installed it, and was checking every merge proposal in the (large) list
[13:16] <Saviq> rvr, yeah, we like our large silos ;)
[13:18] <rvr> Saviq: This one also lacks top approval https://code.launchpad.net/~aacid/unity8/clazy_run/+merge/278326
[13:18] <Saviq> rvr, oh sry
[13:19] <jibel> rvr, jgdx I'm failing silo 39. It doesn't fix the crash.
[13:20] <rvr> jibel: Ack
[13:21] <jgdx> higgins, ack
[13:21] <jgdx> jibel, ack
[13:21] <jgdx> jibel, could you do apt-cache policy libsystemsettings1 ?
[13:22] <jgdx> just to confirm
[13:22] <jibel> jgdx, you're right to not trust me ;) http://paste.ubuntu.com/13526210/
[13:25] <jgdx> jibel, looks good though!
[13:28] <jibel> popey, I approved the clock app
[13:28] <popey> jibel, thanks :) I saw and uploaded it to the store.
[13:29] <jibel> popey, great, thanks
[13:35] <Mirv> thanks p & j for clock!
[13:40] <jibel> xavigarcia, silo 6 looks good, approved
[13:41] <jibel> xavigarcia, I found one configuration that doesn't really make sense and needs design input: 'disable GPS' and select 'GPS only' in location settings.
[13:41] <jibel> xavigarcia, I'll file a bug it is an existing case.
[13:42] <jgdx> cihelp: I'm seeing "UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is
[13:42] <jgdx> running, and the correct socket is being used and is accessible. The shell may have
[13:42] <jgdx> rejected the incoming connection, so check its log file"
[13:42] <jgdx> (sorry) and wondering what to do
[13:43] <jgdx> cihelp: it's happening in a lot of system settings jenkins autopilot jobs
[13:44] <jgdx> phablet-test-run never (on 4th run now) reproduces the issue
[13:45] <xavigarcia> jibel: cool, thanks!
[13:45] <xavigarcia> jibel: yeah, I saw that as well
[13:52] <jibel> xavigarcia, bug 1520580 for info
[14:06] <morphis> sil2100: what does happen if we have a vivid only and a dual landing MP in a silo?
[14:07] <morphis> does that work and land the vivid only manual upload to the overlay ppa only and the MP to both overlay and xenial?
[14:13] <kenvandine> jibel, rvr: the crash you guys found in silo 39, that isn't a regression
[14:13] <kenvandine> i just reproduced that with ubuntu-system-settings 0.3+16.04.20151109-0ubuntu1
[14:13] <kenvandine> different bug
[14:13] <jibel> kenvandine, it is the crash the silo is supposed to fix
[14:13] <kenvandine> no
[14:13] <kenvandine> i've never seen that crash
[14:19] <jibel> kenvandine, without the silo it's https://errors.ubuntu.com/oops/d3f94da4-9505-11e5-9c7f-fa163e525ba7 corresponding to bug 1519046 which is the bug attached to the MP
[14:19] <jibel> kenvandine, and with the silo it crashes with the same test case (retracing failed unfortunately)
[14:20] <jibel> kenvandine, so that bug is not fixed
[14:20] <jibel> kenvandine, or bug 1517254 and 1519046 are not duplicates
[14:20] <jibel> and only the first one has been fixed
[14:24] <psivaa> jgdx: Could you give me the link to the job?
[14:29] <jgdx> psivaa, one example: http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-vivid-touch/5409/
[14:29] <psivaa> jgdx: thanks
[14:31] <jgdx> psivaa, filed here https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520604
[14:31] <jgdx> psivaa, there's a ubuntu keyboard run in there as well. So it seems it's not system settings specific.
[14:37] <psivaa> jgdx: did you say you weren't able to reproduce this locally?
[14:37] <psivaa> if that's the case, just wanted to confirm, on which device you're running locally
[14:38] <jgdx> psivaa, I'm running mako locally and I can't reproduce. Elleo says he can repro sometimes during normal app launch.
[14:38] <jgdx> Elleo, what device was that?
[14:39] <psivaa> jgdx: in our case, we're  only running those tests on krillin
[14:40] <jgdx> psivaa, I know. So this would be device specific, then?
[14:40] <Elleo> jgdx: that was on a mako, I've only seen it a couple of times
[14:40] <Elleo> jgdx: no where near as frequently as seems to be happening in the tests
[14:41] <jgdx> Elleo, okay, and it seems random?
[14:41] <Elleo> jgdx: yeah, and starting the app again after it happens results in a perfectly normal launch
[14:41] <Elleo> jgdx: might be worth grepping your own app logs to see if its happened at all to you without you noticing
[14:42] <psivaa> jgdx: more likely, i can not confirm though. It would be ideal if someone runs those tests locally on krillin. Since we're not doing anything special in jenkins than how you run locally, I dont think we, in CI can do much about this failure
[14:42] <Elleo> jgdx: since unless you're looking at the logs at the time the only thing you notice is that the app didn't start when you click on it
[14:43] <Elleo> jgdx, psivaa: I'll update my krillin and set the keyboard tests going on there and see if they hit it at all
[14:43] <jgdx> Elleo, thanks!
[14:43] <psivaa> Elleo: thanks
[14:43] <jgdx> psivaa, maybe help debug though
[14:45] <kenvandine> jibel, i'm confused, rvr said when he followed the steps to test this bug it passed but it crashed when starting directly in updates with flight mode enabled, which is a different bug
[14:48] <psivaa> jgdx: hmm, I dont think I can do much here though. If there is anything infrastructure related then I could help, but this is not related to any infra setup since there are other tests that run fine
[14:48] <jibel> kenvandine, the thing is if you load the update page with an update available then turn airplane mode on it crashes with the trace in 1519046, and same with or without the silo. So either it is a different test triggering the same crash or the crash is partially fixed or the 2 crashes are not duplicates.
[14:48] <kenvandine> jibel, i'm filing a new bug for that
[14:48] <kenvandine> jibel, oh?  rvr said it didn't crash
[14:49] <jgdx> psivaa, okay
[14:49] <jibel> kenvandine, yeah I don't know why he didn't have a crash, but the crash is the same with or without the silo and whoopsie says it's the bug attached to the tiket
[14:50] <kenvandine> jibel, i can't make it crash when switching flight mode on while in the panel
[14:50] <kenvandine> i can without the silo of course :)
[14:50] <jibel> kenvandine, you need a U1 account registered and at least an update in the list
[14:50] <kenvandine> i have 3 updates
[14:51] <kenvandine> jibel, i did reproduce it with downgrading settings to what's in the overlay
[14:51] <kenvandine> but it doesn't crash when i install the silo
[14:51] <jibel> kenvandine, hm, let me try again
[14:51] <jibel> kenvandine, on which device?
[14:51] <kenvandine> arale
[14:51] <jibel> kenvandine, I didn't try on arale with the silo but krillin, I tried without the silo on both though
[14:52] <jibel> I'm retrying on krillin then arale
[14:52] <kenvandine> jibel, i did the testing from the MR on krillin
[14:52] <kenvandine> but silo testing on arale
[14:53] <kenvandine> it didn't crash on either for me
[14:53] <kenvandine> jibel, i filed bug 1520611 for the other crash
[14:54] <jibel> kenvandine, my case is slightly different, you start the update panel then enable flight mode.
[14:54] <kenvandine> yeah
[14:54] <jibel> I don't know if it makes a difference
[14:54] <kenvandine> which is what i was fixing
[14:55] <kenvandine> while it's doing a check, enable flight mode
[14:55] <kenvandine> that was triggering the crash in 1519046
[14:55] <kenvandine> jibel, what are you doing?
[14:56] <jibel> kenvandine, what I said, with the silo installed, open settings, and enable flight mode, it still triggers this bug
[14:57] <kenvandine> in which page?
[14:57] <jibel> kenvandine, in the updates page
[14:58] <kenvandine> jibel, and you said the stacktrace matches?
[14:58]  * kenvandine doesn't think that could be possible
[14:58] <kenvandine> that code path wouldn't be hit after the check finishes
[14:58] <jibel> kenvandine, no errors.u.c says it's the same
[14:59] <kenvandine> with the silo installed?
[14:59] <kenvandine> got a link to the errors page for the crash with the silo?
[14:59] <jibel> yes. I'm redoing it to double check
[15:01] <kenvandine> jibel, if that's the same crash, that's not what i was looking at while working on this bug :)
[15:01] <kenvandine> i was only working on the case where it went into flight mode(or lost network) which the check was being done
[15:01] <jibel> kenvandine, I confirmed that with the silo installed, open system-settings/updates, wait until the 3 updates are displayed, then enable flight mode, it crashes
[15:02] <kenvandine> i was getting that same crash when it was actively checking for the updates
[15:02] <jibel> confirm*
[15:02] <kenvandine> and this branch fixes that
[15:02] <kenvandine> so i need another fix for your case
[15:04] <jibel> kenvandine, https://errors.ubuntu.com/oops/d23833f6-9517-11e5-b5b7-fa163e22e467
[15:05] <kenvandine> jibel, thx
[15:14] <Elleo> jgdx: here's the crash from unity8 running autopilot: http://mikeasoft.com/~mike/_usr_bin_unity8.32011.crash
[15:14] <jgdx> Elleo, asum
[15:15] <kenvandine> jibel, ok, i pushed a fix that i think should fix the case you hit, i need a build to confirm it
[15:18] <jibel> kenvandine, I was hoping it would take you more time and finish the week with empty queues of silos for QA ;)
[15:18] <kenvandine> haha :)
[15:18] <kenvandine> lets hope you still do... just with this silo landed :)
[15:19] <kenvandine> jibel, i'm confident this will fix it :-D
[15:53] <bzoltan_> ping cihelp
[15:53] <t1mp> cihelp: hello, I got failures in my MR that I think are CI related https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/10-subheader/+merge/278713
[15:53] <bzoltan_> we have seen the same failure with  more and more MRs
[15:53] <bzoltan_> https://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-vivid-i386-autolanding/675/consoleFull
[15:54] <t1mp> It includes errors like this: /tmp/buildd/ubuntu-ui-toolkit-1.3.1688+15.10.20151018.1bzr1733pkg0vivid1268/tests/checkresults.sh: line 53: bc: command not found
[15:55] <psivaa> bzoltan_: let me take a look
[15:55] <bzoltan_> psivaa: thank you
[16:10] <psivaa> bzoltan_: t1mp: that ^ error 'bc: command not found' appears to be a red herring
[16:10] <psivaa> what's bothering me more is the output after 'Fatal server error:'
[16:10] <psivaa> EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
[16:10] <psivaa> _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
[16:10] <psivaa> _XSERVTransMakeAllCOTSServerListeners: server already running
[16:16] <t1mp> psivaa: what can cause that? The MRs are for changes in UI toolkit, no changes directly related to X
[16:16] <t1mp> the tests pass on armhf
[16:17] <t1mp> also they pass on amd64, at least for my MR
[16:25] <kenvandine> jibel, i've confirmed my fix fixes the crash in both cases
[16:31] <psivaa> t1mp: i can't think of the cause, yet. this is only happening in i386 builders. digging a little more to see if there is any history with it
[16:35] <oSoMoN> davmor2, how is the validation of silo 13 going ?
[16:36] <davmor2> oSoMoN: nearly done
[16:36] <t1mp> psivaa: okay, thanks
[16:36]  * t1mp gotta go now
[16:44] <davmor2> oSoMoN: just finished infact with the download of the next track for tubular bells :)  all present and correct qa granting
[16:51] <davmor2> sil2100: did the bot die?
[16:51] <sil2100> davmor2: which one?
[16:52] <davmor2> sil2100: https://requests.ci-train.ubuntu.com/#/ticket/709 passed about 8 minutes ago hasn't been flagged yet here
[16:52] <sil2100> You mean, queuebot? There was a netsplit
[16:52] <sil2100> Queuebot did not return yet
[16:53] <davmor2> sil2100: ah that would explain it then thanks :)
[17:05] <popey> sil2100, for OTA8.5 - how does it work - just like OTA(N) you pluck the latest rc-proposed and promote after QA?
[17:05] <popey> sil2100, or is there some special process which takes OTA8 and adds a few cherry picked items?
[17:06] <sil2100> popey: hey! It's a bit different
[17:06] <sil2100> popey: we prepare an OTA-8 snapshot in a PPA and cherry pick packages that we need to have in the 8.5 release
[17:06] <sil2100> So more like your second idea
[17:06] <popey> ok, so it isn't the things that are in rc-proposed now plus fixes, but ota-8 plus fixes?
[17:06] <popey> ok, good
[17:07] <rvr> Saviq: Approving silo 5
[17:07] <popey> Can we assume silo 9 will _not_ be part of that? (media-hub recent landing) ?
[17:07] <sil2100> Yes, since we want to make sure that there's only a controlled number of fixes/changes in the image we want to release
[17:07] <sil2100> I think it wasn't part of the OTA-8.5 plan
[17:08] <popey> ok
[17:08] <jhodapp> it wasn't indeed
[17:08] <jhodapp> OTA9
[17:08] <sil2100> So the music-app changes still need to wait a bit ;)
[17:09] <ahayzen> :-)
[17:25] <jibel> popey, 8.5 are all the fixes targeted to OTA9 and tagged 'hotfix'
[17:25] <popey> ooh, ta
[17:26] <jibel> and fixed of course :)
[17:45] <bzoltan_> psivaa:  could you figure out anything about that odd failure?
[17:47] <psivaa> bzoltan_:  looks like one of the nodes is misbehaving. still figuring out how. i have offlined that node so the runs are passing
[17:47] <psivaa> https://jenkins.qa.ubuntu.com/job/ubuntu-sdk-team-ubuntu-ui-toolkit-staging-vivid-i386-autolanding/
[17:50] <bzoltan_> psivaa:  nice, thank you
[17:51] <psivaa> bzoltan_: i have kicked off a couple of failed ones, it would help if you're able to rebuild any failed ones that you were waiting on.
[17:51] <bzoltan_> psivaa:  it is this one - https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/resolve_qpointer_data/+merge/278766 what I need the most
[17:52] <psivaa> right, that one is still in progress after my rebuild. thanks
[17:55] <bzoltan_> psivaa:  other ... i see this package is in the proposed pocket https://requests.ci-train.ubuntu.com/#/ticket/711 Is anything holding it or should I expect to land at some point without anything?
[17:56] <psivaa> bzoltan_: since the particular node is offlined, it should not impact any more tests
[17:57] <bzoltan_> psivaa:  cool, thanks. what about that qtcreator-plugin-ubuntu landing?
[17:58] <psivaa> bzoltan_: sorry, i dont see any autolanding job for qtcreator-plugin-ubuntu?
[17:58] <psivaa> bzoltan_:  i only see qtcreator-plugin-ubuntu-ci
[17:59] <bzoltan_> psivaa:  in this silo https://requests.ci-train.ubuntu.com/#/ticket/711
[17:59] <psivaa> bzoltan_: we dont deal with ci-train stuff, should be for trainguards i suppose
[18:00] <psivaa> apologies for my confusing answer before
[18:00] <bzoltan_> psivaa:  ohh, sorry :)
[18:00] <bzoltan_> psivaa:  my bad, thank you for your help with the other issue. That was a clear blocker.
[18:01] <psivaa> bzoltan_: yw :)
[19:04] <davmor2> popey: ^
[19:04] <davmor2> ahayzen: ^
[19:04] <ahayzen> \o/
[19:33] <popey> \o/
[19:33] <popey> thanks davmor2 ahayzen
[19:36] <popey> \o/ store has updated weather
[21:26] <dobey> is fginther around today?
[22:17] <dobey> trainguards: can i get someone to manually ack some autopkgtest failing that has never worked?
[22:17] <robru> dobey: what, in proposed? that's a job for #ubuntu-release
[22:18] <dobey> yes
[22:18] <robru> dobey: also proposed migration is not supposed to block on something that always failed.
[22:19] <dobey> robru: i think maybe something is wrong with how that is determined then? this fails at installing the built binaries on some archs, which i guess we didn't have autopkgtests running for until recently
[22:20] <dobey> well, one of the built binaries
[22:20] <robru> dobey: dunno then. not my area, sorry
[22:20] <dobey> ok
[22:21] <dobey> probably not the best time to be pinging people either, late on a friday, and with most US people on vacation today