/srv/irclogs.ubuntu.com/2015/03/05/#ubuntu-ci-eng.txt

robrutedg: you're welcome00:07
tedgrobru, With the UAL branch we have a build dep on Mir, which means no more PPC for us. Is there a way to note that? Or just tell QA, etc. when I'm done testing.00:58
robrutedg: the mir build dep is new?00:59
tedgrobru, Yeah00:59
robrutedg: k, there's not a great way to "note" this... you need to ask somebody from #ubuntu-release to delete the ppc binaries from the archive. you can build the silo before that happens, but just be aware that the build job will fail due to the ppc failure.01:00
robrutedg: I don't think qa will care or even need to know. but if you don't get those ppc binaries deleted from the archive, the package will fail to migrate through proposed as wel01:00
tedgrobru, ah, okay. But we don't need to do that until they're being published, right?01:00
robrutedg: well the sooner the better. without deleting the binaries the silo will just say 'build failed' so it won't show up on qa's radar to test it.01:01
tedgAh, I see01:02
robrutedg: I can manually poke the silo status to say 'Packages built' so it shows up for qa though, just ping me when you're ready for that01:02
tedgrobru, I think it's ready for that, silo 1701:02
tedgI still need to test it though.01:02
tedgBut the build is complete01:03
robrutedg: ah I see, the other arches are done but ppc is depwait. yeah ok I can poke the silo status to say it's built01:03
robrutedg: k, dashboard looks correct. just mark is as tested:yes when you're ready and it should show up for qa.01:07
robrutedg: also ping me whenever you rebuild it, I'll have to do this manually each time.01:08
tedgrobru, Not sure if you're reading #ubuntu-release, but there's a plan to make PPC work for the other packages to save a library cascading dependency issue.01:16
robrutedg: just read it. k. if you can make the package build on ppc then there's nothing else on our end. if it builds, it builds, and everything is happy.01:20
imgbot=== IMAGE 123 building (started: 20150305-02:05) ===02:05
=== jamesh__ is now known as jamesh
imgbot=== IMAGE 123 DONE (finished: 20150305-03:25) ===03:25
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/123.changes ===03:25
=== chihchun_afk is now known as chihchun
bzoltan_does anybody know what that log means? http://pastebin.ubuntu.com/10535387/ It comes zillions of times when the UITK AP tests started ...05:45
sil2100ogra_: hey! You have a moment for a packaging ACK? It's for unity7, but looks safe: https://ci-train.ubuntu.com/job/ubuntu-landing-016-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity_7.3.1+15.04.20150227-0ubuntu1.diff08:40
ogra_sil2100, ACK08:43
sil2100\o/08:43
sil2100cihelp: hey! It seems the krillin vivid dashboard again didn't run all the tests - can we get the missing devices re-ran? http://rtm-dashboard.ci.ubuntu.com/smokeng/vivid/touch/krillin/134:20150305:20150210-95b6a9f/381/08:53
robrusil2100: ^^^ hmmm I'm looking into this09:51
robruwelll allrighty then09:56
evsil2100: it's with us. How critical is this? Would it be okay if it waited until Francis, our vanguard for the day, started?10:01
sil2100Yeah, I suppose it can wait10:08
nerochiarosil2100: fginther: psivaa_: i think I have a problem with licensecheck again. According to a previous conversation that we had CI runs licensecheck with this script: http://paste.ubuntu.com/9898679/  When I poked you about this before, licensecheck was getting confused because I had files I copied from QT with multiple licenses. I fixed that but I had not noticed that the script also checks that the copyright is by Ca10:14
nerochiarononical,Android,Digia or Google. Why does it do that ? As long as we are using open source licensed software it should not matter who the author is...10:14
sil2100huh, it does?10:18
sil2100Oh, it does10:18
sil2100Ok, strange, I'm sure there was a reason for that, but I don't have the required info10:18
psivaa_nerochiaro: I'm not sure how that policy was used, i'll raise it with fginther10:23
nerochiaropsivaa_: thank you10:24
psivaa_nerochiaro: for the future, please use 'cihelp' for this type of pings for better handling of them :)10:24
psivaa_so that there will be more people that will get notified10:24
nerochiaropsivaa_: i pinged you and the others because you already had background on the issue having helped me before with it10:24
nerochiaropsivaa_: but i will add cihelp (when it is online)10:25
psivaa_nerochiaro: cihelp is not a bot, but a word that will highlight our team10:25
psivaa_and thank you10:25
nerochiarooh I see :) thanks10:26
sil2100robru: btw. aren't you supposed to be sleeping? ;)10:30
nerochiarogreyback: hi, i have seen you are assigned to bug 1422797 now. I don't understand why it has changed target and what is the status. can you please update me ?10:57
ubot5bug 1422797 in qtmir (Ubuntu) "Qt app aborts if it cannot connect to Mir - QtMir rejecting the connection" [High,New] https://launchpad.net/bugs/142279710:57
greybacknerochiaro: the last comment I wrote is my summary so far. What's unclear?10:58
nerochiarogreyback: what kind of information you need to be able to continue10:59
greybacknerochiaro: in a nutshell, I need to verify that it's not possible for 2 instances of camera-app to ever run simultaneously with AP11:02
nerochiarogreyback: I guess also what I don't understand is if Mir is doing the right thing to refuse AP to launch a second instance of camera, and therefore it is AP that has to be fixed so that it does not try to do so11:04
greybacknerochiaro: indeed. It could be AP, or qtmir/unity8, which is to blame here.11:06
greybackand I can't quite tell from the unity8 log which is the case11:06
nerochiarogreyback: and having a CI run with all the other associated logs would help you ?11:07
nerochiarogreyback: i mean, a CI run where this problem happens11:07
greybacknerochiaro: I'd need verbose AP logs, perferably printing when it actually launches & fully has killed the camera process11:08
greybackerr it's actually upstart launching/killing, but you see what i mean11:08
nerochiarogreyback: yes, is that something we can ask the CI people to set up for us11:09
greybacknerochiaro: I'd also be tempted to add more debug output to qtmir11:09
greybacknerochiaro: there's no way you can repro this locally?11:09
nerochiarogreyback: i have not been able to do so so far11:10
greybacknerochiaro: that makes this hard. What are CI doing that we're not?11:14
nerochiarogreyback: not sure. are they just running autopilot3 run camera_app ?11:17
nerochiarogreyback: this is what i did11:17
nerochiarogreyback: in a loop11:17
greybacknerochiaro: I always assumed they follow this guide https://wiki.ubuntu.com/Touch/Testing#Running_Click_tests11:17
greybacknerochiaro: I'll spin up a mako now and see11:18
nerochiarogreyback: the latest and greatest on how to run tests (from some info Bill sent me) just tell me to ssh into the device and run autopilot3 manually. And I never managed to get phablet-click-test-setup anyway (it fails to download some of the AP emulators for the sdk)11:20
greybacknerochiaro: okay. it used to work for me, will see how it goes11:21
nerochiarogreyback: ok. please keep me posted. it is my test-fixing day today so i am trying to get at the bottom of as many issues as i can11:24
nerochiarogreyback: and if you have ideas on things i can run locally too, please let me know11:24
greybacknerochiaro: sure thing11:24
sil2100dbarth_: ping11:35
sil2100dbarth_: do you have any updates related to the u1 issue on ubuntu-rtm? We'd need it fixed by next week's milestone11:35
dbarth_sil2100: trying to land a new patch, which is part of silo 010, but having issues with multi-arch support11:37
dbarth_sil2100: i touched base on that with davmor2 earlier this morning11:37
davmor2sil2100: beat you to it :)11:38
sil2100\o/11:42
sil2100:)11:42
rvrdbarth_: Silo 13 (ubuntu-rtm) doesn't have any bug linked12:12
dbarth_rvr: let me fix that12:19
=== alan_g is now known as alan_g|lunch
=== MacSlow is now known as MacSlow|lunch
nerochiarogreyback: i tried running tests via phablet-test-run and I got a MIR failure13:04
nerochiarogreyback: [1425560625.112570] <ERROR> mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.12.0+15.04.20150228/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int)13:04
nerochiaroDynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_errorEEEE13:04
nerochiarostd::exception::what: Attempt to set swap interval on screencast is invalid13:04
greybacknerochiaro: they can be ignored I think, the tests still pass13:04
nerochiarogreyback: i see13:04
greybackmay cause camera-app to crash instead of cleanly shut down13:05
nerochiarogreyback: let me remove all crash files, so i know if it does13:10
greybacknerochiaro: it doesn't seem to crash here, dunno why13:10
nerochiarogreyback: what platform ?13:10
nerochiarogreyback: i am on krilling, will try mako too13:10
greybackmako13:10
nerochiarogreyback: ok, mako is next13:11
dbarth_rvr: you meant 010 /rtm/ ?13:12
rvrdbarth_: ubuntu-rtm/landing-013 - unity-webapps-qml : alex-abreu, dbarth13:12
greybacknerochiaro: this is my 4th try at the camera-app tests. I've got 5 tests reliably failing , none due to a crash13:13
nerochiarogreyback: let me see what I get here on mako,but i am afraid it will not be very different from what you see13:15
greybacknerochiaro: I'm assuming CI is using mako?13:16
nerochiarogreyback: both mako and krillin13:16
greybackoh13:16
nerochiarogreyback: and both vivid and rtm13:16
greybacknerochiaro: and does this error pop up on _all_ combinations randomly?13:17
nerochiarogreyback: good question. not sure13:18
nerochiarogreyback: both utopic and vivid on krillin for sure13:22
greybacknerochiaro: ok then I'll switch to testing on kryllin13:23
=== alan_g|lunch is now known as alan_g
=== MacSlow|lunch is now known as MacSlow
fginthernerochiaro, I'll start looking at the licensecheck issue shortly. As I recall, that script was supplied by another team, so I need to do a little research on it14:04
nerochiarofginther: thanks14:05
sil2100fginther: maybe Didier would know something about it?14:05
fginthersil2100, looks like mzanetti was involved in the original.14:08
fginthermzanetti, do you remember this: http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/view/head:/hooks/A10checklicenseheaders.in14:09
mzanettifginther: yes14:09
mzanettifginther, what's the issue?14:11
fginthermzanetti, there was a question about why allowedlicenses was limited to "(Canonical|Android|Google|Digia)"14:11
fgintherand not just any opensource copyright14:12
mzanettifginther, hmm... I guess it could be changed... no real reason for that IIRC. It was useful as it pointed out some badly licensed copied code14:13
fginthermzanetti, thanks that does help. I guess it was an adequate check at the time14:14
mzanettifginther, yeah, it only allowed Canonical and Android in the beginning, Google and Digia were added later14:15
mzanettiif more are needed I guess it does make sense indeed to allow any... but IANAL, you might want to check back with Didier or Pat if we're ok with importing any sort of license14:15
mzanettimight be a conflict with the CLA14:16
mzanettifginther, ^14:16
fginthermzanetti, thanks, I will check with Pat14:16
sil2100hm14:16
sil2100Yeah, Didier might know as well but he might not have the most up-to-date info14:16
fginthermzanetti, there's  another check script that appears to be more relaxed: http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/view/head:/hooks/A10checklicense3party.in14:16
mzanettifginther, ah right... now I remember, the first one excludes anything in a 3rdParty directory14:17
mzanettiwe probably don't want to mix those things like crazy to be able to tear it apart again if we ever would need to14:18
fginthernerochiaro, do you have a branch available with the code you are trying to submit so I can test a few things?14:18
nerochiarofginther: the code is actually in camera trunk as far as I know14:19
fginthernerochiaro, ok14:20
fginthermzanetti, thanks again, that makes sense. I'll follow up further with Pat as he appeared to be involved in the origins of this as well14:21
mzanettiyw14:21
nerochiaromzanetti: fginther: don't confuse the type of license with the copyright holder please. checking for only certain license types is something we must do, but AFAIK there is no reason to do checks on the copyright holder14:26
nerochiaromzanetti: fginther: whowever is the original author of some GPL3 code is irrelevant, all we should care about is that it is GPL3.14:26
mzanettinerochiaro, well, we do make contributors sign a CLA. copying other's code bypasses that14:27
mzanettiso... we might want to check on the copyright holder too14:27
fginthernerochiaro, so as this code is already in trunk, is this check blocking you right now?14:29
nerochiarofginther: it blocks every MR, in the sense that CI isn't run on them14:30
fginthernerochiaro, ack, I see it now14:30
nerochiaromzanetti: it is not contributions that someone has written for us, where a CLA would apply. it is open source code we are taking and using according to its license14:31
nerochiaromzanetti: different things14:31
bzoltan_sil2100:  I can reproduce reboot cycle with 100% certainity ... who should I contact ?14:37
sil2100bzoltan_: ouch, ok, first of all - did you fill in a bug?14:37
sil2100bzoltan_: once we have a bug we can track it and escallate14:37
bzoltan_sil2100:  against what?14:37
sil2100Let me think, does it happen in a specific AP test run?14:37
sil2100Or what is the trigger for the cycle to start?14:38
bzoltan_sil2100:  running  the UITK test plan after the dialer app rebooting the device runs inti reboot cycle14:43
sil2100bzoltan_: so basically dialer-app's AP test causes this trouble - then I would set dialer-app as the current component and then it will change once the root cause is identified14:45
bzoltan_sil2100:  I try to make a simple script does it... but I am positive that the dialer app's developers would not be able to fix it14:46
sil2100bzoltan_: yeah, but I suppose it's a good place to start the search15:04
sil2100bzoltan_: bugs can be easily retargetted15:04
bzoltan_sil2100:  true15:04
bzoltan_sil2100:  I wonder if there is a way to get out some logs form the device before it enters the loop15:05
bzoltan_sil2100:  or more precisly said.. what logs should I back up before I let the device reboot?15:05
bzoltan_sil2100:  because I can adp pull before each reboot in my script15:06
sil2100bzoltan_: hard to say, first the most essential ones I suppose - so syslog and the output of autopilot (maybe with verbose debugging enabled)15:14
mterryWhere can I find the pbuilder hook B09qmluitests ?  I want to see what it's doing15:15
sil2100o/15:16
bzoltan_sil2100:  OK, I try to capture as much logs as possible15:16
sil2100bzoltan_: once we have the basic ones maybe we'll know what can cause that, and what additional logs might be useful15:17
sil2100bzoltan_: thanks!15:17
sil2100fginther: hey, regarding smoketesting for vivid+krillin, we noticed that some devices seem to have been down and didn't run tests15:17
sil2100fginther: do you know what happened to those?15:17
fginthersil2100, so far I've restarted the failed builds and took only a brief glance at the problems.15:18
sil2100fginther: I'm asking since bzoltan_ reported that he's able to enter a reboot-loop during AP testing, so I wondered if maybe something like that just happened15:19
fginthersil2100, there were actually 3 different problems, the wifi network failed to come up for one, another the screen unlock never worked, and the third failed to download the image15:19
sil2100Although bzoltan_ is able to reproduce it since a few images15:19
sil2100Ah, ok, so unrelated15:19
sil2100fginther: thanks ;)15:19
fginthersil2100, hmm, that's something I'll check for though15:19
fginthermterry, http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/view/head:/hooks/B09qmluitests.in15:21
mterryfginther, thanks!15:26
om26ertedg, Hi!15:32
tedgom26er, Hi!15:32
om26ertedg, the indicator-messages TestPlan needs to be updated, should atleast contain a testcase for the fixed bug in silo 1815:32
fginthermterry, hey, I just noticed that we're seeing lots of screen unlock failures during smoke testing on krillin. Do you know of anything that might be causing this?15:33
mterryfginther, huh...  no?15:33
tedgom26er, The wiki is out of date: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-messages/trunk.15.04/view/head:/tests/manual15:35
fginthermterry, ack, I'll start with a bug report then15:35
om26ertedg, aah15:35
=== om26er is now known as om26er|dinner
nerochiarogreyback_: when i use phablet-test-run i get this error autopilot.exceptions.ProcessSearchError: Search criteria (pid = 29537, object path = '/com/canonical/Autopilot/Introspection') returned no results , but i don't get it when I run autopiliot3 directly from an ssh shell. do you know what it is ? (i enabled the dbus probe, which is usually the cause for that)15:41
greyback_nerochiaro: not a clue. I had the same fail. Suspect phablet-test-run broken15:42
ogra_isnt phablet-test-run deprecated since a while ?15:42
nerochiaroogra_: that's what I thought, but isn't CI using it ?15:42
nerochiaroogra_: we are trying to run the tests as CI would15:42
ogra_dunno .... i just know that pitti recently promoted adt-run15:42
ogra_and complained that people still use phablet-test-run15:43
* ogra_ was doing snappy work for a while, i'm a little out of the loop15:43
nerochiaroogra_: i normally just ssh in and use autopilot3 run15:43
ogra_iirc adt-run prevents you from making the system writable and modifying it in any way15:44
ogra_which will get you more accurate results15:44
nerochiarocihelp: what tool does CI use to run tests ? phablet-test-run ? straight autopilot3 run ? something else ?15:44
fginthernerochiaro, CI uses a setof scripts that wrap around phablet-test-run: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/15:45
fginthernerochiaro, that doc should help if you want to recreate the exact testing15:45
ogra_fginther, wasnt that supposed to be switched to adt-run by now ?15:45
rvrdbarth_: I took a look to the bug linked to the merge proposal of silo 13. It is not critical nor approved to land in RTM.15:46
evfginther: what a perfectly timed question, eh? :)15:46
nerochiarofginther: "This is a small wrapper that uses phablet-tools to drive the tests. The script can run one or more autopilot tests. By default it will reboot the device between each test and ensure the device is settled using the system-settle script" << does it really do this on CI ?15:47
fgintherogra_, that wold have been nice, but the work that was in progress had a lot of missing pieces and got shelved due to higher priority work15:47
ogra_ah15:47
fginthernerochiaro, yes, it reboots the device between each test suite (not test case in case that was your question)15:48
ogra_well, phablet-test-run is rather unmaintained since a while15:48
plarsogra_: also not everything has adt tests yet15:48
ogra_i thought pitti said he was done so far15:48
plarsogra_: adt-run worked fine last I tried it, but several projects didn't have tests that would work with it yet. But it's been a while since I looked at it15:50
plarsogra_: fairly important ones too, like unity815:50
sil2100dbarth_: can I get these merges approved? :)15:58
sil2100dbarth_: https://code.launchpad.net/~daker/ubuntu-html5-theme/fix.1427729-1427909/+merge/251678 https://code.launchpad.net/~mardy/unity-webapps-qml/app-access/+merge/21932115:58
nerochiarofginther: is the test runner script supposed to work even if we run it on a machine that has not been freshly provisioned with the provision script ? it blocks for me on "+ adb-shell sudo apt-get install -yq --force-yes python3-wand python3-mediainfodll"16:03
nerochiarofginther: (i had these two packages already installed)16:03
ogra_nerochiaro, they make sudo NOPASSWD in their /etc/sudoers16:04
ogra_for the lab16:04
ogra_you would need the same i guess16:05
nerochiaroogra_: so that wiki page is essentially lying ;)16:05
ogra_which wiki page ?16:05
dbarth_sil2100: yes16:05
nerochiaroogra_: nevermind, bad joke. this one http://ubuntu-test-cases-touch.readthedocs.org/en/latest/16:06
fginthernerochiaro, I think ogra_ is right, the sudoers file gets setup by provision.sh, let me have alook16:06
nerochiarofginther: i just checked, it is setup by provision16:06
nerochiarofginther: i don't mind setting up my device once with it, but I would rather not have it wipe all the data. is it possible ?16:07
fginthernerochiaro, I think there is... provision.sh should honor an env that tells it to skip the actual flash16:07
fgintheran env var16:07
nerochiarofginther: i'll look into that, thanks16:07
fginthernerochiaro, nvm, I was thinking of a different script16:08
nerochiarofginther: i think you can pass the arguments to ubuntu-device-flash as a parameter, so probably just omitting --wipe there will do. let me check16:09
fginthernerochiaro, be default is uses --bootstrap16:10
fginthernerochiaro, but you are right in that you can override the u-d-f options with $IMAGE_OPT16:11
fginthernerochiaro, I'll look into adding a 'skip ubuntu-device-flash' option for that script, sounds like it might be useful16:14
nerochiarofginther: the wifi files are the NM wifi config files, right ? from /etc/NetworkManager/system-connections/16:14
nerochiarofginther: agree16:14
fginthernerochiaro, yes, the nm config file is passed directly to phablet-network16:15
ogra_nerochiaro, you can use the -n option if you want to supply a different nm config16:16
nerochiaroogra_: got that, it is running already16:16
ogra_cool16:16
nerochiaroogra_: fginther: unfortunately it still needs to wipe, since we need to setup a password with --password and it is not supported without wiping for some reason16:18
ogra_you can just adb shell and call passwd16:18
nerochiaroogra_: i think i will just comment out the call to u-d-f in the script. might as well do that than trying to convince it to run it with the right options16:19
fginthernerochiaro, also make sure you set the env var PHABLET_PASSWORD if you're not using the default16:20
fginthernerochiaro, by the way, thanks for test driving the how-to, it's been heavily revised this week :-)16:21
mterryfginther, I'm debugging a test failure that happens during a qmluitest run (but not during build), which is why I was curious about the hooks.  One thing that would be nice for investigating such things in the future is a logged call to "env" to dump the environment, right before running tests/building.  Just a thought16:21
nerochiarofginther: my pleasure. thanks for helping me with this stuff. i find it fairly maddening when i go through it alone and weird errors pop up that I have to figure out on my own16:22
nerochiarofginther: for example this one: bzr: ERROR: Requested revision: 'latest' does not exist in branch: bzr+ssh://bazaar.launchpad.net/+branch/camera-app/16:23
fginthernerochiaro, we're tying to polish this so that we can share it more widely. It helps to have someone involved who didn't help write it16:23
nerochiarofginther: why is it even trying to do that ?16:23
nerochiarofginther: can i point it to a local branch ?16:24
fgintherphablet-click-test-setup will read the test branch location from the click manifest on the device16:24
fginthernerochiaro, there a section for overriding this with a local branch "Running Tests for a Modified Click Application"16:25
fginthernerochiaro, but it sounds like that won't work as the manifest is already pointing to something called "latest"16:25
=== om26er|dinner is now known as om26er
nerochiarofginther: wait, should i run the provision script from within the branch of the app i want to test ?16:26
fginthernerochiaro, no that won't help16:26
sil2100bzoltan_: did you fill in the bug :) ?16:27
nerochiarofginther: so where is it getting the "latest" from ?16:27
fginthernerochiaro, what do you get when you run "adb shell click info <app-name>"16:27
nerochiarofginther: where does it get <app-name> from in the first place ? I am not passing any app name to the provision script16:28
fginthernerochiaro, did you manually install a click app?16:29
nerochiarofginther: yes16:29
nerochiarofginther: does it detect that ?16:30
fginthernerochiaro, no it doesn't detect that, but phablet-click-test-setup consumes that information16:30
fgintherthe location of the test sources for what ever app you installed are defined in the manifest16:31
nerochiarofginther: but i am not calling that. i am calling provision.sh, why would provision.sh branch camera-app ?16:31
fgintherit's tryinig to provision the test sources for all installed click apps16:31
nerochiarofginther: where is the manifest ?16:31
nerochiarofginther: oh i see16:31
nerochiarofginther: then it makes sense, since the manifest for camera-app will say "latest" as the version16:32
fgintheryou can manually skip that with export SKIP_CLICK=116:32
nerochiarodoing that16:32
nerochiarobetter add a note to the document about that16:33
fginthernerochiaro, that usually works, I don't really understand why the click app you have is using latest16:33
fginthernerochiaro, ah, I suspect the real revno gets injected when it's built before upload to the store16:34
nerochiaroi think that's the case16:34
nerochiarogreyback_: i just got this : 16:39:36.477 ERROR _launcher:206 - Timed out waiting for Application with app_id 'com.ubuntu.camera_camera_3.0.0.latest' to stop.16:40
nerochiarogreyback_: which i think means i managed to repro the bug16:40
greyback_nerochiaro: I'm not sure what prints that16:40
greyback_it's not a mir/qtmir message anyway16:41
nerochiarogreyback_: i think it is autopilot, but it is one of the messages we get when we encounter the bug from MIR16:42
greyback_nerochiaro: ok. Do you see a camera-app process running?16:42
nerochiarogreyback_: no it was gone16:43
greyback_nerochiaro: is there a "REJECTED" message in the unity8 log?16:43
nerochiarolet me check that16:43
nerochiarogreyback_: where do i find that log ?16:44
greyback_nerochiaro: ~/.cache/upstart/unity8.log16:44
nerochiarogreyback_: ApplicationManager REJECTED connection from app with pid 6080 as no desktop_file_hint specified16:44
greyback_nerochiaro: ok. What device and release are you using?16:45
nerochiarogreyback_: krillin/vivid16:46
greyback_nerochiaro: and did any of the previous AP test fail?16:46
nerochiarogreyback_: yes16:46
greyback_fail due to a crash?16:46
popeysil2100: meeting clash, so won't be at the landing meeting today, sorry.16:47
sil2100popey: ACK16:47
greyback_nerochiaro: output of the camera-app log file in that directory might give a clue maybe16:47
greyback_nerochiaro: could you confirm for me too, is the camera-app being launched by AP with a --desktop_file_hint switch?16:48
nerochiarogreyback_: no crash files for camera, so i guess not16:48
nerochiarogreyback_: i can't tell, but maybe fginther can confirm that ?16:48
greyback_nerochiaro: so qtmir is the one deciding to block your application. lp:qtmir:/src/modules/Unity/Application/applicationmanager.cpp:authorizeSession16:51
greyback_exactly why it's made that decision is the puzzle16:51
nerochiarogreyback_: if it was running the app without desktop file hint it would never be able to run16:54
nerochiarogreyback_: could it be that mir is not receiving the hint for some reason, and refuses the app ?16:54
sil2100robru, davmor2, rvr, ogra_: let's skip the meeting today16:54
rvrsil2100: Ack16:54
greyback_nerochiaro: the correct way would be for it to be launched by upstart-app-launch16:54
robrusil2100: let's skip the meeting every day ;-)16:54
greyback_nerochiaro: as that's using the same code path that users do16:55
sil2100robru: ssshh! That's the plan ;)16:55
sil2100But don't tell anyone16:55
nerochiarogreyback_: let me dive into what the script is doing16:55
greyback_nerochiaro: qtmir is getting the PID of the process, it opens the /proc/$PID/environ and reads the command line arguments listed there. It checks if desktop_file_hint is set, and opens and verifies the desktop file listed there16:56
greyback_nerochiaro: this only happens as a fallback when upstart-app-launch isn't used. It's not a good code path16:57
fginthernerochiaro, sorry, I had stepped away, but it looks like you found the answer?16:57
nerochiarofginther: no, we are still trying to figure it out. does AP run the app via upstart-app-launch ?16:58
fginthernerochiaro, I think that's encoded in the autopilot tests themselves, hopefully this is obvious in the test sources16:59
nerochiarofginther: sorry, are you sayign each AP test can choose how to run the app ?16:59
ogra_sil2100, fine with me16:59
fginthernerochiaro, I believe that's how it works, see: http://bazaar.launchpad.net/~phablet-team/camera-app/trunk/view/head:/tests/autopilot/camera_app/tests/__init__.py17:00
fgintherlaunch_test_installed is setting a hint file17:00
nerochiarofginther: shouldn't it be launch_click_installed ?17:01
nerochiarofginther: sorry, launch_click_package17:01
nerochiarowhich is from autopilot.testcase.AutopilotTestCase17:02
fginthernerochiaro, that's a question that is outside of my expertise17:02
nerochiarofginther: no problem. who should we ask to ?17:02
fginthernerochiaro, tedg perhaps?17:03
fginthernerochiaro, you also might try elopio or veebers17:03
Ursinhasil2100: are you around?17:03
sil2100Ursinha: hey! What's up?17:03
Ursinhasil2100: do you have time to join us in a discussion about smoke testing? :)17:04
sil2100Ursinha: I could drop by for a moment, but I could just give basic insight17:04
Ursinhasil2100: that's good enough17:04
nerochiarogreyback_: no problem, thanks for the help so far. i reprod using the CI scrips, so you migth want to go that way too17:06
greyback_nerochiaro: did you install python3 packages on the device until the CI scripts worked?17:06
greyback_http://pastebin.ubuntu.com/10538830/ is what I got just using ci scripts17:07
nerochiarogreyback_: yes, i installed python3-autopilot manually17:07
greyback_ok17:07
greyback_will do that so17:08
greyback_o/17:08
popeysil2100: & davmor2 Advanced warning, tomorrow morning during the landing call I will request a re-test of reminders - not ready yet, but should be by tomorrow.17:26
sil2100popey: \o/17:28
sil2100Wohooo!17:28
sil2100bzoltan_: ping17:41
=== alan_g is now known as alan_g|EOD
nerochiaroelopio: do you know if it is possible to call methods via AP or if we can just manipulate properties ?18:17
elopionerochiaro: it is possible, but discouraged and it's in a file that might get deleted with AP.18:17
nerochiaroelopio: i don't understand18:17
nerochiaroelopio: what file do you mean ?18:18
elopionerochiaro: generally, when you need something that's not exposed through the user interface, it means that your UI is missing something, or you shouldn't be writing an autopilot test.18:18
elopionerochiaro: so we have been thinking about removing autopilot code to inspect beyond properties.18:18
elopionerochiaro: what's your problem? maybe we can find an alternative.18:19
nerochiaroelopio: when setting up a test I need to add something to a model18:19
nerochiaroelopio: and the way to do it apparently is by calling a method on it18:19
elopionerochiaro: I need a bigger picture. What are you trying to set up?18:21
nerochiaroelopio: in camera app we need to add photo files to the pictures model during a test, so that we can check that the UI element indicating there are no pictures in the photo roll disappears18:34
elopionerochiaro: in a user acceptance test, you should do that by putting a file to the pictures directory.18:35
elopioif you want to test it at a lower level than that, you should do it with qmltestrunner, and then you can hardcode your model.18:36
elopionerochiaro: with your quick explanation, I would prefer to make this as a qml test. I might be missing some details though.18:37
elopiois there a reason why you want to make it with autopilot?18:37
nerochiaroelopio: i am discussing it with Kaleo, it might even be I am testing something that I really shouldn't. thanks for the advice so far18:40
elopionerochiaro: well, it does sound that an automated test is needed :) Please don't land it without tests, but feel free to chose to test it at the level that you consider correct.18:42
elopionerochiaro: if you need something else, please go to #ubuntu-quality and ping whoever is mentioned in the topic.18:43
nerochiaroelopio: thanks18:48
rsalvetisil2100: robru: should we stop doing daily builds for RTM?18:49
rsalvetias we don't expect to have many landings anymore18:49
sil2100rsalveti: hm, we could basically18:49
robrursalveti: makes sense, landings have greatly slowed.18:49
sil2100rsalveti: since we're only waiting for 1-2 more fixes anyway18:50
rsalvetiexactly18:50
sil2100+1 :)18:50
rsalvetiwill disable in cron then18:50
sil2100Thanks!18:50
rsalvetidon't want qa spending time on something that didn't really change18:50
rsalvetidone18:51
popeyrsalveti: what about store uploaded click packages?19:06
popeyrsalveti: we'll have to spin new images just for those?19:07
rsalvetipopey: depends on which click packages19:15
rsalvetithe pre-installed in the images or the ones provided by custom?19:15
rsalvetipopey: do you think there is a way to coordinate these landings with the image build process?19:16
popeyI dont know how they're installed, but calculator, reminders, clock...19:16
popeyI'll have a chat to sil2100 tomorrow.19:16
popeyat the landing meeting, form a plan19:16
rsalvetiright, those a provided by the rootfs indeed19:16
rsalvetipopey: yeah, just to avoid having QA to spend hours testing something that didn't really change19:17
rsalvetiwe don't have a way yet to check for differences before building an image19:17
rsalvetipopey: thanks for following this up with sil19:18
rsalvetilet me know if you want the daily build back and I can re-enable anytime19:18
popeyok19:18
popeywe dont need it that often19:18
popeybut I know we have a few coming soon, and want to make sure people will get them.19:19
popeytechnically users will get it via the store of course.19:19
cjwatsonnothing stopping somebody requesting a manual build for those of course19:19
popeytrue.19:20
rsalvetiyeah19:21
dobeytrainguards: who can do a packaging change ack? has to be release team now?19:45
robrudobey: core devs19:45
dobeyrobru: are you a coredev?19:46
LaneyDepends on the package - anyone who can upload it19:46
LaneyMOTU for universe stuff19:46
dobeysilo 24 needs a packaging ack (new python module package added). it's unity-scopes-shell which i think is still in universe19:47
robrudobey: no I am no, sorry. I usually lean on mterry or kenvandine for that kind of stuff at this time of day19:48
dobeykenvandine: ^^ can you package ack silo 24? :)19:50
kenvandinedobey, i'll look20:45
robrubrb, lunch20:46
=== chihchun is now known as chihchun_afk
dobeykenvandine: thanks20:54
kenvandinedobey, so adding new binaries, you should really get an archive admin to look at it20:57
kenvandinefor a preNEW review20:57
dobeythat's what i was wondering20:57
dobeyslangasek: ^^ would you mind doing the package ack for silo 24 as it has a new bin pkg?20:58
robrudobey: ah you didn't mention there was a new binary package when you first asked me who can ack21:11
dobeyah. there's another silo waiting for qa signoff, which has a new binary package too. hopefully we can get them in quickly, as we need them to enable more testing in other packages21:16
bregmacihelp vanguard, we frequently get Unity 7 build fails due to timeout on amd64 in CI Jenkins although 4 hours should be more than enough for that, would this be a vanguard-level issue or should I just add it to our wishlist for the QA backlog?21:24
fgintherbregma, vanguard is appropriate21:26
fgintherbregma, I'll take a look21:26
fgintherbregma, it looks like the default memory size for the amd64 build was just a bit too small and was causing swapping during the build. I've moved the both amd64 and i386 builds to a build on larger nodes. so far it looks much happier21:48
fgintherer, the "default node memory size"21:48
bregmafginther, thanks, we'll see how that pans out in the next few MPs21:48
* bregma cracks the whip on the team21:49
rsalvetikenvandine: we got 2 system settings landings for rtm21:51
rsalvetikenvandine: just need to make sure we're in sync with QA here :-)21:51
kenvandinersalveti, yeah...21:51
rsalvetilove to see bug 1414762 getting fixed21:52
ubot5bug 1414762 in ubuntu-system-settings (Ubuntu RTM) "Password gets set instead of a passcode during welcome wizard" [High,In progress] https://launchpad.net/bugs/141476221:52
rsalvetihate this so much21:52
kenvandinejust make sure there's a rebuild after the first one publishes21:52
rsalvetiyeah21:52
elopiocihelp: the vms that run dep8 tests in the archive are qemu. Could we use something like kvm/qxl, so we can use mir during dep8 tests, or do we have to make mir work in qemu?22:26
fginthermterry, I finally opened a report for the unlock problem I mentioned earlier today: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/142887522:26
ubot5Ubuntu bug 1428875 in unity8 (Ubuntu) "Seeing high rate of unlock failures in krillin smoke testing" [Undecided,New]22:26
fgintherelopio, are you specifically asking about the proposed-migration tests such as http://d-jenkins.ubuntu-ci:8080/view/Vivid/view/AutoPkgTest/job/vivid-adt-qtmir/ ?22:27
fgintherelopio, if so, work is in progress this sprint to move that testing to nova kvm instances22:29
elopiofginther: I'm talking in general. I want to write a dep8 test for the dialer app that launches the messaging app. That requires mir running, and they tell me that mir requires qxl.22:30
elopioso I don't know what to request, for mir to not require kvm+qxl, or for the tests to not be run on qemu.22:30
mterryfginther, that does seem like just a more frequent version of bug 1428875, yeah22:31
ubot5bug 1428875 in unity8 (Ubuntu) "Seeing high rate of unlock failures in krillin smoke testing" [Undecided,New] https://launchpad.net/bugs/142887522:31
mterryfginther, er..  I mean bug 142100922:31
ubot5bug 1421009 in unity8 (Ubuntu) "unity8 sometimes hangs on boot" [Undecided,Confirmed] https://launchpad.net/bugs/142100922:31
fgintherelopio, one moment, pondering this for a moment22:32
fginthermterry, thanks for taking a look at that22:33
mterryfginther, I'm still not sure even where to start.  Seems like there's a whole collection of similar dbus freeze bugs22:34
fgintherelopio, it sounds like the best route is to make sure the test is restricted to only run on a testbed that can adequately run mir as is. If a nova kvm instance works for this, then you're in luck.22:36
fgintherelopio, but I have no idea what qxl is, googling22:37
slangasekdobey: having a look at ubuntu silo 024 now22:37
slangasekI thought we'd fixed the problem of silo packages bypassing NEW? am I misremembering?22:38
fgintherelopio, hmm. I think this requires more investigation to understand what is needed and if the current path is going to work. I'm not familiar with how graphics operate on these nova kvms.22:40
mterryfginther, I put a birds-eye-view comment on bug 1428875, but I'm EOD and off tomorrow -- you might want to poke kgunn to get someone else to look at this shorter term (and I'm guessing kgunn will probably re-assign to someone lower in the stack)22:41
ubot5bug 1428875 in unity8 (Ubuntu) "Seeing high rate of unlock failures in krillin smoke testing" [Undecided,New] https://launchpad.net/bugs/142887522:41
mterryfginther, actually, let me assign to kgunn myself and leave a comment22:42
fgintherelopio, I'll create a placeholder story for this for now.22:42
fginthermterry, thanks22:42
slangasekdobey: I have objections to some of the packaging changes on this silo; how do you want these submitted?23:04
slangasekdobey, robru: (i.e., this is a nack of the package as currently uploaded)23:05
robruslangasek: no worries on my end.23:05
robruslangasek: oh, in terms of bypassing NEW, what we fixed was diffs failing to be generated causing packaging changes to fly through unreviewed. as far as I know train uploads have always bypassed NEW.23:06
tedgrobru, Can you publish silo 18 please?23:07
slangasekrobru: well, when I say "we" I mean "launchpad", since it was a bug on the LP side that they went through without review23:07
* tedg doesn't have packaging changes23:07
tedgWell, in this silo.23:07
robruslangasek: ah no idea23:07
slangasekwgrant: ^^ any chance you can refresh my memory on where we stand on that bugfix (silos bypassing binary NEW)?23:07
robrutedg: done23:08
tedgrobru, Awesome, thanks!23:08
robrutedg: you're welcome23:08
wgrantslangasek: Bypassing binary NEW is fairly easily fixed, actually being able to be overridden before acceptance is a good bit harder.23:10
slangasekwgrant: so the binary-new-bypass bug is still outstanding, then - ok, thanks23:10
wgrantslangasek: Yep, but my derived distro rewrites of all that code make the actual skipping bit very easy to fix.23:12
wgrantslangasek: https://bugs.launchpad.net/launchpad/+bug/99312023:12
ubot5Ubuntu bug 993120 in Launchpad itself "Copy from PPA with binaries evades NEW and puts new packages into universe" [High,In progress]23:12
robruwgrant: cool, would be nice to fix23:13
slangasekwgrant: yep well maybe one of these days it'll be a priority to put it into the launchpad backlog... but not before ddebs ;)23:13
wgrantslangasek, infinity: Well, you should put it in your priorities on the wikipage. They're an ordered list after all.23:13
wgrantAnd this is fixable without the rest of the larger redesign that Adam already listed.23:14
slangasekinfinity: ^^ yeah, let's go ahead and put bug #993120 on the list (at the bottom)23:16
ubot5bug 993120 in Launchpad itself "Copy from PPA with binaries evades NEW and puts new packages into universe" [High,In progress] https://launchpad.net/bugs/99312023:16
slangasekdobey: fwiw the biggest blocker on this package is the lack of .symbols files for the library, which I believe is a standard requirement for all libraries that go through the train.  I won't sign off on a library package coming through the train that doesn't have ABI checking at the packaging level23:17
=== greyback__ is now known as greyback

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!