/srv/irclogs.ubuntu.com/2013/10/22/#ubuntu-ci-eng.txt

asacdoanac: plars: ok pleas shoot me and dirocks etc. a mail what happened. 'night00:09
veebersIs there anyone around that is able to tell me/find out why I can't see a CI job for this approved MR? https://code.launchpad.net/~veebers/unity8/adding_unlock_emulator/+merge/19132802:51
cjohnstonveebers: what do you mean can't see a CI job?02:53
veeberscjohnston: hmm, actually I might be wrong, I was expecting there to be an autolanding job, but was looking at the wrong one (i.e. -ci) and the autolanding is disabled currently02:54
cjohnstonok02:55
veeberscjohnston: so  a different, better, way to ask my question is: What do I need to do to take that MR from Approved to Merged?02:55
cjohnstonveebers: what is causing all the things to be unstable?02:57
cjohnstonI'd guess that needs to be fixed02:57
veeberscjohnston: ack, cheers03:02
ogra_asac, doanac, i think it would be clever to wait until the session is completely up before running systemsettle ... after all we want to test the user experience07:51
ogra_(i.e. make it check if unity8 is there before firing)07:51
didrocksogra_: do you mind refreshing me on what is systemsettle already?07:54
ogra_didrocks, it takes ten samples from top and waits if the system goes >97% idle07:55
ogra_apparently we run it directly at boot07:55
didrocksah ok ;)07:55
ogra_running after the session is up seems like a better usecase to me07:55
didrocksyeah, makes sense to have multiple tests, one to know how long we take to have everything started07:56
didrocksand another, to know the idle when the session if fully loaded07:56
ogra_well i want to introduce bootcharts into the tests07:56
ogra_so that part should become more fine grained anyway ... if you want to see the load on boot and how much something takes07:57
didrocksright07:57
* ogra_ grins seeing lool's comment on the bonita thread 08:01
didrocksogra_: well, for all java/jboss webapps, I don't expect less time even on a server to start TBH :p08:02
ogra_i meant the "luckily we didnt disable swap" :)08:03
didrocksahah08:03
ogra_we had so many discussions about that before release ...08:03
didrocksyeah08:03
didrocksalso, we didn't disable adb08:03
didrockstold you! ;)08:03
ogra_there is a usecase ... for the crazy ones08:03
ogra_didrocks, well, thats just because i ran out of time08:03
ogra_it was actually planned to habe it off by default so you need to enable it from the terminal first08:04
ogra_*have08:04
didrocksogra_: I know, I just told you we won't have time :)08:04
ogra_true08:04
didrocksogra_: terminal or system settings?08:04
ogra_i'Äm to optimistic at times08:04
=== psivaa-afk is now known as psivaa
ogra_terminal08:04
ogra_there was no UI planned for dev mode08:05
didrocksinteresting, we should maybe08:05
ogra_(we should do that for 14.10 in any case=08:05
ogra_)08:05
ogra_err08:05
ogra_14.0408:05
didrocks;)08:05
didrocksso you always live in the future08:05
didrocksand ev always lives in the past (he keeps telling 12.10 :p)08:05
ogra_bah so i uploaded an internet radio app and now my BT speaker inst found :(08:06
didrocksfor some games as well it seems?08:06
ogra_and some news sites08:06
didrocksyep08:06
ogra_and a TV program planner :)08:06
didrocksahah :)08:07
didrocksand we have 2 xkcd apps08:07
ogra_we might end up havfing 10 ... :)08:07
didrocksright ;) still 0 direction/driving apps08:07
didrocksbut 2 xkcd apps ;)08:07
* ogra_ expects the same chaos as googlew play has over time 08:07
ogra_well we have OSM ...08:08
ogra_not with firections though08:08
ogra_*directions08:08
didrocksyep08:08
ogra_and google maps works as well08:08
ogra_(with directions)08:08
ogra_webapps are just so easy (creating the click package takes less than 10min if you have a template app ... (of which 9min are used to find a proper icon)08:09
didrocksgoogle maps?08:09
didrockswe do have a wrapper for it?08:09
didrocksor not yet?08:09
ogra_sure, go to maps.google.com08:09
didrocksah ok08:09
didrocksI'll try to exercise that as a click app as well08:10
didrockstoday08:10
ogra_it has some user agent issues so the page flips to desktop at times08:10
didrocksbetter that we learn our technology :)08:10
ogra_http://daker.me/2013/10/package-your-webapp-for-ubuntu-touch.html08:10
ogra_thats an intresting hack to force the user agent for a page08:11
ogra_(though thats far more effort than i had to do for my apps)08:11
didrocksogra_: excellent! will try that :)08:11
* didrocks finishes first the morning tasks08:11
asacogra_: didrocks: what time do we want to build the image?09:02
asac:)09:02
asacnow or later?09:02
didrocksasac: as we are unsure that the dashboard is going to pick the right image (and to not confuse result, I would prefer to have the change before we have the image built), I would like to wait for doanac "go" on the dashboard fix09:03
ogra_asac, evening i'D say09:03
ogra_(independently from the dashboard, the more syncs we can get in the better so we have them cross tested)09:04
asacdidrocks: hmm. its not about the dashboard fx, but making a reasonable soon snapshot to make the set of changes more managable09:04
didrocksasac: well, without have dashboard results, we don't know of the real quality of the AP tests results09:05
asaci dont understand why we wouldnt build a new image now and then whenever we feel we need more as well, but *shrug*09:05
asacdidrocks: we dont. so we produce the snapshots now and then get the results later09:05
didrocksso we can just say "well, it boots"09:05
asacdidrocks: right. its for post-testeing09:05
didrocksasac: I mean, it will run the tests against 10109:05
asacso we have bi-sect points in history in case that stuff is broken09:05
asacdidrocks: ah... well, we can surealy ensure that we test the right stuff09:06
asacafter09:06
didrocksand I'm unsure we have a way to reflash/relaunch a whole set of tests again09:06
asacjust produce the images now and we can test them once the dashboard is fixed09:06
asacdidrocks: we have09:06
didrocksif you are sure we can, yeah, +1 for now09:06
asacyes i am sure that we even did that in the past09:06
didrocksasac: but I'm sure we are going to screw old results with new ones09:06
didrocksbut let's see…09:06
didrocksasac: we relaunched some tests09:06
asacwhat is tricky is testing and image that is not the latest, but that is also possible09:06
didrocksin the past09:06
didrocksnot changed the image :)09:07
didrocksogra_: ok, so let's kick an image, we'll see…09:07
asacdidrocks: i hope the infra has matured a bit09:07
* ogra_ goes and kicks 09:07
nik90@ci, with the 13.10 freeze over, would it be possible to get the patches https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-match-all/+merge/191080 and https://code.launchpad.net/~charlesk/indicator-datetime/lp-1233176/+merge/190009 in the phone image?09:07
nik90I need those two patches to verify the working of alarm09:07
ogra_asac, didrocks, build #2 running09:08
ogra_lets see if it even survives :P09:08
didrocksnik90: I think we'll need a landing ask (if not already) for that one09:08
nik90didrocks: I dont think I have the permission to do so..I will ask popey to add a landing task for it.09:09
didrocksnik90: and we'll start resuming landing tomorrow morning (finishing up transitionning today to trusty)09:09
didrocksthanks nik90!09:09
nik90didrocks: okay :)09:09
popeynik90: didrocks i dont have access either09:09
* didrocks gives popey power09:10
popeynoooooooooooooooooooooooo09:10
popey09:10
didrockspopey: powered up! :)09:10
ogra_asac, what about sending a call for MIRing stuff to the MLs. i think we should have people start getting their stuff into main so we dont have to care about that at the end of the cycle09:12
ogra_(and the MIR team can process the requests over the cycle instead of getting them all at the last minute)09:13
didrocksogra_: MIR team == mterry though09:13
ogra_yes :)09:13
ogra_thats what i mean ;)09:14
=== vrruiz_ is now known as rvr
didrockskalikiana: hey, answered on landing ask #185, can you give us more details?09:16
didrockskalikiana: I wonder why it worked for you, there is surely a way you tested it differently from us and I want that we fix that gap :)09:16
kalikianadidrocks: not sure what more detail you're thinking of. you got a bug number and expected fixes09:22
didrockskalikiana: I mean, you filed a first landing ask09:22
didrockskalikiana: so I intended it was working for you09:22
didrockshow was it working? did you disable apparmor?09:22
kalikianaI didn't disable it that I can tell09:22
didrockskalikiana: so, you were getting sensors feedback? the toolkit/apparmor regressed you?09:23
didrockswe try to identify what you differently than us to get sensors feedback working when you requested the landing ask, so that we can write better guidelines on testing09:24
kalikianamy assumption was apparmor changed, though jdstrand told me it didn't have a policy for the vibration before - the next thought would be android layer changes… but I don't know much about it09:27
kalikianais it possible that the container stuff changed permissions?09:28
didrockskalikiana: well, can you check with jdstrand? because we tested in the same image than you did I guess (it was the day you added the landing ask) and didn't get it working09:28
didrocksso maybe it's an application test diff, some confined, some not confined, but would be great that we identify it09:29
kalikianadidrocks: I repeat I wasn't able to test with that particular image to begin with09:29
kalikianaI had an older one when I tested before the ask09:29
kalikianaI ran into tooling problems preventing me from testing anything useful but finding unrelated bugs09:30
didrockskalikiana: hum, so, before filing the landing ask, maybe you can check with us if this reproduce?09:30
didrocksas we were able to test, we can give advice maybe :)09:30
xnoxdidrocks and/or other CI people: Why indicators linked to bug #1241539 haven't been released into trusty yet? =)09:32
ubot5bug 1241539 in indicator-sound (Ubuntu) "ubiquity-dm is missing keyboard, input, sound, system indicators" [High,Triaged] https://launchpad.net/bugs/124153909:32
kalikianawell Mirv was testing also09:32
kalikianaI guess you would have prefered not to add it to the sheet before either of us confirms it with the latest image09:32
didrockskalikiana: right, it's the deal to have a fast landing flow09:32
didrocksxnox: well, we are deploying the switch to T. See the emails by asac, we'll get first landing tomorrow09:33
xnoxdidrocks: on which mailing list?09:33
xnoxubuntu-devel?09:34
didrocksasac: do you remember where you did send that? ^09:34
didrockshum, seems only ue-leads, that would explain…09:34
asacxnox: ue-leads09:35
asacdidrocks: ^^09:35
xnoxdidrocks: i see one to ubuntu-phone just now.09:35
asacyou can forward09:35
asacxnox: thats one without timeline.09:35
asacxnox: forwarded you the initial mail09:36
* asac will stop using ue-leads for high level allignment as managers seem to not forward such info to their teams :)09:36
LaneyIt'd be better to use a public list, really09:38
Laneywhere possible etc09:38
xnoxasac: i think ubuntu-engineering@l.c.c is a good one and/or ubuntu-phone@ even better.09:38
xnoxcause everyone is subscribed to ubuntu-engineering@09:39
LaneyEveryone in UE at Canonical09:41
psivaaasac: didrocks: the smoke is now running trusty image now. the results are starting appear in the dashboard09:48
asacpsivaa: really? wowo!!09:48
psivaawith image 109:48
didrockspsivaa: excellent!09:48
asacncie one09:48
asachttp://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/1:20131021.1:20131015/4783/09:48
asacpsivaa: will maguro also go ahead?09:48
psivaaasac: i'll look at that09:48
asacplars: doanac: so if i run top -b -d 3 i constantly get better than 97.509:50
asacplars: doanac: so if i run top -b -d 5 i constantly get better than 98.5 even09:50
asacplars: doanac: so maybe we should revisit our parameters used09:51
asacplars: doanac: e.g. closer to the ones i initially proopsed than the very quick/fast we have now09:51
didrockssil2100: Mirv: so, we can build all trusty now?10:00
sil2100Mirv: did you redeploy everything? (I did qa)10:02
sil2100Let's keep our fingers crossed that we didn't miss anything ;)10:03
ogra_ load average: 2.19, 1.01, 0.3910:04
ogra_hmpf10:04
ogra_i'd really like to know why our load is so high all the time10:04
didrockssil2100: ok, autorun launched10:05
sil2100Mirv: damn, my qa merge didn't get in (but all is redeployed)10:05
ogra_(there is no obvious process in top consuming anything)10:05
Mirvdidrocks: sil2100: yes, and let's see how it goes now10:12
sil2100Mirv: huh, I can't redeploy the SDK stack for saucy it seems - ERROR Can't set the target branch ~ubuntu-sdk-team/qtcreator-plugin-ubuntu/trunk-2.7 for lp:qtcreator-plugin-ubuntu/2.710:14
sil2100Mirv: I'm not a member10:15
sil2100I guess we need to ask them to add all of us, the ubuntu-unity team as members10:15
Mirvsil2100: yeah sdk team was made more strict lately because the trunk was messed up. I'll add individuals.10:24
didrocksogra_: hum, I click install my own package and don't see it in the installed app10:28
didrocksis there any trick? (I already tried rebooting)10:29
didrocksah, click register surely10:30
didrockshum, not apparearing after that, let's reboot10:31
didrocksah, a reboot did it :)10:32
asacwebbrowser app test failing? is that a known flaki one?10:33
asachttp://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/101:20131018:20131015/4782/ vs.10:33
asachttp://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/1:20131021.1:20131015/4783/10:33
asacdidrocks: unity8 also as results not meeting what we expect, right?10:34
asachttp://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/1:20131021.1:20131015/4783/unity8-autopilot/10:34
didrocksasac: no, we didn't release any other ones10:34
didrocksasac: see my answer to doanac :)10:34
didrocksso it's known to be screwed until we release one10:35
asacdidrocks: release == new unity8 fix?10:35
didrocksyep10:35
asacok. so webbrowser?10:35
didrocksthose are supposed to be good10:35
cjwatsondidrocks: please don't use click install (unless you're very careful with its arguments), use pkcon install-local10:36
cjwatsondidrocks: the click manual page has advice10:36
didrockscjwatson: ah, ok will do then :)10:36
asacdidrocks: yeah. http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/1:20131021.1:20131015/4783/webbrowser-app-autopilot/10:36
cjwatsondidrocks: (I'd point to manpages.ubuntu.com but it doesn't have 13.10 yet ...)10:36
cjwatsonBut   "This is a low-level tool; to install a package as an ordinary user you should generally use pkcon install-local PACKAGE-FILE or some higher-level user interface instead, which take care to use the correct set of options.  (Do not use sudo when invoking pkcon, as it needs to know the calling user.)"10:37
didrockscjwatson: I guess that we should have the tutorial as well pointing to us (I only used --help TBH)10:37
didrocksto pkgcon*10:37
cjwatsondidrocks: the help output does point to pkcon10:39
cjwatsondidrocks: http://paste.ubuntu.com/6282270/10:39
didrockscjwatson: I just click --help10:39
didrocksand figured out the parameters then10:40
cjwatsondidrocks: which points to "click install --help" for more on that specific command, which points to pkcon10:40
didrockscjwatson: right, but I didn't think that care was needed, so I just click --help and then click install <package>10:40
cjwatsonsigh10:41
cjwatsonOK, I'll add a note to the top level as well10:41
didrockscjwatson: well, maybe I'm just stupid thinking that click install <click_file> was safe and didn't need to read something else than click --help10:41
cjwatsondidrocks: +  * Adjust top-level "click help" entry for "install" to point to pkcon.10:44
didrockscjwatson: thanks ;)10:45
asacdidrocks: maliit is crashing :)10:52
asacstill;10:52
didrocksasac: yeah, not news, we knew it, this a crash somewhere in the stack, the keyboard guys were pinged about it10:53
asacok so no regression... kk10:53
psivaaogra_: i think maguro flashing is taking longer than usual with trusty image 2. looks like more than 25 mins. i'll run once more to find out the exact time10:55
ogra_ok10:55
ogra_well, it is usually between 20 and 30 for me10:55
didrocksogra_: you are counting download time for you, right?10:56
ogra_didrocks, no plain flash times10:56
asacogra_: can you see if the unity8 upstream merger a) run their AP and b) if it passes currently?10:56
didrocksogra_: waow…10:56
asacerr10:56
asacdidrocks: ^^10:56
asacogra_: sorry10:57
didrocksasac: upstream merger? we are not upstream for maliit10:57
ogra_http://people.canonical.com/~ogra/touch-image-stats/20131022.changes10:57
asacdidrocks: talking about unity8  itself ... sorry :)10:57
ogra_diff between 1 and 210:57
ogra_(FYI)10:57
asacdidrocks: was back on the "unity8 is failing, but fix is in trunk - most likely" topic10:57
asacdidrocks: i figured that if its fixed, the upstream merger should give green on those10:57
asacbut now i dont know if folks have again turned the AP off :)10:57
didrocksSaviq: https://code.launchpad.net/~unity-team/unity8/trunk10:58
didrocksSaviq: I don't see your fix btw, you told me on Thursday you merged it, right?10:58
Saviqdidrocks, fix for? the autopilot tests?10:58
didrocksSaviq: yep10:59
Saviqdidrocks, http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/47310:59
Saviqdidrocks, asac10:59
didrocksoh, it was at Christopher's name10:59
Saviqbut we need unity-mir released first10:59
Saviqand then drop unity8-setcap.conf from lxc-android-config10:59
Saviqor well, not for image testing10:59
didrocksSaviq: ? yeah, we are only talking about the tests11:00
asacSaviq: what does  UNSTABLE: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/2564 mean?11:00
asactest failed?11:00
asacwhy do you merge anyway? :)11:00
didrocksSaviq: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-touch/3025/console11:00
didrocksunmet dependency on the one I picked11:01
Saviqdidrocks, look up11:01
asaci cant really parse this ... https://code.launchpad.net/~veebers/unity8/ap_env_fix_1240801/+merge/191567/comments/44042011:01
Saviqasac, we're not11:01
didrockslet's look at a MP older then11:01
asacso we have some SUCCESS: ... on armhf ->  SUCCESS: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-saucy-armhf/302311:01
Saviqdidrocks, we never got mediumtests-touch to a working state with mir yet11:01
asacah thats building11:01
didrocksasac: saucy is desktop AFAIK11:02
didrocksSaviq: it was on the image, apart from 1 failure, right?11:02
Saviqdidrocks, yes11:02
asacSaviq: well, the idea is that after your merge11:02
asacit works11:02
Saviqdidrocks, the failure was a random crash, too11:02
asacso you shouldnt merge it if it doesnt :)11:02
didrocks8 is more though11:02
Saviqasac, really, please stop11:02
asacah11:02
asacok11:02
Saviqasac, I'm telling you what's the prerequisite for unity8 even *starting*11:02
Saviqand that is unity-mir release11:03
didrocksSaviq: juts to understand on that one: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/2575/?11:03
didrocksit's your fix11:03
Saviqdidrocks, asac please stop11:03
didrocksI guess it was ran without this unity-mir dep11:03
Saviqand listen11:03
asacyeah lets listen11:03
asacsorry Saviq. go ahead11:03
Saviqwe need to release unity-mir, so that we can drop unity8-setcap.conf from lxc-android-config11:03
Mirvsil2100: unity-ubuntu now part of the sdk team (the 11 team members were ones that I would have added individually as well)11:03
Saviqthat will let us install unity8 in mediumtests-touch11:03
Saviqand only then we can start looking into actually fixing those runs11:04
MirvI trust ~ubuntu-unity members not to push --overwrite to ui-toolkit repo :)11:04
asacok sounds good11:04
asacSaviq: do we have all pieces ... in theory?11:04
Saviqand looking into them if they didn't pass11:04
didrocksSaviq: I still don't undestand why having just the code executed in https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/2575/? (so your fix), I was able to have all tests (but 1) passing on the image11:04
Saviqasac, yes, unity-mir just needs a release11:04
asacand lxc-android-config?11:04
didrockswithout any unity-mir/dropping unity8-setcap.conf11:04
Saviqdidrocks, those failures were intermittent - now fixed in trunk11:05
didrocksSaviq: the 8 of them?11:05
Saviqdidrocks, yes11:05
didrockswe just got really unlucky?11:05
didrocksok11:05
Saviqdidrocks, intermittent as in we fixed them11:06
didrocksok11:06
asacdidrocks: guess we should make an ask for this and do this as one of our first things. seems a few components are involved that require coordination :)11:06
didrocksasac: indeed, I would be interesting if such ask was made to make it a priority11:06
asaclxc-android, unity8, unity-mir11:06
didrocksknowing that will dep on a mir ABI bump which is already in the ppa11:06
asacwell, we didnt tell folks if they shyould continue doing asks11:06
didrocksso we'll need mir as well11:06
asacnow the mail is out11:06
asacso... :)11:06
didrocksas it's built against it11:06
didrocksand so platform-api for this mir abi bump11:07
didrocksas well as u-s-c11:07
asacdidrocks: lets create this one for saviq11:07
didrocksasac: ?11:07
didrocksI disagree11:07
asacwell, your call :)11:07
didrocksotherwise, there is no value, we just add more paperwork to our own soul11:07
didrocksfor the sake of it11:07
didrocksand we aren't sure to have all pieces listed11:08
didrocksnor the impact11:08
asacSaviq: can you add an ask about fixing unity8 APs and give details about all the bits and pieces so we can coordinate getting all in?11:08
asacthanks11:09
psivaadidrocks: ogra_ i am seeing some issues with flashing with trusty image 2.11:18
psivaai get 'ERROR:phablet-flash:Installation is taking too long or an error occured along the way.'11:19
psivaathe installation on my local maguro is hung on boot screen - Google and Padlock11:20
ogra_psivaa, doing an OTA upgrade here atm ... lets see how that behaves11:21
didrockspsivaa: interesting (and worrying)11:21
didrocksogra_: there was no hybris change right?11:21
ogra_http://people.canonical.com/~ogra/touch-image-stats/20131022.changes11:21
didrocksso can't be an android/ubuntu mismatch?11:21
Saviqare we planning to stop this landind-asks business at some point please?11:21
ogra_i dont see one11:21
didrocksSaviq: see asac's email11:22
sil2100Mirv: thanks!11:22
ogra_didrocks, lightdm and libpam are new ...11:22
ogra_as well as lxc11:22
Saviqdidrocks, yeah, didn't find an answer to that question (other than "we'll discuss in OAK")11:23
ogra_they look like the most possible candidates for the session not starting11:23
didrocksSaviq: if there was a decision before the discussion, that wouldn't be a discussion11:23
asacwell said11:23
cjwatsoneffective diff to pam is pretty small11:23
ogra_cjwatson, yeah, let me test first to see whats up here11:24
cjwatsonlightdm or lxc seem more probable11:24
cjwatson(neither was an autosync)11:24
ogra_both just are obviously involved in session startup11:24
didrocksknowing that lxc dropped a fix we still needed yesterday for otto11:25
didrocksnot sure if this one was useful for touch11:25
* ogra_ twiddles thumbs watching the android with rotating guts 11:25
didrocks    - 0006-add-pstore-to-container-fstab.patch11:25
ogra_we really should switch these animations to something ubuntuish :)11:25
didrocksogra_: we needed still that one for otto yesterday ^11:25
didrocksnot sure if it's relevant to you :)11:26
ogra_didrocks, i thought that was upstreamed11:26
didrocksogra_: oh possible (we ship our own fstab for otto, that's why we noticed)11:26
* didrocks looks at the diff11:26
didrocksyep, in -Index: lxc-1.0.0~alpha1/templates/lxc-ubuntu.in11:26
ogra_ok,, seems the container is up fine11:27
ogra_psivaa, confirmed btw11:27
didrocksok, so not lxc :)11:27
ogra_right11:27
* ogra_ tries a manual start lightdm 11:27
psivaaogra_: thx11:27
cjwatsonI'd stop autosyncs but they aren't going to run for 4.5 hours anyway.  Let me know if it's needed11:27
ogra_[+0.34s] DEBUG: Seat: Session authenticated, running command11:28
ogra_[+0.34s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session011:28
ogra_[+0.35s] DEBUG: Session pid=884: Running command /usr/sbin/lightdm-session ubuntu-touch-session11:28
ogra_[+0.36s] DEBUG: Session pid=884: Logging to .xsession-errors11:28
ogra_the lightdm log looks fine as well11:29
ogra_root@ubuntu-phablet:/# ps ax|grep 88411:29
ogra_  884 ?        Sl     0:00 lightdm --session-child 10 1311:29
ogra_and lightdm runs11:29
* ogra_ digs into session logs11:30
Saviqasac, didrocks, ask added11:30
ogra_phablet@ubuntu-phablet:~$ start unity811:30
ogra_start: Job läuft bereits: unity811:30
asacthanks!11:30
ogra_oh wow11:30
didrocksthanks Saviq11:30
ogra_phablet@ubuntu-phablet:~$ ps ax|grep unity11:30
ogra_ 1565 pts/3    S+     0:00 grep --color=auto unity11:30
xnoxogra_: FYI, your job is running away to unity 8 =)11:30
ogra_lies !11:30
* xnox somehow finds technical translations to other languages amusing =)11:31
xnoxogra_: status unity8?11:31
ogra_terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'11:31
ogra_  what():  Could not open hardware module11:31
ogra_all xnox' fault !!!11:31
xnoxogra_: right, let me check if unity/mir was rebuild with new boost. I thought I did.11:32
ogra_xnox, well probably you did but it wasnt let out of CI11:32
ogra_didrocks, ^^^11:32
didrocksogra_: I guess xnox is talking about directly uploads11:33
xnoxdidrocks: ogra_: well mir was rebuilt, but not unity-system-compositor.11:33
didrocksu-s-c isn't used on touch11:33
ogra_didrocks, no idea i thought mir and unity were not direct11:33
xnoxah, then no idea.11:34
ogra_xnox, there is unity-mir though11:34
ogra_which might need a respin too (not sure ask an expert)11:34
xnoxcould be...11:35
didrocksif a boost objects is leaked through mir, can be, xnox -> #ubuntu-mir?11:35
ogra_ricmm, already up ? ^^^11:35
xnoxdidrocks: templates do leak ABI/API mismatches, via transitive dependencies.11:36
xnoxdidrocks: but that's "standard C++" feature.11:36
didrocksxnox: yeah, it's more than possible that they use templates for their public class11:36
xnoxdidrocks: I don't know the code, and only was rebuilding stuff which does link against boost libs.11:36
didrocks(I asked there)11:37
didrocksmeanwhile, ogra_, can you try a rebuild of unity-mir on your phone?11:37
didrocksshould be quick enough to build11:37
ogra_hmm11:37
ogra_have to do that on maguro ... that wont be fast11:38
ogra_but yeah, i can try11:38
cjwatsonxnox: I think you forgot to quote "feature" there too11:38
* didrocks smells some C++ love from cjwatson :)11:39
cjwatsonYou might say I'm not a fan11:39
didrocksheh :)11:40
=== greyback is now known as greyback|food
cjwatsondidrocks: (http://gerald-duck.livejournal.com/591852.html is a good example - slides from *Bjarne Stroustrup* containing errors)11:50
cjwatsontop tip, if your language is so hard that its creator can't get it right in presentations, choose a new language11:50
didrockscjwatson: from Stroustrup? interesting :)11:50
didrockscjwatson: will read it for sure :)11:50
cjwatsonwell, that's an article commenting on said slides, but yes11:51
didrockscjwatson: last time I really wrote a lot of C++ code was 7 years ago (I don't count the unity code I wrote as serious development), and yeah, I have feelings as well :)11:52
=== alan_g is now known as alan_g|lunch
asacpsivaa: did we retry webbrowser?11:57
psivaaasac:  not yet, looking at that to see if the failures were the same as before11:58
asacright11:58
asacthanks11:58
psivaaasac: rerunning it again. i got it confused with weather app tests12:01
asacslangasek: cjwatson: seems we have a first case of our imports/core-dev uploads caused touch to not boot anymore12:34
asacslangasek: cjwatson: we thought it was just a rebuild related to boost regression, but seems that didnt make it12:34
cjwatsonasac: I haven't seen an analysis of what actually broke yet12:34
cjwatsonJust a guess, which you're now saying didn't turn out to be the problem after all?12:34
asaccjwatson: what do you need to know? the symptoms?12:35
cjwatsonasac: I'm just saying that we don't know the cause yet12:35
cjwatsonAFAIK12:35
didrocksMirv: sil2100: is it getting better? I see a lot of red in http://10.97.0.1:8080/view/cu2d/view/Head/12:35
cjwatsonogra_: Any progress tracking this down?12:36
asaccjwatson: right. so a) who is looking and b) what is the course of action until we know12:36
asac(that you suggest)12:36
cjwatsonasac: ogra_ was looking last I heard, and 12:27 <cjwatson> I'd stop autosyncs but they aren't going to run for 4.5 hours anyway.  Let me know if it's needed12:36
ogra_cjwatson, not really, didrocks did a test rebuild of the packages but that doesnt seem to help12:36
asaccjwatson: thanks!12:36
ogra_he claims in #ubuntu-mir that he doesnt get a seat12:37
didrocksI don't have lightdm starting automatically12:37
didrocks(need to start it manually)12:37
ogra_(works for me though)12:37
ogra_let me reboot and see12:37
didrocksogra_: yeah, would like a confirmation12:37
cjwatsonIf it's lightdm, foundations takes no responsibility :)12:37
ogra_root@ubuntu-phablet:/# status lightdm12:38
ogra_lightdm stop/waiting12:38
ogra_not starting ...12:38
cjwatsonThough the effective diff in lightdm is virtually zero12:38
ogra_http://paste.ubuntu.com/6282720/12:39
ogra_ERR !12:39
ogra_where is the rest of this file12:39
cjwatsonWhat package is that file in?12:40
ogra_ubuntu-touch-session12:40
ogra_ugh12:40
cjwatsonThat's the full file in the source package12:40
ogra_its like that in bzr too12:40
cjwatsonI'd expect it to be getting its script or exec from lightdm.conf12:40
cjwatsonSeeing as that's just the override12:40
=== greyback|food is now known as greyback
cjwatsonI wouldn't expect you'd *need* the "rest of this file"12:41
ogra_right seems that worked before so likely a red herring12:41
ogra_i thought override overrides and doesnt merge :)12:41
cjwatsonNo12:41
ogra_k12:41
cjwatson"Files ending in .override are called override files.  If an override file is present, the stanzas it contains take precedence over those equivalently named stanzas in the corresponding configuration file contents for a particular job.  The main use for override files is to modify how a job will run without having to modify its configuration file directly.  See the section Override File Handling below for further details."12:41
cjwatsoninit(5)12:41
Mirvdidrocks: I didn't realize it had tried to run already. it's complaining about missing trusty cow image http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-1.1prepare-notes-app/338/console12:41
ogra_root@ubuntu-phablet:/# status lxc-android-config12:42
ogra_lxc-android-config start/post-start, process 59912:42
ogra_post-start process 60112:42
ogra_aha12:42
ogra_looks like thats the issue12:42
ogra_root@ubuntu-phablet:/# ps ax|grep 60112:42
ogra_  601 ?        Ss     0:00 /bin/sh -e /proc/self/fd/912:42
ogra_hmm12:42
didrocksMirv: https://wiki.ubuntu.com/DailyRelease/MovingNewRelease First setup on the jenkins server12:42
didrockswe need to create a release+1 pbuilder. Ping jibel for it.12:42
didrocks(we need root access to create it, we don't have it12:42
Mirvright, there it reads.12:43
Mirvjibel: could you create trusty pbuilder?12:43
cjwatsonogra_: could you pastebin the whole "ps auxfww"?12:43
vilaMirv, jibel: I thought fginther was working on that yesterday ?12:43
ogra_http://paste.ubuntu.com/6282741/12:44
jibelMirv, sure I can but I thought fginther did it12:44
cjwatsonogra_: So /proc/$containerpid/root/dev/.coldboot_done never gets created, I guess12:44
cjwatsonSince it seems to be in that sleep loop12:44
ogra_we didnt rebuild android, i wouldnt know why12:45
cjwatsonSo where is that file expected to be created12:46
=== alan_g|lunch is now known as alan_g
ogra_root@ubuntu-phablet:/# lxc-info -n android|grep pid12:46
ogra_pid: 65812:46
ogra_root@ubuntu-phablet:/# ls /proc/658/root/dev/.coldboot_done12:46
ogra_/proc/658/root/dev/.coldboot_done12:46
cjwatsonIn android, yes?  http://162.213.35.4/search?weighted=1&q=coldboot_done shows android_20131006-1510-0ubuntu6/system/core/init/devices.c:905 which I guess is related12:46
ogra_so the file is there12:47
ogra_and it worked before the #2 build12:47
cjwatsonhttp://launchpadlibrarian.net/154411166/lxc_1.0.0~alpha1-0ubuntu11_1.0.0~alpha2-0ubuntu1.diff.gz:12:48
cjwatson-printf("pid:%10d\n", initpid);12:48
cjwatson+printf("pid: \t%d\n", initpid);12:48
ogra_oh my12:48
cjwatsonwhile lxc-android-config has:12:48
cjwatson    containerpid="$(lxc-info -n android|grep pid|sed 's/^pid:.* //')"12:48
ogra_yeah, i see it12:48
cjwatsonso that needs to be [[:space:]] instead of the ' '12:48
cjwatsonlxc triggered it but this is an lxc-android-config bug IMO :)12:49
ogra_yay for building on assumptions12:49
ogra_yes, it is12:49
jibeldidrocks, vila do you want me to proceed with the creation of the chroot or wait for fginther?12:49
cjwatsonogra_: Beware similar bug in ./usr/bin/android-chroot12:49
cjwatson./usr/bin/android-chroot:3:pid=$(lxc-info -n android|grep ^pid|sed 's/^pid: .* //')12:49
ogra_cjwatson, yeah, android-chroot is due to be removed12:49
cjwatsonogra_: yeah, but if it isn't actually gone yet it should still be fixed12:50
ogra_it doesnt do what the name suggests and people confuse it12:50
ogra_i'll remove it with the same upload12:50
vilajibel, didrocks: I'd rather check with him to avoid double work and so on, he should be here any time now12:50
fginthermorning12:50
vilatada !12:50
vilafginther: hey, perfect timing12:51
ogra_hey, unity !12:51
fginthervila, chroots?12:52
ogra_and it feels a lot snappier (for 2min using it at least)12:52
vilafginther: ?12:52
vilafginther: pbuilder ?12:52
* cjwatson codesearches to see if there are any similar bugs elsewhere (which would argue for an lxc reversion if so; otherwise I think we should just fix lxc-android-config to tolerate the whitespace change and be done with it)12:52
fginthervila, trying to figure out what the perfect timing is for, are we discussing the daily release chroots?12:52
cjwatsonlxc itself does this kind of thing:12:53
cjwatson        initpid=`lxc-info -P $lxc_path -p -n $container | awk -F: '{ print $2 }' | awk '{ print $1 }'`12:53
vilafginther: yeah, Mirv didrocks and jibel were wondering if the trusty pbuilder have been created, I said I thought you were doing just that yesterday12:53
vilapbuilderS even12:53
fginthervila, Mirv, didrocks, the pbuilders are setup for the upstream merger12:54
didrocksfginther: no, cu2d uses it as well12:54
didrockswith cow12:54
vilasame hosts ?12:54
fginthervila, didrocks, I have not touched the daily release systems yet12:54
vilafginther: will you ?12:55
Mirvfginther: ok. me and sil2100 have been updating the cu2d configurations today and now it seems that on the head side the next step missing is the pbuilder (http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-1.1prepare-notes-app/338/console)12:56
fgintherMirv, vila ack, I'll start work on that12:56
ogra_asac, didrocks, xnox, fix uploaded, session should start again with the new lxc-android-config12:56
cjwatsonogra_: All other callers of lxc-info in the archive use forms that will tolerate this whitespace change12:56
Mirvthanks fginther12:56
ogra_cjwatson, lxc-android-config now too :)12:57
cjwatsonogra_: Thanks12:57
xnoxogra_: didrocks: so it wasn't related to boost?12:57
ogra_xnox, not at all12:57
xnoxasac: ^12:57
ogra_xnox, lxc change that triggered a mis-parsing in lxc-android-config12:57
didrocksogra_: hum, it fixes the boot exception as well?12:58
jibelfginther, the chroot is building, I also updated debootstrap on magners-o so it knows about trusty12:58
fgintherjibel, thanks12:58
ogra_didrocks, unity starts after i changed the upstart job12:58
didrocksoh, interesting12:58
ogra_didrocks, feel free to try yourself12:58
ogra_-    containerpid="$(lxc-info -n android|grep pid|sed 's/^pid:.* //')"12:59
ogra_+    containerpid="$(lxc-info -n android|grep pid|sed 's/^pid:.*[[:space:]]//')"12:59
ogra_in /etc/init/lxc-android-config.conf12:59
didrocksasac: so not boost transition, new lxc need another change in lxc-android-config ^12:59
didrocksogra_: doing12:59
* didrocks stops his unity8 build12:59
ogra_not another change12:59
ogra_that code was there forever13:00
vilafginther: thanks13:00
didrocks  * make parsing the lxc-info output work with new lxc so our session can13:00
didrocks    start again13:00
ogra_yeah13:00
ogra_lxc changed the output format of lxc-info13:00
didrocksyeah, so lxc changed :)13:01
ogra_the parsing above couldnt keep up with thatz13:01
didrocks(that's what I meant)13:01
asacdidrocks: nice. i like blame-games :)13:01
didrocksnot parsing " " but needing [[:space:]]13:01
ogra_yeah13:01
didrocksasac: do we see score going up and down?13:01
ogra_well, it should be safe now13:01
ogra_i'll trigger a new image as soon as thats in13:01
didrocksogra_: I still wonder why that impact unity8 that way though (the boost exception we saw)13:01
* didrocks reboot13:01
ogra_and will meanwhile debug video playback in webapps on maguro13:02
ogra_didrocks, it will at least fill your disk with log spam13:02
Mirvfginther: and after that the next missing step would be https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/switch_from_next_to_daily/+merge/19213913:02
ogra_so it should be fixed asap13:02
ogra_but i doubt it will do actusal harm13:02
ogra_on my maguro the #2 image feels actually snappier13:02
ogra_might be subjective though13:02
didrocksheh :)13:03
didrocksogra_: confirming unity8 starts13:03
didrocksnice debugging :)13:03
ogra_:)13:03
didrockshowever, weird side boost effect in unity8 :-)13:04
* cjwatson scores up lxc-android-config13:04
didrocksxnox: that was close!13:04
fgintherMirv, looks good to me (did not top approve)13:06
didrocksjibel: thanks13:07
jibelfginther, Mirv trusty chroot is ready on m-o13:11
Mirvjibel: thanks, looks good now from that perspective13:16
dobeyMirv, pmcgowan: i have a contribution to qt i'm trying to get pushed to gerrit and am having some problems with git. either of you have a minute to help figure it out? the commit-msg (and maybe others) hook doesn't seem to be running for me when i do commit -a13:16
fginthersil2100, in the services.cfg stack, thumbnailer was enabled for daily_release under saucy, but the head version is not13:16
Mirvdobey: have you copied the hooks to the local checked out .git/hooks?13:17
dobeyMirv: yes, that's the only place they exist13:24
kgunndidrocks: ping13:25
Mirvdobey: that to make it obvious, the instructions talk about  ~/.git but actually they need to be under the checked out repository's .git/hooks. I haven't heard of problems in using the hooks, other than they missing from the correct directory (hmm, not sure if chmod +x is needed)13:26
Mirvso one line there is the cp -av ~/.git/hooks/* .git/hooks/13:26
dobeyMirv: yes, they are only in the checked out repository, i don't have a ~/.git/ directory at all13:26
dobeyand i did chmod +x them13:27
Mirvdobey: I can't think of any reason they wouldn't get executed. so you don't get the Change-Id in the comment then? and it's called "post-commit" (and not the wget:d "git_post_commit_hook")?13:28
Mirvdobey: in other words I can't think of anything that is not already written on the instruction page13:28
dobeyi had it work once, but that was with the wrong committer/author e-mail, so i had to blow away the branch because i couldn't find any way to change the existing commit and trying to use revert made the branch worse. so i had to salvage my changes in a patch file, and make a new tree to do it in. but now it's not working13:28
Mirvdobey: yep, that must be annoying.13:29
dobeyMirv: yes, i followed the instructions correctly. when i do "commit -a" the huge commentary about [ChangeLog][][] and such is not coming up13:29
Mirv:(13:29
dobeyMirv: yes, every time i've ever used git, has been nothing short of wildly frustrating for me ;(13:29
didrockskgunn: pong13:31
kgunndidrocks: hey...i'm premature...sorry....i need to get one more mp approved by ricmm for platform-api mir abi bump13:32
kgunni'll bother you later13:32
didrocksok13:32
kgunndidrocks: question is....can i actually merge those mp's ? prior to mir getting pulled into the daily build ?13:32
kgunni worry about the order13:32
asacdidrocks: do we feel we have the issue fixed? :)13:33
asacwith the new lxc upload?13:33
ogra_asac, yes13:33
didrocksasac: lxc-android-config to fix for new lxc, yeah13:33
didrocksasac: tested locally as well, confirmed by 2 people13:33
ogra_waiting for it to come out of proposed13:33
asacok. then lets tackle the unity test fixes next :)13:33
asaconce we have that we are back to release state i feel13:33
ogra_asac, then i'll do a new build13:33
didrockskgunn: well, mir trunk already have an abi break, so don't worry about it for now, just merge it13:34
didrockskgunn: please add a landing ask as well for the transition13:34
didrocksFYI, we'll start landing again things tomorrow13:34
didrockssil2100: is everything working better now?13:34
asackgunn: can we please have a session or just do the source merge of the componnents that share libmirserver?13:34
asac(and exporting a stable libmirserver for platform-api)13:34
asac(just got reminded by hearing abi break)13:34
kgunndidrocks: ack on landing ask13:36
didrocksthanks ;)13:36
kgunnasac: me more than anyone wants it to settle, unfortunately its not so easy....its the story of begets....we (unity&mir) would like to leverage qt scengraph & refactor mir-data-model....which means some more breaking, and its going to take some time, then we'll be in position to distill api13:38
sil2100fginther: ah, so it seems the head-saucy pieces were out of sync13:39
Mirvdidrocks: I've been looking after the head now, and yes it's looking better and builds are starting to appear https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.series_filter=trusty13:39
sil2100didrocks: yes, Mirv prepared a branch that we missed and redeployed13:39
sil2100It will be merged in soon13:39
didrockssil2100: Mirv: sweet! all prepare jobs cleaned as well?13:39
jdstranddidrocks, kalikiana: regarding sensors> kalikiana told me I needed to add a rw access for apparmor. I did not upload that until just now (apparmor-easyprof-ubuntu 1.0.41) so it isn't surprising if testing didn't work13:40
didrocksjdstrand: well, apparently testing did work when he did the landing ask, (and we saw it wasn't), hence the question13:40
jdstrandI was waiting on feedback from this channel yesterday, but then saw the email this morning so I uploaded it13:40
didrockswe want to ensure we write good guidelines for everyone to test their changes and try to identify gaps :)13:40
jdstranddidrocks: I gave instructions on how to add the access13:40
didrocksoh, so he did that manually and tested at the time13:41
Mirvdidrocks: sil2100: certainly not for the prepare job cleanage, there has been enough work to get this first run done. now finally we'll get up-to-date statuses at the head jobs.13:41
jdstranddidrocks: so he probably had that but the testing didn't13:41
didrocksok, that makes sense :)13:41
didrocksso yeah, we really need to have a big landing ask "group", with everything that was needed to make it work13:41
jdstranddidrocks: I'm guessing that was the case, yes. no matter, now 1.0.41 is uploaded, people can just do that. if it doesn't work, check /var/log/syslog for denials13:41
didrocksjdstrand: yeah, it's just that we need to write good guidelines for landing those kinds of interdependants change :)13:42
didrocksthanks for the hint jdstrand :)13:42
jdstrandmp13:42
jdstrandnp13:42
ogra_asac, didrocks, lxc-android-config is in, triggering a #3 now13:59
didrocksogra_: \o/13:59
ogra_build running13:59
asacgreat13:59
=== alan_g is now known as alan_g|afk
=== alan_g|afk is now known as alan_g
plarsasac, ogra_: so what's the story on the channels? My understanding is that devel-proposed doesn't point at trusty for some reason yet?14:09
ogra_plars, not for some reason no :)14:11
ogra_plars, channels can only exist once they have content14:11
plarsogra_: but there is a trusty image now, yes?14:11
ogra_plars, until we publish trusty-proposed to trusty we cant switch devel14:11
plarsogra_: but shouldn't devel-proposed point to the same thing as trusty-proposed?14:12
ogra_(we could switch devel-proposed but that would cause confusion)14:12
cjwatsonogra_: next cycle we should just copy saucy to trusty to start with14:12
ogra_cjwatson, tzhats what i said in the meeting ;)14:12
cjwatsonno real reason not to do that, except that you have to continue the build numbers (you may or may not consider that a downside)14:12
ogra_right14:12
plarsogra_: It appears to be causing confusion the way it is now, it was my understanding that continuing to use devel-proposed for trusty images was the right thing to do14:12
ogra_plars, once we have devel and devel-proposed populated with images, yes14:13
asaccjwatson: i want the build numbers of devel to always go up :)14:15
asacyes.14:15
asacthanks!14:15
asac:)14:15
asacmaybe should be seeded in our "how to do releases" wiki - so we wont forget next time14:16
cjwatsonfeel free to add touch-specific things to NewReleaseCycleProcess as appropriate14:18
ogra_asac, build numbers are moot ... as long as the OTS upgrader does the right thing14:19
ogra_*OTA14:19
plarsogra_: so are you saying there will be nothing for devel-proposed until an image is green enough to be marked "good"?14:20
ogra_plars, yes14:20
ogra_plars, unless asac wants to override that for #114:20
plarsogra_: that is a change from last cycle then right? We didn't track saucy proposed last cycle, but devel-proposed14:20
ogra_i personally dont think #1 is worse than #10114:21
ogra_plars, we didnt have system-image when last cycle began14:21
ogra_oh, you mean *during*14:21
plarsbut if trusty-proposed is going to really be the tip, and devel-proposed is just the images that have been accepted from trusty-proposed as good, then we should always just be testing trusty-proposed this cycle it seems14:22
plarsasac: ?^14:22
ogra_well, sinc ethey wree equivalent back then ...14:22
ogra_*were14:22
ogra_plars, trusty = devel ... as soon as we switched14:22
ogra_(and equivalently -proposed)14:22
ogra_plars, saucy = stable14:22
plarsogra_: but today, saucy=devel still14:23
ogra_yes14:23
ogra_until we can create a new devel channel14:23
ogra_which we cant without an image in there14:23
ogra_its a catch2214:24
cjohnstonI thought devel-proposed was a symlink to trusty-proposed14:24
ogra_devel = saucy ... until trusty has its first image14:24
ogra_then your assumption is true14:24
plarsogra_: ok14:25
ogra_cjohnston, plars, though since asac wants to keep saucy testing around too, we should always use the release name for utah i think14:25
ogra_that should make it easier to distinguish14:26
plarsogra_: ok, we'll just change to trusty-proposed in ci then, and leave it at that14:26
ogra_right14:26
ogra_that way you can still test saucy-proposed in parallel14:26
ogra_and once Uneasy Unicorn starts we can have that in paralell asd well ;)14:27
=== alan_g is now known as alan_g|tea
asacplars: yes ignore devel* for the time being14:39
asacalso ignore stable* in the same way :)14:39
=== alan_g|tea is now known as alan_g
ogra_image #3 done btw14:45
didrockslet's cross fingers for the dashboard!14:56
slangasekogra_: why does lxc-android-config have this coldboot check at all?  Why should it not be sufficient that 'lxc-wait' says the container is running, and the local bridge handling any other android events that are needed?15:11
ogra_slangasek, ueventd15:12
ogra_slangasek, it creates that file once it is done processing15:12
slangasekright - but doesn't ueventd also set an android property?15:13
slangasekwhich would be a better IPC mechanism than rooting around in /proc/$pid/root15:14
ogra_slangasek, not sure, it is definitaley a candidate for revisiting this cycle15:21
ogra_it should hook into the upstart-local-bridge i think15:21
ogra_thats why we have it after all :)15:22
ogra_ARGH !15:25
ogra_didrocks, asac  ... lxc-android-config update isnt in #315:25
* ogra_ definitely checked with rmadison before starting the build 15:25
ogra_damned15:25
ogra_err15:26
ogra_hmpf15:26
ogra_why did phablet-flash #2 for me again15:26
ogra_didrocks, asac ignore the ablve15:26
* ogra_ doesnt get why he doesnt get #3 ... it was definitely there since a while when i fired off phablet-flash15:27
asacogra_: check with stgraber i guess15:29
ogra_asac, well, i'm starting over now15:29
ogra_just to be sure the error isnt on my side15:29
ogra_probably the telekom has a new proxy i dont know about or some weird stuff15:29
slangasekrsalveti: do you know if there's an android property that's an equivalent to /dev/.coldboot_done ?15:32
=== vrruiz_ is now known as rvr
ogra_ok, this time i got #315:49
didrocksogra_: ok, it looks fine here15:55
ogra_still flashing here15:56
ogra_and probably taking half the meeting15:56
ogra_maguro is slooooow to unpack the tarball15:56
asac:)15:58
Mirvback for the call15:58
didrockssil2100: Mirv: asac: ogra_: plars: joining? (let's try to keep it short and focused ;))16:00
sil2100\o/16:00
plarsdidrocks: will be there in a sec16:01
sil2100Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/transition_webapps_T/+merge/192184 <- can you quickly? :)16:03
asacdoanac: any idea why touch_custom is showing up ont he QA homepage? http://reports.qa.ubuntu.com/16:05
asace.g. why not touch?16:05
didrockshum, no robru…16:06
doanacasac: not sure. josepht, cjohnston: any idea why our trusty touch results aren't showing up in the KPI?16:08
doanacwe have a regex gone bad because of the variant changes?16:09
didrockscyphermox: around?16:09
cyphermoxyes16:11
doanacplars: i think when we ran setup_jenkins we failed to enable the "publish" option16:11
didrockscyphermox: coming to https://plus.google.com/hangouts/_/calendar/Y2Fub25pY2FsLmNvbV91cTRvNmQyMWJvNmJ0bm1mcW9xZWtsNTdnOEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t.cg7k3h1nmqml7psc1nn68223i0?16:11
plarsdoanac: I'm 99.9% certain I did, but let me check my history16:11
plarsdoanac: well, we see build 3 showing up, so I have to have enabled it16:11
doanacyeah. n/m16:12
plarshttp://reports.qa.ubuntu.com/smokeng/16:12
doanacplars: we were missing touch_sf4p16:12
doanactrying to figure out why16:12
cyphermoxargh, just a moment I'm not setup for voice atm16:13
didrockscyphermox: ok, don't worry for today then, sil2100 will tell you what is needed if you have time16:13
cyphermoxok.16:14
cyphermoxsorry i broke some things  while clearing up / resetting stuff for an upgrade to trusty and all, and my headset is elsewhere :)16:15
sil2100No problem ;) I'll poke you with some stuff later probably16:15
sil2100Mirv: approve branch! Please ;)16:15
didrockscyphermox: see, never clear stuff, always go forward! :)16:16
sil2100Mirv: ^16:16
Mirvsil2100: maybe if you ask nicely ;)16:17
didrocksahah blackmailing! that's how it should be :)16:17
sil2100Mirv: pretty pleaaaseee :D16:18
Mirvdone16:18
sil2100Oh, magic word!16:18
ogra_maguro #3 is good16:19
ogra_didrocks, asac ^^^16:19
sil2100Mirv: thanks! :)16:19
didrocksogra_: sweet! :)16:19
didrockslet's hope we are getting good dashboard result16:19
didrocksand publish an excellent first image trusty image tomorrow morning16:19
cyphermoxdidrocks: the problem with going forward (at least for me) is that cruft accumulates16:20
asacogra_: good as in green on automation?16:21
didrockscyphermox: easy, don't make cruft :-)16:21
didrocks</managerspeech> :p16:21
ogra_asac, goog as in manual smoketesting done16:21
ogra_*good16:22
cyphermoxdidrocks: easy, hand over your scripts and tricks :)16:22
ogra_(and passed)16:22
didrockscyphermox: ahah ;)16:22
fginthervila, want to take a crack at review if it's not too late for you? https://code.launchpad.net/~fginther/cupstream2distro-config/upstream-merger-trusty-updates/+merge/19219016:25
cjohnstondoanac: asac working on the touch stuff on the dash16:26
vilafginther: no, not too late, but missed the meeting *again*16:29
vilafginther: approved, does that need an additional review from Mirv/sil2100 if only as a heads-up ? Or is it strictly upstream-merger only ?16:33
fginthervila, this only touches upstream merger pieces, but would definitely welcome another look by sil2100 and/or Mirv16:35
rsalvetislangasek: no, but we can add that16:41
rsalvetislangasek: and indeed, we were checking for that file because we didn't have the bridge running when we did that16:42
rsalvetiwe got a bunch of clean-up related WIs and this is part of it as well16:43
* fginther -> food16:44
slangasekrsalveti: ok17:04
=== alan_g is now known as alan_g|EOD
plarsasac: something is causing powerd-cli crashes now, not in every run though. would killing powerd-cli after using it to turn the display on do that do you think?17:42
plarsasac: actually, nm I don't think it could be that at all17:43
plarsasac: it's happening even on the install test, which doesn't ever run the pieces that unlock the screen or use powerd-cli to turn the display on17:45
asacplars: can you reproduce on image 3?17:53
asacbut not on image 1?17:53
plarsasac: of the tests that we had on 1 at http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/1:20131021.1:20131015/4783/ I couldn't find any that had this powerd crash17:54
asacChickenCutlass: ^^17:55
asacpowerd crash17:55
plarsasac: ricmm said he'd take a look also when I pinged on #u-touch17:56
plarsasac: qmlscene crashes on the filemanager app test too, but that was in 1 as well17:58
dobeywhere's the config for the upstream merger (the tarmac.conf) live at?18:19
asacdobey: check with fginther18:35
dobeyfginther: ^^ if you're around?18:36
fgintherdobey, looking18:37
fgintherdobey, what exactly are you looking for? upstream merger doesn't use tarmac directly18:39
dobeyfginther: what commits the code to projects being merged with the CI/daily-release process?18:41
asacplars: is this putting our dashboard results at risk?18:41
asacor just investigation needed?18:41
fgintherdobey, https://launchpad.net/jenkins-launchpad-plugin18:41
plarsasac: tests are done and seemed pretty consistent asac for pass/fail, no, but it adds to the number of crash files18:42
dobeyfginther: ah, it's a fork of tarmac?18:43
plarsasac: from what I'm seeing, the testsuites failing on maguro are the same as the ones failing on mako for image 3, modulo a few extra system-settle failures on maguro which isn't too surprising. I'll try adjusting things on systemsettle as you recommended though and have it in the next build18:44
plarsasac: maguro would understandably be more sensitive to systemsettle though18:44
fgintherdobey, it's best described as a wrapper. tarmac is used internally for a few functions18:44
dobeyfginther: well half-a-fork then? it doesn't use the tarmac config stuff, or any of the plug-ins?18:48
fgintherdobey, No. From a quick look,  tarmac is just used to provide abstractions for bzr branches18:50
dobeyfginther: is there any way to do validation of contributors with the jlp autolander? this is a plug-in in tarmac, and allows us to check that contributors have signed the contributor agreement (because they get put in a special launchpad team when they do)18:52
fgintherdobey, I think this is what you want - https://bugs.launchpad.net/jenkins-launchpad-plugin/+bug/113442818:56
ubot5Ubuntu bug 1134428 in jenkins-launchpad-plugin "Reject MRs if people don't belong to specific group" [High,New]18:56
fgintherdobey, if tarmac already supports this as a plugin, than that's probably something that can be re-used here instead of re-invented18:56
dobeyfginther: yes, it supports it. i wrote the plug-in :)18:57
fgintherdobey, do you mind adding a pointer to the bug report?18:57
dobeyfginther: i would guess a lot of the stuff could be done directly with tarmac instead of having a fork that only uses the branching abstractions. we wrote tarmac to be generally quite robust in that sense. i didn't realize you guys had gone this far away from using tarmac, though :-/18:58
dobeysure18:58
fgintherdobey, now would be a good time to revisit the divergence this cycle. May I pick your brain regarding tarmac in a week or two?19:04
dobeyfginther: sure, i can answer questions any time.19:06
fginthersergiusens, how does phablet-tools get into ppa:phablet-team/tools? (it needs a saucy version)19:16
sergiusensfginther, with a jenkins job19:16
sergiusensfginther, done, added it here: http://10.97.0.26:8080/view/click/job/ppa-sync-phablet/19:18
fginthersergiusens, thanks19:19
plarsasac: ok, after some systemsettle tweaking, results on mako(saucy-101), mako(trusty-3), and maguro (trusty-3) match - with the exception of the powerd crashes I mentioned earlier19:51
veebersfginther: ping20:57
fgintherveebers, pong21:10
veebersfginther: hey how are things? I wanted to ask you about this: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/2662/console21:10
veebersit failed not because of a test failure21:11
veeberslooks like a dpkg error: E: Sub-process /usr/bin/dpkg returned an error code (1)21:11
fgintherveebers, there is a slew of unmet dependencies. Unfortunately, apt isn't very good at telling you what exactly is missing21:13
fgintherveebers, it's often a dependency at another level that is causing the problem.21:13
fgintherveebers, I can help debug21:14
veebersfginther: awesome thanks21:14
veebersfginther: I was wondering (hoping?) that maybe just firing it off again might do it, as all the other runs installed and worked fine21:15
fgintherveebers, I've seen lots of unity8 builds fail this way21:15
fgintherveebers, I have no idea what the actual problem is as no-one has asked about it until now21:15
cjwatsonfginther: That's usually skew between builds on different architectures, more commonly observed when build queues are long22:44
cjwatsonfginther: Since it's in saucy, I assume that the skew is in a PPA22:45
cjwatsonfginther: This is relevant when there's a mix of architecture-dependent and architecture-independent packages involved, with tight dependencies that constrain each other to be of the exact same version; behaviour then depends on the relative publication dates of builds for i386 and whatever architecture you're testing on22:46
fginthercjwatson, there was actually another error message that looks like the cause of the problem:"unable to make backup link of `./usr/bin/unity8' before installing new version: Invalid cross-device link"22:47
cjwatsonThat's not the cause of the apt messages22:47
fginthercjwatson, oh?22:47
cjwatsonOh, wait, maybe it is22:47
cjwatsonYeah, that's bizarre.  Is some kind of filesystem tetris involved here?22:47
cjwatsonBecause dpkg will be making a link from ./usr/bin/unity8 to ./usr/bin/unity8.dpkg-<some suffix>, which is never cross-device unless somebody's bind-mounted something onto ./usr/bin/unity822:48
cjwatsonSorry, I didn't notice that.  The problem I describe has very similar symptoms at the *end* of the log ...22:49
fginthercjwatson, hmm, there's nothing funky going on, just trying to install into on a touch device22:49
fginthercjohnston, veebers and I investigated a little further and assumed it was a packaging bug22:49
cjwatson./etc/init/boot-hooks/setcap-unity8.conf:29:        mount --bind "$RUNDIR/unity8" /usr/bin/unity822:49
cjwatsonthat's the cause22:50
cjwatsonand I believe I saw an MP go by that gets rid of that file in trusty?22:50
cjwatsonhttps://code.launchpad.net/~saviq/ubuntu/trusty/lxc-android-config/drop-unity8-setcap/+merge/19213122:50
cjwatsonso if you can get rid of that in saucy too, maybe you should?22:50
veeberscjwatson: So I should update this bug an mark it as invalid as it's not actually an unity8 packaging issue? https://bugs.launchpad.net/unity8/+bug/124343222:52
ubot5Ubuntu bug 1243432 in Unity 8 "Packaging issue makes unity un-installable" [Undecided,New]22:52
cjwatsonveebers: It's not a bug in unity8; it's a bug in lxc-android-config22:52
fginthercjwatson, what's the story for saucy and touch?22:52
cjwatsonfginther: I don't know22:52
cjwatsonveebers: I'll reassign it22:53
fginthercjwatson, ack. I'll follow up with Saviq22:53
veeberscjwatson: ah awesome, thanks for that22:53
fginthercjwatson, yes, thank you22:53
* fginther has to leave for dinner22:53

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