[00:53] <sergiusens> fginther: still around?
[00:54] <sergiusens> fginther: I just got back to testing click chroot and it fails for me too; seems we are some versions behind so I did a bin copy of click from utopic into the phablet-team/tools ppa
[08:24] <ogra_> psivaa, hmm, looks like one device hangs again in the lab ... (UITK is definitely running to long already and many jobs are still in syncing state)
[08:24] <psivaa> ogra_: yea, it's the uitk tests that's holding the syncing
[08:24] <ogra_> ah, k
[08:27] <psivaa> uitk has been running for more than 2.5 hrs (started at around 05:49 and running still, 08:26)
[08:27] <ogra_> well, as long as it still runs and doesnt hang ...
[08:28] <brendand> ogra_, why don't we run the ubuntu_keyboard tests?
[08:29] <ogra_> brendand, no idea :)
[08:30] <brendand> i see them mentioned here: https://wiki.ubuntu.com/Touch/Testing
[08:30] <brendand> but i've never seen them run in the dashboard
[09:04] <davmor2> popey: I just got this http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-06-25-100303.png  that was several apps open and then doing a search then closing the apps, however when I search I still find apps
[09:22] <tvoss> seb128, ping
[09:22] <seb128> tvoss, hey
[09:29] <brendand> ogra_, this mediaplayer issue seems like a problem with autopilot, but there is no new autopilot in #96 so there must be something else that changed
[09:29] <brendand> ogra_, could be unity8
[09:29] <brendand> maybe
[09:30] <brendand> i'll raise a bug against mediaplayer-app and try and figure out what's going on
[09:31] <popey> davmor2: i have seen that in the emulator, not on device recently
[09:37] <davmor2> popey: on you devices do you hear a crackling from the speaker without making a call
[09:37] <popey> davmor2: which speaker?
[09:38] <davmor2> popey: the one for the earpiece during a call when you are holding it against your head
[09:42] <popey> yes, happens on android too
[09:42] <popey> nexus 4 is terrible hardware, this is not news ☻
[09:43] <davmor2> popey: ah that's okay then I only just noticed it :)
[09:48] <t1mp> is the osk broken on the latest image?
[09:48] <t1mp> I don't get it in unity8 search or calendar-app
[09:49] <t1mp> neither in browser
[09:49] <davmor2> timp: did you get the welcome screen?
[09:50] <t1mp> davmor2: yes
[09:50] <davmor2> t1mp: Wait 45 + seconds with the scope search it should appear
[09:50] <ogra_> the keyboard itself was last updated in image 85
[09:51] <t1mp> I have image 96 now
[09:51] <davmor2> ogra_: it's the issue I was on about the osk doesn't appear for a good 45 second is the welcome screen is used
[09:51] <ogra_> right
[09:52] <ogra_> but it isnt the kbd itself ... something in the environment changed that causes this
[09:52] <t1mp> I'm still not getting the osk
[09:52] <davmor2> ogra_: the welcome screen kills mallit
[09:52] <ogra_> i still see the G+ issue whhere it doesnt show up at all until i restart the G+ app ... and that was 5.3 induced
[09:52] <t1mp> I reboot the device
[09:52] <davmor2> t1mp: reboot
[09:53]  * ogra_ thinks we have multiple kbd related issues here 
[09:54] <t1mp> yes, it works again after reboot
[09:58] <ogra_> psivaa, heh, the UI is pretty confusin in the re-run mediaplayer tests ... looks like it didnt remove the failed results from the former run
[09:58] <psivaa> ogra_: ohh? let me take a look
[09:59] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch/mako/96:20140625:20140625/8714/mediaplayer_app/
[09:59] <ogra_> it doesnt count them as failures so i guess its just a leftover from the former run
[10:00] <psivaa> ogra_: yes, they are leftovers and more, they should have been skipped in the first run but weren't that's why we are not able to override them
[10:00] <ogra_> right
[10:00] <ogra_> no worries
[10:01] <ogra_> as long as they show as passed now we're all fine :)
[10:01] <brendand> ogra_, those tests are not going to pass, so no amount of re-running will do
[10:01] <ogra_> the sdk test seems to need love though
[10:01] <brendand> ogra_, or did we get a passing run?
[10:01] <ogra_> brendand, right, its just that the failures still show there
[10:01] <ogra_> yes
[10:01] <ogra_> they were properly skipped like they should
[10:02] <psivaa> ogra_: sdk still failed on the second run
[10:03] <brendand> ogra_, that's strange
[10:03] <ogra_> psivaa, right ... do you know where the code for that one is ?
[10:03] <psivaa> ogra_: digging now
[10:03] <ogra_> we need to change the package name
[10:04] <ogra_> s/qtsensors5-dev/libqt5sensors5-dev/
[10:06] <brendand> ogra_, i can reproduce the issue every time here, after reflashing twice
[10:06] <ogra_> which issue ?
[10:06] <brendand> ogra_, the mediaplayer failures
[10:07] <ogra_> ah
[10:07] <ogra_> interesting
[10:07] <brendand> ogra_, and when i rolled back to #95 it was gone
[10:08] <brendand> ogra_, then upgraded to #96 and it was back
[10:08] <ogra_> thats really weird
[10:08] <psivaa> ogra_: that's being used from an obsolete bzr branch: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-qtcreator-plugins/trunk/view/head:/tests/device/check-packages#L21
[10:08] <brendand> ogra_, psivaa - where is this passing run?
[10:08] <ogra_> brendand, i linked it above
[10:08] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch/mako/96:20140625:20140625/8714/mediaplayer_app/
[10:09] <ogra_> the current run passed fine ... but didnt clean up the old results on the dashboard
[10:10] <ogra_> bzoltan, http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-qtcreator-plugins/trunk/view/head:/tests/device/check-packages#L21 needs to change s/qtsensors5-dev/libqt5sensors5-dev/ ... we dropped qtsensors5-dev a while ago, now the test fails
[10:11] <ogra_> (or zsombi ^^⁾
[10:11] <ogra_> )
[10:14] <zsombi> zbenjamin: ^^ check ogra_'s post, that goes to you :)
[10:14]  * zbenjamin looks
[10:15] <brendand> ogra_, don't we store the test results xml file?
[10:17] <ogra_> brendand, thats a question for psivaa :)
[10:17] <brendand> psivaa, i can't find the .xml file in the jenkins job
[10:18] <psivaa> brendand: V
[10:18] <psivaa> http://q-jenkins.ubuntu-ci:8080/job/utopic-touch-mako-smoke-daily/344/artifact/clientlogs/mediaplayer_app/test_results.xml/*view*/
[10:18] <psivaa> brendand: https://jenkins.qa.ubuntu.com//job/utopic-touch-mako-smoke-daily/344/artifact/clientlogs/mediaplayer_app/test_results.xml/*view*/ in the public instanc
[10:23] <brendand> psivaa, well ok. i'll wait for this evenings results and see if it comes back
[10:24] <Saviq> oh noes, where is sil!
[10:24] <psivaa> brendand: ack, but there seems to be a performance/race issue with 96. uitk took too long to finish and this^ supposed to be skipped ones haven't been skipped.
[10:24] <Saviq> ogra_, can you recon a silo for me?
[10:24] <ogra_> Saviq, how do i do that ?
[10:24] <Saviq> ogra_, so no ;)
[10:24] <ogra_> :)
[10:25] <ogra_> i know i technically can ...
[10:25] <ogra_> preactically i havent gotten any training or ever done it
[10:25] <Saviq> OMG who's driving the train!?
[10:25] <ogra_> nobody
[10:25] <Saviq> it's gonna crash!
[10:25] <ogra_> sil isnt around today
[10:25] <ogra_> nah, its french ...
[10:25] <Saviq> ;((
[10:25] <Saviq> that's not good
[10:25] <ogra_> Saviq, i know seb128 knows what to do though ... he does self service
[10:25] <brendand> psivaa, we already know that tests still run setUp even if they are marked to skip
[10:26] <brendand> psivaa, and if they fail there they will show as failed
[10:26] <Saviq> trainguards, can someone please recon silo 4 for me? I added the ubuntu-themes MP
[10:26] <seb128> Saviq, I can do
[10:26] <Saviq> seb128, ooh thanks
[10:26] <brendand> psivaa, it's a problem with testtools that i'm working on a fix for (actually i have a fix but it's not quite in shape for contribution yet)
[10:28] <psivaa> brendand: ack, but with mediaplayer we used to have only one testcase failing during setup once in a while but i thought you said today's issue of 4 failures are reproducible
[10:28] <psivaa> ?
[10:28] <ogra_> Saviq, oh, you wanted it reconfigured ... i could have done that too ... (recon didnt really expand to reconfigure in my head)
[10:29] <ogra_> i just dont know how to assing
[10:29] <ogra_> *assign
[10:29] <seb128> ogra_, that's the same command
[10:29] <seb128> Saviq, that silo has conflicts with other, I guess that's expected/fine?
[10:29] <ogra_> seb128, one is a button in the silo page one is a menu option at the top
[10:30] <Saviq> seb128, yeah
[10:30] <ogra_> i never used the menu option
[10:30] <seb128> ogra_, the button doesn't do new components, that just works if you reconfigure existing sources
[10:30] <seb128> you need the menu option to add components
[10:30] <seb128> or to assign silos
[10:30] <ogra_> right
[10:31] <brendand> psivaa, yes there is a new issue that i can reproduce, which is why i find it surprising you got a passing run. that should be impossible with the issue i'm seeing
[10:31] <brendand> psivaa, https://bugs.launchpad.net/mediaplayer-app/+bug/1334186
[10:33] <psivaa> brendand: ack, yea. confusing. ( i was trying to see if the uitk taking too long issue is related :))
[10:34] <seb128> Saviq, reconfigure done, you can rebuild needed components
[10:34] <Saviq> seb128, thank you
[10:34] <seb128> yw!
[10:35] <brendand> psivaa, i ran the test in isolation so i don't think they're related
[10:35] <brendand> psivaa, they might have the same cause, but one isn't causing the other i don't think
[10:36] <psivaa> brendand: right, i meant the cause
[10:54] <asac> sil off today?
[10:55] <asac> (hello!)
[10:56] <cjwatson> Yes, he is
[10:58] <asac> thx
[11:21] <davmor2> popey: quick confirmation for me on the latest build if you call the phone how many times does it ring?
[11:44] <popey> davmor2: lemme see
[11:44] <popey> davmor2: mine isnt ringing at all, get the snap decision but no sound
[11:44] <davmor2> popey: mine is ringing once
[11:45] <popey> ah, volume was low
[11:45] <popey> sound button didnt raise it
[11:45] <popey> same, only rings once
[11:45] <davmor2> ogra_: ^  that'll be a regression and a blocker then
[11:45] <ogra_> right
[11:46] <ogra_> file a bug and we'll get it into the mail
[11:46] <davmor2> ogra_: we had it before and it got fixed so I don't know what broke it.  I'll blame rsalveti 's revert though :D
[11:46] <ogra_> he only reverted code that never hit an image
[11:47] <davmor2> ogra_: he touched sound last that's enough for me to blame him ;)
[11:47] <ogra_> so if he changes the volume of his hifi at home you blame him for your phone not working ?
[11:47] <ogra_> :P
[11:48] <davmor2> no only touching sound on anything to do with ubuntu I'm not that unspecific :D
[11:54] <davmor2> popey: if you could do the honours, ogra_ one bug number https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1334248
[11:54] <ogra_> huh ?
[11:54] <ogra_> why did you file it against pulse
[11:54] <ogra_> that hasnt changed in weeks
[11:56] <ogra_> i would blame https://launchpad.net/ubuntu/utopic/+source/unity8/7.89+14.10.20140623.1-0ubuntu1
[11:56] <ogra_> but then it would also have to be broken on 95
[11:56] <ogra_> can you check that ?
[11:57] <ogra_> (snap decision sound handling was changed in that landing)
[12:53] <davmor2> ogra_: now I'm back from Lunch I'll have a look
[12:53] <ogra_> thanks
[12:54] <davmor2> ogra_: as for filing it against pulse it's because pulse makes sound :)
[12:54] <ogra_> yeah, but thats totally unrelated
[12:54] <ogra_> if your hifi speakers are broken you dont buy a ne CD player to fix your sund either :P
[12:54] <ogra_> *new
[12:56] <oSoMoN> hey, who’s in charge of assigning silos in the CI train?
[13:00] <popey> davmor2: maybe related to that bug, if you have two alarms at the same time, they both go off together, you can make out two harps at once
[13:03] <ogra_> its a harp concerto
[13:12] <kgunn> ogra_: do you happen to know the last image produced with Qt5.2 ?
[13:12] <brendand> ogra_, is there another build under way?
[13:13] <ogra_> kgunn, #90
[13:13] <ogra_> brendand, nope, thanks for the reminder, triggering one now
[13:14] <asac> rsalveti: there?
[13:14] <ogra_> triggered
[13:14] <ogra_> (bot hopefully picks it up soon)
[13:17] <seb128> oSoMoN, usually sil2100 and Mirv during european hours, but they are off, other people have access though, if you need a silo just ask there
[13:18] <oSoMoN> seb128, ah, thanks, I could use a silo for line 34
[13:20] <imgbot> [13:21] <ogra_> yay
[13:23] <seb128> Saviq, silo 004 is for landing or for testing?
[13:24] <seb128> Saviq, or asked differently, oSoMoN has a bugfix for gallery-app toolbar swapping being buggy, should that be delayed to after silo 4 lands?
[13:24] <seb128> mhr3, you got silo 3 for your apps scope change
[13:24] <seb128> mhr3, do you need somebody to click build for you or do you access to that?
[13:25] <mhr3> seb128, i'm good with clicking, thx ;)
[13:25] <seb128> yw
[13:25] <Saviq> seb128, oSoMoN, I've still a few things to do in silo 4
[13:25] <Saviq> seb128, oSoMoN, so land away
[13:25] <seb128> Saviq, k
[13:26] <oSoMoN> Saviq, thx
[13:29] <seb128> oSoMoN, got silo 5, do you have rights to start the build or should I do that for you?
[13:29] <oSoMoN> seb128, I can do it, thanks
[13:29] <seb128> yw!
[13:35] <davmor2> ogra_: so 95 is working fine
[13:35] <ogra_> hmm
[13:35] <ogra_> i dont get it then
[13:35] <davmor2> ogra_: I think it is just a race condition
[13:36] <ogra_> hmm
[13:42] <greyback> hey, we've a bug in a unity-mir-devel-autolanding job. See https://code.launchpad.net/~gerboland/unity-mir/enable-logs/+merge/222300 as an example
[13:42] <greyback> first off, unity-mir-devel-autolanding should not be running for that branch
[13:43] <greyback> secondly, unity-mir-devel-autolanding has target lp:unity-mir/devel, which was renamed to lp:unity-mir/devel-mir-next
[14:13] <rsalveti> asac: was on a call, what's up?
[14:21] <pmcgowan> no sil2100 today?
[14:21] <asac> yes he is off
[14:21] <pmcgowan> all week or just today?
[14:21] <pmcgowan> he is landing a library for me
[14:22] <asac> pmcgowan: stgraber barry and robru ... and if that fails ask cjwatson and slangasek
[14:22] <asac> pmcgowan: someone should continue for you
[14:22] <asac> imo
[14:27] <zbenjamin> ogra_: ping, can we get gdbserver into the device image seeds? Now that we have a debug apparmor policy we might not want a developer to make his image writeable just to be able to debug apps on the device
[14:28] <plars> psivaa: robru: ogra_: something died on flo in a major way during testing
[14:28] <plars> on one run:
[14:28] <plars> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'com.canonical.Unity.Launcher': no such name
[14:28] <plars> and on the other:
[14:28] <plars> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[14:29] <ogra_> zbenjamin, better ask the security team ... i think size wise nothing would block that ... but if it makes it possible ot open a port on a default install they might not like that
[14:29] <plars> the first was during mediaplayer, the other was during calendar_app, but both times it killed the rest of the run
[14:29] <plars> so we didn't get far
[14:29] <ogra_> plars, well, either dbus or unity crashed
[14:29] <jdstrand> I don't care if it is on the image. I would not want it running by default
[14:29] <ogra_> plars, anything in /var/crash ?
[14:29] <plars> would seem so, didn't see that on mako though
[14:30] <ogra_> jdstrand, define "this image"
[14:30] <ogra_> jdstrand, what we beuild here is the rootfs for RTM
[14:30] <ogra_> oh, sorry, totally mis-read that
[14:30] <ogra_> (ignore me)
[14:30] <jdstrand> you said to ask the security team. I'm saying just cause the binary is sitting on the disk, that isn't a problem. if that binary is running, that is different
[14:31] <plars> ogra_: yes:
[14:31] <plars> _usr_bin_unity8.32011.crash
[14:31] <plars> _usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash
[14:31] <ogra_> right
[14:31] <plars> oddly enough, the unity8 tests passed
[14:31] <ogra_> it might have crashed in some other test
[14:31]  * jdstrand notes that apps in the app store aren't allowed to specify the debug policy group
[14:31] <jdstrand> (just for background info)
[14:32] <plars> and we did get a new unity8...
[14:32] <ogra_> right, are we sure gdbserver doesnt auto-spawn if you dont manually start it though ?
[14:32] <zbenjamin> ogra_: so seems there is no problem?
[14:32] <plars> davmor2: you seeing problems with the new unity8 in 96? especially on flo?
[14:32] <ogra_> plars, i'm running it fine here
[14:33] <zbenjamin> ogra_: it does not , except the user writes some startup script for it, but for that he needs to make the rootfs writeable
[14:33] <ogra_> only used it for browsing a bit though ...
[14:33] <ogra_> zbenjamin, then i'm fine seeding it
[14:33] <zbenjamin> ogra_: awesome :)
[14:34] <davmor2> plars: not really there are minor issues like the apps suddenly disappear but that's not new and the keyboard never goes down and in gallery you can't get the toolbar up but that is about it
[14:35] <plars> davmor2: on flo, the jobs get split up into two runs, and both seemed to crash
[14:35] <plars> both had unity8 crashes in them to be clear
[14:46] <davmor2> plars: nope only welcome screen, mallitt and mediascanner here
[14:50] <imgbot> [14:50] <imgbot> [14:53] <plars> well I guess we'll see how 97 behaves soon enough
[14:55] <pmcgowan> what does 97 fix?
[14:56] <ogra_> pmcgowan, nothing ...
[14:57] <davmor2> pmcgowan: it fixes the fact that there were no afternoon roll outs for a while :)
[14:58] <zbenjamin> ogra_: will you add it to the seeds? Because i have no idea how to do that :)
[15:23] <greyback> plars: who can I poke about a broken CI job?
[15:23] <plars> greyback: start with me, and if I'm not the right person to sort it out, I'll find out who is
[15:23] <plars> greyback: which job is it?
[15:24] <greyback> plars: unity-mir-devel-autolanding job. See https://code.launchpad.net/~gerboland/unity-mir/enable-logs/+merge/222300 as an example (the failed runs)
[15:24] <greyback>  first off, unity-mir-devel-autolanding should not be running for that branch
[15:24] <greyback> secondly, unity-mir-devel-autolanding has target lp:unity-mir/devel, which was renamed to lp:unity-mir/devel-mir-next
[15:24] <greyback> so that needs updating
[15:24] <plars> greyback: isn't that the same problem you described? wrong branch?
[15:25] <greyback> plars: I didn't understand why unity-mir-devel-autolanding runs for lp:unity-mir - it used to run only for lp:unity-mir/devel (but that was recently renamed)
[15:26] <greyback> they both could be symptoms of the same problem
[15:29] <plars> greyback: well I think I know how to fix the branch, so let's start there
[15:29] <greyback> plars: magic, thanks
[15:30] <balloons> fginther, any thoughts on running pep8 selectively on merges?
[15:30] <Saviq> fginther, hey, we
[15:31] <Saviq> 're getting the friendly qmlscene crash in this job https://jenkins.qa.ubuntu.com/job/ubuntu-settings-components-qmltests-trusty
[15:31] <fginther> balloons, yeah, I was testing an updated hook against your branch, just need to finish it now
[15:32] <balloons> fginther, excellent. I was thinking it could be useful to only run it against the test_suite name folder and ignore anything else.. that could be universal
[15:32] <fginther> Saviq, ok, looks like this never got updated from trusty, let me add that to my list
[15:33] <Saviq> fginther, thanks
[15:36] <brendand> psivaa, mediaplayer_app tests failed again, as i was expecting: http://ci.ubuntu.com/smokeng/utopic/touch/mako/97:20140625.1:20140625/8726/mediaplayer_app/
[15:38] <davmor2> ogra_: meh again it seems to break on the second ring and not the first meh trying 95 again
[15:47] <davmor2> ogra_: bingo 95 second incoming call and the ringtone only plays once
[15:47] <davmor2> I'll try 94 now
[16:00] <robru> pmcgowan, it's my day for landings, how can I help?
[16:01] <pmcgowan> robru, its actually a task to get a new lib into the archive
[16:01] <pmcgowan> libqofono, ken and lukasz were working on the packaging
[16:02] <pmcgowan> its a pre-requistie for a bunch of stuff we need to land in settings
[16:02] <pmcgowan> was just asking slangasek if he had heard about it
[16:02] <robru> pmcgowan, ok no worries. can you send me an email with the details? where's the branch etc. I can clean up the packaging and start a silo after this meeting i'm in now
[16:03] <pmcgowan> robru, unfortunately, I dont know where sil was doing his wrok
[16:03] <pmcgowan> work
[16:03] <robru> ah
[16:03] <pmcgowan> robru, is he out for a while?
[16:03] <robru> pmcgowan, just today I think, should be back tomorrow
[16:03] <pmcgowan> ok then no worries
[16:03] <pmcgowan> will wait for him
[16:04] <robru> pmcgowan, https://code.launchpad.net/~sil2100 yeah it doesn't look like he pushed anything, sorry
[16:04] <pmcgowan> ok
[16:10] <seb128> ken has work on https://code.launchpad.net/~ken-vandine/+junk/libqofono-0.53 but sil2100 was supposed to pick that up and continue, so not sure if he did work he didn't push on that, would be annoying to duplicate work done ... when is he back?
[16:11] <robru> seb128, shhould be tomorrow
[16:11] <seb128> slangasek, ^
[16:11] <seb128> (just as a fyi)
[16:11] <seb128> but yeah, better to wait for him to be back then
[16:19] <brendand> robru, make sure to put this on the landing email: https://bugs.launchpad.net/mediaplayer-app/+bug/1334186
[16:20] <robru> brendand, davmor2: those bugs are both blockers for promotion, right?
[16:20] <robru> stgraber, https://ci-train.ubuntu.com/job/landing-003-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scope-click_0.1+14.10.20140625-0ubuntu1.diff can I get a packaging ack?
[16:20] <brendand> robru, i wouldn't say that one is
[16:20] <brendand> robru, it doesn't seem to affect the user
[16:20] <robru> brendand, ok thanks
[16:20] <robru> oh ok
[16:23] <davmor2> robru: mine is from today yes you can easily miss a ringer that only rings once :(
[16:23] <robru> davmor2, ok, thanks
[16:24] <stgraber> robru: looks good
[16:24] <robru> stgraber, thanks
[16:32] <slangasek> seb128: thanks for the pointer - yes, sil2100 is back tomorrow
[17:22] <elopio> ping plars: how do I enable the Jenkins job that build the packages for this project?
[17:22] <elopio> https://code.launchpad.net/~ubuntu-testcase/ubuntu-autopilot-tests/ubuntu-experience-tests
[17:23] <plars> elopio: do you mean in the smoke tests, or autolanding?
[17:24] <elopio> plars: I think I mean autolanding first. And if that works, then smoke tests too.
[17:25] <plars> elopio: adding new autolanding tests is not something I've done before, maybe fginther can help when he gets a minute but I think he's in the middle of some stuff right now. What's the timeline for it? Can you file a bug against ubuntu-ci-services-itself?
[17:26] <elopio> plars: I'll file the bug. And as soon as possible :)
[17:26] <elopio> I would like to have the first tests of that project running on the daily phone images next week.
[17:26] <plars> fginther: if you can point me at some good examples, I'm happy to give it a try
[17:27] <fginther> plars, hang. and sorry about your MP request. I forgot about it
[17:27] <fginther> hang on
[17:27] <plars> fginther: this is something different
[17:28] <fginther> plars, ok, I seenow
[17:29] <elopio> https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1334371
[17:43] <fginther> plars, I don't have a great example for you, the closest is probably ps-qa-tools in stacks/no-dailies/qa.cfg
[17:44] <fginther> plars, this project belongs inthat same cfg file.
[17:45] <fginther> plars, a few things to add to it are "target_branch: lp:ubuntu-autopilot-tests/ubuntu-experience-tests" and a different PPA
[17:45] <fginther> elopio, where does lp:ubuntu-autopilot-tests/ubuntu-experience-tests utimately belong? In the archive or a PPA?
[17:46] <fginther> plars, can the daily smoke tests use a PPA?
[17:46] <plars> fginther: not really
[17:46] <plars> fginther: it kinda defeats the purpose if you do
[17:47] <fginther> plars, that's what I expected, just wanted to confirm
[17:47] <plars> fginther: or do you mean the scripts? I think the scripts support that, if you mean for using it in the autolanding tests
[17:47] <plars> fginther: it's just not something we do for daily smoke, since we want to test the actual image without changes
[17:47] <fginther> plars, if I understand elopio, this is something they want run as part of the image smoke tests
[17:48] <plars> fginther: he said autolanding first, then eventually smoke also once it's really in the image
[17:48] <plars> elopio: is that right?
[17:49] <fginther> plars, that's what I understood, but if this is going into the image, does it need to go through ci-train?
[17:50] <plars> fginther: probably so, does that not still use the tests defined in cupstream2distro-config?
[17:52] <fginther> plars, nope, ci-train uses nothing in lp:cupstream2distro-config. We do still setup MP testing there, so we need to add something. I'm just trying to understand if that something includes autolanidng
[18:00] <kgunn> ogra_: if you're still on, who's looking after qt stuff while Mirv is away ?
[18:00] <ogra_> kgunn, no idea, sorry
[18:02] <elopio> plars, fginther: sorry, I was in a meeting.
[18:03] <elopio> if it's on the archiver or on a PPA is the same for me.
[18:03] <elopio> it should go through ci-train, yes.
[18:25] <rsalveti> ogra_: where is the image bot? :-)
[18:25] <ogra_> imgbot, stunt
[18:25]  * imgbot rolls on its back and purrs
[18:25] <ogra_> awake and happy it seems
[18:26] <rsalveti> ogra_: oh, didn't see it announcing image 97
[18:26] <rsalveti> but cool, just saw the message
  [18:26] <rsalveti> ogra_: do we have a lp link for the image builds?
