/srv/irclogs.ubuntu.com/2013/11/05/#ubuntu-ci-eng.txt

=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
Saviqcihelp01:07
Saviqhey, anyone - seems all maguros are down http://10.97.0.26:8080/job/generic-mediumtests-runner-maguro/ ?01:07
Saviqah, they're being flashed are they...01:07
Saviqit seems the flash process has failed, then...01:08
Saviqhttp://10.97.0.26:8080/job/touch-flash-maguro-014E058C18015006/183/console01:08
doanacSaviq: i don't have access to those systems. I'm going to email the ci mailing list and hopefully someone can get them online03:32
Saviqdoanac, thanks, it might be that the image is completely b0rked or something, if all of them fell down03:32
veebersdoanac: oh hey, can you add to your email that I've modified http://10.97.0.26:8080/job/generic-mediumtests-trusty-touch/ -> I removed generic-mediumtests-runner-maguro  from the queue03:34
doanacveebers: shure03:34
veebersdoanac: awesome thanks03:34
Saviqveebers, so new jobs will pass?03:46
Saviqveebers, or at least ignore maguro?03:46
veebersSaviq: well, new jobs won't use the maguro runner so will get further03:46
veebersSaviq: yes :-)03:46
Saviqveebers, that's useful, thanks03:46
* Saviq cancels all the hanging unity8 jobs03:47
veebersSaviq: we will either have to kill the current jobs or wait for them to timeout03:47
veebersSaviq: heh03:47
Saviqveebers, how long the timeout?03:47
Saviqveebers, they've been at it for 10hrs now or something...03:47
veebersSaviq: ugh right, not sure but 10 hours is too long03:50
Saviqveebers, yeah....03:50
Saviqdoanac, FWIW, I'm not sure ssh alone would've helped in that case... there's no adb to the devices (as a result of failed flashing), so unless they're stuck in bootloader, and willing to listen to fastboot reboot, they need physical intervention...03:53
Saviqdoanac, there was talk of a supposedly standard 3.5mm jack contraption for low level access to the hardware03:54
doanacSaviq: usually i just see devices stuck in the bootloader.  ie - i haven't seen to many stuck03:56
Saviqdoanac, do they then accept `fastboot reboot` and such?03:57
doanacSaviq: i normally just do a "fastboot reboot" and it boots03:57
Saviqdoanac, right03:57
doanacnote: if its really stuck, a serial console might not be much help either03:57
doanacyou really need to be able to hold the power button down somehow03:58
=== Ursinha-afk is now known as Ursinha
MirvFYI I've been doing the needed hoops to transition to libmirserver10 this morning08:09
sil210010 already?08:11
sil2100How time flies...08:11
sil2100At least all the FTBFS problems right now seem to be related to the mir transition...08:39
Mirvsil2100: not all08:43
sil2100Right, unity7 and indicators are still real problems08:48
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
Mirvsil2100: indicators not, should be hopefully fixed now, but mir unity-system-compositor + unity7 yes09:06
sil2100Mirv: is unity8 stack ready for re-build? It was failing because of libunity-mir-dev : Depends: libunity-mir1 (= 0.1+14.04.20131104-0ubuntu1)09:06
sil2100Mirv: well, there was a chroot problem besides the mir transition problem in indicators, but I guess that got fixed with the subsequent run09:07
sil2100Mirv: so it wasn't just mir problems in indicators ;)09:07
sil2100Mirv: for unity7 I'm still waiting for updates from bregma09:07
Mirvsil2100: it's not failing because of unity-mir, but because unity-mir FTBFS09:09
didrocksthomi_: not sure if you are around, but can we proceed with step 1, are you ready for transitioning to 1.4 tomorrow?09:09
Mirvhi didrocks!09:10
didrockshey Mirv!09:10
sil2100Hi didrocks!09:10
didrocksmorning sil2100 :)09:10
Mirvdidrocks: we've a problem with mir again I think. I've been rebuilding stuff to transition to libmirserver10, but unity-system-compositor and unity-mir FTBFS against it (bugs filed)09:10
didrocksMirv: Mir was pulled to trunk?09:10
Mirvdidrocks: so it'd be the usual deadlock, can't publish, can't rebuild09:10
sil2100Mirv: oh, I see now that unity-mir looks like a 'real' compilation problem, missing/removed include it seems?09:10
didrockswithout warning us?09:10
Mirvdidrocks: I guess so, new commits in there09:11
didrocksMirv: please revert trunk09:11
didrocksand remove everything from the ppa that built against it09:11
sil2100Mirv: did you fill in the bugs to "Stack status" ?09:11
Mirvsil2100: yes09:12
Mirvdidrocks: ok09:12
sil2100Oh, it might not be needed soon09:12
popeydidrocks: AIUI thomi_ was travelling yesterday so wasn't online, and won't be until ~20 UTC09:12
Mirvdidrocks: I need to somehow find what the trunk used to be before the pull09:12
didrockspopey: ok, thanks :)09:12
popeynp09:12
didrocksMirv: you do have that info, right? the changelog + merge back should point to a rev?09:13
Mirvdidrocks: sure09:14
* ogra_ -> coffee ... brb09:27
* Mirv removed hud, indicator-location, mir, platform-api, qtubuntu, ubuntu-keyboard, unity-mir from PPA09:27
sil2100;/09:28
didrockspopey: coming?09:31
popeyya09:32
popeystupid browser09:32
xnoxdidrocks: Hello! =) i made a merge proposal, and the merger is test-building my package against "trusty", but i need "trusty-proposed" enabled as well.10:50
didrocksxnox: you mean about the upstream merger, not daily release, right?10:51
xnoxdidrocks: i believe so, yes. Let me get URL.10:51
xnoxhttps://code.launchpad.net/~xnox/ubuntu-keyboard/libpinyin4/+merge/19385910:52
xnoxand10:52
xnoxhttps://jenkins.qa.ubuntu.com/job/ubuntu-keyboard-ci/210/10:52
didrocksxnox: ok, yeah, upstream-merger: that would be for vila or fginther I guess ^^ (cu2d is using -proposed enabled)10:52
viladidrocks, xnox: We'll need fginther indeed :-/ But I'm surprised that -proposed is not enabled, that would diverge from cu2d and will break far more often no ?10:59
didrocksvila: IIRC, it's indeed not enabled. There were strong argument in both cases11:00
didrocksin practice, enabling -proposed isn't too much troublesome for cu2d, so I guess it won't for upstream merger11:00
cjwatsonwell, clearly needs to be *possible* to enable it at least11:01
didrocksbut we still need a way to enable/disable it easily11:01
didrocksyeah11:01
xnoxdidrocks: vila: does upstream merger have any PPAs enabled? e.g. same ones that cu2d is using? Maybe pinyin from trusty-proposed can be copied into one of those?11:02
* xnox only needs libpinyin4-dev from trusty-proposed.11:02
didrocksxnox: well, I would prefer that we fix it properly, let's see once fghinter is around. But otherwise yes, from what I know, it's using the daily-build ppa, so we can copy it there if needed11:03
xnoxI did file a bug against ci-services.11:04
xnoxhttps://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/124799211:04
ubot5Ubuntu bug 1247992 in Ubuntu CI Services "upstream merger builds do not have -proposed enabled" [Undecided,New]11:04
vilaxnox: perfect11:05
asacdidrocks: so from what i know upstream merger uses ppa-purge etc. to get back to a pristine state... do you know if ppa-purge feature is usable with -proposed? otherwisxe the devices would accumulate all kind of not-wanted stuff - or would always need a complete reinstall, which would be time consuming:)11:06
asacmaybe we need proposed-purge - if that doesnt work :)11:06
vilaxnox: I'll make sure to ping fginther about it, also, use 'cihelp' to get vanguard attention11:06
didrocksasac: ? upstream merger doesn't use ppa apart from daliy-build one?11:07
didrocksasac: it's using a local repo from what I know11:07
didrocksnot sure what ppas you are refering to :)11:07
cjwatsonI would hope that the upstream merger is using a clean chroot each time, rather than relying on purging11:07
asacdidrocks: hmmm.... good point :)11:08
didrockscjwatson: from what I know it's a clean chroot + a local repo + daily-build ppa11:08
didrocks(local repo being mostly "per stack")11:08
ogra_asac, hey, happy jetlag :)11:09
asacdidrocks: so guess we would still need something like proposed-purge as we would basically have to do one run of installing all deps that might come from proposed11:09
asacogra_: thx. I really think it's over now :)11:10
ogra_heh11:10
xnoxasac: why? cu2d is running with -proposed enabled, and so should the upstream merger.11:10
asacwell, to a bearable degree11:10
asacxnox: its different :)11:10
ogra_didrocks, did you file a bug against friends ? else i'll do11:10
didrocksogra_: I didn't, please feel free :)11:10
asacxnox: a) yues, we should install the depends from proposed for testing in upstream merger11:10
ogra_will do then11:10
didrocksogra_: assign robru to it, I guess he was the one to release it11:10
ogra_ok11:11
xnoxasac: .... but without inheritting all other uninstallables... true.11:11
asacxnox: b) no, its not very simple11:11
asac:)11:11
asacxnox: right. we want exactly all the depends and nothing else (as that might be broken and what not)11:11
asacxnox: and since we dont reflash devices, we need a reliable way to get back to the current clean archive/image :)11:12
* didrocks doesn't understand the "we want the depends thing", that's how sbuild is working: installing only the build-deps from what we want to build11:12
asaci relaly think a feature in ppa-purge to disable proposed would be helpful11:12
asacdidrocks: installing is simple, yes. but we need to uninstall those things as we dont have the time to reflash devices for every run11:13
didrocksI guess it's more in the new infra world "we want to freeze the deps" (but still be able to test against latest)11:13
asacuninstall -> revert11:13
didrocksasac: ah, on the device, avoiding reflashing?11:13
asacdidrocks: in the new world thats an additional feature, yes11:13
didrocksnot related to upstream merger, it doesn't build on the device11:13
asacdidrocks: upstream merger doesnt reflash so it can keep up with the big amount of merge proposals coming in11:13
didrocksbut yeah, I think we should "just" remove the delta rw part11:13
asacright11:14
asacso i think:11:14
asac1. devices get auto flashed if a new proposed (or released?) image is available11:14
asac2. we add proposed into /etc/apt/sources.lists.d/11:14
asac3. install stuff from sbuild with proposed deps11:14
asac4. test11:14
asac5. ppa-purge --proposed  :)11:15
ogra_asac, how do you make sure to not accidentially get other deps pulled in from proposed ?11:15
didrockswell, I think 5 is more reset-to-vanilla-image11:15
didrockswhich remove the rw part11:15
asacogra_: well, we get all the depends from what we work on... which is sane i think11:15
ogra_you need a per -ackage copy mechanism, not enable proposed altogether11:15
asacogra_: we dont run apt-get dist-upgrade11:15
asacor upgrade11:15
asacjust apt-get update11:15
ogra_but apt-get install11:15
asacapt-get install mycipackage11:16
asacogra_: that will pull in all the deps11:16
asacafaict11:16
asacbut nothing else... e.g. exactly what we want11:16
asacor very close at least :P ... no?11:16
ogra_well, i would find it safer to have them copied into a PPA first11:16
asaci dont think that adds safety unless we dont want to install all dependcs that are dangling in proposed11:17
* ogra_ would also not apt-get install but build a complete image from the PPA ... 11:18
asacassuming that ppa-purge --proposed does the right thing11:18
ogra_making the image writable might taint your results11:18
asacogra_: read backlog :)11:18
asacogra_: we dont have the luxury to install complete images11:18
asacogra_: yeah. wauit11:18
ogra_why not ?11:18
asacogra_: so later we SHOULD indeed have the image delat produced and use system image updates11:18
ogra_build an image with the change, flash the device/emulator with it, run the tests11:19
asacbut right now we dont have all of that in upstream merger code11:19
asacogra_: flashing on device takes too long for upstream merger11:19
asacogra_: too many merge requests11:19
cjwatsonTBH, this is a problem you have regardless of whether -proposed is involved; -proposed exacerbates it but that's all11:19
asaccjwatson: right.11:19
cjwatsonConsider the case of one stack that introduces a new dependency, and another stack with an unstated reliance on that new dependency11:20
cjwatsonIf you aren't arranging for a clean environment then the latter will pass tests when it shouldn't11:20
cjwatsonSo you shouldn't think of this as something specific to -proposed11:20
asaccjwatson: i am not :)11:20
cjwatsonGood :)11:20
ogra_testing with apt-get'ed packages on a rw image isnt really getting you the same results i think ... that was the point i was making ... independently of where the packages come from11:21
asaccjwatson: i was just explaining that we would something like ppa-purge --proposed feature if we wanted to apply the concept used in upstream merger currently11:21
asacogra_: thats a separate problem11:21
didrocksogra_: this won't be the case in the "new CI world"11:21
asacogra_: yes, we will produce more images and we can then use the image delta and system image approach11:22
cjwatsonSure, and I'm just saying that option name would either be misdescribing what the code does, or not really solving the problem :)11:22
asacwould require a system image revert feature though if we dont want to reflash all :)11:22
ogra_revert feature ?11:23
cjwatsonSimilar problem for autopilot testing in general11:23
ogra_yes11:23
ogra_in any case we need the emulator first ...11:24
ogra_and the thing we have doesnt seem to be suiting our needs as it is ... i guess getting this into shape to even be remotely usable will still take quite some time11:25
asacogra_: what do you mean?11:25
asacupstream merger?11:25
ogra_asac, emulator11:25
ogra_to get more test facilities that arent HW bound11:26
asacxnox has a short term problem that he cannot merge due to upstream merger not pulling in proposed bits.11:26
asac:)11:26
ogra_yes, i know, i was more referring to the general part of oour conversation :)11:26
asachehe11:27
asacright. all the funky bits are blocked on emulator11:27
ogra_right11:27
asacand the ability to produce many images from everywhere :)11:27
ogra_that one we'll have with LP buildds11:27
asacyeah. thats the hope. I don't think we have super sharp plans on that aspect though. e.g. we also have to invest in our image tooling so it can be effectively run in such a scalable env.11:31
asacetc.11:31
asacanyway, didrocks pulling through CI team for the featutes needed to get to his vision will ensure that we get there - once we have the emulator :)11:33
* asac stops distracting channel11:33
ogra_right, but that "one we have" is imho in a far future ... at least regarding the current emulator we have ... the hardware it emulates is very far from our minimal specs11:36
ogra_s/one/once/11:36
psivaadidrocks: ogra_: almost done with image 11 and friends-service is the one that's causing the pass rate to be lower than image 1011:38
ogra_yeah11:38
psivaaboth gallery and friends app tests fail systemsettle after for friends server taking up processor resource11:38
ogra_yup, as discovered in the meeting ... they either need to re-upload a rolled back version or a proper fix before we do a new image buuld11:39
ogra_it is very intresting that it oly affects mako though11:40
cjwatsonFWIW I got the slave side of livefs-in-LP done over the weekend (pending review)11:41
ogra_oh11:41
ogra_ [ Robert Bruce Park ]11:41
ogra_  * Save battery life by decreasing default polling frequency. (LP:11:41
ogra_    #1238083)11:41
ogra_i would guess that is what bites us11:42
ogra_bug 123808311:42
ubot5bug 1238083 in friends (Ubuntu) "friends-dispatcher is a little busy doing data updates on idle systems" [Undecided,Fix released] https://launchpad.net/bugs/123808311:42
cjwatsonBug 1247461 is tracking this work now11:42
ubot5bug 1247461 in Ubuntu CD Images "Move live filesystem building into Launchpad" [High,Triaged] https://launchpad.net/bugs/124746111:42
* ogra_ subscribes11:42
didrockspsivaa: ok, nice to know what's the cause :)11:42
didrockspsivaa: we'll need to talk with robru/ken I guess11:43
psivaadidrocks: ack11:43
didrockspsivaa: the regression we saw on maguro is as well due to it?11:43
psivaadidrocks: ogra_ yes, only in one attempt it's unity8 that's causing and the rest it's friends-service11:44
psivaahttp://10.97.0.1:8080/job/trusty-touch-maguro-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/11:44
psivaaalso i logged into the device and it's friends that's at the top11:46
didrockspsivaa: ok, nice to know that all those regressions are due to one and only one component :)11:46
didrockspsivaa: is there a way for you to downgrade the version of friends in one device and restart those tests?11:46
psivaadidrocks: was about to try that :)11:47
didrocksgreat ;)11:47
ogra_didrocks, psivaa asac bug 124814311:48
ubot5bug 1248143 in friends (Ubuntu) "the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases" [Undecided,New] https://launchpad.net/bugs/124814311:48
ogra_(pleas someone confirm :) )11:48
psivaawill do11:48
ogra_thx11:49
psivaadidrocks: confirmed that with the older version the issue does not occur: https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-maguro-smoke-friends-app-autopilot/14/12:01
didrockspsivaa: \o/12:01
didrocksMirv: mind you step ahead and revert friends?12:01
didrocksI guess we have enough elements now12:02
didrocksthanks for the hunt psivaa :)12:03
psivaadidrocks: yw, ogra_ found it first :)12:03
ogra_thanks for verifying !12:04
ogra_:)12:04
psivaa:)12:04
didrocksogra_: sharing the congrats of finding the guilty component ;)12:05
Mirvdidrocks: is that lp:friends revert to previous release, rebuild, and release?12:11
Mirvsome decrease of polling frequency is the only non-test change there12:12
* Mirv notes that ogra quoted that commit in particular12:12
Mirvok then, understanding enough, reverting that one commit12:13
Mirvdidrocks: before I forget what I was doing before that, can you check process-cpp from platform stack is whitelisted for publishing?12:15
Mirvwe finally got it working12:15
didrocksMirv: excellent! checking :)12:15
ogra_right, seems to be just a gconf key change after all12:15
didrocksMirv: yeah, whitelisted12:16
Mirvdidrocks: thanks12:16
didrocksyw12:16
didrockssil2100: did you get in saucy download-manager?12:18
sil2100didrocks: it's in the unapproved queue12:19
didrockssil2100: did you poke the SRU team? It needs to be in quickly as there is the 7 days period and we need to kick an image after that12:19
sil2100Didn't get an aswer yesterday, but I'll poke people directly today :)12:21
didrockssil2100: thanks!12:21
Mirvdidrocks: process-cpp in NEW queue12:30
didrocksMirv: checking12:30
didrocksinclude/posix/linux/proc/process/state.h: LGPL (v3)12:32
didrocks  [Copyright: 2012-2013 Canonical Ltd]12:32
didrocks(mutliple of them)12:32
didrockswhen debian/copyright states only 201312:32
didrocksnitpicking, not important, but just FYI Mirv $12:32
didrocks^12:32
didrocks-doc should suggests the -dev IMHO (but again, not that important)12:34
didrocksand the long description is quite short…12:34
=== greyback is now known as greyback|lunch
didrocksMirv: otherwise sounds good (didn't change that much since my first checking and pass/reject). Can you make tvoss aware of those for a future fix? ^12:36
didrocks(accepted)12:36
Mirvdidrocks: ok, I'll let him know.12:38
Mirvor better yet, make a quick branch12:38
didrocksthanks ;)12:39
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== greyback|lunch is now known as greyback
sil2100didrocks: what to do in case when I get test failures for calendar-app? The trunk calendar-app has much more tests than the one on the image, but still it's a solid 4-reproducible-failures13:43
sil2100didrocks: (bug filled)13:43
didrockssil2100: ok, please ping upstream as well, but there is no regression, right?13:43
sil2100didrocks: I guess not, those tests are new as far as I see (will double check)13:44
didrockssil2100: ok, I think it's okish to push then13:44
sil2100didrocks: ok, as for pushing... how do we actually 'release' click packages ;p?13:46
didrockssil2100: it's click only? I think just ping sergio13:46
didrockssil2100: how did you test it then? from the ppa?13:47
didrocks(it overrides the click ones?)13:47
sil2100didrocks: popey gave us instruction on how to test it ;)13:49
didrockssil2100: oh, do you have a link?13:49
sil2100didrocks: the click packages are being built on jenkins, so you download them from there, reconfigure and test13:50
sil2100Yes, let me fetch it13:50
sil2100http://10.97.0.26:8080/view/click/?13:50
sil2100We wouldn't know if not for popey ;p13:50
didrockssil2100: ah ok, sorry, I thought those were with daily releases13:50
didrockssil2100: so, that's why I gave them to you13:50
sil2100No, those are click-only core-apps13:51
Mirvdidrocks: sil2100: how do I get the removed packages back to the PPA? each of the removed ones seem to be in a state that 'build' jobs consider them building but they're not there in daily-build PPA and the build jobs get stalled. I tried force rebuild already (with qtubuntu)14:00
cjwatsonyou can copy a removed package back in (with binaries) as long as you haven't later done something that the copy would conflict with14:01
Mirvcjwatson: the PPA packages were removed for reason (mir transition that was wanted), I'm wondering why the dput the cu2d should be doing doesn't seem to be working14:02
Mirvnot wanted14:02
Mirvnow that the rebuilds are tried14:03
cjwatsoncu2d does a copy rather than a dput, I'd have thought.  But anyway, what package name and version number is this?14:06
fginthermorning14:09
Mirvcjwatson: I'm talking about cu2d -> PPA, not PPA -> archive14:16
Mirvdidrocks: sil2100: anyway, feel free to fix if you find out what's the problem.14:17
cjwatsonMirv: OK; still happy to dig out the failure reason from logs if I know what I'm looking for (package name, version number)14:18
Mirvcjwatson: ok I think I'm now seeing the problem already without checking the logs, it's trying to upload a package with the version number14:21
Mirvthe same version number as previous14:21
Mirvdidrocks: sil2100: so next step, if you can think of why force rebuild does not increment the number, feel free to fix.. otherwise I guess the first build of tomorrow will work for all14:21
MirvI'll cancel platform, services, indicators ongoing runs now14:22
sil2100Ok, I'll backtrack the discussion in a moment14:22
cjwatsonMirv: that would certainly do it14:23
didrocksMirv: interesting, do you have logs with FORCE_REBUILD not incrementing numbers?14:25
Mirvdidrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-1.1prepare-qtubuntu/472/console14:25
didrocksMirv: IIRC, ppas were taking back the same version if the previous one was removed, didn't they?14:28
didrockshttps://launchpad.net/~ubuntu-unity/+archive/daily-build/+builds?build_text=qtubuntu&build_state=all I don't see the reupload of  0.52+14.04.20131105-0ubuntu1, did we got an email with the reject?14:29
* didrocks didn't see one in mails14:29
cjwatsondidrocks: no, you can't reupload the same version14:29
cjwatsoneven if the previous one was removed14:29
didrocksinteresting, I should have dream that ppa was enabling that now14:30
cjwatsonit's possible to *copy* the previous one back in if that's necessary14:30
didrockswell, I need to fix cu2d to even considered deleted version then14:30
cjwatsonand you can upload an older version after a removal, I believe14:30
cjwatsonbut I don't expect we'll ever consider it desirable to reupload the same version14:30
didrockscjwatson: no worry, I juts thought that was now handled on the LP side, I'll just add the logic to consider those versions14:31
didrockscjwatson: I'm using dest.getPublishedSources(status="Published", exact_match=True, …), is there a way to get Published or Deleted with the same query for instance? (I was reluctant, maybe for no good reason on looping on all sources disregarding their state)14:36
cjwatsonSadly not, bug 84548614:37
ubot5bug 845486 in Launchpad itself "cannot pass sequence to Archive.getPublishedSources through API" [High,Triaged] https://launchpad.net/bugs/84548614:37
didrockscjwatson: ok, so you would suggest I should just disregard the status (and have more api calls then when looping over all sources), and just take the highest version?14:39
cjwatsonYou should have some arrangement to avoid iterating over the entire collection, probably14:40
didrockswhat do you mean?14:40
didrocksactually, I'm just interested in "getting the higher version that ever existed for that source in this ppa"14:40
didrockshighest*14:40
cjwatsonDo you actually need to walk over all publications?  You should generally get the most recent first14:41
didrocksgenerally == ensured? ;)14:41
cjwatsonWell, it's always most recent first; that's guaranteed to be highest version first AS LONG AS people aren't playing tricks to wind versions backward14:41
didrocksok, so, in that case, even the removed version (which is the highest) will be the first one?14:42
cjwatsonIf I understand things correctly then yes14:42
cjwatsonYou get them in reverse order of publication14:43
cjwatsonIf that's what you need then you can avoid the full traversal14:43
didrocksok, making sense. I can just try relying on that without looping over14:43
cjwatsonIf it's not then you probably just have to walk everything14:43
didrocksthanks cjwatson14:43
cjwatsonOh, in fact, it's better than that14:43
cjwatsonif version is not None:14:43
cjwatson    ...14:44
cjwatsonelse:14:44
cjwatson    orderBy.insert(1, Desc(SourcePackageRelease.version))14:44
cjwatsonSo you get them in descending version order14:44
didrocksnice! I'll definitively use that14:45
cjwatsonThe full ordering will be by source package name, then by descending version, then by id (~= most recent first)14:45
didrocksMirv: around?14:52
sil2100cu2d updated? :)14:54
didrocksyep, I'm trying with that on qtubuntu right now14:54
didrocksat least, we now see it:14:55
didrocks2013-11-05 14:54:14,731 INFO A version in the ppa (0.52+14.04.20131105-0ubuntu1) is higher than the proposed version in bzr (0.52+13.10.20131016-0ubuntu1) (previous tests/builds failing?). Basing on that one.14:55
didrocksUploading to ppa (via ftp to ppa.launchpad.net):14:55
didrocks  Uploading qtubuntu_0.52+14.04.20131105.1-0ubuntu1.dsc: done.14:55
didrocksok, seems to be fine :)14:55
didrocksMirv: not sure what you wanted to rebuild, but qtubuntu is done and cu2d now supports it14:55
didrocks(with the tests updated as well)14:55
sil2100I guess he wanted to rebuild it against the old mir, I think?14:56
* sil2100 isn't sure14:56
didrockssil2100: I think so14:56
didrocksqtubuntu in rebuild anyway14:56
sil2100But as long as it's possible now, then good! Since this was also blocking ubuntu-keyboard sadly ;)14:56
didrockssil2100: you can relaunch then :)14:56
sil2100\o/ Thanks! Can I use jenkins UI?14:56
didrockssure14:57
sil2100FORCE_REBUILD is required, or without it will work as well?14:58
didrockssil2100: if there is no diff with distro, FORCE_REBUILD is required14:58
=== Ursinha is now known as Ursinha-afk
didrockssil2100: any news on the other apps, apart from ubuntu-ui-toolkit, gallery-app, ubuntu-keyboard, unity8 are under progress?15:21
=== Ursinha-afk is now known as Ursinha
sil2100didrocks: I'll take care of notes-app in the meantime if you don't mind, it wasn't on the list but I guess those will be done when 'ready'15:22
didrockssil2100: notes-app is a click app, isn't it?15:23
sil2100didrocks: we have it in cu2d, so I don't know?15:23
sil2100I was never entirely sure about the status of that one15:23
didrockssil2100: ok, please release it anyway, just in case15:23
didrocksI think some are both in the archive and in click15:24
didrocksnot sure why sergio kept them like that15:24
Mirvdidrocks: I can rebuild the rest. do we have a team meeting / telco in 18min? as seb128 e-mailed today, the UTC time should not be change so in winter time now it'd be 1h "earlier"15:42
=== gatox is now known as gatox_lunch
Mirvand they're having their half of the meeting at the moment15:44
sil2100hm, I think ours is scheduled for like in an hour still, didn't see any mention of us using the old time15:57
seb128sil2100, we decided previous cycle to used a fixed UTC time, that should apply to your half of the meeting as well15:58
seb128didrocks doesn't seem to be around though15:58
sil2100Indeed15:58
Mirvsil2100: we don't have "ours" scheduled in calendar, since it has been lately replaced by the CI call. but on the other hand I don't know whether it makes sense for me to join the evening call once a week if it hasn't got anything to do with what used to be team chats before.16:02
MirvI mean I can of course, but that's again 12h after I started my day16:04
didrocksseb128: in a hangout16:04
sil2100Mirv: I consider that as 'ours', since this basically replaced our weekly meetings16:04
sil2100As we didn't have a normal weekly meeting since this was scheduled16:05
didrocksogra_: cyphermox: sil2100: robru: kenvandine: cyphermox: ready to have the meeting now?16:06
sil2100Mirv: the timing is not too good for you I guess indeed anyway16:06
ogra_didrocks, no16:06
cyphermoxdidrocks: I'm in the phonedations one16:06
ogra_didrocks, i always have another meeting at this time16:06
didrocksok, 2 people not available, let's postpone in one hour?16:07
ogra_(same as cypher)16:07
sil2100Mirv: ^16:07
kenvandinesure16:07
Mirvsil2100: I've no problem with that as such, I just guess the Tuesday telco is no different from other days, so it's not as much of a "weekly"16:07
didrockssorry Mirv :)16:07
sil2100;)16:07
sil2100didrocks: publishing notes-app and gallery-app now - there are 2 gallery-app failures, but those do not happen on my local device, I had all green16:08
Mirvdidrocks: no problem. I'm just interested in clarification that indeed once a week we have this one telco that we invite everyone to, while on other days just those who are around at that time normally?16:09
didrockssil2100: great!16:09
didrocksMirv: exactly my thoughts16:10
sil2100didrocks: packaging ACK needed! http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_notes-app_1.4+14.04.20131104.2-0ubuntu1.diff <- seems like migration of the naming parts to be more click-click16:10
* Mirv snoozes alarm for 50mins16:10
didrockssil2100: hum, is the .mo picked up then?16:10
didrocksand no more binary?16:10
didrocksthanks Mirv16:10
sil2100didrocks: no binary, the desktop file opens qmlscene directly16:11
didrockssil2100: is it already translated, did you check that the translation are loaded up?16:12
sil2100Let me change the locale and check, one moment16:13
sil2100didrocks: the app is translated, so I guess all works ok?16:18
didrockssil2100: +1 then :)16:20
didrockssil2100: you started them from the package? how were you sure? ;)16:20
sil2100I'm not! But I checked that notes-app installed the .desktop file, and unity8 uses desktop files for launching the app, so I think I ran the right thing ;p16:21
didrockssil2100: ok, trusting you, it's all fuzzyness for me TBH ;)16:22
sil2100Same here, I want some docs for this!16:23
didrockssil2100: do you think you'll have time for doing ubuntu-keyboard and unity8 before the meeting?16:23
didrockssil2100: +100016:23
didrocksI guess lool has the best understanding, maybe he can help16:23
sil2100didrocks: doing ubuntu-keyboard now, will try finishing unity8 too16:23
didrocksthanks16:23
looldidrocks, sil2100: Actually this should just be covered in https://wiki.ubuntu.com/Touch/Testing#Testing_your_Ubuntu_Touch_Code_before_submission16:24
loolsee Running Click tests16:24
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
didrockslool: but if we install a .deb for testing for a click package16:27
didrockslike this notes-app16:27
didrockswhen we have both16:27
didrocksclicking on unity8 to start it16:27
didrockswill it starts the click version16:27
didrocksor the debs one?16:27
sil2100didrocks: there is an extrapackage issue for unity8 on cu2d, but I won't be wasting time to fix that now as I anyway run the unity8 AP tests on my phone if you don't mind16:36
looldidrocks: I dont know!16:36
looldidrocks: but it seems a bad idea to have both16:37
didrockssil2100: sure16:37
looldidrocks: it's not a real life use case to have both .deb and .click (it might be when desktop converges though  :-/)16:37
didrockslool: well, I agree, but it seems that we want to have .debs and click for some cases16:37
didrockslool: and we need to know how to test both then16:37
didrockslool: can you clarify this up with sergio? I'm all for dropping the .debs if we can16:37
looldidrocks: Maybe we want to add a mode to force usage of this or that set of tests from phablet-test-run16:37
loole.g. phablet-test-run --click-only, and --deb-only16:38
loolwhich would mangle sys.path in the right way16:38
loolHmm no Sergio here16:38
didrockslool: that would be enough to me :)16:38
looldidrocks: I'm about to step out, but I will followup with Sergio either over email or on Thursday16:38
didrockslool: thanks16:39
=== gatox_lunch is now known as gatox
tedgThis branch didn't get a Jenkins review.  I'm not sure why: https://code.launchpad.net/~marcustomlinson/libdbusmenu-qt/virtual_base_destructors/+merge/19387916:47
tedgdoanac, Do you know how I can figure out what's up? ^16:56
doanactedg: i'm investigating with fginther right now16:56
fginthertedg, the owner of the MP wasn't on the whitelist, that's been fixed16:56
tedgAh, okay.  I thought all ~canonical was on the whitelist?16:57
sil2100didrocks: unity8 tests still running sadly, had a device reset inbetween strangely16:57
didrockssil2100: no worry, keyboard is good?16:58
sil2100didrocks: been dogfooding it, looked good but wanted to see unity8 tests if those are ok with it16:59
sil2100didrocks: we doing the meeting in a hangout?17:00
sil2100Or IRC?17:00
didrockssil2100: hangout17:00
didrockskenvandine: cyphermox: joining?17:00
didrocksplars:  ^17:00
cyphermoxes17:06
cyphermoxyes17:06
sil2100didrocks: unity8 is GREEN, so ubuntu-keyboard as well17:06
sil2100didrocks: can I publish?17:06
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Services/job/cu2d-services-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-keyboard_0.99.trunk.phablet2+14.04.20131105.1-0ubuntu1.diff <- packaging change, but still browsing through it - the changes seem ok, although I need to dig in deeper to understand some changes17:10
sil2100didrocks: seems ok, there is one line in copyright that I don't understand (the first +"License: LGPL-3" under Format:)17:16
ogra_kenvandine, robru i'll be around ofr at least another 2h (probably even 4) if you want the image triggered ...17:19
didrockssil2100: general license of the package, not really useful, but not harmful17:19
didrockssil2100: +1 then17:19
kenvandineogra_, thx17:19
robruogra_, ok, will let you know17:19
sil2100ACK :)17:20
didrocksrobru: kenvandine: cyphermox: resent the instructions by email17:25
didrockshope they all make sense :)17:25
robrudidrocks, ok, thanks17:26
didrocksyw!17:26
cyphermoxok17:26
Mirvphew, ok now really gone again. I may have had click intervening the ui toolkit results, but the sdk team is meanwhile investigating the maguro failures they have (without any click-setup) and robru is testing ui-tk + apps on his maguro.17:45
Mirvcomplex17:46
Mirvbug #1248264 is for the UITK probs17:46
ubot5bug 1248264 in Ubuntu UI Toolkit "Failing AP tests with trunk ui-toolkit on top of image #11" [Critical,New] https://launchpad.net/bugs/124826417:46
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
robruogra_, still around? i'll be releasing ubuntu-ui-toolkit soon if you want to kick a build in 30 mins or so?19:10
kenvandinerobru, it might take longer than that for it to make it to the release pocket19:13
robruoh, right19:13
robruit'll just be in proposed. ugh19:13
ogra_yeah, so in ~1h or so then19:15
ogra_no prob :)19:15
robruogra_, ok, great, just finished the publish job19:18
ogra_k19:19
robrukenvandine, cyphermox, thomi_, Mirv, can somebody confirm that this is the correct way of enabling ap 1.4 in qa stack? https://code.launchpad.net/~robru/cupstream2distro-config/autopilot-1.4/+merge/19399419:32
thomi_robru: I *think* that's correct, but I'm not the right person to ask really19:33
thomi_robru: will you let us know when we can start merging 1.4 branches to trunk?19:33
kenvandinerobru, so the 1.4 branches merged into trunk?19:33
=== thomi_ is now known as thomi
robruthomi, it will be really soon that you can start those merges.19:33
kenvandinethomi, i guess once we get the qa stack built19:33
thomirobru: sweet! \o/19:34
thomikenvandine: cool19:34
robruthomi, maybe 30 minutes19:34
robruthomi, i guess my question is "trunk means 1.4, right?"19:35
kenvandinerobru, approved19:36
robrukenvandine, oh, i realized that target_branch was redundant, please re-review19:36
kenvandineoh right... good catch19:37
robrukenvandine, cyphermox: ok, i kicked the build19:39
robrukenvandine, cyphermox: I guess we need to publish qa stack before thomi's team can start landing branches?19:39
robruor is the PPA enough?19:39
kenvandinePPA should be enough19:39
kenvandineright thomi?19:39
kenvandinerobru, remember to check the prepare logs on the build19:40
kenvandinemake sure there isn't merge problems19:40
thomikenvandine: robru: I think the idea was to get a clean image published with 1.3, then do one with 1.419:40
thomiI'm not sure I understand the question though19:40
thomiso...19:40
thomi:)19:40
kenvandinei'd suspect the prepare will have problems since we switched branches19:41
kenvandinethomi, yeah... cu2d will build the qa packages into the daily ppa19:41
kenvandinethen you can start working on getting all the other branches merged building against that19:41
robruthomi, ok, but I mean like, lp:autopilot trunk contains v1.4. there's not some separate 1.4 branch somewhere, right?19:41
thomirobru: that's correct. trunks (for the four AP-related projects) are all 1.419:43
thomi1.3 lives in a separate series19:43
robruthomi, ok, perfect. so we're building those in the PPA now. after ogra builds an image we can land them in distro.19:43
thomirobru: so the MP you linked above should work19:43
thomicool19:43
thomirobru: well, so once they're in the PPA, we need to merge all the 1.4 changes to the various projects19:43
thomithen ogra can build an image :)19:43
thomiso... let us know when we can start merging :)19:44
robruthomi, well, we still need an image pre-1.4 i think19:44
robruthomi, do you need autopilot 1.4 in distro or just in PPA?19:44
thomirobru: ahh, yes. understood19:44
thomirobru: ultimately in the distro. what happens while we merge is up to you guys I guess, as long as it's used in the upstream-merger job runs19:45
robrufginther, do you know if autopilot gets pulled from the daily-build ppa during CI, or does it have to be in distro for that?19:45
fgintherrobru, most jobs use the daily-build ppa19:45
robrufginther, but i mean specifically for the autopilot packages too? or just whatever package is being built?19:46
fgintherrobru, sorry, I'm not following. Are you talking about an $app-autopilot package?19:48
fgintherlike galler-app-autopilot?19:49
fgintherlike gallerr-app-autopilot?19:49
fgintherlike gallery-app-autopilot?19:49
robrufginther, sorry19:54
robrufginther, I mean, if I propose a branch against lp:gallery-app, and it runs the autopilot test, will it install autopilot itself from the PPA, or does it get autopilot from distro?19:55
thomiHey guys - we have good reason to believe that the python-autopilot package in the daily-build-next ppa is borked19:57
thomiit seems to be version ed 1.4.X, but is built from the 1.3 sources.... which is odd19:57
thomirobru: any ideas?19:58
fgintherrobru, gallery-app is backed by the daily-build ppa so it would resolve dependencies from there19:59
robruthomi, stop using daily-build-next? that's only used during final release freeze before ubuntu+1 opens. trusty is open now, so please use daily-build ppa instead19:59
robrufginther, ok, thanks19:59
fgintherrobru, all projects should be building against the daily-build ppa (there may be 1 or 2 exceptions)20:00
fgintherthomi, I'm trying to understand the problem20:00
fgintherthomi, are you referring to this? http://10.97.0.26:8080/job/autopilot-testrunner-otto-trusty/43420:01
robruthomi, ok, it looks like autopilot* and xpathselect 1.4 all just landed in the PPA as of 3 minutes ago. I think that should be good enough to get CI working, so please land one branch just to see what happens, and if it works then you can go ahead and land all your AP branches now. let me know of any problems20:01
fgintherthomi, ohhhhhhh20:03
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
thomifginther: robru: ummmm20:06
thomifginther: the trusty/ap 1.4 test job you set up for us uses daily-build-next20:07
thomifginther: which is causing problems for us20:07
thomirobru: I'll try an experimental merge now20:07
robrufginther, hm, yeah, shouldn't be -next anymore I don't think?20:08
robruunless we're starting on ubuntu 14.10 already ;-)20:08
fgintherthomi, it's using ppa:ubuntu-unity/daily-build20:09
thomifginther: ugh, sorry - yes20:10
fgintherwhew20:10
thomifginther: I still think that AP package is busted though20:10
fgintherthomi, I did see the version mismatch thing20:10
ogra_=== Image #12 is building ===20:10
thomiyeah20:10
davmor2ogra_: woop woop! \o/20:10
thomifginther: /var/local/autopilot/autopilot.log: 19:47:16.560 INFO autopilot:141 - Autopilot Source Version: 1.3.120:10
thomifginther: sure;y that's wrong?20:11
robrucyphermox, can you confirm this change? you did a manual upload that is confusing jenkins. https://code.launchpad.net/~robru/autopilot/fix-changelog/+merge/19400220:11
cyphermoxdone20:12
robruthomi, oh, yes, it's possible that autopilot package is wrong. i see in the jenkins job that the changelog has some inconsistencies so the new version didn't build yet20:12
thomirobru: OK. that would explain the oddities that elopio has seen20:12
thomirobru: can you please fix and ping me when I should retry?20:12
robruthomi, that mp ^^ should fix it, once that lands i'll rebuild soon20:12
robruthomi, ok20:13
thomirobru: thanks man20:13
robruthomi, no worries20:13
ogra_argh !20:15
ogra_crap20:15
robruogra_, what?20:15
ogra_robru, lillipilly was rebootedm so proposed migration didnt happen20:15
ogra_i guess we need an image 13 right afterwards ...20:15
robruogra_, ok well we are doing all this AP stuff in the PPA so the archive should be safe for an image build whenever you can.20:15
ogra_yeah20:16
* ogra_ only ran "rmadison -S ubuntu-ui-toolkit|grep proposed" ... 20:16
ogra_but rmadison hasnt been updated either20:16
ogra_(since it runs on lillipilly too)20:16
ogra_checking without the grep actuallye revels that it didnt even end up in proposed yet20:17
ogra_*actually reveals20:17
kenvandineit's pending in proposed20:22
ogra_yes, it shouldnt20:23
ogra_it was copied 1h ago20:23
popeyshould #12 be available?20:30
ogra_popey, yes, but not with the expected new ui toolkit20:32
ogra_that seems to be stuck entering proposed20:32
robruogra_, anything I can do to help ubuntu-ui-toolkit along? need me to republish in jenkins?20:40
ogra_robru, stgraber is looking into it in #ubuntu-release20:41
ogra_<stgraber> last publisher failed because of missing access to the seeds20:42
ogra_<stgraber> yeah, the publisher looks stuck20:42
ogra_its an infrastructure issue ...20:42
robruthomi, ok, i fixed that one issue with the old autopilot version and kicked some new builds. you can watch their progress here: https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages?field.name_filter=autopilot&field.status_filter=published once you see some green checkmarks there, then you can try proposing branches again. i gotta head for lunch, will be back in a bit20:42
thomiok, thansk20:43
thomi*thanks20:43
elopiothomi, I see green checkmarks, I'll rebuild the job.21:19
thomielopio: thanks21:26
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
thomifginther: robru: I tried this MP as a test landing: https://code.launchpad.net/~elopio/ubuntu-calculator-app/autopilot-1.4/+merge/19264321:42
thomifginther: robru: but it failed... I wonder if you guys could help me figure out what went wrong?21:43
thomithe error is in here: http://91.189.93.70:8080/job/generic-mediumtests-trusty/58/console21:43
thomi"ImportError: No module named ubuntu_calculator_app"21:43
thomilooks like the test suite was never installed?21:43
fgintherthomi, looking21:43
thomithanks21:44
fgintherthomi, ubuntu-calculator-app-autopilot : Depends: libautopilot-qt (>= 1.4) but 1.3+13.10.20130814-0ubuntu1 is to be installed21:45
fginthernow to figure out why21:45
thomioh, I missed that21:45
thomiwell, it seems the AP 1.4 stuff hasn't fully landed in the right places yet21:45
fgintherthomi, oh, I know why. need the daily ppa21:45
fgintherone momento21:45
thomifginther: apparently unity8 doesn't use the daily PPA either (according to Saviq), so that might be a problem for us down the line as well21:47
robotfuelI just had this happen in my webbrowser app MP, it's not suppose to be 1.4 WireProtocolVersionMismatch: Wire protocol mismatch at <session bus org.freedesktop.Application /com/canonical/Autopilot/Introspection>: is 1.4, expecting 1.321:47
robotfuelhttps://code.launchpad.net/~chris.gagnon/webbrowser-app/troubleshoot-select-many-noorder/+merge/193988 from this Merge proposal21:48
Saviqfginther, should we be using the daily ppa in the jobs at all? I thought it's dangerous since things from daily release are built there, even if down the line they're not published, and if another stack gets published, built against daily-build, it might get broken dependencies, at best21:48
* popey updates to 1221:49
thomirobotfuel: We're landing 1.4 fixes now21:49
thomirobotfuel: so AP is version 1.4 for everyone21:49
thomirobotfuel: so maybe merge that branch with the 1.4 compatibility one21:50
thomiand merge them together21:50
thomis/merge/land/21:50
robotfuelthomi: ack21:51
fgintherSaviq, using the daily ppa is the only way to resolve dependencies that are inflight and must be released together. For example, in this case we need to release autopilot 1.4 and the apps with updates to 1.4 tests at the same time. As a result, we have to use the daily ppa to resolve that dependency21:54
fgintherSaviq, yes, as a result we can end up building a MP with a dependency that is never published.21:55
Saviqfginther, well, we could push ap 1.4 through to the distro first, and then publish other projects without the need for daily-build PPA21:56
Saviqfginther, obviously unless there's something preventing ap 1.4 from getting into distro21:56
Saviqfginther, anyway, if that's an exception, I'm fine with it :)21:58
thomifginther: let me know when I can re-approve that MP eh?22:01
robruthomi, fginther: sorry just got back from lunch22:03
robruthomi, yeah, looks like autopilot built ok but it looks like there was some issue building autopilot-gtk and autopilot-qt. not sure what. retrying...22:04
fgintherthomi, it's building now22:05
* thomi needs to be more patient22:05
robruthomi, https://launchpadlibrarian.net/155909983/buildlog_ubuntu-trusty-amd64.autopilot-gtk_1.4%2B14.04.20131105.1-0ubuntu1_FAILEDTOBUILD.txt.gz does this failure mean anything to you?22:05
thomirobru: yes, it's using autopilot 1.3, instead of 1.422:05
fgintherSaviq, that's sort of the problem, autopilot couldn't move to the archive until all of it's rdepends have been updated22:06
robruthomi, hmmm, maybe it's just a staging issue then. 1.4 is in the ppa now so hopefully simply retrying it will fix it22:06
thomiso either it's not finding the new AP package, or it's using the borked package from this morning22:06
thomirobru: hopefully22:06
Saviqfginther, got it22:06
fgintherSaviq, but I think this model is being designed away by didrocks new release model22:06
Saviqfginther, yeah, it should be better with flight control ;)22:07
fgintherSaviq, AIUI we would only depend on this monster PPAs when necessary22:07
robruthomi, oh yeah, looking closely it's using 1.4+14.04.20131105 which is the borked one, it really needs 1.4+14.04.20131105.1 to work22:07
fgintherand not for ever MP22:07
elopiocihelp, what does this mean? "bzr: ERROR: Error parsing trunk.recipe:2:2: Indent not a multiple of two spaces."22:08
elopiohttp://10.97.0.26:8080/job/generic-mediumtests-builder-trusty-armhf/463/console22:08
kenvandineogra_, robru:  uitk published in release pocket22:10
fginthercrap ppa-purge failed me22:11
robrukenvandine, excellent22:11
fgintherthomi, plan b, will try again in a moment22:14
thomifginther: ok22:14
fgintherelopio, there are extra spaces in front of the job parameters22:14
elopiofginther: ah, found it. Thanks.22:15
ogra_kenyeah, but didnt arrive yet22:19
ogra_ogra@chromebook:~/Desktop$ rmadison -S ubuntu-ui-toolkit|grep proposed|wc -l22:20
ogra_622:20
ogra_next publisher run is ours22:20
ogra_ogra@chromebook:~/Desktop$ rmadison -S ubuntu-ui-toolkit|grep proposed|wc -l22:21
ogra_022:21
ogra_and there we go :)22:21
fgintherthomi, building again22:22
ogra_=== Image #13 is building ===22:22
thomifginther: ok :)22:25
fgintherthomi, \o/ merged22:25
thomiI can re-approve that MP?22:26
thomioh22:26
thomiyou did it already, I see now22:26
thomifginther: sweet22:26
thomiI'll start approving some others.22:26
thomifginther: do you guys have permission to top-approve everything?22:27
thomilike, are you in some super-team?22:27
fgintherthomi, I happen to be part of lots of teams, but no super team22:28
thomihmmm22:28
thomisome of these MPs I don't have permissions to approve22:28
fgintherthomi, I should22:29
fgintheror balloons22:29
balloonsI can top-approve..22:30
plarsogra_: 13? 12 is still not done testing even22:32
plarsbut things are looking pretty decent so far22:33
robruplars, yeah, 12 got kicked prematurely, it didn't have the uitk fix we needed. so 13 is what 12 was supposed to be; ignore 12.22:35
robruthomi, looks like autopilot-gtk build is fixed, so it looks all good on my end. are you having success with your merges now?22:36
thomirobru: one merged OK, kicked off a few more22:36
robruthomi, k, great. i'm around for 3 more hours, let me know of any problems you encounter.22:37
thomithanks22:38
thomirobru: what's happening with the friends app MP? I notice you re-approved it...23:40
elopiocihelp, do we have a hook that installs qtdeclarative5-nemo-qml-plugin-folderlistmodel ?23:41
fgintherelopio, shouldn't that just be a dependency? or do you need the ppa?23:46
fgintherelopio, link to job or mp?23:46
elopiofginther: here's the failure: http://10.97.0.26:8080/job/autopilot-testrunner-otto-trusty/444/console23:47
elopioI suppose I need the ppa.23:47
thomifginther: do you have permissions to top-approve this? https://code.launchpad.net/~elopio/ubuntu-ui-toolkit/autopilot-1.4/+merge/19257423:48
fgintherelopio, yep, I think so. you can add it with the hook "D09add_ppa~ubuntu-touch-coreapps-drivers~daily"23:48
elopiojust what I was looking for.23:48
elopiofginther: ty23:48
fgintherthomi, that's the one team I'm not a member of :-(23:49
thomihmmm23:49
fgintherthomi, maybe robru ^ ?23:49
* fginther goes offline for a bit23:49
robruthomi, sure23:56
thomirobru: If you can, can you please add me to the relevant team so I can do that myself?23:57
robruthomi, not sure about the friends merge, the failure log indicated that wait_select_single was missing, I assume that's new API in 1.4, which means that it was just running with 1.3 there. re-approved in the hopes that it'd get 1.423:57
thomirobru: your conclusion sounds correct. Are you sure that borked 1.4 package from this morning isn't still hanging around somewhere?23:58
robruthomi, not sure; was hoping a simple re-approve would flush it out ;-)23:58
robruthomi, I don't seem to have permissions to add you, but a great team to be in is https://launchpad.net/~ubuntu-unity23:59
thomiok23:59
thomiwell, I hope youdon't plan on sleeping in the next 24 hours :)23:59
robruthomi, that's the super-team that is a member of almost all canonical-run teams, I seem to be able to push directly to trunk on almost any branch ;-)23:59

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