/srv/irclogs.ubuntu.com/2013/12/09/#ubuntu-ci-eng.txt

Mirvhmm why does my updated mako just flickr and crash unity8...05:24
Mirv(54)05:36
didrockshey Mirv, how was your week-end?07:07
Mirvhi didrocks, fine (and long!)07:27
didrocksheh, I hope you enjoyed your Friday!07:27
didrocksdid you go outside?07:27
didrockslike, were they fireworks and such?07:27
MirvI did go outside, but not that far away. there aren't permissions for "fireworks at will" (like in the New Year), so there would have been only some in some more official festivities places.07:30
didrocksyeah, I guess so… ;)07:31
didrocksMirv: did you suffer from issues with latest upstart-app-launch?07:33
didrocksMirv: there is an ABI transition, so it should have picked other packages as well07:33
Mirvdidrocks: so it seems I have some other problem, I just have unity8 flickering and crashing when I try to open it.07:37
Mirveven after I downgraded the upstart-app-launch07:37
Mirvand yes upstart-app-launch has the bump now07:37
Mirvmaybe a time for phablet-flash -b to be sure I'm seeing this on image 5407:39
didrocksMirv: yeah, sounds like a phablet-flash -b time :)07:41
didrockscan you keep me posted?07:41
didrocksMirv: FYI, I just reuploaded an url-dispatcher for the soname libupstart change07:41
didrocksMirv: we don't want the hazardous commit in :)07:41
Mirvok full flash seems to fix whatever problem I had08:53
sil2100Mirv: ok, good to know - my device is still flashing08:56
didrocksFYI, I've uploaded url-dispatcher from sil2100's branch and disabled automatic rebuilds08:58
sil2100didrocks: thanks!08:59
sil2100didrocks: hm, maybe we should change the driver of content-hub btw.?08:59
sil2100didrocks: since from what I see only Ken has the power to top-approve there right now, which is tragic ;/08:59
didrockssil2100: yeah, sounds legit, we will need to ping Ken for it08:59
sil2100didrocks: do you think it would be wise to switch the driver now to phablet-team (for now), I can do the switch and move trunk to that team so we can approve the ted's branch09:14
=== ev changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: ev | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
didrockssil2100: that would be good, but we need Ken to change the driver09:22
sil2100didrocks: why? I see I can do that as well on LP, strangely09:22
didrockssil2100: oh, if you can, please do then :)09:23
Mirvsil2100: didrocks: if I recall correctly, the driver doesn't actually matter that much, the only thing that matters is that under which user/team the trunk branch is set to be pushed09:25
didrocksMirv: yeah, I guess it is the case09:26
sil2100didrocks: I re-target ted's branch in a moment as well!09:26
didrocksgreat ;)09:27
sil2100didrocks: can you approve? Would feel silly to do it myself ;p https://code.launchpad.net/~ted/content-hub/ual2/+merge/19821009:28
didrocksdone09:29
Mirvsil2100: I can also run all of the upstart-app-launch tests if you have other stuff to do, since I'm relatively far already09:38
sil2100Mirv: my device is free right now, so if there are some big tests that you still didn't run, I can pick those up09:39
popeydidrocks: FOUND IT!09:40
popeyhttps://bugs.launchpad.net/unity-mir/+bug/123453809:40
ubot5Ubuntu bug 1234538 in unity8 (Ubuntu) "With Mir enabled - Applications randomly failed to start" [High,Confirmed]09:40
didrockspopey: ok, sounds like the same bug that is getting to be fixed by upstart-app-launch, let's cross fingers :)09:40
Mirvsil2100: well click tests are todo, there are some slow ones there.. dropping_letters_app ubuntu_rssreader_app calendar_app music_app ubuntu_terminal_app ubuntu_clock_app ubuntu_calculator_app ubuntu_weather_app ubuntu_filemanager_app ?09:40
MirvI'm running unity8 + webbrowser, they're quite slow09:40
popeybug 1243665 also related09:40
ubot5bug 1243665 in qtubuntu "qmlscene crashed with SIGABRT in QMessageLogger::fatal()" [Critical,Confirmed] https://launchpad.net/bugs/124366509:40
popeyso yeah09:41
popeyhope so09:41
Mirvall others run so far09:41
sil2100Mirv: ok, then I'll prepare for some click-package testing to make things move faster09:41
Mirvupdating landing plan as I go09:43
sil2100Mirv: doing the same, working now on calendar-app10:07
sil2100hmmm, many calendar-app failures, re-running to make sure what's up10:14
Mirvsil2100: I've now finished running all except those click tests I listed. so when/if you're happy with your results (compared to the dashboard), feel free to publish10:22
Mirvsil2100: I tend to re-run those single failing tests to see if they work alone10:22
sil2100Mirv: could you run calendar-app tests on your device?10:22
Mirvinstead of rerunning the whole suite over and over10:22
Mirvsil2100: ok, doing in a moment10:22
sil2100Mirv: yes, but here I get 14 failures, that's like almost all tests10:23
sil2100Mirv: all the other tests look good so far10:32
sil2100Mirv: hm, filemanager also resulted with a lot of tests10:33
sil2100Mirv: it looks to me that sometimes it is unable to start the app for testing, resulting with only a white screen instead of the application10:33
sil2100Mirv: do you have the same on your device?10:34
sil2100Re-running the test usually fixes the issue10:34
sil2100Not sure if this can be upstart related?10:35
sil2100didrocks: ^10:35
sil2100The tests are then failing with: "RuntimeError: Could not find autopilot interface for click package 'com.ubuntu.filemanager_filemanager_0.1.1.95' after 10 seconds." and there is a white screen on my device10:36
didrockssil2100: really weird, doesn't sounds like upstart, right?10:40
didrockssil2100: did you try to downgrade?10:40
sil2100didrocks: yes, running the tests with content-hub downgraded, should have results soon10:41
sil2100I mean10:41
sil2100upstart10:41
sil2100....10:41
Mirvsil2100: I got only 2 failures in calendar-app10:45
sil2100Ok...10:46
Mirvsil2100: and no I haven't seen white screen instead of application kind of thing. now running filemanager.10:47
MirvI simply ran phablet-config autopilot --dbus-probe enable + phablet-click-test-setup + phablet-test-run now for these click tests10:47
sil2100Mirv: I see it's unrelated, with downgraded upstart I see the same ;/10:47
sil2100Mirv: I would say, let's release10:48
Mirvsil2100: well I'll run this test still and since everything seems to be fine at here end, I'll release after that?10:49
sil2100Indeed :) Thanks! I wonder what's up with my device, I'll try a reboot and try then10:49
didrocksMirv: did the tests pass?11:05
sil2100Mirv: are we ready with everything now? I guess all other tests went fine here, not counting those times I had to re-run in the white-screen case11:08
Mirvdidrocks: 3 failures, same as #54. so publishing now.11:10
sil2100\o/ upstart-app-launch, content-hub and unity-mir + the url-handler that's in daily-release11:11
sil2100I mean11:11
sil2100url-dispatcher11:11
Mirvdidrocks: or actually, after this http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Misc./job/cu2d-misc-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_upstart-app-launch_0.3+14.04.20131209-0ubuntu1.diff11:11
sil2100Damn, so many typos today...11:11
didrocksMirv: did you check that there is no common files shipped between -1 and -2?11:16
didrocksMirv: I'm afraid the -dev are shipping the same files without replaces:, right?11:17
didrocksoh, nm, there is the replaces11:17
didrocksMirv: +1 then11:17
didrocksMirv: remember that url-handler needs to be uploaded manually11:18
didrocksurl-dispathcer*11:18
sil2100;)11:18
didrocksMirv: still around?11:21
didrockssil2100: in case, can you publish them?11:21
sil2100didrocks: sure, what should I do with url-dispatcher though?11:21
didrocksI think we are already really late to get something promoted tonight11:21
didrockssil2100: I'll upload it11:21
Mirvdidrocks: ok, thanks, but sil2100 is apparently doing it now11:22
sil2100content-hub and unity-mir I publish as well11:23
Mirvsil2100: thanks!11:24
Mirvurl-dishandler11:24
sil2100didrocks: as a formality: http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.2+14.04.20131209-0ubuntu1.diff and http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Services/job/cu2d-services-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_content-hub_0.0+14.04.20131209.1-0ubuntu1.diff ACKed? :)11:24
didrockssil2100: +111:25
sil2100Ok, published, just url-dispatcher left - but I guess didrocks has it covered already11:26
didrocksuploaded11:26
didrockssil2100: I don't see content-hub11:38
sil2100didrocks: oh, hm, stack is red, wait11:41
sil2100Shit11:41
didrockssil2100: can we ensure we look at the stacks when publishing them? ;)11:41
didrocksso that we don't end up in situations where things are not published11:41
didrocks(or looking at -changes)11:41
sil2100but but it rarely ever happens that suddenly cu2d reds our a force publish11:41
sil2100bzr: ERROR: Parent not accessible given base "bzr+ssh://bazaar.launchpad.net/+branch/content-hub/" and relative path "../../../+branch/content-hub/"11:42
didrocksyeah, but better to care rather than being worry11:42
Mirvsil2100: that error is maybe because of the content-hub owner?11:42
didrocksseems like it can't merge back?11:42
sil2100Is it because of my re-targetting branch?11:42
Mirv"The lp-propose command returned an error."11:42
didrocksprobably yeah11:42
sil2100Will a redeploy of the stack help?11:42
didrockssil2100: depends, does the bot and you have access right to the redeploy one?11:43
didrocksretargeted*11:43
sil2100The retargetted one is in ~phablet-team, so it should be fine11:43
didrocksok, so redeploy11:43
didrockswith -U11:43
didrocksnot -US11:43
sil2100didrocks: if I force-publish content-hub from the stack now after the redeployment, it won't force a rebuild of the package, just push the one that's in the PPA now, right?11:46
didrockssil2100: yep11:47
sil2100didrocks: ok, this time it went through11:51
sil2100didrocks: noting down to make sure stacks get published when publishing11:51
didrockssil2100: thanks!11:55
cjwatsonMirv: Could you re-trigger https://code.launchpad.net/~canonical-qt5-edgers/+recipe/ubuntu-keyboard-daily-qt52 ?  I'd like to see how it gets on with the new chroot.12:06
=== MacSlow is now known as MacSlow|lunch
Mirvcjwatson: retriggered... after ~15 reloads (LP timeouts on recipe pages are really bad)12:14
Mirvhttps://code.launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2/+recipebuild/60348112:14
cjwatsonthanks, let's see12:15
sil2100Mirv: oh! You haunted by this as well?12:18
Mirvcjwatson: looks good now!12:19
Mirvsil2100: dejavu... :D12:19
cjwatsonMirv: excellent12:20
cjwatsonso just stupid handling of forced removals of packages in the chroot, not failed :any support at all12:21
Mirvok then. this is at a good time since I'm about to have a lot more recipe builds against Qt 5.2 right now, and others might have been affected as well.12:22
Mirvsil2100: I'd guess your similar issue might be resolved now too12:24
sil2100Mirv: yay, although it's no longer an issue, the guys found a workaround for that12:27
didrockscjwatson: hum, I'm not really sure to understand something in the build-dep wait12:30
didrockshttps://launchpad.net/ubuntu/+source/url-dispatcher/0.1+14.04.20131209.1-0ubuntu1/+build/531756912:30
didrocks-> but rmadison libupstart-app-launch2-dev12:31
didrockssays it's published in -proposed12:31
didrocksI'm sure I'm missing an obvious typo mistake…12:31
cjwatsonit's in universe12:31
didrocksoh right12:31
cjwatsonurl-dispatcher source is in main and can only use binaries in main12:31
* didrocks promotes12:31
didrocksyeah yeah12:31
didrockssorry for the ping12:31
cjwatsonI'll move it12:31
didrocksthanks cjwatson :)12:32
cjwatsonit should auto-retry (eventually)12:32
cjwatsonoh dear, why the new build-dep on liblttng-ust-dev?12:33
didrocksI guess it's a question for tedg once he's around12:33
cjwatsonthat'll need to be made architecture-specific - see "apt-cache showsrc ust | grep ^Architecture"12:34
=== Ursinha-afk is now known as Ursinha
cjwatson(please don't make it [!arm64] - make it a subset of the positive architectures supported by ust instead)12:34
didrocksoh, so we'll have url-dispatcher blocked in proposed I guess?12:35
didrocksas it will be in dep-wait12:36
cjwatsonyes12:37
didrockscjwatson: why not this !arm64 btw?12:39
didrocksbut rather listing explicitely12:39
cjwatsonTwo reasons12:39
cjwatsonFirstly, it's silly not to use the same terms that ust itself does, since the url-dispatcher restriction is a direct consequence of the list of packages supported by ust12:39
cjwatsonSecondly, we'll have another new port shortly which is also not in ust's list12:39
didrockscjwatson: ok, I'll use the same list than for ust (including debian ones then)12:40
didrocksthanks cjwatson12:40
cjwatsonIt should also make it easier to visually spot discrepancies in future12:40
cjwatson(you could put a comment above it in the control file, e.g.)12:40
didrocks(already there ;))12:40
cjwatsonheh, ok12:40
didrocks(uploaded)12:43
didrockscjwatson: in fact, it's upstart-app-launch which deps on ust12:50
didrockscjwatson: so, I just uploaded that one (in addition, to url-dispatcher)12:51
cjwatsonok12:51
didrockswhat's the best way to unblock those in britney once built? I think I need to rebuild all reverse-build-deps of upstart-app-launch12:51
didrocksbut should I keep them as arch: any and we remove the binaries on other archs to help britney?12:51
didrocksor should I list the arch for all of them?12:51
didrockscjwatson: ok, I guess I'm going to list then13:00
cjwatsondidrocks: I don't understand.  Why would we remove them?13:01
cjwatsonConfused.13:01
didrockscjwatson: so, upstart-app-launch is going to dep on a subset of archive it was building against before (so no arm64 for instance) because of ust13:02
didrocksI guess as the list is written in debian/control, britney will let go it through13:02
cjwatsonNo13:02
didrocksah?13:02
cjwatsonWhy can't upstart-app-launch continue to build on arm64, just without ust?13:02
didrocksok, for that, we'll need upstream support I guess then13:03
=== alan_g is now known as alan_g|lunch
didrockswhich is then going to block an image promotion13:03
didrocksI understood you wanted Architecture: <list>13:03
cjwatsonNo, I was expecting Build-Depends: liblttng-ust-dev [list]13:03
cjwatsonBut it's a question.  Is this truly mandatory now or can it have a sensible fallback?13:04
didrockscjwatson: let me look at the code13:04
sil2100The new ust in the archive seems to cause some trouble for us? Or the troublesome part is the upstart dependency here?13:04
cjwatsonupstart-app-launch, not upstart13:04
cjwatsonNothing to do with the new ust either13:04
cjwatsonPlease read the scrollback13:04
sil2100Right, by upstart I mean upstart-app-launch, just was saving up typing time13:05
cjwatsonPlease don't do that :P13:05
sil2100Ok, so the new dep then ;)13:05
cjwatsondidrocks: if it's truly mandatory, adding an explicit architecture list achieves nothing and we should remove the binaries13:05
cjwatsondidrocks: And indeed the changes you uploaded were largely pointless, I'm afraid13:06
didrockscjwatson: it sems to me13:06
cjwatsondidrocks: If you'd given me an opportunity to review the diffs :P13:07
didrockscjwatson: it seems to be mandatory13:07
cjwatsonThen it might as well just dep-wait13:07
didrockscjwatson: well, sorry, I was assuming that britney parsed debian/control to take decisions13:07
cjwatsonAn explicit architecture list is just something that needs to be kept in sync in future13:07
cjwatsonNo, it doesn't, and this is well-documented13:07
cjwatsonhttps://wiki.ubuntu.com/ProposedMigration gives the full list of criteria13:07
didrockscjwatson: yeah, I read the page but didn't read back13:08
cjwatsonI'd actually recommend reverting those changes again if liblttng-ust-dev is mandatory13:08
cjwatsonThey mean that if ust is ported to arm64 in future, url-dispatcher and upstart-app-launch will need changes in sync, while they otherwise wouldn't13:08
didrockscjwatson: agreed, but i'll just prepare that in trunk13:08
didrockswithout re-releasing13:08
didrocksif you don't mind13:08
cjwatsonsure13:08
didrocksok, so, I guess once upstart-app-launch is built, what is needed is:13:08
didrocks* promote the new binaries to main13:09
didrocks(if not done already)13:09
didrocks* removing the arm64 and powerpc?13:09
cjwatsonwhat has powerpc got to do with anything, aside from your vendetta against it? :P13:09
didrocks* doing that removal for all deps of libupstart-app-launch*13:09
cjwatsonust builds on powerpc13:09
didrockscjwatson: sorry, it was too much at the end of the list for my brain to catch it :)13:10
didrocksso yeah, arm64 only13:10
cjwatsonI'm looking through its rdeps13:11
didrockscjwatson: content-hub, url-dispatcher and unity-mir IIRC13:12
cjwatsonugh, painful13:12
cjwatsonI'm not going to rely on memory ...13:12
cjwatsonthere are indicators and such too13:12
didrocksfor ust itself, right13:12
cjwatsonI wish upstream had discussed this with foundations first13:12
didrocksyeah, going to be painful :/13:13
cjwatsonremoving architectures is an annoying thing to do13:13
didrocksagreed13:13
didrockscjwatson: can I help for anything?13:15
cjwatsondon't think so, I'm just chasing the dep chain13:18
didrocksok, revert done in trunks FYI for the arch: list thing13:18
cjwatsondidrocks: there is one thing - I'm going to need to remove unity-greeter-session-broadcast/arm64, but it only has a run-time dependency on upstart-app-launch, not a build-dep13:22
cjwatsondidrocks: so if I remove it it'll just reappear on the next upload13:23
didrockscjwatson: ok, so for this one, I need to change the binary dep to list archs13:23
cjwatsondidrocks: do you think it could have an artificial build-dep on upstart-app-launch instead?  that's usually better than a hardcoded arch list13:23
didrockscjwatson: with a comment, I think that could do it, I'll get you something to review13:24
cjwatsondidrocks: or maybe on a less intrusive binary package13:24
cjwatsondidrocks: libupstart-app-launch2-dev?  shame there's no unversioned -dev package there13:24
cjwatsondidrocks: upstart-app-launch itself is quite heavyweight for a b-d, it depends on click/click-apparmor13:24
didrockscjwatson: yeah, I already had that discussion with tedg, hard to get them agreeing on what we need for a -dev13:25
didrockscjwatson: ok, doing on libupstart-app-launch2-dev13:25
cjwatsonok, thanks13:25
cjwatsonI've removed url-dispatcher and its rdeps13:25
didrocksthanks :)13:25
cjwatsonso I think just upstart-app-launch and unity-greeter-session-broadcast are left13:25
didrocksupstart-app-launch has just been published I guess13:26
didrocks(seeing it in rmadison)13:26
cjwatsonI wasn't waiting for that anyway13:26
cjwatsonsince I'm removing things from trusty, it doesn't matter13:26
didrocksindeed13:26
cjwatsonhopefully systemtap/ust will get ported to arm64 soon - I see there's upstream work in progress on it13:27
didrocksah, excellent, so the consideration to dep on ust will be valid or better to still chat with ted?13:27
cjwatsonit's still a roadblock to new ports; I still think it should be optional13:27
cjwatsonit's a heavyweight and complex piece13:28
cjwatsonwhich is hard to port13:28
didrockscjwatson: ok, I'm noting to talk to ted then13:28
cjwatsonthanks13:28
didrockscjwatson: how about that description? https://code.launchpad.net/~didrocks/unity-greeter-session-broadcast/add-upstart-app-launch-build-dep/+merge/19825913:30
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== alan_g|lunch is now known as alan_g
didrocksok, so seems the only blocker is out of date on arm64: libupstart-app-launch1, libupstart-app-launch1-dev, upstart-app-launch, upstart-app-launch-tools (from 0.3+14.04.20131126-0ubuntu1)14:00
didrocksnot sure if you've done the removal or not already (maybe pending publication, but rmadison says the binaries are still around on arm64 in trusty pocket)14:01
=== MacSlow|lunch is now known as MacSlow
cjwatsondidrocks: r=me (for whatever that's worth)14:28
cjwatsondidrocks: I haven't done the removal, am waiting for unity-greeter-session-broadcast to land14:28
didrockscjwatson: you mean, in trunk or in archive? is that blocking? (we have an image build depending on it)14:29
didrockscjwatson: like, if I land it in trunk, I can ensure that we are going to publish the next version with it (in tonight's landing)14:29
didrocksjust want to get an image build and promoted14:30
cjwatsondidrocks: trunk would be fine14:31
didrockscjwatson: ok, I top-approved14:31
=== gatox_ultra is now known as gatox
didrocksfginther: can you give a kick for https://code.launchpad.net/~didrocks/unity-greeter-session-broadcast/add-upstart-app-launch-build-dep/+merge/198259? image build is depending on that14:48
didrocksah merged :)14:52
didrockscjwatson: ok, so upstart-app-launch binaries and unity-greeter-session-broadcast are the last ones I guess ^14:52
didrocks(should be all good now)14:52
sil2100\o/14:55
cjwatsondidrocks: removed14:57
didrocksthanks cjwatson and sorry for the trouble, I'm watching the transition and may annoy you or lool for an image build (I don't see the button on cdimage yet)14:58
cjwatsonit's on iso.qa, not on cdimage15:00
didrockscjwatson: I'll try to sync up with stgraber asap to know where this tool is15:03
cjwatsondidrocks: http://iso.qa.ubuntu.com, log in15:03
didrocks(done)15:03
cjwatsonshould be usual sso15:03
didrocksI don't see anything15:04
didrocksYou are currently on: Ubuntu ISO Testing15:04
didrocksand then, nothing15:04
cjwatsonthen select "Trusty Daily" on the front page15:04
cjwatsoncheck "Ubuntu Touch armhf", scroll to the bottom, check that it says "Request a rebuild" under "Rebuilds", press "Update rebuild status"15:04
didrocksin the actions, I only have "passed with no bugs", "subscribe", "unsuscribe"15:05
didrocksI logged in checking the touch release team15:05
didrockslet me logout and retry15:05
didrockscjwatson: confirming I don't see any Rebuilds section on http://iso.qa.ubuntu.com/qatracker/milestones/308/builds/58757/testcases15:06
cjwatsontry http://iso.qa.ubuntu.com/qatracker/milestones/308/builds15:08
cjwatsonyou shouldn't actually *click* on Ubuntu Touch armhf15:08
cjwatsonjust check the checkbox beside it15:08
didrockscjwatson: ah ok, yeah, you're right, was just one path to deep15:08
didrockssorry for being so dummy…15:08
=== greyback is now known as greyback|london
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
rsalvetididrocks: how are we in terms of merging/landing new stuff in the archive?16:17
rsalvetididrocks: are we still in a soft freeze to be able to promote an image?16:17
* rsalveti wants to land a new hybris and ofono16:17
didrocksrsalveti: we are in hell :)16:17
didrocksrsalveti: yeah, I just kicked an image build, for the promotion candidate16:18
didrocksrsalveti: I would prefer before we promote it we don't take risks please16:18
didrockswe had enough collisions… :/16:18
rsalvetiok, will get the code in trunk and available in a ppa for now, will ping you again tomorrow then16:19
didrocksrsalveti: let's really cross fingers we can promote this time…16:21
rsalvetiseems it's really easy to reproduce bug 1258655 with latest image16:21
ubot5bug 1258655 in Unity 8 "Abort when blanking/unblanking screen" [High,Triaged] https://launchpad.net/bugs/125865516:21
rsalvetinot sure if we want to fix that first before promoting a new image16:22
rsalvetiit's kind of a blocker for dogfooding imho16:22
rsalvetiI could get unity8 to crash a bunch of times in a row16:22
didrocksrsalveti: last comment from Saviq told it's not a regression compared to latest promoted image16:25
rsalvetididrocks: right, but it seems way easier to reproduce it now16:25
rsalvetiI was using the phone for a few minutes and could make it crash a few times already16:25
rsalvetithe issue was probably there already16:25
didrocksyeah, just easier to trigger hum…16:26
rsalvetibut something changed with latest unity8 that made it easier to be triggered16:26
didrocksrsalveti: I would still be in favor of promoting (if the tests pass), we still have no unity8 fixes for it and have big issues unfixed in current images16:26
didrocksrsalveti: however, putting that one on top of Saviq's team list16:26
didrocksdoes it sound ok for you?16:26
rsalvetididrocks: yeah, can easily trigger that16:57
didrocksrsalveti: ok, let's do that then, promoting but keeping that on top of unity8's team list16:58
rsalvetididrocks: yeah, can easily trigger the bug with r5416:59
didrocksbe more relax on the power button-side! :)16:59
rsalvetiyup, sounds fine17:00
didrocksjoke apart, at least, we'll unleash the flood gate for people to push more updates17:00
rsalvetididrocks: did we fix the lack of video carousel?17:00
didrocksrsalveti: yeah, this one is supposed to be fixed17:00
didrocksI think there is no carousel if you have few videos (as I have)17:01
didrocksbut robru tested with more17:01
rsalvetiand the issue that made us unable to start videos from the lens17:01
didrocks(and this is by design)17:01
rsalvetilet me test :-)17:01
sil2100didrocks: meeting!17:01
didrocksrsalveti: please do retest, yeah ;)17:01
didrockskenvandine: coming?17:01
kenvandinedidrocks, doh! yeah...17:02
rsalvetididrocks: no carousel17:02
didrocksno robru17:02
didrocksrsalveti: and you do have enough videos to get the carousel?17:02
rsalvetibut can at least launch the video now17:02
rsalvetididrocks: well, I always had carousel with 4 videos17:02
didrocksrsalveti: seems it's the official design17:03
didrocksfrom what Saviq told17:03
rsalvetiwhat is the minimum amount of videos needed?17:03
didrocksI can dig back the bug report17:03
didrocksone sec17:03
Saviqdidrocks, 617:03
Saviqrsalveti, ↑17:03
rsalvetihm, interesting, let me try that17:03
Saviqbug #122628817:03
ubot5bug 1226288 in Unity 8 "Carousel should only be used when there's enough items" [Medium,Fix released] https://launchpad.net/bugs/122628817:03
didrocksthanks Saviq!17:03
Laneycan we have notify-osd released please?17:06
didrocksLaney: again a new release?17:07
Laneyhmm?17:07
Laneyis it a problem?17:07
rsalvetiSaviq: yay, working fine :-)17:07
didrocksLaney: just trying to ask for a reason :)17:08
LaneyFixes a double g_source_remove() or two17:09
didrocksLaney: ok, we'll do it17:09
Laneythe autopkgtest fails which blocks migration of some stuff17:10
Laneyactually, let me double check that passes now17:10
didrocksLaney: robru is doing it now17:11
Laneyok17:11
robruLaney, is notify-osd trunk ready for release? or is there an MP i should wait for?17:15
Saviqrsalveti, cool17:15
popeyhm, i tried to install an app on #55 and it download failed17:16
popey[unity-scope-click] - DEBUG: click-scope.vala:176: action started: download_failed17:16
Laneyrobru: it got merged, but just give me 5 minutes to check it fixes the tests17:17
Laneywould be annoying to have to go around again if not17:17
robruLaney, ok17:17
popey2013-12-09 17:14:09,845 - DEBUG - "Fatal error: /home/phablet/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.doflah.realtai_0.1_all.click failed to install.17:17
popeyCannot install /home/phablet/.local/share/ubuntu-download-manager/Downloads/com.ubuntu.developer.doflah.realtai_0.1_all.click: Cannot acquire permission to write to /opt/click.ubuntu.com; either run as root with --user, or use "pkcon install-local" instead17:18
popeydrwxr-xr-x 133 dnsmasq ssh 8192 Dec  2 20:57 click.ubuntu.com17:19
popeywut17:19
=== gatox is now known as gatox_lunch
Laneyrobru: ya, looks good17:22
robruLaney, ok, on it17:22
Laneymerci17:22
sergiusensfginther, do you have a minute to discuss the status of android image builders with jenkins?17:23
fginthersergiusens, sure17:23
sergiusensfginther, bascially need something like the builder for building ubuntu touch as we had before17:25
sergiusensfginther, but to build a different branch from the repo to detect breakages17:26
popeybug 125925317:26
ubot5bug 1259253 in ubuntu-download-manager (Ubuntu) "Application fails to install after downloading #55 mako" [Undecided,New] https://launchpad.net/bugs/125925317:26
fginthersergiusens, what's in the branch?17:27
sergiusensfginther, a git branch17:27
sergiusensfginther, well, a bundle of git repos on a different branch; it's for android17:27
sergiusensfginther, the branch is just a different android version with our patchset on top17:28
fginthersergiusens, don't we already have some jobs that almost do this? is this just a matter of updating them?17:29
fgintherat least the build part17:29
sergiusensfginther, yeah, that was my question; we used to have ubuntu-touch-image (the jenkins job); which had a specific assigned builder17:29
sergiusensfginther, the builders are sort of hardcoded to the job as we don't want to repo sync ~10GB from scratch all the time17:30
fginthersergiusens, so we did retire some of the machines we were using for these jobs17:31
fginthersergiusens, but we should be able to identify replacements and get them setup17:31
sergiusensfginther, sounds good; need a formal request somewhere?17:31
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
fginthersergiusens, yes, please: https://bugs.launchpad.net/ubuntu-ci-services-itself/+filebug17:32
fginthersergiusens, do you have a timeline for when this is needed?17:32
sergiusensfginther, end of year at the most I think; I'll get back to you on that one (or add it to the bug report17:34
fginthersergiusens, thanks17:34
sergiusensthanks to you too :-)17:34
popeysergiusens: why did the uid for clickpkg change? see second comment on https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/125925317:35
ubot5Ubuntu bug 1259253 in ubuntu-download-manager (Ubuntu) "Application fails to install after downloading #55 mako" [Undecided,New]17:35
popeyit will break app apps for anyone upgrading to #5517:35
popeys/apps/upgrades and installs/17:36
robrusil2100, are you tinkering with url-dispatcher? i just saw it has a yellow prepare job; if you're working on it i'll leave it with you; otherwise i can fix it17:39
sergiusenspopey, the clickpkg user is dynamically created on rootfs build17:40
popeyodd that the users have moved about UIDs17:40
popeywe shouldn't let that happen IMO17:41
sergiusenspopey, I guess that's why android uses hardcoded uids17:41
popey17:41
popeyany idea which bit of the toolchain I should move that bug to? It's clearly not ubuntu-download-manager at fault17:41
sergiusenspopey, we were supposed to move away from hard coded UIDs but this system image stuff would need us to rethink some stuff17:42
sergiusenspopey, livecd-rootfs would be my guess; but this could probably be fixed with an update hook for the writable parts17:42
sergiusenscjwatson, any thoughts on clickpkg uid changing across image updates? ^^17:43
cjwatsonsystem image update hook sounds appropriate17:43
cjwatsonI don't want to give it a fixed uid - it's the wrong trend17:43
cjwatsonadduser --system is the right thing to be using here17:44
* popey fettles the description of that bug17:44
cjwatsonand even if I did give it a fixed uid, it'd still be a different one and we'd need to solve the same problem anyway17:44
sergiusensagreed17:44
cjwatsonit's clearly not ubuntu-download-manager, indeed.  loath though I am to care about this, maybe click should be shipping a system-image hook, seeing as it owns the clickpkg user17:49
=== bfiller is now known as bfiller_afk
popeymoved it to livecd-rootfs for now. bug 125925318:00
ubot5bug 1259253 in livecd-rootfs (Ubuntu) "UID changes for clickpkg user breaks app updates/installs" [High,New] https://launchpad.net/bugs/125925318:00
cjwatsonpopey: definitely not18:03
popeyheh18:03
cjwatsonthat's several layers above anything that can do anything about it18:03
popeyknock yourself out ☻18:03
cjwatsonI've moved it to click, but won't get to it today18:04
popeyok, thanks.18:04
=== mhall119 is now known as mhall119|afk
=== gatox_lunch is now known as gatox
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== mhall119|afk is now known as mhall119
=== bfiller_afk is now known as bfiller
rsalvetibfiller: maybe you know already, but the only crash in 55 is from the dialer app: http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/dialer-app-autopilot/21:15
rsalveticyphermox: robru: are we promoting 55?21:15
cyphermoxrsalveti: I don't know, are we?21:16
rsalvetiseems there are still some missing tests for mako21:16
robrursalveti, no idea. i was only working on notify-osd, which is desktop only21:16
cyphermoxwhich?21:16
robrutoday21:16
cyphermoxrsalveti: which? I'm not sure how we'd be involved :)21:16
rsalveticyphermox: probably tomorrow only then, didrocks was taking care of it21:16
cyphermoxok21:16
cyphermoxbesides pushing the button, I guess it's up to QA21:17
rsalvetiyeah21:17
cyphermoxdidrocks didn't mention any manual testing we should have been doing21:17
rsalvetihe wants to promote 55 (iirc), so maybe some more manual testing (dogfooding) with it should be good21:17
bfillerrsalveti: need to get boiko to take a look21:18
cyphermoxhrm21:20
cyphermoxrsalveti: didrocks did mention dogfooding21:20
cyphermoxlet's split what's missing and we can do the testage.21:21
cyphermoxrobru: ^?21:21
popeyrsalveti: i wouldn't promote 55 with bug 125925321:41
ubot5bug 1259253 in click (Ubuntu) "UID changes for clickpkg user breaks app updates/installs" [High,Triaged] https://launchpad.net/bugs/125925321:41
rsalvetioh, crap21:45
popeyrsalveti: Has it been promoted?21:46
rsalvetipopey: no, but I wanted it to be :-)21:47
popeyheh21:47
plarspopey, rsalveti : pity, the automated tests looked so awesome :)21:49
popeyWell maybe once the mythical mir fix lands we'll get a clean green sheet and we can promote that21:50
popey#hopeful21:50
robrucyphermox, yeah I can do some testing. what ya need?21:51
rsalvetiyeah21:52
cyphermoxrobru: perhaps nothing after all21:54
cyphermoxso, what do we do with this image?21:54
Laneyhow do we get adt-britney to notice that there's a new version of notify-osd which passes its autopkgtest?22:14
cyphermoxLaney: good question. I'd usually ask jibel or pitti about this stuff22:18
Laneyok, would rather not force - bugs like this happen fairly regularly so would be good to fix22:22
thomifginther: if we'd like some CI config changes... is the best thing to file a bug? or talk to someone here directly?22:33
fgintherthomi, lets talk about it first22:34
thomifginther: OK, so the first thing is we'd like the full autopilot test suite to be run daily, on amd64 & i386.22:34
thomipretty soon we'll have the test suite so it can be run on a phone as well, but we're not there yet22:35
thomifginther: I imagine it's already being run *somewhere*, it's just not very visible to us at the moment22:36
fgintherthomi, ack, we can get amd64 and phone added w/o too much trouble22:36
thomifginther: maybe leave phone off the list for a while, we're not ready for that22:36
thomibut we need to know where to go to see the results.22:37
thomiand I'll make sure the team knows to look at them22:37
fgintherthomi, right, just trying to convey that i386 isn't something we've been doing for autopilot tests22:37
fgintherthomi, so we have no platform configured for that combination22:37
thomifginther: I see. I guess maybe it's time to drop i386 support?22:37
thomiI see22:37
thomiwell, OK, so lets go with amd64 today, amd64 + phone later22:38
fgintherthomi, ok, we'll make i386 a stretch goal22:38
thomiok :)22:38
thomifginther: the second thing we'd like is for the CI system to block merges that lower the unit test coverage.22:38
thomiI've already worked out what commands are needed to run the tests and produce the XML coverage report, so I can send that to someone if it makes it easier.22:39
thominot sure if it works like this, but if it's easy to make jenkins show the coverage numbers (perhaps a graph) somewhere that would be sweet as well, but if not, as long as we block MPs that regress test coverage we'll be happy :)22:40
fgintherthomi, right. the way we enable coverage for cmake projects isn't going to work here...22:40
thomiyeah22:40
fgintherthomi, if jenkins is aware of code coverage, it can do a trend graph and it has some facilites for failing on coverage metrics22:41
fgintherwill need to review what's easily doable22:41
fgintherthomi, any thing else?22:41
thomiok. Can you get back to me on that when you have some time? number 2 is less urgent than number 1.22:41
thomifginther: also, while I remember, could you please invite nuclearbob to the subunit  & dashboard meeting? (https://www.google.com/calendar/render?eid=aGd1bDJhNjY3OTZlb3V1bmVoaWhjanAybzRfMjAxMzEyMDlUMjEwMDAwWiB0aG9taS5yaWNoYXJkc0BjYW5vbmljYWwuY29t&sf=true&output=xml)22:42
fgintherthomi, will do on both items22:42
thomithanks man, I'll owe you... several :)22:42
fgintherthomi, I'll create a bug in momento22:42
fgintherthomi, can you review https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1259334 and add the details for collecting code coverage?22:53
ubot5Ubuntu bug 1259334 in Ubuntu CI Services "Add autopilot suite and code coverage gating to autopilot MPs" [Undecided,New]22:53
thomifginther: yup, will add the info this afternoon22:53
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -

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