[18:26] <rsalveti> didn't yet check the work done by colin
[18:26] <ogra_> for the logs you mean ?
[18:27] <rsalveti> ogra_: yeah, if we have a launchpad interface, and how to trigger it as well
[18:27] <ogra_> nothing changed there yet
[18:27] <ogra_> it is still driven by nusakan/via the iso tracker
[18:27] <rsalveti> got it, cool then
[18:27] <rsalveti> just the backend part of it was moved
[18:27] <ogra_> right
[18:28] <ogra_> and the old builders turned into package builders
[18:28] <rsalveti> yeah, that's nice
[18:28] <ogra_> the triggering of builds via LP is part of the derived distro stuff i think
[18:35] <plars> greyback: I think the patch for the unity-mir branch you raised earlier landed if you want to try it again and see if it does what you expect now?
[18:36] <greyback> plars: will do
[18:49] <sil2100> Geez...
[18:50] <sil2100> So, I wanted to actually log in earlier, but of course my utopic seems to be b0rken
[18:51]  * sil2100 just now tries to get his X back
[18:53] <robru> sil2100, hmm, what's the danger, should I avoid upgrading?
[18:58] <sil2100> robru: yeah... I think I either upgraded in a wrong moment or had some leftovers
[18:58] <robru> sil2100, i see
[18:59] <robru> sil2100, so, welcome back! how was the painting project? ;-)
[18:59] <sil2100> robru: pffff, never again!
[18:59] <sil2100> ;p
[18:59] <robru> haha
[18:59] <robru> sil2100, did your parents make it too stressful? I've painted houses before, usually i find it relaxing
[19:02] <kgunn> robru: happen to know where the source for Qt is ? like if we wanted to distro patch a bug...which branch would we target ?
[19:03] <robru> kgunn, uh... nope. rsalveti or Mirv I think would be the best to ask about that
[19:03] <rsalveti> kgunn: I'd basically say to use the src package
[19:03] <robru> kgunn, usually in silos I see those as source package uploads, which means neither I nor citrain knows where that code is actually hosted
[19:04] <rsalveti> we have a packaging branch as well if needed
[19:04] <rsalveti> but they are usually uploaded directly as source package uploads
[19:05] <rsalveti> kgunn: I'd recommend grabbing the source package for the package you want to change, and checking if there is a packaging branch available
[19:05] <rsalveti> like for qtbase:
[19:05] <sil2100> robru: in this case the problem was that the walls in that building are terrible
[19:05] <rsalveti> debian/control: Vcs-Bzr: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src
[19:06] <rsalveti> then just propose a merge request and ping the maintainer (usually Mirv)
[19:06] <sil2100> robru: how to say it... they're not 'flat', so there was a lot of polishing, filling, smudging, painting, painting over
[19:06] <kgunn> rsalveti: so not all qt packages have packaging branches?
[19:06] <sil2100> Scratching, caughing
[19:06] <sil2100> ;)
[19:06] <robru> sil2100, ahhh, heh
[19:06] <robru> sil2100, sooooooo, since you're back, are you doing the landing email? or should I? ;-)
[19:07] <rsalveti> kgunn: not in ubuntu necessarily, as some might just be the same package available in debian
[19:07] <kgunn> rsalveti: got it...so in case of "no mods" we just copy over
[19:07] <kgunn> until we need to change, then we create a branch ?
[19:07] <rsalveti> one way that always work is getting the src package, changing as needed and giving the debdiff to a core-dev
[19:07] <rsalveti> kgunn: yeah
[19:07] <sil2100> robru: I'll try doing it, but if I fail in getting lightdm up in some near time then I'll ask you to do it :D
[19:08] <robru> sil2100, ok
[19:08] <sil2100> Since I would really hate using Mutt for this
[19:08] <robru> sil2100, I was asked to include Bug #1334186 and Bug #1334248 but only the second one is a promotion blocker
[19:09] <sil2100> robru: ouch
[19:15] <cjwatson> rsalveti: The backend part is still the same, yes; to build an image with an extra PPA, you prefix the command on nusakan with EXTRA_PPAS=owner/name (and the PPA in question must be devirtualised, for the time being)
[19:16] <rsalveti> cjwatson: got it, cool
[19:16] <cjwatson> ogra_: Triggering of builds> No, not quite.  There are no plans at present to allow triggering builds from LP (although in the slightly further future when LP becomes a portal to various information held outside LP then maybe that will be possible).  However, it's planned for the new CI engine to have a separate cdimage instance which can do image builds from silos.
[19:17] <ogra_> ah
[19:17] <ogra_> then i mixed that up
[19:17] <cjwatson> ogra_: The old builders aren't quite package builders yet because we ran into a roadblock (they're also used as dak-based builders for IS, and the sbuild/buildd there clashes with LP at the moment), but hopefully we'll get that fixed soonish.
[19:19] <cjwatson> ogra_: I have got way more familiar with the details of our buildd setup over the last few months than I entirely wanted to be ;-)
[19:19] <ogra_> haha
[19:20] <cjwatson> But we're near a tipping point of lots of cool stuff.
[19:20] <cjwatson> Once scalingstack happens it should be possible to do livefs builds on virtualised builders as well, although maybe not for ARM.
[19:21] <cjwatson> (Doesn't work before that because live-build and the hardy kernel are not friends ... like I say, details I didn't entirely want to know about)
[19:21] <ogra_> ugh, hardy ?
[19:21] <cjwatson> Xen
[19:21] <cjwatson> Which is not allowed to be upgraded in the DC, it has to be cloudified
[19:21] <ogra_> oh
[19:22] <cjwatson> Hence the saga which is https://rt.admin.canonical.com/Ticket/Display.html?id=62272
[19:23] <ogra_> wow, thats a lot to scroll !
[19:27] <sil2100> Oh crap, I think I found the reason why my lightdm doesn't start
[19:38] <sil2100> It's alive!
[19:57] <robru> sil2100, what was wrong with lightdm?
[20:02] <fginther> balloons, can you check the latest test results for https://code.launchpad.net/~nskaggs/reminders-app/fix-evernote-sdk-python3/+merge/223493
[20:06] <sil2100> robru: eh... I had some custom modifications in init/lightdm.conf which now became obsolete ;/
[20:06] <robru> sil2100, ah so i should be safe then
[20:06] <sil2100> So lightdm didn't even start
[20:06] <sil2100> Yeah...
[20:07] <balloons> fginther, ohh right.. so if anyone asks you about weird stuff with pep8 and jenkins, do let them know a new version landed in utopic which implements new rules
[20:07] <balloons> fginther, this is one of the new rules, so it passed before but doesn't under the new rule ;-)
[20:09] <balloons> fginther, so this looks good I'll update the mp to fix these errors, ty
[23:38] <josharenson> I might be asking this incorrectly, but is there a way, from within the jenkins website, to determine if a build is a normal MP or a siloed build?