[00:00] <robru> thomi, actually yeah, it's showing https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/3118/console here the version is lacking the necessary .1 that fixes everything. hrm
[00:01] <thomi> robru: :-<
[00:02] <robru> thomi, no, wait
[00:02] <robru> thomi, was looking at the wrong thing. this one isn't just missing the .1, it's actually grabbing 1.3...
[00:02] <robru> hmmm, weird, the log is showing that it has the PPA...
[00:03] <robru> fginther, can you see why this one has the PPA but isn't grabbing autopilot from it? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/3118/console
[00:03] <thomi> robru: which MP is that for?
[00:03] <robru> thomi, that's for the friends-app one
[00:03] <robru> https://code.launchpad.net/~chris.gagnon/friends-app/autopilot-1.4/+merge/193293
[00:03] <thomi> robru: looks like robotfuel forgot to update debian/control perhaps
[00:04] <thomi> so it's pulling in 1.3 of those packages
[00:04] <thomi> robotfuel: are you able to update & re-push please? ^^
[00:07] <robotfuel> sure
[00:10] <elopio> cihelp, how do I create an account here? 91.189.93.70:8080 I only see the option to log in.
[00:11] <robotfuel> thomi: done, will you re-approve?
[00:11] <thomi> robotfuel: yup
[00:11] <thomi> robru: Can you cancel the old friends-app run please?
[00:11] <thomi> robru: or better yet, kick it off again?
[00:12] <robru> which run, the CI one?
[00:15] <robru> thomi, hmmmm, not sure. this CI stuff is more fginther's territory. i cancelled one job but i'm not sure how to restart it
[00:16] <robru> thomi, re-approved anyway, hopefully jenkins picks it up soon
[00:16] <thomi> robru: the autolanding
[00:16] <thomi> but that's OK, I guess it'll get picked up again in time
[00:29] <elopio> our the maguros having problems again? http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/
[00:32] <elopio> thomi: autopilot-trusty-master is stuck.
[00:32] <thomi> :(
[00:37] <thomi> fginther: Can you please make the unity8 autolanding use the daily-build PPA, since otherwise it picks up autopilot 1.3 still
[00:39] <Saviq> http://s-jenkins:8080/job/unity8-autolanding/648/
[00:39] <Saviq> thomi, fginther added the hook ↑
[00:39] <thomi> Saviq: gonna kick it off again then?
[00:40] <Saviq> thomi, already running
[00:46] <Saviq> thomi, yup, picked up 1.4
[00:46] <robru> damn, just got my mako by fedex. I now have mako, maguro, and grouper on my desk. I'm a testing machine!
[00:52] <Saviq> thomi, seems we got green on amd64, let's see if devices are happy, too
[00:52] <thomi> \o/
[01:07] <thomi> fginther: looks like the maguro's are stuck again
[01:08] <thomi> can we disable them please? They're holing up the landing process more than is healthy IMO
[01:08] <thomi> cihelp - maybe smoeone else can help with that?
[01:11] <Saviq> yeah, two maguros stuck in flashing again :/
[01:11] <Saviq> veebers, you disabled them yesterday didn't you ↑?
[01:12] <Saviq> shame all the jobs that are running will break again
[01:12] <veebers> Saviq: I disabled the job in mediumtests-touch, not the actual devices (as yesterday they were all down)
[01:12] <veebers> looks like it was added back to the jenkins job
[01:12] <Saviq> veebers, yeah yeah, two of them still running now (at least until they're taken up to flashing...)
[01:13] <veebers> right, at which point they will have issues, perhaps we should disable it from the job again
[01:13] <Saviq> veebers, we've already a significant queue http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/ :/
[01:14] <Saviq> and now the other two are flashing... wonder if they'll come up...
[01:16] <xnox> cihelp: can https://code.launchpad.net/~xnox/ubuntu-keyboard/libpinyin4/+merge/193859/comments/447347 be retried? the i386 build failure seems spurious.
[01:22] <Saviq> thomi, ok, so touch couldn't pass, as we don't have >= 1.4 in debian/control for autopilot :/
[01:23] <thomi> Saviq: for u*/
[01:23] <thomi> err, for u*?
[01:23] <thomi> dammit
[01:23] <Saviq> thomi, yeah, unity8
[01:23] <thomi> u8?
[01:23] <thomi> sticky shift key :)
[01:23] <thomi> robotfuel: still awake?
[01:24] <thomi> Saviq: if robotfuel isn't arund I'll propse a new branch with that in it as well
[01:24] <robotfuel> thomi: which one?
[01:25] <Saviq> robotfuel, https://code.launchpad.net/~chris.gagnon/unity8/autopilot-1.4-wip/+merge/193529
[01:25] <thomi> robotfuel: unity8
[01:25] <thomi> needs >= 1.4 for the autopilot deps
[01:25] <Saviq> robotfuel, autopilot >= 1.8 please
[01:25] <robotfuel> you mean 1.4?
[01:25] <Saviq> 1.4 that is ;)
[01:25] <thomi> Saviq: >= 1.4 :)
[01:25] <Saviq> yeah, too many 8s
[01:26] <Saviq> oh, looks like the two maguros came back from the dead
[01:27] <Saviq> scratch that, the two are still dead, the two that were just flashing seem to have flashed fine
[01:27] <robotfuel> thomi: Saviq done
[01:27] <Saviq> robotfuel, cheers
[01:28]  * Saviq kicks the build again...
[01:28] <thomi> thanks Saviq
[01:37] <Saviq> jeez they're being flashed after every job? no wonder they're dying...
[01:43] <fginther> xnox, the build is retried
[01:43] <xnox> fginther: thanks.
[01:43] <Saviq> fginther, two maguros stuck again in flashing :/
[01:44] <fginther> Saviq, saw that, our attempts to switch hosts and hubs this week have not helped :-(
[01:44] <fginther> Saviq, I'm considering removing the maguro job so they don't get wedged while I'm sleeping
[01:45] <Saviq> fginther, yeah, it helped yesterday
[01:45] <Saviq> fginther, we're not getting anything over what makos are giving us, either
[01:45] <fginther> Saviq, they can't be fixed without someone physcially resetting the devices :-(
[01:45] <Saviq> fginther, you've got +1 from me and thomi on just dropping them from mediumtests-trusty-touch
[01:46] <fginther> Saviq, thomi done
[01:46] <Saviq> the current jobs will hopefully trickle down through the two (assuming they don't get stuck, too)
[01:46] <fginther> Saviq, that's my hope
[01:47] <Saviq> fginther, we should try the system-image-cli approach I mailed about
[01:47] <Saviq> it might be less error prone since it only reboots the phone into recovery and back
[01:47] <fginther> CI will have to revisit the continued use of these devices. If we can't get them to be stable, they do more harm then good
[01:48] <Saviq> in earnest we shouldn't even do that, the system.img file could just be duplicated and reused instead of flashing
[01:48] <fginther> Saviq, I saw that, how does that method work with manually installed deb packages?
[01:48] <Saviq> fginther, it just replaces the rootfs
[01:48] <Saviq> fginther, with the pristine image
[01:48] <fginther> Saviq, hmm
[01:48] <Saviq> fginther, what phablet-flash gives you over that is it wipes userdata, too - system-image-cli does not
[01:49] <Saviq> but if our tests modify userdata, they're broken anyway
[01:49] <Saviq> fginther, but, to not download the image over and over again - we should have two modes - "hard" and "soft" flash
[01:50] <Saviq> fginther, "hard" could be just phablet-flash
[01:50] <Saviq> fginther, or system-image-cli -b0
[01:50] <Saviq> fginther, we should then copy system.img on the device
[01:50] <Saviq> and subsequent "soft" flashes would just replace the system.img used with the copy
[01:50] <Saviq> thus not requiring networking to bring the device to clean state
[01:51] <fginther> Saviq, that's reasonable, I'll investigate
[01:51] <fginther> gotta go for a bit, will check back in later
[01:51] <Saviq> fginther, o/
[01:54] <Saviq> fginther, fwiw, such "go to dev mode, revert to read-only mode" could be built into system-image-cli itself
[01:55] <thomi> fginther: thanks man
[01:56] <thomi> fginther: do those old jobs need to be kicked off again?
[01:58] <robru> thomi, alright, I'm EOD. I'll probably be around for a few more hours, but slow to respond. ping if you need anything (but ping fginther about that friends-app merge, i'm not sure how to fix that)
[01:58] <thomi> robru: ok
[01:59] <thomi> fginther: are you going to be around for a bit longer?
[02:00] <Saviq> thomi, there are still two maguros in play, so hopefully they'll trickle through
[02:02] <Saviq> thomi, looking at friends-app merge... I'd say those are real test failures https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/445/? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/3122/
[02:07] <robru> Saviq, nah, if you click through to the console output, it says "Class 'friends-app' has no attribute 'wait_select_single'." which implies autopilot 1.3 is in use, not 1.4.
[02:07] <Saviq> robru, you can see autopilot 1.4 being installed there...
[02:08] <Saviq> python-autopilot_1.4+14.04.20131105.2-0ubuntu1_all.de
[02:08] <robru> Saviq, "00:01:39.805 INFO autopilot:141 - Autopilot Source Version: 1.3.1"
[02:08] <thomi> robru: I bet it's that borked autopilot versin again
[02:08] <Saviq> robru, ah, that's on device?
[02:08] <robru> Saviq, i'm looking at https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/3122/console
[02:08] <Saviq> robru, there's no autopilot (>= 1.4) there, then?
[02:09] <robru> Saviq, in that log i can't find any evidence that it's installing autopilot from the PPA, it seems to just be using whatever's on device already, which would be old
[02:09] <Saviq> robru, yeah, missing version dep in the merge
[02:09] <Saviq> same we just had in unity8
[02:09] <Saviq> robru, but https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/445/? is using 1.4 - and still one test is failing
[02:09] <thomi> Saviq: which merge?
[02:10] <Saviq> thomi, https://code.launchpad.net/~chris.gagnon/friends-app/autopilot-1.4/+merge/193293 afaics
[02:10] <Saviq> thomi, the autolanding job didn't use the latest revision
[02:10] <thomi> Saviq: debian/control is up-to-date
[02:10] <thomi> robru: can you double check that the borked AP package is really deleted please?
[02:11] <Saviq> thomi, there's a new autolanding running http://s-jenkins:8080/job/friends-app-autolanding/26/ with the correct rev
[02:11] <robru> thomi, well it would have never been 'deleted', just superceded by the newer one. there's now two newer ones that replaced it, .1 and .2
[02:11] <thomi> hmm, ok
[02:11] <thomi> Saviq: ahh ok
[02:11] <thomi> so we just gotta wait :)
[02:12] <Saviq> thomi, yeah http://s-jenkins:8080/job/friends-app-autolanding/26/console
[02:12] <Saviq> thomi, we'll know about unity8 on mako soon enough, too
[02:13] <robru> Saviq, https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/445/console does look like a 'real' failure, but i don't understand it. friends-app test is practically a no-op, i'm not sure what could possibly fail there.
[02:13] <Saviq> robru, self.assertThat(toolbar.state, Equals(''))
[02:13] <robru> Saviq, thomi: seriously, the friends-app test is so simple, all it does is launches the app, confirms it's launched, and then tests that the toolbar can be revealed.
[02:13] <Saviq> robru, but it remains at 'spread'
[02:13] <Saviq> robru, maybe it's just missing an Eventually()?
[02:14] <robru> Saviq, nope, it wouldn't be an Eventually
[02:15] <robru> Saviq, that test is first testing that the toolbar defaults to hidden, it's testing that the initial state is as we expect
[02:15] <thomi> hmmm
[02:15] <robru> thomi, do you know anything about toolbar.state? it should be '' when hidden and 'spread' when revealed, right? that's what we test for. but now it seems to start as 'spread' in this test failure
[02:16] <thomi> robru: I don't know, sorry - elopio would be a better person to ask I think
[02:16] <robru> elopio, ^^ ?
[02:16] <elopio> hey, I'm just getting back.
[02:17] <elopio> I'm not sure about spread. Is that a property?
[02:17] <Saviq> robru, maybe it's just that the UITK changed the behavior to be shown initially?
[02:17] <Saviq> robru, there was talk of doing that
[02:17] <thomi> elopio: 'toolbar.state' property
[02:18] <Saviq> robru, and when you launch the app, it's indeed there for a few seconds
[02:18] <Saviq> sounds like we need an emulator for the panel (isn't there one yet?)
[02:18] <robru> Saviq, hmmm, yeah, it seems so
[02:18] <elopio> robru: the toolbar properties is something you shouldn't be testing on the apps, that should be tested on the toolkit.
[02:18] <Saviq> robru, http://pad.lv/1207369
[02:19] <robru> elopio, yeah, i agree, but we weren't sure how to get any mock accounts to be able to test friends itself, so the toolbar is really the only thing we can fiddle with there ;-)
[02:19] <Saviq> yeah, at most it should be using the emulator
[02:19] <elopio> on the apps you should just call the emulator toolbar.opened.
[02:20] <Saviq> eh... mako dead now? http://s-jenkins:8080/job/generic-mediumtests-runner-mako/3131/consoleFull ;/
[02:21] <thomi> elopio: so.. I'mleaning towards filing a bug against uuitk, and merging this manually?
[02:22] <thomi> elopio: or maybe we just remove that line from the test?
[02:22] <Saviq> thomi, uitk is correct
[02:22] <elopio> robru, thomi: I think you can just remove this test_toolbar.
[02:23] <robru> robotfuel, still around to do that on your branch? or should i just do it?
[02:24] <robotfuel> robru: which branch?
[02:24] <robru> robotfuel, https://code.launchpad.net/~chris.gagnon/friends-app/autopilot-1.4/+merge/193293 that
[02:24] <robru> that's you, right?
[02:24] <robotfuel> yes
[02:24] <robru> robotfuel, yeah, can you just delete the test_toolbar test? it's bad
[02:24] <elopio> as Saviq said, it's failing because now the toolbar starts visible and then it's hidden.
[02:25] <Saviq> grr
[02:25] <Saviq> thomi, if http://s-jenkins:8080/job/generic-mediumtests-runner-mako/3131/console does not recover, just cancel, re-approve, restart http://s-jenkins:8080/job/unity8-autolanding/649/
[02:26] <Saviq> past 3am here, gonna go now
[02:26] <Saviq> if I find the above to still be hanging in the morning, I'll tackle it first thing
[02:26] <thomi> Saviq: thanks man
[02:26] <thomi> this is starting to get seriously frustrating :-(
[02:26] <Saviq> it does
[02:27]  * Saviq wants the emulator
[02:27] <Saviq> have fun peeps o/
[02:28] <elopio> I've just approved the file manager app. It has passed on autopilot-trusty-master
[02:28] <robotfuel> robru: is there the friends app passes locally.
[02:28] <thomi> elopio: thanks man
[02:28] <robru> robotfuel, yeah, you probably don't have the updated ubuntu-ui-toolkit yet
[02:29] <elopio> maguros are coming back :)
[02:29] <elopio> keyboard is running atm.
[02:31] <robotfuel> robru: can I get a link to a failing test? maybe there is a simple fix?
[02:32] <robru> robotfuel, yeah, the simple fix is to delete test_toolbar. it's a stupid test, it's not testing the app but tests ui-toolkit, and ui-toolkit changes, to the test is broken. it doesn't need to be fixed, just deleted
[02:33] <robru> robotfuel, the test failure is somewhere in the scrollback, sorry I don't remember which one.
[02:35] <robotfuel> robru: done
[02:37] <robotfuel> robru: I don't even think we should have ported that one to 1.4, there are no real tests.
[02:43] <fginther> down to one maguro
[02:45] <fginther> and down to two makos
[02:49] <robru> robotfuel, well, the idea is that we have that stub there so that it will be easier to write more tests in the future. it definitely needs to be ported to 1.4
[02:49] <robru> robotfuel, and thanks
[03:07] <thomi> fginther: any idea WTF is going on here? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-maguro/2982/console
[03:11] <thomi> robru: fginther: Are either of you able to kick off the UI toolkit autolanding? It seems it's not enabled by default
[03:13] <thomi> well, I may have done it correctly, maybe not: http://s-jenkins:8080/job/ubuntu-ui-toolkit-autolanding/427/
[03:38] <plars> looks like some new failures with the new image
[03:38] <plars> webbrowser_app.tests.test_title.TestWindowTitle.test_window_title  for one
[03:41] <fginther> thomi, hey
[03:41] <thomi> hey fginther
[03:41] <fginther> thomi, looking at phone-app now
[03:42] <thomi> so... I'm not a happy man- the CI hardware seems totally fucked from my POV :(
[03:42] <thomi> soooo many failures, and one job that seems permenantly stuck here: http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/
[03:43] <thomi> and I'm seeing some strange otto-related issues here as well: https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/453/console
[03:48] <thomi> fginther: TBH, It must be getting late for you, I think the problems we're seeing are more systemic, and it's probably best if you get some sleep and attack this tomorrow
[03:49] <thomi> I'll send a status update tomorrow
[03:49] <thomi> err, today
[03:49] <fginther> thomi, I see you found the package name issue with friends-app
[03:50] <fginther> thomi, is phone-app depricated?
[03:50] <thomi> I have no idea... I would hope that the project would be deleted, if that were the case
[03:51] <fginther> It's not too late yet, I'll try to help if I can..
[03:52] <thomi> OK, I'm just going to approve all the branches, and hope that a few make it through
[03:52] <fginther> thomi, phone-app is not on my device and hasn't been updated in months
[03:52] <thomi> OK, I'll delete that then
[03:52] <fginther> ugh, why wasn't it deleted :-(
[03:53] <thomi> yeah
[03:53] <thomi> Words cannot convey my emotional state right now...
[03:54] <veebers> fginther: quick query: says in this log that there was a bunch of files archived (i.e. the ogv) but the jobs Build artifacts only contains the xml: http://10.97.0.26:8080/job/generic-mediumtests-trusty/488/console
[03:54] <veebers> fginther: oh, is that the log of the child job that was fired off, because I've found the files on that job
[03:54] <fginther> veebers, right, walk down to the child job, they should be there
[03:55] <veebers> fginther: awesome thanks
[03:58] <robru> thomi, agreed, we have many systemic issues
[03:58] <thomi> robru: are you able to top-approve this please? https://code.launchpad.net/~chris.gagnon/webbrowser-app/select-many-noorder-ap1.4/+merge/194031
[03:59] <robru> thomi, hmmm, oddly not.
[03:59] <robru> thomi, osomon should be up soon i think
[04:01] <robru> lool, around? i think you can approve this for us: https://code.launchpad.net/~chris.gagnon/webbrowser-app/select-many-noorder-ap1.4/+merge/194031
[04:04] <thomi> elopio: still around?
[04:10] <plars> thomi: will that fix the error I mentioned earlier?
[04:11] <thomi> plars: I'm not sure which error that is?
[04:11] <thomi> plars: oh
[04:11] <plars> webbrowser_app.tests.test_title.TestWindowTitle.test_window_title failing in the smoke tests on the latest image
[04:11] <thomi> plars: I'm not sure. was the image built with autopilot 1.4?
[04:11] <plars> was supposed to be... checking
[04:12] <plars> thomi: no, looks like 1.3 still
[04:12] <plars> so, nm
[04:12] <robru> thomi, ok, I'm out for reals. I think friends-app will land shortly, anything else i'll help out with in the morning.
[04:13] <thomi> robru: ok, thanks for your help
[04:13] <robru> thomi, you're welcome
[04:38] <fginther> thomi, ubuntu-rssreader-app and ubuntu-weather-app have merged
[04:38] <thomi> wooo!
[04:40] <thomi> fginther: ui toolkit merged as well - sweet!
[04:48] <fginther> thomi, sudoku-app doesn't look good. Not sure how important it is as the results are not included in the dashboard
[04:48] <fginther> thomi, also ubuntu-filemanager-app fails, but it also fails on the dashboard, appear to be some existing issues
[04:48] <thomi> fginther: OK, can we manually merge the filemanager app branch in that case?
[04:49] <fginther> thomi, yes
[04:49] <thomi> do you do that, or...?
[04:49] <fginther> thomi, I'll take care of it
[04:49] <thomi> thanks
[04:53] <fginther> thomi, done
[05:12] <Mirv> let's see...
[05:15]  * Mirv looks at the redness at cu2d
[05:18] <elopio> thomi: I'm here.
[05:19] <thomi> elopio: it's ok, I sorted it
[05:20] <elopio> thomi: ok, it seems we are almost done.
[05:20] <thomi> elopio: well, I doubt that very much :)
[05:22] <elopio> thomi: well, 10 branches landed, that's almost all of them. Where do you need help now?
[05:23] <thomi> elopio: I imagine there will be further issues we need to resolve - tests failing ec.
[05:23] <thomi> *etc
[05:23] <thomi> but I'm done for today
[05:25] <elopio> I see tomorrow as the day we can start cleaning tests, so it's not a problem if some fail, those will be the place to start.
[05:26] <thomi> yeah
[05:34] <fginther> thomi, good luck on the remaining work for today, I'm off to bed.
[05:34] <thomi> cheers!
[05:34] <thomi> I'm off to cook dinner, will BBL
[05:51] <elopio> lucky shot, the mediaplayer-app works fine on autopilot 1.4.
[05:51] <elopio> now there are no apps TODO.
[05:58] <Mirv> QA stack now green again
[05:59] <Mirv> (needed update to xpathselect1.4 in package list)
[07:08] <thomi> elopio: awesome!
[07:08] <thomi> Mirv: so, there's nothing more I need to do urgently today?
[07:14] <Mirv> thomi: if there is, we'll find out about it only later today. I'm now trying to ensure trevinho's unity branch is ok and will then merge it manually if it is
[07:14] <Mirv> if it works properly it will resolve many of the remaining problems
[07:15] <Mirv> thomi: but already having autopilot itself, unity8 and ui-toolkit in releasable state is promising
[07:16] <thomi> Mirv: OK, I'll EOD then. Can you email me with whatever you find please?
[07:17] <Mirv> thomi: yep, I'll keep up with the thread
[07:17] <thomi> Mirv: oh, and if you can find someone with the permissions to merge the webbrowser-app branch, that'd be awesome
[07:17] <thomi> thanks
[07:17] <Mirv> thomi: ok, I'll see about that
[08:50] <vila> Mirv: ping
[08:51] <vila> Mirv: I've lost track of what needs to happen regarding https://wiki.canonical.com/UbuntuEngineering/CI/IncidentLog/2013-11-04-otto-outage
[08:51] <vila> Mirv: we've reverted the kernels but is someone looking at the corresponding bug ?
[08:51] <vila> Mirv: is there even a bug filed for that ?
[08:57] <sil2100> Mirv: so the cmake bit is still not merged in? We might need to help finding someone who can top-approve that branch then
[08:57] <Mirv> vila: I don't know what was worked on that, but the autopilot machines currently seem to be happy. the last I remember was that it was asked to revert the kernel.
[08:57] <sil2100> Since it's slowing things down
[08:58] <Mirv> sil2100: yes, I suspect didrocks can help us here, that's why I sent the e-mail.
[08:58] <didrocks> hey Mirv
[08:58] <Mirv> hey didrocks
[08:58]  * didrocks looks at the discussion
[08:58] <sil2100> Morning!
[08:59] <Mirv> I've also pinged osomon to get the webbrowser AP 1.4 branch in today
[08:59] <vila> Mirv: argh, yeah, they are happy but they are not testing the latest kernel so if new bugs appear there... worth bringing to attention during the hangout ?
[09:00] <sil2100> Mirv: what about gallery-app? Since I see many many tests failing, and the merge is still not in
[09:00] <sil2100> Mirv: CI seems to be failing
[09:00] <Mirv> vila: ah, I see (reading the page further), indeed I don't know how the 3.12 should now be tested/fixed without causing problems on the machines themselves
[09:00] <didrocks> Mirv: ok, you need a cmake change for unity7?
[09:00] <vila> Mirv: outside the ci lab ? :-D
[09:01] <sil2100> Mirv: should we merge in manually? I'm looking at the failures now
[09:01] <Mirv> sil2100: I've not looked at that, my time has been consumed by cu2d + unity7
[09:01] <didrocks> psivaa: hey, are you looking at why image 13 as a bad pass rate?
[09:01] <Mirv> didrocks: yes, with the cmake change proposed unity7 starts working
[09:01] <sil2100> Mirv: ok, I'll pick that up
[09:01] <sil2100> didrocks: yes, that's the fix bregma did to take care of the annoying FTBFS for unity7
[09:01] <sil2100> But getting it merged in takes certainly too long already
[09:02] <Mirv> sil2100: the cmake MP however didn't have any approve before
[09:02] <Mirv> sil2100: so I tested compiling with it and approved it (needs top-approve / sponsoring now)
[09:03] <sil2100> Mirv: right, that's what I meant basically, no one besides you had even made a proper review, not to mention anyone from the cmake maintainance guys
[09:03] <didrocks> argh, bregma didn't base on latest upstream releas :/
[09:04] <didrocks> and I see inline changes
[09:04] <didrocks> Mirv: sil2100: I think we need to wait for bregma for unity7
[09:04] <didrocks> just handle the rest
[09:05] <sil2100> didrocks: ACK
[09:05] <didrocks> sil2100: Mirv do you manage to track what's release/what's still needed releasing? I don't see a landing ask for tracking that, are you ok?
[09:05] <didrocks> I don't see latest landing ask updated as well, doing
[09:05] <sil2100> didrocks, Mirv: since veebers doesn't seem to be around anymore, I'll merge in the gallery-app 1.4 transition branch manually to avoid CI failures and we can then get someone else fixing the 2 remaining failing tests
[09:05] <didrocks> seems the lxc-android-config from ogra_ landed as well. Updating the spreadsheet
[09:06] <didrocks> sil2100: yep
[09:06] <Mirv> didrocks: isn't it just the patch applied, correctly on top of current ubuntu release?
[09:06] <didrocks> Mirv: no, it's not (for cmake)
[09:07] <didrocks> Mirv: sil2100: do you know what's still needed to be released for autopilot 1.4?
[09:08] <sil2100> I guess Mirv is more up-to-date ^
[09:08] <Mirv> didrocks: I don't think anything has been released yet for AP1.4 to archives. I fixed QA stack in cu2d only this morning, and unity8, and most of the other stacks depend on unity7 getting fixed
[09:09] <psivaa> didrocks: i'll take a look now
[09:09] <sil2100> Mirv: did veebers and thomi prepare 1.4 changes for unity7?
[09:10] <sil2100> didrocks: for sure dialer-app needs fixing... many test failures with 1.4 and no 1.4 AP branch ;/
[09:10] <didrocks> Mirv: sil2100: can you list all the components somewhere, like in the landing spreadsheet so that we can track?
[09:10] <Mirv> sil2100: they didn't have unity7 on their radar it seems, so I'm working as described on the e-mail
[09:10] <didrocks> sil2100: working with upstream?
[09:11] <sil2100> didrocks: will do, but upstream starts later for these components usually, but keeping that on the radar
[09:11] <sil2100> I'll update the Landing Plan
[09:12] <didrocks> thanks
[09:12] <Mirv> didrocks: ok
[09:13] <Mirv> well sil2100 is writing now something, so not interrupting that
[09:13] <sil2100> ;)
[09:13] <sil2100> I'll try listing the components that need 'tweaking and releasing'
[09:16] <Mirv> didrocks: and true, the cmake thing is not completely clean, although the only thing I see is not from applying the added patch is the 12 lines in Tests/CMakeLists.txt
[09:16] <sil2100> Mirv: I updated it a bit, you can add the component status that you handled more or less - I only included unity8 and autopilot from yours, but make sure it's the right status
[09:17] <didrocks> Mirv: yeah, but there are other changes, better to not urge on unity7 anyway
[09:17] <Mirv> sil2100: I don't think autopilot is done if it's not released, or 'done' is maybe not the correct word?
[09:17] <didrocks> yeah, please do not forget anything :)
[09:18] <sil2100> Mirv: right, maybe let's use READY for those
[09:19] <Mirv> sil2100: or maybe ready for testing, I guess we can't release without testing all of that on device?
[09:19] <Mirv> so ready for testing would mean that it's ready in cu2d with 'green light' enough to be tested and after that published from PPA
[09:19] <sil2100> Mirv: indeed! You didn't test it on the phone yet?
[09:19] <sil2100> ACK, sure
[09:19] <didrocks> ogra_: hey, do you know why there is no ubuntu-ui-toolkit in http://people.canonical.com/~ogra/touch-image-stats/20131105.1.changes as well? (this one is image 13, right?)
[09:20] <ogra_> didrocks, reload
[09:20] <didrocks> ogra_: you cheated! :)
[09:20] <Mirv> sil2100: I haven't had time to even attach the phone yet to my computer
[09:20] <ogra_> yep :)
[09:20] <Mirv> sil2100: let alone upgrade it to AP1.4 etc
[09:21] <ogra_> didrocks, for some reason it compared 20131105 again, not 20131105.1 .... i assume something was slow still due to the wider probs last night
[09:21] <sil2100> I need to upgrade it to the new image I guess as well
[09:21] <didrocks> ogra_: ok, thanks for fixing!
[09:21] <ogra_> didrocks, sadly that doesnt make 13 any better :(
[09:21] <didrocks> ogra_: no, I'm unsure what happen, can't wait for psivaa's report :)
[09:22] <ogra_> (the breakage started in 12 though)
[09:31] <didrocks> sil2100: popey: coming?
[09:32] <didrocks> sil2100: we are waiting for you :)
[09:35] <sil2100> AAa!
[09:45] <Mirv> hmm what happened to my hangouts
[09:50] <Mirv> I know a cat was involved but that doesn't explain getting redirected to a hangout error url on retry
[09:51] <Mirv> sil2100: but I guess the meeting was near end, or was there still something / being discussed?
[09:51] <Mirv> eh, now it works
[09:52] <sil2100> Mirv: I guess it's more or less over ;)
[09:53] <ogra_> wow
[09:53] <Mirv> that was a weird error I got into, but animals have the ways of finding interesting key combos
[09:53] <ogra_> so doing a call test for image 13 i just managed to make my Nexus 5 hang hard
[09:54] <ogra_> heh, the kitkat phone app is definitely worse than ours :)
[09:54]  * ogra_ manages to hang it reproducably 
[09:58] <ogra_> wow, and it is unintuitive as hell ... trying to store a contact requires you to jump through plenty of hoops
[10:08] <didrocks> psivaa: is there a way to increase the number of loops in systemsettle idling and rerun against image 13?
[10:09] <didrocks> to check that indicators is going quiet after a while
[10:11] <psivaa> didrocks: let me try that
[10:11] <didrocks> psivaa: maybe try -d 6
[10:11] <didrocks> as for the main run
[10:11] <didrocks> instead of -d 2
[10:13] <Mirv> sil2100: didrocks: releasing ubuntu-ui-toolkit, only change the AP1.4 one and all tests succeed. I'd wish for another to test unity8 since I don't get a full pass with that (3 tests fail)
[10:14] <Mirv> didrocks: pkging ack http://10.97.0.1:8080/view/cu2d/view/Head/view/SDK/job/cu2d-sdk-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+14.04.20131106-0ubuntu1.diff
[10:15] <didrocks> psivaa: can you review and merge that one? https://code.launchpad.net/~didrocks/ubuntu-test-cases/fix-delay/+merge/194095
[10:16] <didrocks> then, if you can retry a full tests on image 13
[10:16] <didrocks> sil2100: are you on unity8?
[10:16] <didrocks> Mirv: +1
[10:17] <psivaa> didrocks:  i'll take a look, -d is the delay in between each iteration and default is 6 though
[10:18] <didrocks> psivaa: yeah, but it's set to 2 for normal app runs
[10:19] <didrocks> and in the global run, we see that they need 3 loops to settle
[10:19] <sil2100> didrocks: if you meant local testing, then yes
[10:20] <didrocks> sil2100: thanks!
[10:26] <Mirv> filed bug #1248477 about the unity8 tests
[10:26] <didrocks> Saviq: ^
[10:26] <didrocks> OSError: [Errno 3] No such process
[10:26] <Saviq> didrocks, yeah, we're talking, didn't happen in autolanding
[10:26] <didrocks> seems a crash?
[10:26] <didrocks> ah ok ;)
[10:26] <Saviq> didrocks, yeah
[10:28] <Mirv> didrocks: for autopilot itself I guess the automatic testing by cu2d is enough?
[10:28] <psivaa> didrocks: making the default run with 6 s delay make the default tests to pass. but default tests are not regressing in between image 11 and 13
[10:28] <didrocks> Mirv: hum, you did run the AP AP tests on the devices, right?
[10:29] <didrocks> psivaa: yeah, we are slower to boot it seems, but I still need a run without the system settle flawing the results
[10:29] <didrocks> psivaa: even if we commit to 6 for a couple of days and then reverting
[10:30] <psivaa> didrocks: ack, makes sense. would you mind making the MP to lp:ubuntu-test-cases/touch rather than lp:ubuntu-test-cases ?
[10:30] <didrocks> psivaa: oh sure!
[10:30] <didrocks> stupid bzr config :p
[10:30] <psivaa> didrocks: thanks :)
[10:31] <didrocks> psivaa: anddddddd https://code.launchpad.net/~didrocks/ubuntu-test-cases/fix-delay/+merge/194099
[10:33] <psivaa> didrocks: approved, thanks
[10:33] <didrocks> psivaa: thanks to you! you will do the rerun?
[10:33] <psivaa> didrocks: sure
[10:34]  * didrocks crosses fingers…
[10:35] <vila> Mirv: hey ! Thanks for https://launchpad.net/ubuntu/+source/glamor-egl/0.5.1-0ubuntu6 !
[10:35] <vila> Mirv: can you explain https://launchpad.net/ubuntu/+source/glamor-egl/0.5.1-0ubuntu6/+publishinghistory to a poor noob ?
[10:37] <Laney> it moved from proposed to release
[10:37] <Laney> as part of https://wiki.ubuntu.com/ProposedMigration
[10:37] <Laney> vila: ^
[10:37] <vila> Laney: that's the expected and usua... let me read that ;)
[10:38] <Laney> yes, that's normal
[10:38] <vila> Laney: but I don't see it when running apt-get update --dry-run on a machine where I want to verify the fix
[10:39] <vila> Laney: ha, but it's us.archive.ubuntu.com
[10:39] <vila> what's the expected delay ?
[10:40] <Laney> rmadison -S -s trusty glamor-egl shows it, so shouldn't be too long before it's mirrored
[10:40] <Laney> you can grab the debs from launchpad if you don't want to wait
[10:41] <vila> Laney: right, thanks for explanations !
[10:43] <psivaa> didrocks: http://reports.qa.ubuntu.com/smokeng/trusty/touch/maguro/13:20131105.1:20131031.1/4909/default/
[10:43] <psivaa> that's the only test that gets affected with the chage
[10:44] <psivaa> s/chage/change
[10:44] <didrocks> psivaa: hum, all tests didn't rerun? only the default one, right?
[10:44] <asac> cwayne: in theory yes, in practice this is not enforced/implemented to full extend yet.
[10:44] <psivaa> didrocks: yes, all the other tests are using -d6 already
[10:44] <asac> cwayne: who should we call if customization test fails?
[10:45] <asac> psivaa: not the other way around?
[10:45] <didrocks> psivaa: hum, we saw -d2 with asac
[10:45] <asac> the default one uses -d6 and the others are using -d2
[10:45] <didrocks> argh, seems you're right: https://jenkins.qa.ubuntu.com/job/trusty-touch-maguro-smoke-friends-app-autopilot/17/console
[10:45] <psivaa> didrocks:  asac: no it's the otherway around. like the link above
[10:45] <didrocks> https://jenkins.qa.ubuntu.com/job/trusty-touch-maguro-smoke-ubuntu-filemanager-app-autopilot/27/console
[10:46] <didrocks> I think we mixed this with asac
[10:46] <asac> well, it feels really odd that we are stricter about time in the default one
[10:46] <asac> compared to the one we run on every test
[10:46] <psivaa> asac: that's now fixed with didrocks 's change :)
[10:47] <psivaa> now every run has 6 s delay
[10:47] <didrocks> asac: ok, so 30s is not enough with the system settle idling
[10:47] <didrocks> psivaa: can you try to increase the number of run, like 10? (I think it's -c10) and run some tests failing?
[10:48] <asac> didrocks: right. so my initial patch was about 10min :0
[10:48] <didrocks> psivaa: we just want to know if we are slower in boot time or it's something else
[10:48] <asac> we should at least give it 2min :)
[10:48] <didrocks> so 20?
[10:48] <asac> who knows what other races might exist
[10:48] <didrocks> 20*6?
[10:48] <didrocks> psivaa: mind trying that? ^
[10:48] <asac> i think i had 10 * 6
[10:48] <psivaa> didrocks: sure will try that as a temp measure. we may need to find why indicator is taking up resources
[10:49] <asac> 10 * 10 * 6
[10:49] <didrocks> psivaa: right, let's see with 10*6 for now. We'll need to dig on the regression
[10:49] <psivaa> didrocks: ack
[10:49] <didrocks> but let's see where we stand for first
[10:49] <didrocks> thanks!
[10:50] <didrocks> libido3 changed
[10:50] <didrocks> it's the only possible guilty for indicators
[10:50] <didrocks> I didn't see a landing ask for it
[10:50] <didrocks> seb128: sil2100: do you know more about it? ^
[10:51] <seb128> didrocks, ido is desktop specific, it's GTK widgets
[10:51] <didrocks> new network-manager as well
[10:51] <didrocks> seb128: it's installed on the touch image though
[10:51] <seb128> didrocks, that seems a bug, let me check why
[10:51] <didrocks> seb128: thanks :)
[10:51] <didrocks> ido or network-manager
[10:51] <seb128> didrocks, it can't work there, there is no GTK-Mir backend
[10:51] <didrocks> as we don't know which indicators is going crazy
[10:52] <sil2100> didrocks: I published it as seb128 and the team asked for it, but ido makes only sense on desktop
[10:53] <didrocks> psivaa: is there a way for you (once you tweaked the value and run this tests) to log into a device and just rerun one test, after having downgraded some packages?
[10:53]  * didrocks feels the indicator we see is indicator-network and it's screwed by network-manager
[10:53] <psivaa> didrocks: yea that's possible, i'm going to run first this with my personal branch
[10:54] <didrocks> yeah ;)
[10:56] <asac> didrocks: so i think the value is not going to help that much
[10:56] <asac> didrocks: what really kills stuff is the timeout here: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/tests/systemsettle/systemsettle-before/tc_control
[10:56] <Mirv> sil2100: what are you testing now?
[10:57] <asac> didrocks: but let me first validate
[10:57] <didrocks> asac: I don't understand how the timeout plays regarding to the command
[10:58] <asac> didrocks: so -d means how many top samples to take for each run ... and not how many top runs in total (thats == 10 and is constrained by the timeout)
[10:58] <didrocks> -c you mean?
[10:58]  * didrocks looks
[10:58] <asac> didrocks: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/tests/systemsettle/systemsettle.sh
[10:58] <didrocks>    echo " -d  seconds to delay between each top iteration (Default: 6)"
[10:58] <didrocks> but yeah, -c won't help
[10:59] <asac> didrocks: so for top run: 0 we basically get -c5 times a top sample of -d6 seconds
[10:59] <didrocks> I don't get why we stop after 5 iterations then
[10:59] <asac> whcih is 30 seconds for each top run
[10:59] <asac> which sums up nicely to top run: 4 for 120 seconds
[10:59] <didrocks> ah, so we are already at this 120s
[10:59] <asac> didrocks: we are getting killed by the timeout
[10:59] <didrocks> ok
[10:59] <asac> http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/tests/systemsettle/systemsettle.sh
[10:59] <asac> http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/files/head:/tests/systemsettle/systemsettle-before/
[10:59] <didrocks> so yeah, sounds like you're right
[10:59] <asac> didrocks: i dont think we do it for default in the same manner
[11:00] <didrocks> yeah, I don't understand why we settle in the default though
[11:00] <didrocks> and not after the reboots
[11:00] <ogra_> bah, that new toolbar behavior is extremely annoying
[11:00] <asac> didrocks: right so the default settle has 720 seconds
[11:00] <asac> didrocks: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/tests/default/systemsettle/tc_control
[11:00] <didrocks> interesting…
[11:00] <asac> didrocks: so its abuot tweaking the timeout
[11:00] <didrocks> to 720s? :)
[11:00] <Mirv> didrocks: I've some errors on autopilot autopilot on device, but I'm not sure what to expect as it has eg. errors on mouse devices / X11
[11:01] <asac> didrocks: in theory yes, but its basically the time we believe is fine until system is good
[11:01] <asac> maybe more like 4 minutes
[11:01] <asac> byut yeah they should be the same
[11:01] <didrocks> asac: do you reproduce locally btw?
[11:01] <asac> brb
[11:01] <didrocks> Mirv: argh, I think write it somewhere, but then, please right it down so that we can get the QA team fixing those
[11:02] <didrocks> Mirv: I meant: publish it still*
[11:02] <didrocks> psivaa: ok, so from what asac told, can you rather try to downgrade network-manager and run an app test?
[11:02]  * ogra_ wonders who decided that crazyness ... seems the toolbar is always expanded when starting an app ... so you have to wait several seconds until you can start typing input if your app has an input field at the bottom
[11:02] <didrocks> just so we see if system settle is still going crazy
[11:03] <didrocks> ogra_: yeah, new toolkit
[11:03] <ogra_> (this is really annoying when trying to use the messaging app)
[11:03] <ogra_> didrocks, right, i would like to know who nods off such stuff ...
[11:04] <psivaa> didrocks: ok, i'm in the middle of couple of runs in each device, once they finish i'll try that
[11:04] <didrocks> ogra_: want a ticket to London? :)
[11:04] <didrocks> psivaa: thanks!
[11:04] <ogra_> didrocks, already have one for jan. :P
[11:04] <didrocks> heh
[11:04] <Mirv> didrocks: ok. then there's the matter of packaging acks http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot-gtk_1.4+14.04.20131106-0ubuntu1.diff + http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot-qt_1.4+14.04.20131106-0ubuntu1.diff +
[11:04] <Mirv> http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot_1.4+14.04.20131106-0ubuntu1.diff + http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_xpathselect_1.4+14.04.20131106-0ubuntu1.diff
[11:04] <ogra_> it fells just half thoughgt throug ... people dont know about the toolbar, so lets put it in their face all the time ...
[11:04] <ogra_> *feels
[11:05] <didrocks> Mirv: for xpathselect, the soname changed? (no common file installed between 1.3 and 1.4?)
[11:06] <ogra_> do people actually USE the phone before deciding such things ?
[11:06] <ogra_> (sorry, i'll stop ranting now)
[11:06] <Mirv> didrocks: yes, it's so.1.3 now
[11:06] <didrocks> so.1.4 you meant? :)
[11:06] <Mirv> didrocks: 1.4 :)
[11:06] <didrocks> ok
[11:06] <didrocks> -               python-autopilot,
[11:06] <didrocks> +               autopilot-desktop (>= 1.4),
[11:06] <didrocks> that sounds wrong to me to bind autopilot-gtk to X
[11:06] <didrocks> and desktop
[11:07] <didrocks> with bamf and anything
[11:07] <didrocks> Mirv: I won't block on it, but do you mind pinging upstream about it?
[11:07] <didrocks> + python-autopilot (>= 1.4) | python3-autopilot (>= 1.4),
[11:07] <didrocks> as well, in autopilot-gtk -> tabs vs spaces, fixing?
[11:07] <Mirv> didrocks: it's build depend only
[11:07] <Saviq> didrocks, Mirv's ~phablet/autopilot was messing with him
[11:07] <Saviq> didrocks, u8 is 100%
[11:08] <didrocks> Saviq: sorry, what do you mean?
[11:08] <Mirv> didrocks: ok, fixing
[11:08] <Mirv> didrocks: he means that u8 is ok, I'll publish it too later
[11:08] <Saviq> didrocks, the click autopilot script installs stuff into ~phablet/autopilot
[11:08] <didrocks> Mirv: same in autopilot-qt (tab vs space)
[11:08] <Saviq> didrocks, and that takes precedence before a .deb install
[11:09] <Saviq> didrocks, so if you don't clean that up, you might be running some unmatched suites
[11:09] <didrocks> Saviq: so the click script installed AP 1.3?
[11:09] <didrocks> locally?
[11:09] <Saviq> didrocks, not ap itself, but old unity8's suite most probably
[11:10]  * didrocks doesn't understand, what command exactly installed those? (I think we are only testing click for click packages, not unity8)
[11:10] <didrocks> or when you test a click package, it's running unity8 AP tests as well?
[11:10] <didrocks> (and so install them)
[11:11] <Mirv> didrocks: click-test-setup downloads unity8 autopilot tests always, and if they linger in /home/phablet/autopilot the .deb tests are ignored
[11:11] <didrocks> that's why we need to clean up this click vs debs tests mess
[11:12] <Saviq> didrocks, +1
[11:12] <sil2100> didrocks: in unity8 there are 3 tests constantly failing locally, mostly notification-related - should I publish unity8 anyway?
[11:12] <sil2100> Saviq: ^
[11:12] <Saviq> sil2100, read up
[11:12] <didrocks> sil2100: you are lagging dude :)
[11:12] <sil2100> No one pinged me so I didn't read ;p
[11:12]  * sil2100 reads up
[11:13] <sil2100> Mirv: as for what I'm working on, I always update the Landing Plan on what I am working on ;)
[11:14] <sil2100> Mirv: so just look for 'sil2100'
[11:14] <Mirv> sil2100: yeah I looked it up, but there was nothing at that time
[11:14] <didrocks> Mirv: and +1 on autopilot
[11:15] <didrocks> Mirv: so all good
[11:15] <sil2100> Mirv: I'm sure it was, as I changed it some time before your question I guess!
[11:17] <Mirv> didrocks: ok, not sure, but I didn't see that unity8 note until now. but I'd guess you've also /home/phablet/autopilot messing up things, as I now had the tests passing
[11:17] <Mirv> sil2100: to you ^
[11:17] <Mirv> didrocks: ignore :)
[11:17]  * didrocks is always happy to ignore
[11:18] <sil2100> Mirv: oh, excellent then
[11:19] <sil2100> Mirv: I'll maybe check mediaplayer-app and camera-app in the meantime
[11:19] <sil2100> ...or are those click packages now?
[11:20] <Mirv> sil2100: alright, I need to eat a late lunch anyhow at some point
[11:20] <sil2100> Since I really get a bit confused with all of this already
[11:20] <Mirv> sil2100: those are not
[11:24] <sil2100> Ok, camera-app requires fixing as well...
[11:24] <sil2100> No merge in sight
[11:25] <didrocks> sil2100: test failing? the 1.4 branch was not merged?
[11:26] <sil2100> There is no 1.4 branch
[11:26] <didrocks> sil2100: http://pad.ubuntu.com/autopilot-1-4
[11:26] <didrocks> sil2100: seems no porting was needed for that one
[11:26] <sil2100> Nothing got merged, no branch prepared, and 3 failures
[11:26] <sil2100> Well, I get reproducible 3 failures all the time
[11:27] <sil2100> Maybe something in my config screws up things, I'll check
[11:27] <didrocks> (that's why I didn't list it yesterday)
[11:27] <didrocks> psivaa: did you get a chance to have this run done?
[11:27] <didrocks> (just one one app test at least)
[11:28] <psivaa> didrocks: just in the process of downgrading nm, it has a lot of dependencies with it
[11:29] <sil2100> didrocks: no matter how many times I run it, I always get the same 3 failures sadly, related to DBus introspection - so I guess it needs some 1.4 porting?
[11:29] <sil2100> StateNotFoundError: State not found for class 'Rectangle' and filters {'objectName': 'main'}.
[11:29] <didrocks> sil2100: probably yeah, please note it
[11:31] <sil2100> didrocks: mediaplayer-app is fine as it is, so nothing needed here
[11:31] <didrocks> great
[11:32] <didrocks> sil2100: it seems we needs friends as well
[11:32] <didrocks> sil2100: but they did push other commits than the 1.4 transition, right? :/
[11:32] <didrocks> ah, it's friends-app, not friends
[11:33] <sil2100> didrocks: for friends-app you mean?
[11:33] <sil2100> didrocks: it just has the transition
[11:33] <didrocks> yeah, we're fine :)
[11:33] <sil2100> didrocks: is it tested or should I test it now?
[11:33] <didrocks> Mirv: you wrote unity8 and ubuntu-ui-toolkit published, I don't see them in -changes?
[11:33] <didrocks> sil2100: I guess you need to test it
[11:34] <sil2100> No problemo
[11:34] <didrocks> Mirv: also, do you have the bug report for AP desktop tests failing?
[11:35] <didrocks> sil2100: please open one for camera-app
[11:36]  * didrocks sees ubuntu-ui-toolkit, but not unity8
[11:36] <sil2100> didrocks: ACK, friends clean and ready for release, I'll push it out in a moment
[11:37] <didrocks> sil2100: great!
[11:38] <Mirv> didrocks: unity8 should be right there in a ~minute. I found bug #1211140 for autopilot
[11:39] <didrocks> Mirv: ok, thanks
[11:40] <didrocks> Mirv: hum this bug is not what you see, right?
[11:40] <didrocks> Mirv: you told that it's failing on the desktop, not on the device?
[11:40] <Mirv> didrocks: no, failing on device was what I was talking about
[11:40] <Mirv> desktop ok
[11:41] <didrocks> Mirv: oh, so AP tests (without that package installed) pass on the device?
[11:41] <didrocks> or AP tests themselves are all failing?
[11:41] <Mirv> didrocks: some of AP's own AP tests fail on device, citing X11 errors and such
[11:41] <didrocks> ok
[11:42] <psivaa> didrocks: calendar app tests which regressed in image 12 is being run with downgraded n-m in maguro. let you know the outcome
[11:43] <didrocks> psivaa: crossing fingers!
[11:43] <sil2100> didrocks: hm, I'd like to publish friends-app, but the friends stack is waitonstacks - should I wait for platform to finish, or should I just abort waitonstacks and force a publish?
[11:43] <didrocks> sil2100: no, as long as it's waitonstacks, you can force a publish (withut stopping it)
[11:43] <didrocks> it's going to publish previous run
[11:44] <sil2100> didrocks: right, but I wanted to first do a 'not-forced publish' to see if there are packaging changes - but I guess I'll just check the latest trunk commit
[11:44] <sil2100> So right
[11:44] <sil2100> ;)
[11:44] <sil2100> didrocks: packaging ACK needed! http://bazaar.launchpad.net/~super-friends/friends-app/trunk/revision/115
[11:44] <sil2100> ;p
[11:44] <didrocks> sil2100: +1
[11:47] <sil2100> didrocks: sadly it's still waiting on waitonstacks to finish ?!
[11:47] <didrocks> sil2100: do you have a bug for the test failures on camera-app?
[11:47] <didrocks> sil2100: hum, let me look
[11:47] <sil2100> http://10.97.0.1:8080/view/cu2d/view/Head/view/Friends/job/cu2d-friends-head/343/parameters/?
[11:48] <sil2100> And the console says it's waiting for onwaitforstacks
[11:48] <didrocks> sil2100: it's just a viewing artefact
[11:48] <didrocks> sil2100: http://10.97.0.1:8080/job/cu2d-friends-head-3.0publish/
[11:48] <didrocks> see it ran
[11:48] <sil2100> http://10.97.0.1:8080/job/cu2d-friends-head-3.0publish/307/
[11:49] <didrocks> hum no
[11:49] <sil2100> Not sure, it says 21hrs ago?
[11:49] <didrocks> it didn't
[11:49] <didrocks> wth, it worked before, right?
[11:49] <sil2100> Yes!
[11:49] <sil2100> Not sure when it regressed and stopped working even
[11:49] <didrocks> sil2100: ok, let me kill the previous run then
[11:49] <vila> didrocks: remember http://10.97.0.1:8080/job/otto-test-radeon ? I have a gut feeling the default parameters have to adjusted to fix http://10.97.0.1:8080/job/otto-test-radeon/label=qa-radeon-7750/11/console
[11:50] <vila> didrocks: I'm trying to verify the fix for radeon and run into a bunch of accumulated issues (including having to revert the kernel so at least we'll have a reproducing env for that ;)
[11:51] <didrocks> vila: yeah, liblttng-ust0 migrated, you should take the latest parameters
[11:51] <didrocks> vila: remove it from the package list, it will tell you what's needed then
[11:52] <didrocks> sil2100: ok, publishing
[11:52] <didrocks> sil2100: I don't know why it doesn't work anymore, like if someone put a lock again on the jobs and no concurrent build can happen
[11:52] <sil2100> didrocks: thanks!
[11:52] <sil2100> hmm, didn't hear anyone mention a modification to that
[11:52] <didrocks>   <concurrentBuild>true</concurrentBuild>
[11:53] <didrocks> sil2100: and the config of the job is telling concurrentBuild is allowed on waitonstack
[11:53] <didrocks> sil2100: maybe a jenkins regression?
[11:58] <sil2100> Maybe? But I would find that rather unlikely
[11:58] <didrocks> psivaa: so, it seems that calendar-app isn't better on mako?
[11:58] <Saviq> sil2100, didrocks, Mirv, can we start merging into unity8 again?
[11:58] <didrocks> still this insane system settling idle?
[11:59] <didrocks> Saviq: not as long as we don't have an image showing 100% for unity8
[11:59] <psivaa> didrocks: the downgraded n-m is only on maguro, at least systemsettle failures have gone with the old n-m
[11:59] <didrocks> Saviq: will take some hours still
[11:59] <Saviq> didrocks, ok
[11:59] <didrocks> psivaa: ah ok :)
[11:59] <didrocks> psivaa: really \o/
[11:59] <didrocks> psivaa: you are relaunching everything with that downgrade?
[11:59]  * Saviq merges the changelog update then
[12:00] <psivaa> didrocks: one by one i'm doing that
[12:00] <didrocks> psivaa: can you try on mako as well and give us the list of what you downgraded exactly?
[12:00] <didrocks> psivaa: I'm considering backing it out from trusty
[12:00] <psivaa> didrocks: in the process on mako
[12:02] <sergiusens> didrocks, should I just get the latest click apps in the store and hope for the best? or how do I get ap 1.4 on my image which I guess has to be read write
[12:03] <didrocks> sergiusens: if you can run the tests, would be awesome so that we know where we stands. But as we started the transition, we have no other way than pushing everything I guess
[12:04] <didrocks> sergiusens: we saw that some 1.4-compatible branches were not merge btw, you need to ensure that I guess
[12:04] <sergiusens> ok, I x-check the branches
[12:04] <didrocks> sergiusens: thanks :)
[12:05] <vila> Mirv, didrocks: http://10.97.0.1:8080/job/otto-test-radeon/label=qa-radeon-7750/13/ -91, not bad
[12:05] <vila> 13 is my lucky number ;)
[12:05] <didrocks> vila: heh ;)
[12:05] <didrocks> nice!
[12:06] <vila> didrocks: so, let's say the radeon issue is fixed but I won't re-provision it so we have a reproducing host for the kernel issue ?
[12:06] <didrocks> psivaa: were all your revert only part of network-manager source package?
[12:06] <didrocks> vila: exactly
[12:06] <didrocks> vila: so now, you should sync with leann I guess
[12:06] <didrocks> for the kernel part
[12:07] <psivaa> didrocks: i'm downgradeing all of them in https://launchpad.net/ubuntu/+source/network-manager/0.9.8.4-0ubuntu3/+build/5203185
[12:07] <vila> didrocks: will need to document all the tweaks I did for the radeon verification first (or that knowledge will be lost)
[12:08] <vila> didrocks: but yeah, that's the idea
[12:08] <didrocks> psivaa: ok, great, no other dependencies!
[12:08] <didrocks> vila: indeed
[12:08] <psivaa> didrocks: yes
[12:09]  * vila lunches &
[12:10] <Mirv> vila: ok!
[12:13] <psivaa> didrocks: there is a systemsettle failure even with downgraded n-m in http://10.97.0.1:8080/job/trusty-touch-maguro-smoke-ubuntu-system-settings-online-accounts-autopilot/11/artifact/clientlogs/top_before.log/*view*/
[12:13] <psivaa> this time ofono appears the reason
[12:14] <didrocks> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
[12:14] <didrocks> 1748 phablet 20 0 128752 95104 3872 S 57.6 13.4 1:06.43 indicator-+
[12:15] <didrocks> psivaa: so indicator is still on top?
[12:16] <didrocks> psivaa: can you try to downgrade libido3-0.1-0?
[12:17] <psivaa> didrocks: ok, i'll try that
[12:23] <sergiusens> didrocks, terminal app doesn't have code updates or an MR for it, was it not needed?
[12:23] <sergiusens> the upadte that is
[12:24] <didrocks> sergiusens: http://pad.ubuntu.com/autopilot-1-4
[12:24] <didrocks> seems they say no update code was needed
[12:25] <sergiusens> didrocks, ack; forget the pad; just bothers me it needs auth every hour or so :-)
[12:25] <sergiusens> sorry
[12:25] <sergiusens> as in *I forget the pad*
[12:25] <didrocks> heh, no owrry ;)
[12:25] <didrocks> worry*
[13:00] <Mirv> sil2100: what was the problem with camera-app?
[13:01] <sil2100> Mirv: 3 tests are failing all the time: https://bugs.launchpad.net/camera-app/+bug/1248495
[13:01] <sil2100> Mirv: so it seems it needs to be fixed for 1.4
[13:01] <sil2100> I'll try doing that in a moment
[13:02] <Mirv> sil2100: hmm, ok, it was just marked as not needing changes so then that's wrong info
[13:02] <sil2100> Mirv: yes, we saw that with didrocks, but it doesn't seem to be the case
[13:03]  * didrocks asks once again to have a bug to sil2100
[13:03] <Mirv> sil2100: yep, updated the pad
[13:05] <sil2100> didrocks: made a bug
[13:05] <sil2100> didrocks: ^
[13:05] <didrocks> sil2100: link?
[13:05] <sil2100> https://bugs.launchpad.net/camera-app/+bug/1248495
[13:05] <didrocks> thanks
[13:05] <sil2100> I pasted it to Mirv just now ;p
[13:05] <didrocks> wasn't pinged
[13:07] <sil2100> Damn, ubuntu-keyboard merge is failing to merge for reasons unknown to me
[13:07] <sil2100> Like FTBFS
[13:14] <cwayne> asac: you should call me if customization fails
[13:16] <cwayne> asac: so we plan on having it gating, but it's not quite there yet?  (again, just trying to gauge exactly where we are :) )
[13:31] <sergiusens> didrocks, forgot to ask, where's ap 1.4?
[13:31] <didrocks> sergiusens: in trusty
[13:31] <sergiusens> didrocks, oh, great
[13:31] <didrocks> sergiusens: you have ap 1.4, ap-gtk, ap-qt and xpathselect
[13:32] <sergiusens> didrocks, but latest trusty-proposed image doesn't have it and we are blocking a build until everything is in, right?
[13:32] <didrocks> sergiusens: exactly
[13:33] <sergiusens> ack
[13:40] <zyga> doanac: hey
[13:43] <sergiusens> didrocks, is it stuck in proposed? http://paste.ubuntu.com/6370521/
[13:43] <didrocks> sergiusens: it is (the transition isn't finished). I guess Mirv/sil2100 are looking into it
[13:43] <didrocks> as they published it
[13:44] <didrocks> sergiusens: it's a good thing that it's blocked in proposed btw
[13:44] <didrocks> so that we can investigate on the other issue
[13:44] <sergiusens> didrocks, ok, I think I should hold back on the clicks since rolling back is not as easy
[13:44] <sil2100> I guess Mirv pushed it, I'm still poking/fixing to get the other branches 1.4-able
[13:45] <sergiusens> that is, I'll test what's there, but won't put them in the store
[13:45] <didrocks> sergiusens: well, how long is it for you to push?
[13:45] <didrocks> sergiusens: there is no more rolling back for us, so you can push
[13:46] <sergiusens> didrocks, not much; the packages just need an approver and I have popey hooked to that task ;-)
[13:48] <sergiusens> didrocks, the testing part is the slow part ;-)
[13:48] <didrocks> sergiusens: can you get me a summary of what failed then?
[13:48] <didrocks> so that we can hook up the QA team before they see the failures
[13:48] <sergiusens> didrocks, yeah, let me install ap first ;-)
[13:49] <sergiusens> didrocks, going to do same thing as yesterday if that's ok
[13:49] <Mirv> yep AP1.4 is still in -proposed
[13:49] <didrocks> sergiusens: sure! but in any case: the tests will be broken if you don't push, so please push
[13:50] <didrocks> Mirv: are you working on it?
[13:50] <sergiusens> didrocks, ah, what's the ETA for a new image?
[13:50] <sil2100> camera-app fixed, preparing merge
[13:50] <didrocks> sergiusens: I would have hoped in the next couple of hours, but I'm afraid that won't happen
[13:50] <sergiusens> didrocks, might as well circle back with QA if tests fail right?
[13:50] <sergiusens> didrocks, well, it's chicken and egg; I'll push anyways
[13:50] <didrocks> sergiusens: yeah, but anyway, they will fail if you don't push latest :)
[13:50] <didrocks> sergiusens: so better to show "those are the real failures"
[13:50] <didrocks> "please fix it now" :p
[13:52] <didrocks> Mirv: so what's getting AP stuck in proposed? (again, that's fortunate in some way, enabling us to run the tests right now still against image 13°
[13:53] <Mirv> didrocks: I was waiting for normal migration. it's mentioned at a valid candidate on the other page, but I don't know to read http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt regarding it.
[13:54] <didrocks> Mirv: yeah, the valid candidate on the other page is always giving trouble to people
[13:54] <didrocks> I think cjwatson wrote a page on the migration, one sec
[13:55] <didrocks> Mirv: https://wiki.ubuntu.com/ProposedMigration
[13:56] <cjwatson> the line to read is
[13:56] <cjwatson>     * i386: cordova-ubuntu-autopilot, ubuntu-keyboard-autopilot, unity-autopilot, unity-webapps-qml-autopilot
[13:57] <cjwatson> After "leading: xpathselect,autopilot-gtk,autopilot-qt,autopilot,unity8,friends-app,ubuntu-ui-toolkit" - which means that p-m tried that set and discovered that the list of packages above is newly uninstallable on i386 after doing so
[13:57] <fginther> morning
[13:57] <cjwatson> None of the source packages for those binaries is even listed in excuses, which likely means they still need uploads to transition them to the new AP
[13:59] <Mirv> ok, so under the 'Apparently successful'
[14:00] <Mirv> those packages seem to use the 'libautopilot-qt (<< 1.4)' unfortunately
[14:00] <cjwatson> "Apparently successful" refers to what comes above it
[14:00] <cjwatson> The block is actually from "Trying easy from autohinter: xpathselect/..." to "FAILED"
[14:00] <cjwatson> cyphermox was going to propose a branch to rearrange the newlines so that that's clearer, I think
[14:00] <Mirv> aha, right
[14:01] <Mirv> well, I'm branching now those to propose changes to the dependencies
[14:01]  * cjwatson goes back to being on holiday
[14:08] <Mirv> ubuntu-keyboard has the branch already, unity needs bregma to readjust cmake + merge my branch to make a new release. not sure yet what cordova-ubuntu-tests + unity-webapps-qml would need, but I added "Unblocking AP 1.4 from -proposed" to the pad.ubuntu.com/autopilot-1-4
[14:10] <sil2100> Right, ubuntu-keyboard is merging, camera-app is merging as well, gallery-app is being worked on (CI checking the merge), dialer-app still needs attention I guess
[14:10] <sil2100> About dialer-app I poked boiko but I guess bfiller could help as well
[14:10] <bregma> Mirv, the patch to cmake is working its way through the system:  if you're in a hurry, back out the broken version of cmake from -proposed
[14:12] <Mirv> bregma: I had the problem with release pocket make as well
[14:12] <Mirv> bregma: didrocks mentioned your cmake branch was touching some file(s) outside of the patch
[14:12] <bfiller> sil2100: what is the issue with dialer-app?
[14:14] <sil2100> bfiller: hi! It hasn't been re-written yet to 1.4 and tests are failing, let me get a bug
[14:15] <Mirv> sil2100: can you continue with the "Unblocking AP 1.4 from -proposed" from the pad?
[14:16] <Mirv> sil2100: and maybe toss cordova at least to robru
[14:16] <Mirv> sil2100: only ubuntu-keyboard really had the << 1.4, I'm not sure why the other show up as uninstallable - I've now AP 1.4 on desktop + installed all of cordova-ubuntu-autopilot, unity-autopilot and unity-webapps-qml-autopilot without issues
[14:17] <sil2100> bfiller: https://bugs.launchpad.net/dialer-app/+bug/1248553
[14:18] <sil2100> Mirv: I'll move on to that once I finish coordinating these fixes/merges, let me open the pad again
[14:19] <didrocks> bregma: failed on pbuilder btw
[14:19] <didrocks> I meant
[14:19] <didrocks> passed on my pbuilder
[14:20] <didrocks> FTBFS in proposed
[14:20] <didrocks> bregma: https://launchpadlibrarian.net/155964101/buildlog_ubuntu-trusty-arm64.cmake_2.8.12-0ubuntu2_FAILEDTOBUILD.txt.gz
[14:20] <didrocks> arm64
[14:20] <didrocks> but I guess that won't block it
[14:20] <didrocks> (should pass on others)
[14:21] <didrocks> almost done on i386
[14:21] <Mirv> didrocks: great!
[14:21] <bregma> I don;t think an ICE on arm64 is the fault of my patch
[14:22] <Mirv> bregma: so after cmake is in, then https://code.launchpad.net/~timo-jyrinki/unity/xpathselect-1.4/+merge/194077 is what I had unity building again. it has trevinho's branch merged.
[14:23] <Mirv> sil2100: ah, found the reason, needs just recompile I think
[14:23] <bregma> Mirv, as soon as jenkins is happy with that merge we can globally approve it
[14:24] <bregma> we've got a Nux ABI change pending, so we need to get this straightened out
[14:24] <didrocks> bregma: can you backout the ABI change?
[14:25] <didrocks> so that we just unblock unity
[14:25] <didrocks> and not having a transition on top of a transtion :p
[14:25] <didrocks> transition*
[14:25] <bregma> see, this is why we need a separate dev branch
[14:25] <didrocks> this is already so messy and crazy, I would appreciate any small help
[14:27] <sil2100> It's like a dream inside a dream inside a nightmare
[14:27] <sil2100> Intransitionepcion
[14:28] <Mirv> sil2100: didrocks: ok I launched no-change rebuilds in cu2d of cordova-ubuntu-tests and unity-webapps-qml. please publish when they're ready, and together with unity ^ and ubuntu-keyboard AP 1.4 should be unblocked. I need to go now.
[14:28] <sil2100> \o/
[14:28] <bregma> nothing has been merged into Unity because of the cmake bug, if we stop that pending merge asnd you don't build (or use) the newest Nux and Compiz, there should be no effect
[14:29] <sil2100> Mirv: thanks! Bye!
[14:29] <bregma> can you do that easily?
[14:29] <didrocks> sil2100: can you remove nux frmo the ppa?
[14:29] <didrocks> so that we don't pick it
[14:29] <didrocks> and once we can rebuild unity, we'll be fine
[14:29] <sil2100> didrocks: ACK
[14:31] <sil2100> didrocks: ok, nux removed, let's make sure we only rebuild unity when it's ready
[14:31] <didrocks> yeah
[14:31] <didrocks> Mirv: have a good evening
[14:34] <bregma> sil2100, also remove compiz from the PPA, just in case
[14:34] <didrocks> yeah, nice idea
[14:34] <bregma> we need only one degree of freedom for this transition
[14:36] <sil2100> bregma, didrocks: done
[14:37] <didrocks> sil2100: thanks
[14:38] <sil2100> Rebuilding ubuntu-keyboard
[14:48] <sergiusens> didrocks, http://paste.ubuntu.com/6370857/
[14:49] <didrocks> sergiusens: stockticker and sudoku coming?
[14:49] <didrocks> or the x means you can't merge them?
[14:49] <sergiusens> didrocks, [x] is bad :-)
[14:49] <sergiusens> fromt he legend above
[14:49] <sergiusens> didrocks, trunk doesn't have the ap 1.4 stuff yet
[14:49] <didrocks> sergiusens: ok, you are working with upstream to get that merged?
[14:50] <sergiusens> didrocks, am I responsible for that?
[14:50] <didrocks> sergiusens: not sure, balloons maybe?
[14:50] <sergiusens> didrocks, I would rather have QA deal with that
[14:50] <didrocks> sergiusens: balloons seems to be the core apps team linking
[14:50] <sergiusens> since it's their transition
[14:51] <didrocks> sergiusens: TBH, I would rather having QA dealing with everything for that transition. As you can see, we need to push ourself :/
[14:51] <sergiusens> didrocks, tb(more)h, I would of just blocked ap 1.4 until it were backwards compatible
[14:52] <didrocks> sergiusens: wasn't my decision…
[14:52] <sergiusens> didrocks, I know :-)
[14:52] <didrocks> sergiusens: but nice! most of the work is done :)
[14:52] <didrocks> balloons: can you handle the 2 last branches
[14:52] <didrocks> thanks sergiusens
[14:52] <sergiusens> didrocks, calendar needs work too
[14:53] <sergiusens> np
[15:05] <fginther> sil2100, can you review: https://code.launchpad.net/~fginther/cupstream2distro-config/remove-phone-app/+merge/194162
[15:05] <sil2100> fginther: with pleasure, it's been haunting us in cu2d for a while now
[15:07] <cwayne> asac: ping
[15:07] <sil2100> fginther: approved
[15:09] <fginther> sil2100, thanks
[15:11] <doanac> zyga: hey
[15:12] <zyga> doanac: can you tell me more about this channel
[15:12] <zyga> doanac: how is this different from ubuntu-qa?
[15:15] <doanac> zyga: might be easier to read about the two teams. A decision was made a few months ago to split responsibilities between a QA team and a CI team:
[15:15] <doanac> https://wiki.canonical.com/UbuntuEngineering/CI/
[15:15] <doanac> https://wiki.canonical.com/UbuntuEngineering/QA/
[15:19] <zyga> doanac: interesting, thanks
[15:24] <sil2100> didrocks: should I test the AP 1.4 ubuntu-keyboard tests on my phone or should I not bother with it right now? As we're not running those tests anywhere right now from what I see
[15:25] <sil2100> And by publishing ubuntu-keyboard now we'll be closer to unblocking AP 1.4
[15:26] <didrocks> sil2100: can you still try to run it?
[15:26] <sil2100> didrocks: will do my best then
[15:27] <didrocks> thanks
[15:34] <sergiusens> didrocks, ping me if I get distracted; I'm going to go back to the emulator work
[15:35] <didrocks> sergiusens: yeah, I think it's fine from your side
[15:41] <sil2100> didrocks: in the meantime, can I maybe publish the webapps bits? Like cordova and unity-webapps-qml?
[15:41] <sil2100> didrocks: since the ubuntu-keyboard deal is a bit more complicated for unknown reasons
[15:42] <sil2100> didrocks: but ubuntu-keyboard tests were always a bunch of trouble ;/
[15:43] <didrocks> sil2100: ok, fine then
[16:06] <cjwatson> didrocks: the cmake/arm64 failure would block it because it was previously built on arm64.  However I've retried since that's just an unreliable-hardware problem
[16:12] <didrocks> cjwatson: thanks
[16:24] <didrocks> sil2100: where do we stand? unity7 handled as well? nothing else blocking AP?
[16:25] <sil2100> didrocks: the required unity7 merge is in the process of reviewing by Chris
[16:25] <sil2100> didrocks: now I'm testing gallery-app for publishing as well
[16:28] <sil2100> didrocks: it seems that from the 'big guys' only unity7 is left - once I publish gallery-app, there's also dialer-app with failures, but I guess that can be fixed pretty soon
[16:29] <didrocks> sil2100: this is blocking AP 1.4 moving to the release pocket as well, right?
[16:32] <sil2100> didrocks: sadly yes... it's a blocker, but the merge that needs to be approved is a bit big, as it's the xpathselect-1.4 changer
[16:32] <sil2100> didrocks: oh, it's approved now
[16:33] <sil2100> Ok, I think I need to update myself on the unity7 issue, as Chris says there's still the cmake issue going on... Thought it was resolved already
[16:33] <didrocks> hum, weird?
[16:35] <sil2100> Just checked, Chris was a bit wrong, as it's in -proposed
[16:40] <didrocks> great
[16:41] <didrocks> sil2100: should we juts disable automated cu2d builds?
[16:41] <didrocks> I guess we don't want nux/compiz to build
[16:44] <ev> didrocks: does https://blueprints.launchpad.net/ubuntu/+spec/core-1311-developing-process-definition need to be proposed for vuds?
[16:45] <didrocks> ev: I guess it's a little bit too early, let's have a first CI system and then we can work on the process
[16:45] <sil2100> didrocks: good idea! How can we do that?
[16:45]  * sil2100 never done that
[16:45] <ev> didrocks: :) sure
[16:46] <didrocks> sil2100: juts disabling the build head_all job
[16:46] <didrocks> sil2100: look at it, for future reference (just did it)
[16:46] <robru> Mirv, what about cordova?
[16:46] <sil2100> Right
[16:47] <sil2100> robru: published, all is in the Landing Ask I guess
[16:47] <sil2100> didrocks: ok, see it, thanks
[17:02] <didrocks> sil2100: cyphermox: plars: psivaa: kenvandine: coming?
[17:02] <plars> didrocks: yes, brt
[17:02] <sil2100> Yes
[17:02] <kenvandine> didrocks, just a moment, wrapping up another call
[17:03] <psivaa> didrocks: i dont normally attend the afternoon meetings but could do if needed
[17:03] <sil2100> Damn, my system is really laggy
[17:03] <cyphermox> shortly... I'm reproducng hte bug now...
[17:03] <didrocks> psivaa: for that one, please :)
[17:04] <psivaa> didrocks: ack, i'll need the link to the ho
[17:04] <psivaa> :)
[17:04] <didrocks> psivaa: https://plus.google.com/hangouts/_/calendar/Y2Fub25pY2FsLmNvbV91cTRvNmQyMWJvNmJ0bm1mcW9xZWtsNTdnOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t.cg7k3h1nmqml7psc1nn68223i0
[17:04] <fginther> cjwatson, After reading https://bugs.launchpad.net/ubuntu/+source/click/+bug/1225023, it appears you know a way to remove a click package. Is this true?
[17:22] <kenvandine> at least share-app hasn't been ported to 1.4, so it's blocking autopilot
[17:22] <kenvandine> maybe more...
[17:22]  * kenvandine creates a full list
[17:24] <sil2100> kenvandine: share-app is a click package, right?
[17:24] <robru> sil2100, what was the merge for dialer-app you were talking about?
[17:25] <sil2100> robru: ah, ok, so: https://bugs.launchpad.net/dialer-app/+bug/1248553 <- no merge yet, but boiko told me he's working on this
[17:25] <sil2100> robru: if he's EOD, it would be nice to find someone else
[17:25] <robru> sil2100, oh, ok, so I just have to wait for that and then make sure it lands when boiko is done?
[17:26] <sil2100> robru: yes, or if boiko doesn't manage to finish it, maybe poke someone from the AP guys to get it fixed
[17:31] <kenvandine> sil2100, no, it has been removed from the image
[17:32] <sil2100> kenvandine: ah, since I have been wondering, since share-app wasn't built in cu2d for quite a while
[17:33] <kenvandine> http://paste.ubuntu.com/6371704/
[17:35] <kenvandine> sil2100, looks like a bunch of packages that depend on autopilot that haven't landed in trusty-proposed
[17:35] <kenvandine> as well as one package that needs to go away
[17:35] <kenvandine> and notes-app which is now click
[17:35] <sil2100> kenvandine: those didn't need the new AP
[17:35] <kenvandine> so i guess that needs to get removed too
[17:35] <sil2100> I mean
[17:35] <kenvandine> oh?
[17:35] <kenvandine> no change required?
[17:36] <sil2100> kenvandine: messaging-app didn't need releasing, because no changes were required
[17:36] <sil2100> dialer-app is being worked on
[17:36] <sil2100> address-book-app also didn't need changing
[17:36] <sil2100> There's a list for that actually!
[17:36] <sil2100> kenvandine: anyway, unity-webapps-qml-autopilot and cordova-ubuntu-autopilot also seemed fine I guess
[17:37] <sil2100> Timo checked those
[17:37] <kenvandine> ok
[17:37] <sil2100> kenvandine: you can see what we did on the Landing Asks
[17:37] <kenvandine> something out of this list is causing it to choke
[17:37] <sil2100> Maybe unity-autopilot
[17:37] <sil2100> hmmm
[17:38] <kenvandine> libxpathselect1.3
[17:38] <kenvandine> bingo
[17:39] <kenvandine> unity-autopilot depends on that
[17:39] <sil2100> Right!
[17:39] <kenvandine> i think that is the only thing
[17:39] <sil2100> This will be fixed in a moment then :)
[17:39] <kenvandine> great
[17:39] <kenvandine> :)
[17:39] <sil2100> Thanks for looking into that!
[17:39] <kenvandine> the rest are fine
[17:39] <kenvandine> no problem
[17:40] <sil2100> Now we know that unity is the source of all evil
[17:40] <sil2100> 3vil
[17:41] <plars> didrocks: if all else fails on the networkmanager spam/cpu usage issue, we could remove the sim card from that phone
[17:41] <didrocks> plars: yeah, maybe check with cyphermox
[17:41] <didrocks> plars: is having a SIM card is new on those phones?
[17:42] <didrocks> maybe it's something external which triggered that issue
[17:42] <didrocks> not sure if ev would know…
[17:42] <plars> sil2100:  kenvandine: there's a patch to remove the unity-autopilot dep from cordova-ubuntu-autopilot
[17:42] <plars> didrocks: no, it's been there for a while
[17:43] <plars> https://code.launchpad.net/~robru/cordova-ubuntu-tests/drop-unity-autopilot/+merge/194046
[17:43] <ev> if I would know if these phones recently have had a sim card inserted into them?
[17:43] <cyphermox> don't bother to change anything with the sim card, it has nothing to do with the problem at hand
[17:43] <plars> ev: they have not - they have had sim cards for a while
[17:43] <didrocks> ev: or if something else changed in the DC
[17:43] <plars> cyphermox: ok
[17:44] <cyphermox> why are you mentioning the SIM cards though?
[17:44] <cyphermox> was something pointing to that that I have not noticed?
[17:44] <robru> plars, yes, i want to test that merge a little bit further before landing it
[18:05] <sil2100> eeeh
[18:05] <sil2100> cu2d for unity seems b0rken
[18:05] <sil2100> kenvandine: since Didier is not around, I'll try redeploying the unity stack
[18:06] <sil2100> kenvandine: since I cannot force cu2d to re-run just with the unity component ;/
[18:08] <kenvandine> ok
[18:23] <sil2100> kenvandine: still not working... does it make any sense to you? http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head/563/console
[18:24] <kenvandine> no idea... that doesn't look like there was a failure
[18:24] <kenvandine> only one instance of a stack can be queued for building
[18:24] <kenvandine> ah
[18:24] <kenvandine> the stack already building?
[18:25] <kenvandine> at least it seems to think it's building
[18:25] <kenvandine> sil2100, ^^
[18:26] <sil2100> hmmm
[18:26] <sil2100> Maybe that's the catch, yes
[18:26] <sil2100> Let me check that, thanks!
[18:27] <kenvandine> np
[18:27] <kenvandine> the queue doesn't show one...
[18:28] <sil2100> Yes!
[18:28] <sil2100> This was it! kenvandine good catch
[18:28] <sil2100> We even had this one time, but I guess the error message was different
[18:28] <sil2100> kenvandine: there was a leftover stack.started file on mangers
[18:28] <sil2100> Probably due to some aborting we did
[18:29] <sil2100> Now it's running \o/
[18:29] <sil2100> kenvandine, robru: guys, I need to be EODing now, could you keep an eye on the unity stack, make sure that the new unity is build and publish it (just unity, DON'T rebuild anything else from this stack)?
[18:30] <sil2100> This is the last blocker, the unity-autopilot!
[18:30] <robru> sil2100, ok, can take a look at that in a bit.
[18:30] <sil2100> Thanks guys
[18:30] <sil2100> See you tomorrow
[18:30] <kenvandine> good night
[19:03] <thomi> morning
[19:03] <fginther> thomi, o/
[19:28] <cyphermox> awe: you know how the phonesim stuff works for testing?
[19:29] <awe> I know pitti set it up specifically for dialer-app tests
[19:29] <awe> but I havn't worked with it directly myself
[19:30] <awe> I also am pretty sure he pulled some patches from upstream, as there'd been some new features implemented post ofono 1.12
[19:30] <awe> cyphermox, he sent a detailed email to the phone ML
[19:30] <awe> cyphermox, what're you trying to do?
[19:30] <cyphermox> trying to figure out why it's so broken
[19:30] <awe> why *what* is so broken?  phonesim?
[19:31] <cyphermox> like, what could have changed to cause phonesim to have indicator-network, dbus, and ofono to get stuck in high CPU
[19:31] <cyphermox> yeah
[19:31] <awe> during auto-pilot testing?
[19:32] <awe> if so, I'd ping pitti
[19:32] <cyphermox> well, that's going to be a little complicated atm
[19:32] <awe> we haven't done an ofono upload since 13.10 released
[19:32] <cyphermox> yeah I know
[19:32] <awe> that said, there could have been an update to the phonesim pkg
[19:43] <cyphermox> doesn't seem to have been something that would break this since yesterday though
[19:44] <robru> fginther, https://code.launchpad.net/~boiko/dialer-app/fix_ap_1.4/+merge/194205 can you take a look at this failure? seems infrastructural
[19:47] <fginther> robru, looks like network failure for both, digging deeper
[19:47] <robru> fginther, thanks
[19:54] <fginther> robru, a different system had network failure for the autolanding job, will approve again
[19:54] <fginther> robru, also checking to see if the lab network is sane
[19:54] <robru> fginther, great
[20:00]  * robru -> lunch
[21:29] <thomi> fginther: is it possible that the autopilot docs publishing job is no longer being run?
[21:29] <thomi> We've made some AP docs changes in the last few days, but I don't see them reflected online
[21:33] <fginther> thomi, let me take a look
[21:35] <cjwatson> fginther: https://lists.launchpad.net/ubuntu-appstore-developers/msg00553.html (last paragraph, with pkcon remove)
[21:35] <cjwatson> well, last bullet point
[21:35] <cjwatson> fginther: or these days this should be hooked up in the UI though I don't remember exactly where
[21:36] <fginther> cjwatson, I'm trying to script this, so CLI is best
[21:36] <fginther> cjwatson, thanks
[21:36] <cjwatson> there's also the low-level interface, "sudo click unregister --user=phablet PACKAGE-NAME"
[21:37] <cjwatson> but you should generally prefer the version that involves the PK D-Bus interface if you can
[21:38] <fginther> cjwatson, do you know if this actually removes the files? AIUI 'click unregister' does not remove and there is no 'click uninstall'
[21:38] <cjwatson> you understand incorrectly
[21:39] <cjwatson> click unregister will trigger garbage-collection (i.e. removing the files) if there are no registrations left
[21:39] <cjwatson> and therefore the absence of click uninstall is intentional
[21:39] <fginther> cjwatson, ahh, thanks for the lesson
[21:40] <cjwatson> certainly it's possible that click unregister won't actually remove files if there are other registrations (esp. on a multi-user system) but that's also deliberate :-)
[21:40] <cjwatson> anyway, that's what pkcon remove backends onto
[21:41] <fginther> cjwatson, thanks again
[21:44] <sergiusens> same for preinstalled apps
[21:45] <cwayne> asac: ping
[21:48] <fginther> thomi, yep found the problem with the doc upload, it was stuck with the 1.3 branch during the transition
[21:48] <fginther> thomi, should have it fixed soon
[21:48] <thomi> fginther: thanks - it's not urgent, but it'd be good to get it done today some time
[21:54] <fginther> thomi, the docs should be updated now
[21:55] <thomi> fginther: indeed they are, thank you!
[21:55] <fginther> thomi, you're welcome
[22:02] <dobey> fginther: got a minute to review a branch for tarmac?
[22:02] <fginther> dobey, I can make the time
[22:02] <dobey> fginther: https://code.launchpad.net/~dobey/tarmac/fix-wt-check/+merge/194242
[22:02] <dobey> thanks
[22:27] <cjwatson> sergiusens: Yes, although preinstalled apps are a bit different under the hood as the files are on a RO filesystem and you can't remove them, so unregistering consists of leaving a note to indicate that the app shouldn't be shown for that user
[22:35] <fginther> dobey, reviewed