[02:09] <imgbot> [03:44] <imgbot> [03:44] <imgbot> [06:22] <robru> tedg, hey. i see you marked silo 18 as testing: done. I'm in meetings for a bit but I'll try to get to that within a few hours.
[06:23] <tedg> robru, Cool, if you want to throw it on a device I'm all for more testing on that one :-)
[06:23] <tedg> robru, Lots of packages changing :-)
[06:23] <robru> tedg, yeah, absolutely, sil2100 and I will be doing extra testing on this one ;-)
[06:24] <ogra_> looks like all testing is broken ... :(
[06:25] <Mirv> robru: it needs a lot of packaging acks, so if you can find someone who can ack through https://ci-train.ubuntu.com/job/landing-018-2-publish/27/ over there it'd help
[06:26] <Mirv> and then archive admin is needed to accept the new ubuntu-app-launch package
[06:30] <robru> yeah
[06:33] <bzoltan> Mirv: robru: ogra_: here is the MR for the gallery AP tests to unblock the UITK -> https://code.launchpad.net/~elopio/gallery-app/workaround1324556-get_header/+merge/221415
[06:33] <ogra_> bzoltan, whee ! thanks !!
[06:33] <bzoltan> this MR fixes the gallery app failures with the new UITK
[06:34] <ogra_> (i thought elopio wanted us to wait for the actual fix)
[06:34] <bzoltan> ogra_: the problem was that on the header autopilot helper we are assuming that the container is called MainView. There are many applications that extend the MainView component and it gets a new name. We should use a different way to get the parent without knowing the name.
[06:34] <ogra_> yeah, he explained that yesterday ...
[06:35] <bzoltan> ogra_:  cool
[06:35] <sil2100> bzoltan: hi! So, did you add this to your landing as per my yesterdays proposition? :)
[06:35] <ogra_> bzoltan, but he also said we should better wait for the true fix
[06:36] <bzoltan> sil2100:  I would do it after somebody else reviewed it
[06:36] <sil2100> ogra_: as mentioned yesterday, there seems to be some problem with the workaround (or with other parts of the gallery landing)
[06:36] <bzoltan> ogra_:  that will be the more permanent solution
[06:36] <ogra_> sil2100, right
[06:36] <sil2100> ogra_: so, we didn't release the workaround yet
[06:36] <sil2100> ogra_: actually we didn't release ANYTING
[06:36] <sil2100> ;)
[06:37] <ogra_> thats how i understood leo ...
[06:37] <ogra_> sil2100, and we should wait with landing anything til we know when we will be able to get image tests again
[06:37] <t1mp> the true fix is here https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/fix1324556-get_top_container/+merge/221426 but jenkins is failing on that one
[06:37] <ogra_> seems that went up in flames over night
[06:39] <t1mp> can someon trigger a new CI run on that one^? looks like jenkins broke there
[06:41] <ev> Saviq: https://docs.google.com/a/canonical.com/document/d/18L7c3_w-Ls65Gccda-K3eOPbjOmUCi3wv2TQwtS1V9M/edit
[06:47] <ogra_> plars, looks like the image testing server has a readonly fs or some such ?
[06:48] <plars> ogra_: yes, I was just looking for you :)
[06:48] <plars> ogra_: the phablet-config writable-image step seems to be silently failing to deliver us a writable image
[06:48] <ogra_> strange ... i dont think we changed anything
[06:49] <ogra_> sergiusens, ^^^any idea ?
[06:49] <plars> looking at http://people.canonical.com/~ogra/touch-image-stats/54.changes, there were quite a few changes! :)
[06:49] <ogra_> plars, yeah
[06:49] <sergiusens> ogra_: we saw that last night, but I have no idea since the world is broken
[06:49] <sergiusens> we didn't change anything
[06:49] <ogra_> i just upgraded my flo here and it runs still fine
[06:50] <sergiusens> ogra_: do a clean upgrade
[06:50] <ogra_> there are definitely issues with mountall etc ... see #ubuntu-devel
[06:51] <ogra_> but i dont see them affect anything on my flo
[06:52] <sil2100> Crappy internet
[06:53] <sil2100> ogra_: so, from what we saw, there seems to be problems with making the images writable
[06:54] <rsalveti> ogra_: it is broken, we had that on a clean image yesterday as well
[06:54] <ogra_> sil2100, yeah, apparently
[06:56] <plars> ogra_, sergiusens: hmm, worse yet one of the devices I'm seeing this on in the lab didn't come back after a reboot
[06:57] <ogra_> sergiusens, rsalveti ... right, confirmed, cant make my flo writable anymore here
[06:57] <ogra_> (by simply touching /userdata/.writable_image)
[06:59] <ogra_> writable_image is parsed from the initrd
[06:59] <ogra_> which we didnt change at all recently ...
[06:59] <ogra_> i wonder if it actually is writable initially ... and then the mountall issues turn it readonly again
[06:59] <rsalveti> yeah
[07:35] <plars> ogra_: yeah, rebooting puts the device into a bad state, I can't see anything on the screen and can't see it with adb
[07:36] <plars> ogra_: interestingly, I can remount / with rw and it seems happy with that
[07:36] <ogra_> indeed
[07:47] <robru> tedg, hey, I saw your new request, but I can't assign it to a silo because I need an MP URL, not a branch URL in there, thanks
[07:47] <tedg> robru, Sorry, fixed.
[07:47] <robru> tedg, thanks
[07:48] <robru> tedg, ok you got silo 13 ;-)
[07:49] <bzoltan> ogra_:  thanks for your mail :) I managed to Ctrl-C the flashing and use the rev53 :)
[07:55] <ogra_> :)
[07:55] <tedg> robru, Woot! Lucky silo! ;-)
[08:08] <sil2100> Just so everyone knows - we're not landing anything until the images are fixed
[08:16] <ogra_> sil2100, i have a hack ready to uplload that will get us going again ... but currently xnox seems to have some actual fix ...
[08:30] <Mirv> are having landing meeting?
[08:49] <ogra_> robru, http://paste.ubuntu.com/7549809/
[09:06] <robru> tedg, ok, finally got silo 18 correctly enabled on my mako, just running some tests now. so far so good but I really want to be sure with this one
[09:06] <tedg> robru, Understandable. Me too :-)
[09:08] <plars> ogra_: as an act of paranoia, I installed 54 and ran through the list of init scripts to run the same thing your hook is running
[09:08] <plars> ogra_: the good news is that after a reboot, I come back in read/write just fine. The bad news is that reboot still fails
[09:11] <plars> ogra_: I'm not sure what's going on in the background, it starts killing process so I lose the display and adbd, but it never power cycles
[09:12] <ogra_> worked fine on my flo when i tested
[09:12] <plars> ogra_: not sure about flo, I'm looking at mako
[09:12] <ogra_> my flo is infortunately in xnox' hands now so i dont have a test device
[09:12] <ogra_> and he needs it more
[09:13] <plars> If you get time, we can use my mako to look at it. But unless we can fix this, all the tests will die even if we have your workaround I think
[09:13] <ogra_> plars, did you try to force adb on ? (by hacking the start on stanza of the emergency adbd job)
[09:14] <ogra_> (make it "start on startup" or on filesystem or so)
[09:14] <plars> ogra_: hmm, I don't think that would help, but perhaps I could hack the stop stanza to just return 0 and not stop anything
[09:14] <plars> ogra_: adbd comes up just fine if I power cycle it manually, but it just never reboots
[09:14] <ogra_> so you see adbd starting ?
[09:15] <ogra_> oh
[09:15] <ogra_> i see
[09:15] <sil2100> ogra_: yeah, the problem seems to be happening on stop, not start
[09:15] <plars> yes. but I have to hold buttons down
[09:15] <ogra_> its the shutdown process not the start after this
[09:15] <plars> right
[09:16] <ogra_> plars, could you try: adb shell reboot -f
[09:16] <ogra_> that should directly call the kernel reboot function without processing scripts
[09:16] <ogra_> i belive what xnox is working on will help on shutdown too
[09:17] <ogra_> plars, probably we could temporary change the lab server to call reboot -f for this round of tests ?
[09:17] <ogra_> (if that works)
[09:18] <sil2100> ogra_: plars is away right now, so we can't really check this
[09:18] <ogra_> sil2100, ok, have him check it if he comes back ...
[09:19] <sil2100> He's trying
[09:19] <plars> ogra_: yes, looks like that will work
[09:20] <plars> ogra_: I can make that change, hopefully it's safe enough...
[09:20] <ogra_> should be
[09:23] <plars> ogra_: appears to just be a problem with adb shell reboot, adb reboot also works ok
[09:23] <plars> at least on my laptop
[09:24] <ogra_> yeah
[09:24] <ogra_> that calls the kernel function too
[09:24] <ogra_> working around any shutdown scripts
[09:28] <sil2100> Mirv: just to make sure, which PPA should I use for the latest qt 5.3? Is it the silo PPA?
[09:36] <ogra_> [09:44] <imgbot> [09:44] <robru> tedg, actually I'm getting strange AP failures with your silo enabled, I'm not really sure what's going on (inconclusive if the failures are your fault or more related to the recent archive problems or something else). I'm gonna wait for a new image to be built in a good state before I can proceed with publishing this
[09:50] <tedg> robru, Okay, I ran the unity8 tests, are there other APs I should look at?
[09:50] <davmor2> sil2100: so 55 is the one that is worth testing more right?
[09:51] <robru> tedg, I was running different app ones, and found problems with address book and messaging app
[09:51] <sil2100> davmor2: right... but we hoped it didn't have many changes
[09:51] <sil2100> But yes, 55 seems a better choice
[09:51] <robru> tedg, https://wiki.ubuntu.com/Touch/Testing#Running_Deb_tests
[09:52] <tedg> robru, Which are causing issues for you?
[09:53] <robru> tedg, I got 16 errors in messaging app and 7 in address book app. didn't try very many others yet though
[09:53] <tedg> Huh, the app onese.
[09:53] <tedg> ones
[09:53] <tedg> I wouldn't have expected that.
[10:02] <popey> davmor2: ever get this bug 1324851
[10:03] <davmor2> popey: I've never seen that I'll keep my open for it though
[10:03] <ogra_> tedg, both are running unconfined i think ... might be related
[10:03] <tedg> ogra_, robru, not quite done yet, but it's working on my device.
[10:03] <tedg> :-/
[10:04] <robru> tedg, yeah, mostly I was running app tests just to check if the apps could even launch, seems they did launch, but there were other issues, which is why I said it was inconclusive.
[10:06] <popey> davmor2: ta
[10:09] <Mirv> sil2100 in your case probably silo is better since it correctly shows the need to rebuild maliit, but for device use qt5-beta2 (until at least maliit issue is solved)
[10:15] <sil2100> Mirv: ok, thanks!
[10:15] <sil2100> ogra_: I guess we can start reverting your fix now, as the real one is in -proposed
[10:16] <ogra_> sil2100, will do, after the meeting
[10:17] <sil2100> ogra_: thanks!
[10:17] <xnox> sil2100: yeap, just need it migrate before image build.
[10:19]  * sil2100 goes off to lunch
[11:01] <davmor2> popey: just hit it so I've confirmed it
[11:02] <popey> magic, thanks
[11:03] <davmor2> popey: terminal app uses konsole right? Would the version in the archive being updated effect the terminal app?  I'm just wondering if that migh be what broke stuff
[11:04] <popey> we know what broke it, t1mp is working on it.
[11:04] <davmor2> ah nice
[11:04] <imgbot> [11:04] <imgbot> [11:04] <sil2100> \o/
[11:05] <davmor2> oh I just got a push notification
[11:06] <Chipaca> sil2100, Mirv: hi! do the changes cjwatson and ScottK are talking about on ubuntu-devel impact how I land things for ubuntu-push?
[11:06] <cjwatson> Chipaca: Still plenty of discussion needed on that
[11:07] <Chipaca> I'm not understanding whether the ubuntu developer review happens already, or if it's extra (or if I should apply for per-package upload for ubuntu-push?)
[11:07]  * sil2100 was away from IRC so has no context
[11:07] <Chipaca> sil2100: mail, not irc
[11:07] <cjwatson> I think you should apply for PPU for ubuntu-push regardless
[11:07] <cjwatson> It would be the right thing to do
[11:07] <sil2100> Ah, that
[11:07] <Chipaca> sil2100: constructive thread out of what started as a "what's the point of reviews" rant
[11:08] <Chipaca> cjwatson: but for PPU you need to be an ubuntu developer, yes?
[11:08] <cjwatson> No, PPU is one of the paths to being an Ubuntu developer
[11:08] <Chipaca> ah
[11:08] <Chipaca> i had it backwards
[11:08] <Chipaca> is there a ppu template?
[11:09] <Chipaca> or do people copy-and-edit?
[11:09] <cjwatson> https://wiki.ubuntu.com/UbuntuDevelopers#Per-package_Uploaders
[11:09] <cjwatson> https://wiki.ubuntu.com/UbuntuDevelopment/DeveloperApplicationTemplate
[11:09] <cjwatson> and https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess
[11:10] <cjwatson> I think it'll be a while before any change happens, assuming enough people agree with me that it's the right thing to do - it was all contingent on the Airline anyway
[11:15] <Chipaca> cjwatson: well, AIUI from that thread, and unless I'm missing something, the way I'm getting ubuntu-push in right now is wrong wrt the ubuntu rules or policy or whatever it's called
[11:15] <davmor2> popey: media player did you file a bug for that?
[11:18] <popey> davmor2: for what?
[11:19] <cjwatson> Chipaca: That's my understanding too, so it would certainly help for upstreams to be proactive in helping to fix that :)
[11:19] <davmor2> popey: it not playing that music track properly
[11:19] <cjwatson> (wrt community tension etc.)
[11:19] <popey> davmor2: no
[11:19] <cjwatson> I'd hope to avoid too much practical disruption
[11:21] <ogra_> yay, only nuntium and apparmor profiles
[11:22] <Chipaca> cjwatson: is it better to apply for a single ppu, and perhaps expand it to other packages later, or should i make it broader now?
[11:22] <davmor2> ogra_: and I'd tested nuntium outside and inside the silo previously too so that is good :)
[11:23] <cjwatson> Chipaca: I'm not on the DMB so not certain, but my general feeling would be that it's better to apply for whatever's clear now
[11:23] <cjwatson> and, yeah, expand later
[11:23] <ogra_> davmor2, so all breakages showing up now must be apparmor ;)
[11:23] <Chipaca> ok
[11:23] <Chipaca> cjwatson: ta :)
[11:24] <davmor2> ogra_: you were in the meeting right, Today all breakages are pitti's fault ;)
[11:24] <ogra_> oh, right
[11:26] <davmor2> ogra_: it also means that all fixes are pitti's doing too so it swings both ways :)
[11:29] <ogra_> revert of the hack uploaded ... seems lsb also migrated out of -proposed
[11:29] <Mirv> dbarth: could you possibly answer mitya57 on ubuntu-devel mailing list regarding qtwebkit 5.2 upgrade ETA (when it's allowed)?
[11:30] <ogra_> plars, looks like there are still some issues with the tests
[11:30] <plars> ogra_: indeed, I just connected
[11:30] <plars> ogra_: checking it out now, flo died completely
[11:31] <ogra_> should we ignore #55 and just fire up #56 now ?
[11:31] <ogra_> (with the proper fix)
[11:31] <sil2100> ogra_: you don't want to wait for livecd-rootfs revert landing?
[11:31] <sil2100> ogra_: if that's ok with you we can build now
[11:31] <ogra_> sil2100, well, after that lamded
[11:31]  * sil2100 would prefer it to land though
[11:31] <sil2100> Right
[11:32] <plars> ogra_: actually so far it looks like most of the problems are due to bzr hitting errors while trying to pull things in phablet-click-test-setup
[11:32] <plars> mako is all still running ok
[11:32] <ogra_> plars, right, i see that
[11:33] <ogra_> someting is still wonky there .... the error looks very weird as if it tries to create a logfile under /dev/null/.bzr.log
[11:34] <davmor2> so popey big buck bunny is playing fine so I'm beginning to wonder if it is a codec issue
[11:34] <popey> davmor2: worked before.
[11:50] <ogra_> plars, can you make sure to revert your adb reboot hack too again for 56 (we actually want to catch issues with the shutdown scripts )
[11:50] <plars> ogra_: actually the rebooting was fine in our scripts, I didn't have to change that anywhere
[11:51] <ogra_> oh
[11:51] <plars> ogra_: it was just me being paranoid because of what I had noticed with adb shell reboot
[11:51] <ogra_> ah, k
[11:51] <plars> ogra_: ...which is still broken afaik
[11:51] <ogra_> not in 56
[11:51] <plars> ogra_: oh, ok good. I didn't try yet in 56
[11:51] <plars> err, I mean 55
[11:51] <plars> but I'll try it by hand in 56 at least
[11:51] <ogra_> i mean 56 ;)
[11:52] <plars> I know
[11:52] <ogra_> i tried xnox' fix on my flo and it is all fine there
[11:52] <ogra_> plars, it would make sense to switch the lab scripts to actually use adb shell reboot ...
[11:53] <plars> ogra_: well if it has the risk to leave them in an unrecoverable state, I'd like to wait until they are all instrumented. Otherwise rfowler will be plotting my murder
[11:54] <xnox> ogra_: adb shell reboot, may not work.
[11:54] <xnox> ogra_: because of loop mounting filesystems, our adb shell reboot is never clean.
[11:55] <xnox> ogra_: adb reboot is the most reliable way....
[11:55] <xnox> ogra_: one should test "adb shell reboot" though as a test case.
[12:02] <dbarth> Mirv: yup, just got the message from Olivier
[12:03] <ogra_> xnox, it worked up to now :)
[12:03] <xnox> ogra_: oh. good =) didn't expect it to.
[12:03] <ogra_> xnox, and i think it would be good to see if it breaks
[12:03] <ogra_> the UI reboot dialog wont call adb ;)
[12:06]  * sil2100 waits for the livecd-rootfs to migrate
[12:09] <ogra_> it is close ... i hear it knocking at the archive door already :)
[12:10] <sil2100> Can't wait!
[12:10] <Chipaca> any ubuntu dev in here want to endorse my ppu, please feel free: https://wiki.ubuntu.com/Chipaca/PPU
[12:10] <plars> argh
[12:11] <Chipaca> (also dis-endorse it if you know^Wthink i'm evil)
[12:11] <plars> ogra_, sil2100: might have to restart the tests in a bit, adb host is misbehaving
[12:11] <plars> it's being looked into right now
[12:11] <ogra_> k
[12:11] <ogra_> i think we said we would consider that image a throw away piece anyway ...
[12:12] <ogra_> just to get the fix out to -proposed users
[12:12] <sil2100> plars: ok, thanks
[12:12] <sil2100> Yeah, 56 is the one that we can look into
[12:16] <ogra_> sil2100, firing up a build ...
[12:16] <sil2100> ogra_: ! \o/
[12:16] <ogra_> sil2100, and once that finished mterry should finally land his greeter :)
[12:16] <sil2100> ogra_: I hope so, his silo is still not set to ready
[12:20] <t1mp> ogra_: should I flash #55 or #53?
[12:20] <t1mp> for testing apps with a new UITK
[12:21] <ogra_> t1mp, 55 should be fine ...
[12:21] <sil2100> 55 more I would say
[12:21] <sil2100> As it's fixed and is more up-to-date
[12:21] <t1mp> ok, thanks. I didn't know whether the writable image issue was fixed
[12:21]  * t1mp flashing 55 now
[12:24] <imgbot> [12:49] <balloons> cihelp, ping
[12:51] <dbarth> Mirv: ok, done; hopefully we can make a transparent switch next week
[12:51] <balloons> fginther, ping? seems core apps jenkins isn't very happy at the moment. Had a 15 hour test run
[12:56] <Mirv> dbarth: great, thanks for crafting an answer!
[13:01] <renato_> fginther, ping
[13:34] <elopio> ping cihelp, this is broken http://91.189.93.70:8080/computer/mediumtests-utopic-slave/?
[13:34] <elopio> can you give us a hand please?
[13:49] <imgbot> [13:49] <imgbot> [13:50] <ogra_> yippie :)
[13:51] <sil2100> o/
[13:54] <fginther> elopio, balloons, it's hosed pretty bad
[13:54] <balloons> yay fginther :-) thanks for allowing me to interrupt happy hour
[13:54] <fginther> balloons, I'm not sure happy hour is going to be enough time :-(
[13:54] <balloons> fginther, there was a slew of jobs backed up.. I did end up canceling them
[13:58] <fginther> balloons, the stop gap solution is to disable the utopic machine until it can be fixed
[13:58] <balloons> fginther, that's probably not a bad idea; we will keep going on trusty
[14:00] <t1mp> I think https://wiki.ubuntu.com/Touch/Testing has mistakes
[14:00] <t1mp> I cannot run phablet-click-test-setup after installing the PPA for a new UITK
[14:01] <t1mp> it fails like this: http://pastebin.ubuntu.com/7551635/
[14:01] <balloons> that seems interesting
[14:02] <t1mp> that's the autopilot tests for the new UITK, which is not in the archive yet
[14:02] <fginther> renato_, hello
[14:02] <balloons> right, archive.ubuntu.com/ubuntu/pool/main/u/ubuntu-ui-toolkit/ubuntu-ui-toolkit_0.1.46+14.10.20140527-0ubuntu1.dsc
[14:03] <renato_> fginther, hi, I am still having problems with the staging branch, do you have time to help me on that?
[14:03] <fginther> renato_, if this is the otto tests failing, then no. I don't have time to work on that right now
[14:04] <fginther> renato_, the best short term fix I can do is disable the otto tests for that project until I get a chance to fix the tests
[14:05] <bfiller> sil2100: can I have a silo for line 31 please
[14:05] <robru> sil2100, ogra_: image 56 flashed, silo added, rebooted, things are looking good!
[14:06] <sil2100> bfiller: ok! You'll get the last silo ;)
[14:06] <renato_> fginther, is not necessary, this will not solve the problem, I can merge the branches manually for now
[14:06] <bfiller> sil2100: nice thanks
[14:07] <t1mp> balloons: any ideas how I should be running app AP tests with the updated uitk AP "custom proxy objects"?
[14:07] <balloons> t1mp, you don't have to use phablet-test-setup
[14:07] <balloons> t1mp, install the uitk helper locally and push it to the device yourself
[14:08] <renato_> fginther, I am trying to avoid big problems when trying to merge on trunk
[14:08] <balloons> t1mp, adb push /usr/lib/python3/dist-packages/ubuntuuitoolkit /home/phablet/autopilot/ubuntuuitoolkit
[14:09] <t1mp> balloons: with installing locally, do you mean install the deb for ubuntu-ui-toolkit-autopilot? I did that on the device
[14:09] <t1mp> still I need to run phablet-click-setup to get the AP tests for gallery-app, but that doesn't work because the uitk helper cannot be downloaded
[14:09] <sil2100> bfiller: could you wait a moment? As tedg already has a lock on content-hub, just need to coordinate with him on if we can override
[14:09] <balloons> t1mp, I mean on your desktop.. Assuming you have the package installed on your desktop you can do the push command above to copy it over
[14:10] <bfiller> sil2100: sure
[14:10] <balloons> otherwise, you can pull the package and do the same thing
[14:10] <sil2100> (after the talks that are happening now)
[14:11] <t1mp> balloons: but after that I still need to get the tests for gallery-app. I can get the debs for that as well but I am not sure that will give 100% the same test results
[14:11] <balloons> t1mp, the tests for gallery app? push those to the device as well then
[14:11] <balloons> if you check out lp:gallery-app
[14:11] <balloons> cd gallery-app
[14:11] <balloons> adb push tests/autopilot/ /home/phablet/autopilot/
[14:13] <dbarth> Mirv: just a heads up fo qtwebkit 5.3; when you transition next week, make sure to have the branch with the oxide switch in the same silo as well
[14:14] <dbarth> Mirv: or maybe we can pass that one just before; will see w/alex on Monday when he returns
[14:21] <t1mp> balloons: oh thanks :) I'll do that
[14:21] <balloons> t1mp, :-)
[14:22] <t1mp> it seems so easy when you type it here, but I got lazy using all the scripts :)
[14:23] <t1mp> still would be nice if the scripts also worked for new uitk versions
[14:27] <balloons> t1mp, I'm not sure why it's broken exactly, but I'm pushing for us to migrate off the cobbled scripts to a proper solution
[14:27] <balloons> I'm been sick this week so I'm not sure how far they got in Malta on it
[14:30] <t1mp> ah, ok. I'm all for a proper solution :)
[14:30] <t1mp> this works usually, but it is a hassle for me when I need to run all the app tests
[14:32] <balloons> t1mp, the idea is to use autopkg to be able to properly specify depends and provision
[14:33] <robru> tedg, hey, I'm retesting your silo on image #56 and it's looking *much* better
[14:35] <dbarth> robru: hiya, we have silo 10 finally validated
[14:35] <t1mp> balloons: I don't know autopkg. Is it t his one? https://github.com/autopkg/autopkg
[14:36] <t1mp> re-using stuff that works++ :)
[14:36] <balloons> t1mp, http://packaging.ubuntu.com/html/auto-pkg-test.html
[14:37] <t1mp> ah, something else :)
[14:55] <davmor2> popey, dbarth, sil2100: there is some odd behaviour with the the twitter account setup and the keyboard in the accounts section of the settings app it constantly triggers to uppercase all the time
[14:59] <davmor2> same thing on facebook
[15:09] <robru> dbarth, cool, will release, thanks!
[15:10] <sil2100> davmor2, popey: hey guys, you around?
[15:10] <davmor2> sil2100: yeap
[15:10] <robru> dbarth, hmmm, needs a core dev ack
[15:10] <robru> dbarth, might be tricky to come by, sprint is just ending, everybody's in the bar already
[15:11] <popey> sil2100: ya
[15:12] <davmor2> sil2100: why?
[15:12] <sil2100> davmor2, popey: let's do the meeting NOW
[15:12] <sil2100> :)
[15:12] <popey> ok
[15:12] <davmor2> pfff you just want to go party you can't blag our heads
[15:13] <sil2100> HUSH!
[15:13] <robru> dbarth, luckily got ogra here to ack it
[15:15] <fginther> renato_, I updated the container to the latest I could (unfortunately the latest image is still 10 days old) and still seeing test failures: http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-utopic/485/console
[15:16] <renato_> fginther, I updated the required packages versions to the last one on the autopilot package but it still using the old one
[15:17] <fginther> renato_, is this the uitoolkit?
[15:17] <renato_> yes
[15:18] <renato_> fginther, http://bazaar.launchpad.net/~renatofilho/address-book-app/search/revision/220
[15:21] <fginther> renato_, I'll try to rebuild that branch, I was attempting a different branch
[15:21] <renato_> thanks
[15:28] <dbarth> robru, ogra_: thanks
[15:29] <robru> dbarth, you're welcome
[15:29] <sil2100> Saviq: any news? :D (no pressure)
[15:29] <sil2100> Saviq: (no pressure, really :> )
[15:41] <dbarth> davmor2: you mean with the new branches?
[15:48] <davmor2> dbarth: when you open the accounts window for twitter or facebook the first character is lower case and the rest are upper it's like the keyboard got switched over somehow but on google and ubuntu1 it is the correct way round only happened in todays images
[15:49] <davmor2> dbarth: I'm not sure if it is the keyboard or if it is the webrowser account windows that are causing it
[15:52] <robru> Saviq, can I publish prettty please??
[15:54]  * sil2100 stares at Saviq 
[15:55] <sil2100> Ok, I close down now o/
[15:55] <davmor2> sil2100: safe journey dude
[16:09] <dbarth> davmor2: hmm, ok, noted, but i don't see that in the silo i was just testing (but was on #51)
[16:09] <dbarth> i'll re-test with #55 on monday
[16:25] <balloons> anyone running the latest image on the device? I can no longer run AP tests due to apparmor errors. Are you seeing the same?
[16:32] <popey> balloons: I would try but...
[16:32] <popey> alan@deep-thought:~/phablet/scripts$ phablet-test-run -v clock_app
[16:32] <popey> sh: 1: /usr/bin/python: not found
[16:32] <popey> oh my bad, ubuntu_clock_app
[16:32] <popey> duh
[16:33] <balloons> popey, that means module not found
[16:33] <balloons> hah
[16:33] <balloons> lovely error messages
[16:33] <popey> nice error handling there buddy
[16:33] <popey> clock tests running here on #56
[16:34] <balloons> popey, I get this running any test: http://paste.ubuntu.com/7552608/
[16:36] <balloons> apparmor is denying the introspection request from AP
[16:36] <balloons> are you on a mako?
[16:36] <popey> this is flo
[16:37] <balloons> wow, same for me
[16:41] <popey> clock worked fine here
[16:41] <popey> Ran 20 tests in 429.165s
[16:42] <popey> bah, i can't connect to the vpn to get to jenkins
[16:42] <popey> I'm calling it a week.
[16:43] <Mirv> ogra_: it seems 20 mins ago Saviq has approved the split greeter for landing, but there are 3 pieces of packaging acks https://ci-train.ubuntu.com/job/landing-002-2-publish/2/
[16:43] <balloons> popey, what time does dpm need the new pkgs?
[16:44] <popey> you have new stuff to upload?
[16:44] <balloons> popey, well if jenkins cooporates, there are mp's for music, calendar and calc so we can release trunk
[16:45] <balloons> I'm happy to leave them, just don't want to leave David hanging
[16:47] <popey> well, if you can test and upload to store, then I'm happy to download from store, test and accept them
[16:47] <balloons> and yes the vpn is down :-) Just wanted to make sure before you left we were on the same page
[16:48] <balloons> I'll assume you pushing them in Monday is good enough for David, so that's fine. Hopefully everything will be sorted before then
[16:48] <popey> ☹
[16:48] <balloons> enjoy your weekedn
[16:48] <popey> well, MWE isn't until 11th une
[16:48] <popey> *june
[16:48] <popey> I'm more interested in getting the tests running reliably, and getting those fixes into trunk
[16:49] <popey> infrastructure issues are a bit out of our control.
[16:49] <popey> e.g. vpn
[16:51] <balloons> sure thing.. well jenkins too.. poor francis did a temp workaround by disabling the utopic builder that broke horribly
[16:52] <balloons> anyways, time for you to head out
[16:52]  * balloons punts popey
[16:52] <popey> heh
[16:55]  * balloons reruns ap config
[16:57] <balloons> my guess is I needed to recompile the apparmor configs, including the autopilot one..  Seems to have fixed things up
[17:31] <bzoltan> does anybody know if the phablet-click-test-setup is expected to get fixed to work when there is a PPA enabled?
[17:32] <bzoltan> Also is there a chance to use the UITK helpers from the release candidate from the Silo instead of the phablet-click-test-setup fetched ones?
[17:32] <bzoltan> ogra_: Mirv: these issues are killing the silo verification ^
[20:09] <boiko_> rsalveti: hi, is there any chance to get landing-019 published?
[20:10] <boiko_> rsalveti: it would be nice to have it for Mobile Asia Expo
[21:35] <rsalveti> boiko_: hey
[21:42] <boiko> rsalveti: thanks :)
[21:45] <rsalveti> boiko: np