/srv/irclogs.ubuntu.com/2014/03/20/#ubuntu-ci-eng.txt

ToyKeeperrobru: Confirmed, simply rebooting didn't help, but silo 15 fixed the thumbnail issue.  (libthumbnailer0_1.0+14.04.20140319-0ubuntu1_armhf.deb)00:02
robruToyKeeper, oh excellent00:02
robruToyKeeper, can you dogfood a little bit more with silo 15 to make sure it doesn't break anything?00:02
robrui'm testing a different silo right now00:02
ToyKeeperYes, but it probably won't be until a bit later.00:02
robruoh ok00:02
ToyKeeperHmm, my time zone bug seems to be back.00:14
ToyKeeper(basically, Denver is not UTC+1: http://toykeeper.net/tmp/phablet-tz-denver-wrong.png )00:16
ToyKeeper... will continue when I get back later, though.00:16
robrualright, I'm heading out for dinner, will check in after a few hours00:41
imgbot=== trainguard: IMAGE 248 building (started: 20140320-03:05) ===03:04
imgbot=== trainguard: IMAGE 248 DONE (finished: 20140320-04:15) ===04:14
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/248.changes ===04:14
MirvLaney: thank you for publishing qtbase, you were the lander after all. I have a note of proposing that to upstream.04:38
MirvI mean, Debian04:38
didrocksMirv: hey! are you looking at the calendar-app thread on the phone ML? Seems as it's Qt related, you would be the best to understand it06:44
Mirvdidrocks: yes I've been looking. maybe sdk team can also help.06:48
didrocksMirv: that would be sweet!06:49
thostr_can I get a silo for line 6407:52
Mirvthostr_: sure, just a minute07:56
Mirvthostr_: actually not, it's already on line 1507:56
Mirvthe question is whether to release it since it claims to be tested, or how risky it is now that we're almost having a promoted image07:57
sil2100Indeed07:58
Mirvand did the build actually include the exif branch, hmm07:58
Mirvyes, yes it did07:59
thostr_so, what about then adding the fix to line 1507:59
thostr_and rebuilding it07:59
thostr_then we can still decided whether to land or not07:59
Mirvthostr_: it is already there, I just checked  that it was included during the build: http://162.213.34.102/job/landing-015-1-build/20/consoleFull07:59
Mirvthe same branch07:59
thostr_Mirv: ah, ok. then we're good for now08:00
Mirvsil2100: would you have time to double test gallery-app? I'm trying to debug the calendar app problems at the moment on my device.08:01
sil2100thostr_, Mirv: the changes look pretty safe, but I would only land it if someone from our team could double-test it08:01
sil2100Mirv: sure08:01
sil2100Mirv: you're reading my mind!08:01
Mirvthanks :)08:02
sil2100Let me just re-flash08:02
Mirva crasher fix is a crasher fix after all (thumbnailer)08:02
didrocksthostr_: can you cleanup the req you have from line 6 to line 10? seems some can be removed08:09
sil2100thostr_: hmmm, regarding landing 10...08:10
thostr_didrocks: still applicable... some where blocked or waiting on other fixes08:10
sil2100thostr_: landing line 10 I mean08:10
thostr_didrocks: i have been the bottle neck as well...08:11
didrocksthostr_: most of them are ready: no though?08:11
didrocksthostr_: see the comment on line 9 as well08:11
didrocksit's already merged?08:11
sil2100thostr_: the FFe bug you mentioned is not the curent one - that one is from 13.1008:11
sil2100thostr_: url-dispatcher is not in the FFe list from https://bugs.launchpad.net/ubuntu/+bug/128259008:12
ubot5Ubuntu bug 1282590 in Ubuntu "[FFe] standing freeze exception in trusty for Ubuntu Touch-specific packages" [Undecided,Confirmed]08:12
sil2100didrocks: ^ is the old FFe still valid? The one from last cycle that Steve filled in?08:12
sil2100didrocks: or should we only look at the trusty one now?08:12
thostr_didrocks: sil2100: I'll recheck all my landing requests today... need to wait for some for ted/charles though08:14
didrocksthostr_: ok, please do :)08:15
didrockssil2100: no, its not08:15
didrockssil2100: so yeah, we need a new one for trusty08:15
sil2100thostr_: ok :)08:20
Mirvthe calendar-app issue looks complex. I can confirm reverting the last commit fixes the crasher on x86, which was mentioned to be blocking a fix for the autopilot test. I pinged tsd_geos so that he could look at my local backtrace bug #129499508:23
ubot5bug 1294995 in qtdeclarative-opensource-src (Ubuntu) "qmlscene crashed with SIGSEGV in value() when running calendar-app" [Undecided,New] https://launchpad.net/bugs/129499508:23
Mirvthen regarding the flaky test, it hasn't flaked during the last five images at all it seems08:23
Mirvand I remember I didn't get the failure on my tests either08:24
didrocksMirv: I think we may want to follow reverting both?08:34
sil2100Mirv: regarding that landing 15 - I'm starting to test it right now, but I see some of the MRs there are not approved or reviewed even08:35
sil2100I would say we wait for Bill to appear with landing this one08:35
Mirvdidrocks: which both? so https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/revert-212/+merge/211813 seems to fix the x86 crasher balloons mentions to be a blocker for landing fixes for the AP problems in bug #129348908:35
ubot5bug 1293489 in Ubuntu Calendar App "Multiple test failures since move to Qt5.2 #238 on Mako" [Undecided,New] https://launchpad.net/bugs/129348908:35
sil2100I'm not confident in releasing something from merges that don't have a visible review on them, it's state is a bit 'unknown' right now08:36
Mirvsil2100: yeah, even though it's mentioned to be tested the branches should be top-approved08:37
didrocksMirv: there is as well that one: https://code.launchpad.net/~nskaggs/ubuntu-calendar-app/standalone-ap-for-1293489/+merge/21185408:38
didrocksto fix the real AP test issue08:38
Mirvdidrocks: oh, ok, you just said "reverting both" but that other one is refactoring08:39
Mirvbut yes, approving both of them. I should test the autopilot on desktop more with/without branches.08:40
didrocksMirv: ah sorry, yeah, needing both branches :)08:40
sil2100didrocks: so, the flaky messaging-app test fix that boiko did - there is a landing for that but I cannot assign a silo for it as messaging-app is already part of landing-009, which is 'Testing pass' but seems a little bit risky for me08:59
didrockssil2100: please override, add a commit to the other one with the rationale and set testing to no08:59
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: none
sil2100didrocks: ACK08:59
seb128sil2100, http://irclogs.ubuntu.com/2014/03/19/%23ubuntu-release.html#t20:4109:05
seb128sil2100, that's where the url-dispatcher ffe got discussed (you are being overzealous on that one it seems ;-)09:06
* didrocks prefers overzealous than having something to be reproached for :)09:07
seb128I can see that09:07
sil2100seb128: well, I just checked the FFe bug back then and didn't see it ;) Just doing my duties!09:07
seb128sil2100, I had the link to the bug in the comment, it just happens that they are 2 bugs for touch ffe now?09:08
seb128if that one is invalid/from last cycle we should maybe fix released it?09:08
sil2100seb128: yes, one is for last cycle, one is for this cycle09:08
seb128we should close the old one then09:08
sil2100seb128: probably, I already once made the mistake on looking at the wrong one...09:08
seb128to avoid those confusions09:08
didrocksseb128: I'm unsure from the discussion it came to a resolution though09:09
didrocks(seeing your IRC link)09:09
didrocksand yeah, they are not leftover, they were in last cycle one because those weren't in the desktop seed, and they are now09:09
seb128didrocks, I'm based on "slangasekso if we're sure that lib isn't used except on touch, then yeah, that all sounds reasonable"09:10
seb128we don't use url-dispatcher in the indicator to run stuff on desktop09:10
seb128so I think virtually that's not being used09:10
didrocksseb128: I'm just looking at what's pulling it in, one sec09:10
seb128but if you guys want a formal confirmation we need to go back to slangasek09:11
didrocksso, the indicators09:11
seb128didrocks, indicators to call settings mostly I think09:11
didrockspulling liburl-dispatcher109:11
didrocksok09:11
seb128right09:11
didrocksI think if there is no ABI breakage and based to yesterday discussion, that we can +109:11
didrockssil2100: wdyt?09:11
Mirvdidrocks: correction. the revert-212 branch includes the other branch, the other branch alone just isn't enough09:11
didrockson*09:11
didrocksMirv: ok, it's a prereq?09:12
sil2100didrocks: sounds good to me I guess09:12
Mirvdidrocks: no, it's included, the other one is just the "other fixes" but not the revert which is needed to fix the crash09:15
Mirvthen, to fix the actual AP bug two more branches from bug #1293489 are needed09:15
ubot5bug 1293489 in Ubuntu Calendar App "Multiple test failures since move to Qt5.2 #238 on Mako" [Undecided,New] https://launchpad.net/bugs/129348909:15
seb128didrocks,  do you have a "<n> free silo" counter somewhere? looks like it would be useful ;-)09:15
didrocksseb128: for people with the right commit access level, it's possible, but yeah, can do that09:16
didrocksseb128: I'm working on making reconfigure/assignement easier first09:17
didrocksMirv: ok, seems we need to test this whole bundle09:17
seb128didrocks, ok, that would be nice (I keep wondering if stuff are waiting because there are no silo left :p)09:18
sil2100seb128: I'll be assigning silos in a moment ;)09:19
sil2100Was busy testing09:19
seb128sil2100, no hurry, it's just that the topic came back a few days this week09:19
sil2100seb128: well, in overall we're a bit 'stuffed' with things which we either don't want to land before promoting an image or need to test manually and/or need comment from the authors09:20
sil2100So things tend to stretch a bit longer, I hope we'll get a promotable image soon...09:21
seb128sil2100, well, Mirv assigned me silos for my desktop specific entries so I'm happy enough09:21
seb128it feels like l32&33 should be fine as well09:21
seb128one touch the wizard in settings, which is not used09:21
seb128the other one is in a test tool09:21
sil2100All seem safe09:22
didrocksseb128: G109:22
seb128didrocks, thanks!09:23
didrocksyw :)09:23
seb128so we are on top of the normal assignment atm09:23
sil2100seb128: ok, one more silo assigned - but the rest needs to stay free for emergency needs ;)09:24
didrocksyep09:24
seb128sil2100, right, thanks09:24
sil2100I'll test some ready safe-landings in the meantime09:24
sil2100yw09:24
mhr3sil2100, publish 28 pls?09:28
sil2100mhr3: one moment, resolving that one, some doubts09:30
sil2100(and meeting)09:30
didrocksMirv: coming?09:31
MirvI needed to juggle between laptops a bit09:34
ogra_psivaa, doanac seems to only have the phonesim install/remove code to the dialer-app test, but not to the messaging-app one, could we get it there too ? (messaging-app fails with "no phonesim found" on both tablets ... it works on N4 because there is a physical SIM apparently)09:43
ogra_*have added09:43
ogra_(that will get us 16 failures less per tablet :) )09:44
psivaaogra_: 'messaging-app-autopilot' does not look to have it as a dep.. but i'll take a look at this deeper. thanks for looking at it09:47
ogra_psivaa, no, thanks to you :)09:47
sil2100mhr3: testing the landing and publishing - just tell me sincerely: how 'risky' you thing those changes are? ;)09:49
sil2100*think09:49
mhr3sil2100, very low, plus no effect without new-scopes09:50
sil2100mhr3: I love landings like that, thank you for that!09:50
sil2100mhr3: anyway, expect it being published in the nearest minutes, just want to run unity8 tests till the end as a quick double-check09:51
mhr3it really can't affect that, it's all new-scopes only09:51
popeyhmm, phone is plugged into usb, does that prevent deep sleep?09:59
didrocksogra_: ^10:00
* popey starts the song again10:00
popeygetting sick of this song now ㋛10:00
ogra_i think adbd keeps a wakelog in the kernel10:00
popeyok10:00
* popey unplugs10:00
didrocksogra_: wakelock, you meant? (you keep sayig wakelog, so maybe I missed something? :p)10:01
didrockssaying*10:01
ogra_err, not really awake locked here :P10:01
ogra_(indeed i meant wakelock ;) )10:01
sergiusensdidrocks, hey, fyi; last night it seems cjwatson gave me the hint that components landing only for ubuntu touch are covered by the spirit of the original bug/FFe ... the only thing I forgot to ask yesterday was if we should add a comment or edit the description of such bug10:05
didrockssergiusens: hum, I think the description was clear it was about that, (and that's why there is the exact list). It's telling:10:06
didrocksI would like to request a blanket FFe wrt Ubuntu Touch, for those packages that are part of Ubuntu Touch but not part of Ubuntu Desktop10:07
sergiusensdidrocks, oh, I'm not talking about the current list; but about additions to that list10:07
didrockssergiusens: ah, it needs to be acked first, so I guess on comment10:08
didrockssergiusens: and then, we add it to the description10:08
=== vrruiz_ is now known as rvr
didrockssergiusens: maybe in a subsection, mentioning that they are in other seeds, but won't have any backward incompatible breakage/not used really on the desktop10:09
didrocksto make the separation clear10:09
sergiusensdidrocks, yeah, my case is for totally new components like media-hub and push-notifications10:10
didrockssergiusens: oh sure, I guess once it's recorded in the comment that the RT +1 on it, feel free to append at the bottom of the description10:11
sergiusensok, good that we have a process; fwiw media-hub was separately logged and approved already :-P10:11
didrockssergiusens: ah great, so if you want to add to the list, please do (and reference the other bug in a comment)10:12
sil2100didrocks: packaging ACK: http://162.213.34.102/job/landing-005-2-publish/46/artifact/packaging_changes_unity-scopes-shell_0.4.0+14.04.20140320-0ubuntu1.diff <- looks sane10:15
didrockssil2100: +110:16
cjwatsonsergiusens: I think it's appropriate to ask, just saying that from the point of view of the release team it probably means we normally don't need to think *too* hard10:24
sergiusenssounds good, thanks10:28
sil2100dbarth_: hi, wanted to ask some questions regarding landing line 1210:44
seb128sil2100, ok, I freed some silos, you are back to 4 ;-)10:56
dbarth_sil2100: go ahead10:57
dbarth_sil2100: it's good to go; i was just checking and sounds like robru didn't land it10:58
dbarth_sil2100: tests pass, we verified that with alex_abreu yesterday; can you press publish?10:59
dbarth_sil2100: then i can merge and clean that silo10:59
sergiusensMirv, can you look at silo 1? it should be low risk fwiw; but land after promoting if you want10:59
sil2100dbarth_: I just wanted to double check if all is ok from the phone side, but it seems ok11:05
sil2100dbarth_: how would you assess the risk factor of this landing?11:05
sil2100seb128: thanks! I noticed already earlier, that's why I assigned an additional silo for you ;)11:07
seb128sil2100, thanks ;-)11:07
dbarth_sil2100: limited, it changes JS code used by the html5 stack; only html5 app developers would be affected if there is a regression we haven't seen11:12
davmor2popey: didrocks: Stairway to heaven 8:02 played from start to finish no issues11:12
popeydavmor2: while plugged in or not?11:12
davmor2popey: not I was downstairs11:13
popeyhm, okay11:13
popeyhow odd11:13
sil2100dbarth_: publishing!11:13
davmor2didrocks: also I've replied to the phone list11:13
dbarth_sil2100: ok11:14
davmor2morning all11:16
Mirvsergiusens: you're correct that it looks safe since it only adds a plugin not touching other things. that said, it wouldn't hurt to have the promotion happening either11:16
Mirvsergiusens: the docs branch is not top-approved11:16
sergiusensMirv, right; the top approving is really necessary these days?11:21
Mirvsil2100: ^11:21
Mirvsergiusens: I don't know, asking from the more experienced train mover :)11:21
davmor2popey: just played it again to prove it wasn't a fluke still not plugged in11:22
sil2100sergiusens, Mirv: it's nice to have, but it's not necessary - as long as we see there is someone from upstream doing any approval for the newest and latest of the commit11:22
sil2100*commits11:22
Mirvsil2100: yeah, so some approval is enough. ok.11:22
Mirvsil2100: would you mind looking too if https://code.launchpad.net/~diegosarmentero/ubuntu-download-manager/udm-qml-plugin/+merge/209573 seems safe to you? it only adds stuff so that's why it'd seem to me it's safe to publish.11:23
sil2100Mirv: u-d-m! Oh noes! Let me check11:23
Mirvsil2100: yeah, I've some memories of u-d-m breaking earlier, that's why it feels like it's useful to be extra sure :)11:23
sil2100Mirv: I think you're right - it seems really nice and safe, only adding the plugin - is it tested in a silo already? :)11:25
sergiusensMirv, fwiw; we landed u-d-m 2 times this week already11:25
Mirvsil2100: yes, it's tested. there's another MP that claims to be docs only but I see slight weird differences there otherwise too: https://code.launchpad.net/~mandel/ubuntu-download-manager/documentation/+merge/20966411:26
Mirvsergiusens: why there's a registerMetaType() function removed in the docs commit?11:26
mandelMirv, let me double check, but it is mainly docs and I did the test plans for udm, click scope and system image updates11:26
Mirvand there are consts added, and &:s moved around11:26
Mirvmandel: ok, just pointing out since it claims to be about documentation but has some other slight changes11:27
mandelMirv, the function call was removed because it was never used and makes no sense11:27
mandelMirv, const were added but are just for internal objects in the priv lib11:27
mandelMirv, I can link bugs about that to document it, no problem11:28
Mirvmandel: it'd be enough if the MP commit / description would state that some function and some constructors were removed and consts:s added, in addition to docs changes11:28
Mirvwell and of course if there are already bugs open, those are welcome too to be linked11:29
mandelMirv, there are no bugs added, no, but I'll update the commit msg, does that sound good?11:29
Mirvs/constructors/destructors/11:29
Mirvmandel: sounds good11:29
Mirvother than the group_download_struct.cpp changes it's quite clear11:30
popeydavmor2: bug 1295086  if you can reproduce pls..11:30
ubot5bug 1295086 in mtp (Ubuntu) "Content doesn't refresh when viewed in desktop file manager" [Undecided,New] https://launchpad.net/bugs/129508611:30
popeyseen it for ages, only just got round to filing it11:30
mandelMirv, MR updated11:31
Mirvmandel: thanks11:31
mandelMirv, no proble, sorry for that I did it without thinking it was very important :-/11:32
Mirvdidrocks: I'd need packaging ack for http://162.213.34.102/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.3+14.04.20140319.1-0ubuntu1.diff - seems good, unless all plugins are wanted to be forced to be of the form qtdeclarative5-[packagename][version]. I'd allow that, but I'm not sure how strict our policy is. that current version sounds better than qtdeclarative5-ubuntu-download-manager0.111:33
mandelMirv, we can ping gatox about that11:34
Mirvmandel: you just did :)11:34
mandelMirv, I think is better to follow the norm if possible11:35
mandelMirv, awesome, then I'll let you guys decided about qml, is out of my area :)11:35
gatoxmandel, if it's about naming, i think it shold follow the convention11:35
Mirvmandel: gatox: yeah, I don't see too many deviations from that norm, so possibly qtdeclarative5-ubuntu-download-manager0.1 should be used11:35
Mirvok, commenting on the MR then11:35
Mirvdidrocks: unping11:35
mandelgatox, please, can you update that? I think with that change we can land the qml so that the browsers guys can start looking into it11:36
sil2100;)11:36
Mirvcommented, also mentioning the version-specific install directory which we are implementing quite poorly in general but that was the proposed policy and makes sense11:38
Mirvworking unping would actually be useful11:38
gatoxmandel, updated11:39
mandelMirv, didrocks ^^11:39
mandelgatox, sweet, thx11:39
Mirvmandel: gatox: then the version specific install directory too, please11:39
Mirvso eg. UbuntuDownloadManager.0.1, so that when you'll have 0.2 the new package can be co-installed11:40
gatoxmandel, Mirv version added to the install folder11:41
Mirvit might need a bit more tweaking in the .pro files11:41
gatoxMirv, how's that?11:42
Mirvgatox: the make install obviously needs to install to that directory too11:42
Mirvit could be tricked with packaging maybe too, though, but that'd need creating directory manually and moving files or such11:42
Mirvfriends has something like http://bazaar.launchpad.net/~super-friends/qml-friends/trunk/view/head:/modules/Friends/Friends.pro11:43
Mirvso modifying installPath11:43
davmor2popey: I get the same even if I hit reload I think it is an issue in mtp infrastructure and instantly blame ogra_ ;)  can you see if the same thing happens on your iphone?11:45
davmor2popey: ie if it is mtp at fault or just our implementation of it11:45
davmor2popey: oh by the way were you able to replicate the issue I found with contacts/dialer app?11:46
gatoxMirv, mandel .pro updated11:48
Mirvmandel: ok, kick a rebuild?11:51
Saviqdidrocks, just thought of a relatively simple thing that could be helpful if possible - updating the PPA description with some data like the description of the landing, list of included MPs and such11:51
mandelMirv, sure11:51
davmor2popey: confirmed and commented11:52
popeydavmor2: thanks, also.. can you test alarms? They're not going off for me11:59
davmor2popey: and confirmed it works correctly on android so it is just our implementation of mtp11:59
davmor2popey: in which case I definitely blame ogra_  :D11:59
davmor2popey: alarm set for 5 minutes past12:01
davmor2popey: should they go off with the phone screen blank?12:02
davmor2popey: or is that still not implemented yet?12:02
=== cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: -
popeydavmor2: even with the screen on12:03
popeyit should ring.12:04
davmor2popey: okay, did you look at this in the end https://bugs.launchpad.net/bugs/129471012:05
ubot5Ubuntu bug 1294710 in dialer-app (Ubuntu) "Call log view contact flashes the contact details then goes to the normal list" [Undecided,New]12:05
davmor2popey: ringing with screen on and the clock app closed12:05
popeydavmor2: no, i have no contacts on my phone12:05
davmor2popey: right trying again now with the screen off12:06
davmor2popey: do you have like a 150 number to check your balance that is free to call?12:08
popeyi have lots of numbers i can call for free, I just have no contacts on my device so will need to set them up to try it, not got round to it thats all12:09
davmor2popey: ah okay cool :)12:10
davmor2popey: Huston I think we have a problem12:10
didrocksSaviq: that's a good idea. I have other things I want to do first, but if you open a bug, I'll do that after the bot :p12:10
Saviqdidrocks, ;D12:11
davmor2popey: with the screen on I got an alarm, with the screen off I don't and looking at the device it seem that the clock got stopped when the alarm should of gone off12:11
popeydavmor2: tried your bug, can't reproduce, contact appears12:11
popeydavmor2: clock doesn't trigger alarms, indicator-datetime does12:12
davmor2popey: yeah the time in the indicator is stuck when the alarm should of gone off12:12
Saviqdidrocks, bug #129509612:13
ubot5bug 1295096 in Canonical Upstream To Distro "Description of silo PPAs should be updated with some relevant info" [Wishlist,New] https://launchpad.net/bugs/129509612:13
davmor2popey: can you edit an alarm twice and have it update correctly?12:14
* popey tries12:15
popeydavmor2: when i try to edit an alarm I get this... http://popey.com/~alan/phablet/device-2014-03-20-121531.png12:15
sil2100boiko: hello! Your messaging-app is in silo 01412:16
davmor2right so I've set an alarm now for 18 minutes past I'll let the phone sleep and I'm betting at 19 minutes past the clock will still say it is 18 minutes past12:16
didrocksSaviq: thanks :)12:16
popeydavmor2: also, clock crashes when you delete an alarm12:17
popey[Thu Mar 20 12:07:55 2014] type=1400 audit(1395317761.205:493): apparmor="DENIED" operation="mknod" parent=1928 profile="com.ubuntu.clock_clock_1.0.373" name="/home/phablet/.config/com.ubuntu.clock_clock_1.0.373.conf.L21550" pid=21550 comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=3201112:17
davmor2popey:  oh I don't get that what happened for me is the last alarm was at 12:08 I changed it to 12:15 hit save and it still showed 12:0812:17
boikosil2100: thanks, let me build that12:17
didrocksdavmor2: popey: IIRC, alarms were not triggered already in previous promoted image, right?12:17
davmor2popey: it just deletes them here12:17
popeydidrocks: lemme try12:18
boikosil2100: oh, they are already built, nice12:18
sil2100boiko: I already pressed build to speed things up if anything ;)12:18
* didrocks has never seen that working12:18
boikosil2100: nice! thanks12:18
popeydidrocks: having two phones means i find it hard to remember what works where ☻12:18
* sil2100 wants this fix badly ;)12:18
davmor2didrocks: iirc it did if the phone was awake but not when it was asleep12:18
didrockspopey: ETOOMANYPHONES!12:18
didrocksdavmor2: hum12:18
popeyyou're right12:18
davmor2didrocks: which is what I am seeing now12:19
didrockson arlams or on the too many phones? :p12:19
popeydidrocks: bad news!12:20
davmor2popey: it looks like the alarm just went off and now won't stop so 2 minutes late and the clock says 12:1812:20
popeyalarm just went off on my stable phone!12:20
davmor2didrocks: ^12:21
didrockshum12:21
didrocksgrrr, ok :(12:21
didrocksnot sure what our tests, there are alarms tests12:21
davmor2just had to reboot the phone to stop the alarm12:21
didrockspopey: davmor2: so I guess it's alarm testing time…12:21
davmor2didrocks: now I know it works I will I wasn't adding it till it did though there was no point :)12:22
didrocksso, the question is… is it a blocker in your opinon?12:23
davmor2popey: Column AD does the description make sense?12:24
didrocksdavmor2: popey: so on latest promoted image, it was only working if the screen wasn't blank?12:25
popeywait 2 mins for my alarm12:26
davmor2popey: ^  does it work with the screen blank as well as active?12:26
* popey taps power button12:26
* popey waits12:26
didrocksdavmor2: IMHO, if didn't work with a blank screen ~= non functional for me12:26
popeyalarm rings when screen is blank12:27
didrocksok, and so, not on latest image, right?12:28
popeyon current build number: 23712:28
didrocksaah12:28
didrocksbut?12:28
didrocksyou didn't say the contrary12:28
* didrocks is lost12:28
popeyso, in summary:-12:28
didrocksah, #237, so latest promoted12:28
popeyYou asserted that the alarms never worked on a promoted image. I'm saying they did. When blanked.12:28
didrocksok12:28
popeydpm just heard it via a hangout :D12:29
didrocksso, we need to bisect12:29
dpmhahaha12:29
popeylet me test again on latest image12:29
didrocksyep12:29
popeynote though that I see a lot of this...12:29
popey[Thu Mar 20 12:07:56 2014] type=1400 audit(1395317761.205:493): apparmor="DENIED" operation="mknod" parent=1928 profile="com.ubuntu.clock_clock_1.0.373" name="/home/phablet/.config/com.ubuntu.clock_clock_1.0.373.conf.L21550" pid=21550 comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=3201112:29
popeyon the latest promoted image12:29
didrocksjdstrand: ^12:29
popeygnnnn12:30
sergiusenspopey, make sure alarms work on flo which doesn't have the wakeloc problem12:30
popeylatest non-promoted image12:30
popeyffs12:30
sil2100;/12:30
didrockssil2100: so, continue to not publish anything risky :p12:30
popeybah. clock crashes on alarm save12:31
sil2100I hate news like this! I want to publish everything as it goes already ;p !12:31
didrockssil2100: well, even once we promote, we need to ramp up publication12:31
didrockssil2100: and cut images regularly12:31
davmor2popey: on current when the alarm goes off does it wake the screen in the same way a call would?12:31
popeyno12:31
popeyjust rings12:31
popeyright, cleared out all alarms and created a new one12:32
popeyno errors in dmesg, no crash12:32
sil2100didrocks: indeed12:32
* popey hits power and waits 2 mins12:32
davmor2popey: okay that's odd are you leaving the clock app open?12:33
jdstranddidrocks, popey: that is bug #128874212:34
ubot5bug 1288742 in ubuntu-ui-toolkit (Ubuntu) "clock app using incorrect path for config file" [High,In progress] https://launchpad.net/bugs/128874212:34
popeythanks jdstrand12:35
jdstrandnp12:35
davmor2popey: last alarm didn't go off but the clock app was open, trying again now with the clock app closed12:35
popeydidrocks: alarm didnt ring on latest unpromoted12:35
popeyaha!12:36
popeyit displays but doesn't ring!12:36
popeybut if the display is off, obviously you can't see it12:36
didrocksjdstrand: argh, so it was known?12:36
jdstrandyes, I filed it weeks ago12:36
didrocksjdstrand: but I guess you didn't know it was preventing the alarm going off12:36
didrockssil2100: Mirv: can we try to land that with bzoltan's help?12:37
jdstrandand reported it on the list when I examined new denials12:37
jdstranddidrocks: actually, I think I said as much-- ie, that the app wouldn't work right. I told Pat about it. looking at the bug there is an MP12:37
popeydidrocks: davmor2 http://popey.com/~alan/phablet/device-2014-03-20-123802.png12:38
popeythats latest unpromoted, the alarm _does_ trigger, but no ring12:38
jdstrand(ie, I told Pat, Pat escalated it, there is an MP)12:38
didrocksjdstrand: ok :( sad that Pat didn't report the info12:38
jdstrandwell, I did12:38
* jdstrand finds the thread12:39
Mirvdidrocks: sil2100: with bzoltan's help, yes12:39
Mirvbzoltan: can you check https://bugs.launchpad.net/ubuntu-clock-app/+bug/1288742 and add a line for that MP only?12:39
ubot5Ubuntu bug 1288742 in ubuntu-ui-toolkit (Ubuntu) "clock app using incorrect path for config file" [High,In progress]12:39
didrocksMirv: I guess if bzoltan isn't aroud, we have to land and test ourself ASAP12:40
davmor2didrocks, jdstrand: so till this is fixed are we saying that alarms should be flakey then?12:40
didrocksjdstrand: on the ML == on the Qt 5.2 discussion? it wasn't raised as a blocker (not meaning by you, but when I asked for remaining bugs)12:40
jdstrandactually, I didn't mention that bug in the thread I was thinking of, cause I had already reported it and it was escalated12:40
Mirvdidrocks: ok, adding line12:40
sil2100Mirv: ok12:40
popeydidrocks: davmor2 i believe the issue jdstrand is talking about is separate from the alarm sounding.12:40
didrocksMirv: and build and so on :)12:41
sil2100Mirv: need some help with testing?12:41
didrockssil2100: can you help on the testing ^12:41
* jdstrand doesn't actually know the impact of the bug12:41
popeythe alarm saves, and we get the DENial, but when the alarm time comes, it _does_ trigger, just makes no noise.12:41
didrocksjdstrand: do you think it can impact the current bug we are talking about?12:41
jdstrandI just assume that things won't work right cause it can't write out its .conf file12:41
sil2100didrocks, Mirv: just in case poke me once the packages are built and I'll perform the testing as well12:41
jdstrandI have no idea. All I reported is what I saw in the log12:41
asacdidrocks: whowever owns this MP should have pusehd for landing it12:41
asacdidrocks: who owns the MP?12:41
davmor2popey: how are you taking screenshots now?12:42
jdstrandthis isn't a new bug though12:42
popeydavmor2: magic12:42
popeydavmor2: http://paste.ubuntu.com/7125032/12:42
didrocksasac: we are still unsure it's going to fix it though, seems we just know apparmor denies something12:42
didrocksasac: you have the bug link, I'm like you, just discovering it12:42
didrocksand I wasn't on those meeting nor coordinating the landing12:42
jdstrandI reported it on the 6th. if they were working and now don't, it is unlikely due to only this bug12:43
asacdidrocks: just saying that pat seeded the priority somewhere and that somewhere probably failed to continue talking to us12:43
didrocksasac: the MP is https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/statesaver-discard-shutdown/+merge/20504212:43
asacbzoltan: ^^ can you check why this wasn't pushed for landing yet?12:44
asacif thats not right etc.12:44
asacthanks12:44
didrocksasac: we are trying/testing ourselves for now12:44
jdstrandbut it is easy to test: update /var/lib/apparmor/profiles/click_com.ubuntu.clock_clock_* to have 'owner @{HOME}/.config/com.ubuntu.clock.conf* rw,', then run sudo apparmor_parser -r /var/lib/apparmor/profiles/click_com.ubuntu.clock_clock_*12:44
didrocksas it seems bzoltan isn't around12:44
didrockspopey: can you try that? and then try the alarm again? ^12:44
asacok asked zsombi as well what he remembers12:44
asacin -touch12:44
popeysure thing didrocks12:45
didrocksjust to see if this is a side-effect (no nose made)12:45
didrocksthanks popey12:45
ogra_davmor2, you blame me for what exactly ?12:46
ogra_(seems part of your conversation got lost in my disconnect)12:46
popeyogra_: probably for the best ☻12:47
MirvI'm trying to get zsombi here to discuss..12:48
ogra_heh12:48
popeyjdstrand: any particular place in that file?12:48
popeyinside the "profile" stanza I guess?12:48
jdstrandpopey: just within the {}12:48
davmor2ogra_: mtp on the phone doesn't update on the fly.  If you add a file via nautilus to Videos, say.  It shows in Nautilus and on the phone.  If you remove it via adb shell rm /home/phablet/Videos/*  it still shows in nautilus even if you remount the device or reload nautilus12:48
popeykk12:48
davmor2ogra_: tried it on android and it removed the file immediately12:49
boikosil2100: I have just finished testing landing-014, it is ready to go12:49
ogra_davmor2, blame nautilus :P12:49
MirvUITK building at https://launchpad.net/~ci-train-ppa-service/+archive/landing-008/+packages12:49
davmor2ogra_: no tis mtp honest let me try one more thing though12:49
ogra_well, file a bug, did that ever work ?12:50
popeyogra_: no12:50
ogra_ah12:50
popeyits always been like this12:50
popeyi did file a bug ☻12:50
davmor2ogra_: there is a bug12:50
popeyStep 1: File a bug.12:50
popeyStep 2: berate ogra_12:50
ogra_davmor2, cyphermox owns the daemon, i guess it needs to learn about inotify12:51
MirvI still didn't get zsombi here, but t1mp is here for your UITK questions at least :)12:51
mandelMirv, sil2100 the silo 01 has been rebuilt, can you please take a look12:51
mandel??12:51
didrocksMirv: read #ubuntu-touch12:51
Mirvdidrocks: ah!12:51
davmor2ogra_: yes but if we pick on you it magically gets fixed that's the way it always works ;)12:52
davmor2popey: there you go assign the bug to cyphermox :)12:53
Mirvmandel: the binary looks good to me now in the PPA! could do just a quick testing and mark it then to be tested again (I marked it "no" earlier)?12:53
mandelMirv, sure, I'll do a second run of the tests (including system image updates && click scope12:53
sil2100boiko: excellent! I'll publish it after quickly grabbing something to eat12:53
Mirvit's useful to test the plugin still works actually etc12:53
Mirvmandel: excellent!12:54
sil2100Mirv: I'll grab some food right now, if you can ping me once packages are ready for testing I would be grateful :)12:54
sil2100I'll be around the PC all the time12:54
mandelMirv, will do a schroot test for the plugin since I have no app that uses it12:54
boikosil2100: nice! any ETA on when general landing is going to be allowed again? we have been blocked on landing for quite some time now12:54
popeyjdstrand: sudo apparmor_parser -r is taking quite some time but I see nothing eating cpu12:55
Mirvsil2100: sure I'll do12:55
sil2100Mirv: thanks!12:55
sil2100boiko: we hoped to have things unblocked today, but we'll see...12:56
jdstrandpopey: that is weird. can you just tap the Enter key? it shouldn't take more than a couple seconds12:56
popeyyeah, did that12:56
popeyWarning from stdin (line 1): apparmor_parser: cannot use or update cache, disable, or force-complain via stdin12:56
popeygot that when i started it12:56
* popey checks he didnt mess the file up12:56
jdstrandpopey: can you paste your full command and the contents of the file?12:57
davmor2ogra_: on a plus side I've not found the bug that blocks the build from being promoted it's all popey's fault today :D12:57
popeyjdstrand: sure12:57
ogra_davmor2, yeah, agreed :)12:57
popeyjdstrand: http://paste.ubuntu.com/7125093/12:57
popeyroot@ubuntu-phablet:/var/lib/apparmor/profiles# sudo -u phablet -i12:58
popeyphablet@ubuntu-phablet:~$ sudo apparmor_parser -r12:58
sil2100boiko: in the meantime, I'm double testing that landing and then publishing12:58
popeythen the warning and ... Time passes...12:58
=== alan_g is now known as alan_g|lunch
boikosil2100: we didn't even finished flushing the pile of MRs we had since the qt5.2 switching, it is getting complicated :/12:58
didrocksjdstrand: sil2100: Mirv: reading #ubuntu-touch, doesn't seem so clear it's related to that12:59
jdstrandpopey: the file parses fine. can you paste the command you are running?13:00
MirvI'm confused at least, but it's worth a shot upgrading and seeing if it affects the found bug13:00
popeyjdstrand: see above13:00
popeyjdstrand: my bad, missed a parameter. what a putz13:01
popeysorry13:01
jdstrandpopey: ah! it is sudo apparmor_parser -r <path to profile>13:01
popeyok, works now13:01
jdstrandcool13:01
* popey reboots to set an alarm13:01
sil2100Mirv: +113:03
popeyjdstrand: ok, the apparmor denials go away13:04
jdstrandk, so now you can rule out apparmor definitively if the bug is still there13:04
popeyok. so now... it's different13:07
sil2100didrocks, boiko: messaging-app looks nice, publiishing13:08
boikosil2100: thanks13:08
didrockssil2100: hum, is it sane?13:09
didrockswith the current regressions we have?13:09
didrockssil2100: or is it the fix for the flaky test?13:09
boikodidrocks: fix for the flaky test13:09
didrocksok13:09
didrocksthanks boiko :)13:09
sil2100didrocks: fix for tests ;)13:09
boikonp13:09
* boiko is just hoping to get unblocked soon to land more stuff :)13:10
didrocksboiko: well, seems there is yetanotherregression13:10
didrocksso it all depends on anyone's help13:10
Mirvsil2100: ppa:ci-train-ppa-service/landing-008 has the new UITK now13:18
Mirv(published)13:18
sil2100Mirv: thanks! Upgrading :)13:21
didrocksMirv: sil2100: so, seems we can drop it13:22
sil2100...oook13:22
sil2100;)13:22
Mirvdidrocks: I'm just testing if magic happens13:22
didrocksyeah, let's see13:22
Mirv"it shouldn't work!"13:22
didrocksbut based on the feedback13:23
didrocksI'm not hopeful13:23
Mirver, um, somehow I got the alarm ringing even though my screen was blanked13:23
sil2100uh13:24
sil2100Let me try then13:24
Mirvmaybe I didn't do everything the same way, I among else removed the earlier one and added new one13:24
ogra_davmor2, i'm hitting the same bug with the UI being unresponsive for a whille here ... seems apport is running when that happens13:26
ogra_(eating 95% CPU)13:26
Mirvsil2100: ok, now I got the "usual" behavior, ie same as before upgrade13:27
davmor2ogra_: when you wake the device from a sleep right?13:27
Mirvso nothing sounds, but when I turn on the screen after some time I see the visual alarm is there13:27
ogra_davmor2, yes, just wanted to upgrade it after i hadnt touched it for two days13:27
davmor2ogra_: and then it works fine afterwards right?13:28
ogra_yes, but i just noticed i'm 10 versions behind (238)13:28
sil2100Mirv: rebooting my device to make sure and testing to see if I have the same13:28
ogra_so probably not relevant for what you are seeing13:28
davmor2ogra_: no I've hit it on and off for a little bit so it could be I'd not seen it for a few days so threw me when I got hit by it again this morning, let me see if there is a crash file13:29
ogra_well, it was definitealy apport eating the device for me here13:30
didrocksdavmor2: mind checking with Mirv? ^13:30
didrocksMirv: before you update or after?13:30
davmor2ogra_: _usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash13:30
ogra_i see a unity8 and system-settings one here13:31
didrocksMirv: so, it fixes it for you?13:31
didrocksif I read correctly?13:31
Mirvdidrocks: no, it worked once and no again doesn't, so maybe same as davmor213:31
didrocksMirv: ok, maybe try to upgrade then13:31
didrocksadd a new alarm13:32
didrocksand see…13:32
Mirvdidrocks: this is after upgrading, I also tested it before updating13:32
didrocksah ok :(13:32
didrocksso yeah, ditch the silo13:32
Mirvsure, sil2100 will probably soon come up with the same report as well13:32
sil2100Mirv: for now I can't seem to get an alarm working at all!13:32
davmor2Mirv, didrocks: yeah that sounds like what I saw it works sometimes with a delay and doesn't work again properly with the screen off, but with the display active it seems to work13:32
davmor2biab lunch13:33
dobeydidrocks: can we get ddebs support enabled on the silo PPAs please?13:36
didrocksdobey: you do have ddebs support, but they can't be published13:36
didrocksor binary copies don't work then13:37
dobeyhuh? where can i get the dbgsym packages then?13:37
cjwatsonI think they get slurped to ddebs.ubuntu.com in a nasty way13:38
wgrantNasty and not always totally reliable.13:39
cjwatsonyeah, so e.g. https://launchpad.net/~ci-train-ppa-service/+archive/landing-015/+build/5828962 has its ddebs on http://ddebs.ubuntu.com/pool/universe/g/gallery-app/13:39
cjwatsonright13:39
thostr_didrocks: sil2100: how are the chances to promote a Qt 5.2 image today? I'm really want to switch scopes...13:41
dobeyick13:41
sil2100thostr_: well... the alarm and music regressions are a bit troublesome right now13:42
didrocksthostr_: none13:42
popeydavmor2: added a video to your clock bug13:42
didrocksthostr_: but good news is that the alarm regressions is set to your team13:42
didrocksthostr_: so you can help us getting back to green :)13:42
thostr_didrocks: amazing, regressions without changes... will take care of it13:42
thostr_didrocks: so, for scopes, do I have to sacrifice a cow to finally get it in next week?13:43
didrocksthostr_: well, you need even more than a cow :)13:43
didrocksthostr_: the regression is from first day of Qt 5.2 btw13:44
didrocksthostr_: but no test apparently13:44
didrocksso only spotted today13:44
thostr_didrocks: mhhh, ok. but scopes need to land next week... it's getting embarassing slowly13:45
didrocksthostr_: don't you think I am embarassed either?13:45
thostr_didrocks: good point13:46
didrocksthostr_: not sure if you realize how much complains and handling regression is hard13:46
thostr_didrocks: I do believe you13:46
cjwatsondobey: we'll be able to do better once we have the new wonderful expandable librarian, which is blocked on prodstack 413:51
cjwatsondobey: but right now, well, https://lpstats.canonical.com/graphs/LibrarianFreeDiskSpace/13:52
cjwatsondeath in one month13:52
=== alan_g|lunch is now known as alan_g
didrocksthostr_: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122 btw13:58
ubot5Ubuntu bug 1295122 in indicator-datetime (Ubuntu) "Alarms not going off reliably on recent touch images" [Undecided,New]13:58
didrocksthostr_: seems the sdk team says it's charles being the best asset for it13:58
didrocksthostr_: this is one of the blockers13:58
didrocksthostr_: I'm inviting you to the landing meeting as well, as now, all landers having blockers are invited13:58
didrocksso that we can share status and so on13:59
sil2100Mirv: pun intended :D14:05
Mirvsil2100: :)14:08
asacthostr_: on qt5.2 ... help us nail the two/three late coming regressions found that prevent sending this to dogfooders14:12
boikosil2100: looking at the update_excuses file, it is saying that messaging-app has unsatisfiable dependencies on telephony-service and history-service stuff14:13
sil2100Mirv, didrocks: as notes-app is anyway click and trunk is already in our images, I'll publish the silo with notes-app to flush it as a deb package14:13
sil2100boiko: let me see14:13
Mirvsil2100: yeah, thanks, I was meaning to ask about it but then other things rushed forward14:13
sil2100boiko: ah, ok, so it seems we need powerpc and ppc64el in the end14:13
thostr_asac: will take care of the datetime thing14:13
cjwatsonsil2100: oh, I think I started looking at that, let me have another poke14:14
boikosil2100: so, will that land on trusty or do I need to take any action on that?14:14
cjwatsonboiko: ^-14:14
cjwatsonsince I'm blocked on something else right now anyway ...14:14
sil2100cjwatson: thanks! :)14:14
boikocjwatson: thanks14:14
didrockssil2100: yeah, things like that is fine14:14
ogra_asac, thostr_, so we nailed the issue down to "*all* events get queued when suspended" volume changed as well as playing the next song from the playlist (and i suspect also alarms) get queued up as long as the screen is off ... and get applied immediately when we wake up the device14:15
ogra_*volume changes14:15
ogra_didrocks, ^^^14:16
sil2100ogra_: oh14:16
didrocksso it would be -2 issues14:16
didrocks(still 2 to go)14:16
ogra_i think all our bugs have the same source14:16
ogra_(well at least music and alarms)14:16
didrocksogra_: do you think it's due to unity-mir or Qt?14:16
ogra_eirther ...14:17
ogra_or unity814:17
asacSaviq said its MIR, no?14:27
asaci dont even kno whow to stop event loops in qt14:27
asacis that a central feature?14:27
didrocksasac: mir as unity-mir, app lifecycle maybe…14:28
asacif we know how to do that we can find clients that do that and probably get one step closer to the soruce :)14:28
didrocksI wonder if you put your phone off14:28
asacfolks are discussing in #phablet14:28
didrocksand try to call you14:28
didrockspopey: davmor2: do you try that? ^14:28
asacif theory is right, nothing should really work with screen off14:29
asacthough phone all might trigger something else that might make things wake up14:29
sil2100I'll try that as well14:29
popeydidrocks: lemme test14:29
Saviqasac, that was a suspicion, and Mir, not MIR14:29
popeydidrocks: it does ring14:29
sil2100didrocks, popey, asac: so, on my phone it rings14:30
Saviqasac, and we're discussing, might be that Qt queues events when it can't render (and it can't render because buffers are not being swapped)14:30
didrocksSaviq: popey: it's off, like screen blank and low power?14:30
didrockshum sil2100 ^14:30
popeywell, screen off, dunno how to tell low power14:30
sil2100didrocks: yes, I had the screen off for a longer time now, but when I call it lights up and rings14:30
Saviqdidrocks, no, enough to be screen blank and no low power14:30
popeyi press power button14:30
Saviqdidrocks, keeping it active via powerd-cli doesn't help14:30
sil2100didrocks: not sure how long should I wait14:30
didrocksSaviq: so, seems some events are proceeding still, but it's another app14:31
Saviq:'( can we not do this in two channels in parallel?14:31
didrocksok sil210014:31
Saviqsomeone decide #phablet or here14:31
davmor2didrocks: wakes, shows the notification and ringfs14:31
davmor2rings even14:31
didrocksSaviq: not sure why the discussion should be in another than public channel14:31
asacdidrocks: ok... lets give Saviq some time to investigate with his teams ... probably more helpful to not distract them for an hour or two :P14:32
ogra_didrocks, well, it happens in two public and one private channel atm14:32
asaclol14:32
sil2100o_O14:32
Saviq@all: #ubuntu-touch please14:32
asacyep14:32
sil2100Ah crap, it's Thursday again14:33
ogra_can we move all conversation about it to #ubuntu-touch ?14:33
ogra_ah14:33
ogra_Saviq, beats me14:33
sil2100When does Bill appear usually?14:50
ogra_didrocks, wow, the last notes-app changelog looks funny14:51
ogra_(on trusty-changes)14:52
didrocksogra_: how funny? it matches commit messages14:52
didrockshttps://code.launchpad.net/~phablet-team/notes-app/trunk14:52
didrockspeople are using "merge"14:52
ogra_bah14:53
sil2100._.14:53
ogra_couldnt it pull the info about "which branch" in automatically ?14:53
cjwatsonOh.  Suddenly the history-service failure makes more sense - it actually fails to build on all architectures now.14:53
sil2100cjwatson: oh, why now?14:54
cjwatsonmethod signature change in telepathy-qt514:54
cjwatsondiagnosis not helped by (I think) clashing versions between the primary archive and the landing-006 PPA when Qt 5.2 was landing14:54
balloonsdidrocks, so I'm landing the merge for calendar to get a stable build into the store14:55
balloonscan we make the next image?14:55
didrocksballoons: yeah, I guess you tested not any other AP tests failure/regressions?14:55
balloonsdidrocks, it passes on all my devices, my desktop and in jenkins. I feel good about the changes14:56
balloonspopey will still be vetting it as well of course before it lands completely14:56
didrocksballoons: ok, then please, go ahead (anyway popey is retesting)14:56
didrocksyep14:56
didrocksso sounds good14:56
cjwatsonboiko: do you think you could fix the history-service and telephony-service build failures?  they aren't power-specific, should reproduce easily14:58
cjwatsonyou can probably do it a lot quicker than me14:58
cjwatsonboiko,sil2100: The rest of it should consist of landing https://code.launchpad.net/~cjwatson/libusermetrics/valgrind-optional14:59
=== cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: -
sil2100cjwatson: so, the libusermetrics is also one of the things blocking messaging-app, or is it only history-service and libusermetrics is simply one of the leftovers with arch build problems?15:01
cjwatsonsil2100: the former15:02
cjwatsonsil2100: (indirectly)15:02
sil2100boiko: could you ping me once you have a fix for those? We would bundle it up along with the libusermetrics merge in one silo15:02
sil2100bfiller: hi!15:03
bfillersil2100: hi15:05
sil2100bfiller: so, we were looking at landing 14 in the morning and I noticed that some of the merges from the landing do not have any approvals or even reviews15:05
sil2100bfiller: did anyone from upstream look through them code-wise ;) ? Could we at least have some local approvals of those MPs from someone?15:05
bfillersil2100: which landing?15:06
bfillersilo 14?15:06
bfillersil2100: if you're talking about gallery-app line 14, I literally tested all day yesterday these fixes15:07
bfillersil2100: I'll double check the mr's but all should be approved15:07
sil2100bfiller: yes, line 14, silo 15 - if you could just check it code-wise real quick we'll at least have a +1 on that15:08
sil2100didrocks, Mirv: I would like to publish gallery-app and thumbnailer as well - the gallery-app changes anyway should not break anything as gallery is now click (so it will not be visible to the users), and the thumbnailer only fixes a crasher, and the code is safe15:10
didrockssil2100: ok then15:10
sil2100didrocks, Mirv: I already ran all the gallery-app tests in the morning twice and it was +115:10
sil2100(with only the new .deb installed)15:10
sil2100bfiller: if you could give me a quick poke if the MRs code wise are ok and/or approved then I'll publish15:13
bfillersil2100: done15:13
sil2100Fast!15:13
sil2100;)15:13
bfillersil2100: I did this over hte past few days, just did not update the MR's15:13
sil2100Excellent, we just weren't sure, as we knew it was tested but didn't know about the code15:14
bfillersil2100: my mistake, sorry about that15:14
mandelMirv, sil2100 silo 01 looks good as it is15:15
didrockssil2100: remember that tomorrow will be DEFCON0 is we can't promote an image today15:16
didrockssil2100: if you are not going to attend the meeting this evening15:17
sil2100didrocks: http://162.213.34.102/job/landing-015-2-publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67+14.04.20140319-0ubuntu1.diff <- packaging ACK needed!15:19
sil2100didrocks: :<15:19
sil2100mandel: I'll look, but I'm only publishing things that are not risky15:19
sil2100mandel: ah, this!15:20
mandelsil2100, ok, although I'm quite sure is ok15:20
didrockssil2100: +115:20
sil2100mandel: ok, I would say it's good indeed, I'll just take a one-more-look before pressing any buttons15:20
mandelsil2100, great, thx!15:20
bregmasil2100, if you're not busy, could I get a silo assigned to line 39 (Unity7/Compiz bugfixes)?15:21
sil2100mandel: since we're on PHONECON1 right now still15:21
sil2100bregma: ok, if it's only desktop then I would be happy to provide a silo for you ;p15:21
Saviqsil2100, icanhassilo for row 42? it's not in landing state yet, but we wanted to start dogfooding split greeter15:22
Saviq42!15:22
cjwatsonsil2100: ah, it looks like boiko already fixed history-service and telephony-service in the middle of other branches (http://bazaar.launchpad.net/~boiko/telephony-service/conf_call/revision/780, http://bazaar.launchpad.net/~boiko/history-service/fix_filtering/revision/138)15:22
* Saviq will always put his landings in row 42 from now on!15:22
Saviqcan we have a silo -042, too? ;D15:23
cjwatsonboiko: are those changes going to be ready to land soon, or would it perhaps be better to split them out into build-fix-only branches so that we can get them landed today?15:23
sil2100;)15:24
=== alan_g is now known as alan_g|tea
sil2100Saviq: hmmm! I might add you one, just know that you'll be flushed out if we need a fix for unity8!15:24
sil2100bregma: silo ready15:25
bregmawicked, thanks15:25
bfillersil2100: after the gallery-app is published can we get a silo for line 22? I think it should be clear of clashes with other silo's then15:27
bfillersil2100: kenvandine and I itching to get that one tested and landed :)15:27
kenvandineplease!15:27
sil2100bfiller: I'll see what we can do about that ;)15:31
=== alan_g|tea is now known as alan_g
Saviqsil2100, already discussed with didrocks15:33
Saviqsil2100, let's not for now15:33
sil2100Saviq: mhm, a good choice I guess15:34
didrocksSaviq: bfiller: line 22 seems a risky change involving multiple component, right? as we have difficulties to promote an image, not sure15:34
bfillerdidrocks: just asking for a silo to test15:35
bfillerdidrocks: yes many components15:35
=== gatox is now known as gatox_lunch
sil2100bfiller: I didn't assign it till now because it seemed big, and we wanted to first flush out everything else and get a promoted image15:35
bfillersil2100: right, plus it was blocked on the gallery silo15:36
bfiller(and others)15:36
bfillerbut we need a test bed at this point to test all the changes together15:36
didrocksbfiller: please be aware that long-standing silos are the airline model, not ci train (not shaped for that), but if you are ok with your work potentially been flushed out anytime because we are low on silo for things to release, it's ok15:36
didrocksSaviq: we can do that as well, but you'll loose even more work than bfiller's I guess ^15:36
bfillerdidrocks: ok, my hope is it will all work very quickly and can be released in the next image :)15:37
bfillerbut understood15:37
didrocksbfiller: next image == after next promoted image, right? :)15:37
bfilleryup15:37
kenvandinedidrocks, we've been testing from a ppa while waiting for a silo, so hopefully no surprises15:37
didrocksbfiller: ok then15:37
didrockssil2100: mind doing? (with that ocmming)15:37
didrockscomment*15:37
Saviqdidrocks, I don't really think that's a problem for us15:37
didrocksSaviq: to be potentially flushed out?15:37
Saviqdidrocks, it's not like getting a silo is a lot of work15:37
Saviqdidrocks, yeah15:37
Saviqdidrocks, the row in Pending will still be there15:38
didrocksSaviq: yeah, but building Mir in the right order due to ABI breakage is, right?15:38
Saviqdidrocks, sure, assuming there is a breakage, which I don't know yet15:38
didrocksSaviq: well, you'll figure out I guess :)15:38
sil2100didrocks: ok15:38
didrockssil2100: maybe we should do that as well ^15:38
Saviqdidrocks, truth be told once the silo is there I can transition to some other PPA15:39
didrocksassign, be ready to be flushed guys!15:39
Saviqdidrocks, in case we need to flush15:39
didrocksyeah15:39
Saviqdidrocks, I don't expect to rebuild all that often15:39
sil2100didrocks, Saviq, bfiller: I'll mention in the comment for other landers that these silos are candidates for flushing if we're really low on silos if you don't mind ;)15:39
Saviqdidrocks, can we get one for right-edge, too? ;D15:39
didrockssil2100: yeah :)15:39
Saviqsil2100, great15:39
didrocksSaviq: hum… we are really really low, don't push too much :p15:40
didrocks< 3 silos isn't ok15:40
Saviqdidrocks, hence the ;15:40
didrockswe have 4 regression :p15:40
Saviqdidrocks, so 3 is the limit? /me only has 1 atm ;)15:40
didrocksSaviq: no, 3 remaining15:40
Saviqdidrocks, sorry, j/k15:40
Saviqdidrocks, ah15:40
didrockssee cell G1 :p15:41
Saviqdidrocks, really, I don't want to push, just the fact that this thing touches so many projects makes it a chore to do manually15:41
SaviqI mean the split one15:41
Saviqnot right-edge, that can wait15:41
didrocksyeah, let's assign the split15:42
didrockssil2100: ^15:42
sil2100didrocks: sure, I was just reviewing a packaging change, since there's something I don't like15:43
sil2100didrocks: http://162.213.34.102/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.3+14.04.20140320-0ubuntu1.diff <- I don't like how the new qtdeclarative5-ubuntu-download-manager0.1 has a dep on qtdeclarative5-dev, seems invalid15:44
sil2100mandel: ^15:44
mandelgatox_lunch, ^^^15:44
sil2100mandel: do you know why a dev package, qtdeclarative5-dev, is needed to use qtdeclarative5-ubuntu-download-manager0.1 ?15:44
didrockssil2100: yeah, it should be invalid15:45
mandelsil2100, no idea, we need to ask gatox_lunch15:45
sil2100mandel: sorry that 001 is blocked again ;)15:45
mandelsil2100, sure, better to be blocked than sorry, we can ask diego and tell him to fix it15:46
cjwatsonwhat should I do about history-service and telephony-service?  I really want to unblock messaging-app ASAP, the fixes exist but they're in branches with other stuff in them, and boiko seems to be away15:47
cjwatsonshould I cherry-pick them onto fresh branches that just fix the build failures, and get that set into a silo?15:47
cjwatsonor should I wait for boiko to get back?15:48
sil2100cjwatson: I would say that's the right way to go, as we might not be able to land the branches that boiko has prepared anyway, as they might have some other risky changes in them15:48
sil2100didrocks: wdyt? ^15:48
cjwatsonyeah, one is called "conf_call", I don't think it's trivial15:48
sil2100bfiller: I'll prepare a silo for you in the meantime, just remember about the flushing when low on silos until we are promoted again15:50
sil2100bfiller: can I assign a silo or are you modifying the MR list right now?15:52
bfillersil2100: think we're good15:52
sil2100bfiller: you can m&c some silos in the meantime if you have a spare moment ;)15:53
bfillersil2100: sure, looking15:53
bfillersil2100: m+c on two of them. line 14 says needs ack for packaging changes still so I didn't do that one15:55
sil2100bfiller: ah, I'll assign in a moment, as gallery-app still didn't migrate15:56
sil2100bfiller: yeah, mis-click from my side ;/15:56
sil2100It should be merge-and-clickable in a moment15:56
sil2100ETOOMANY15:56
sil2100Saviq, didrocks: unity8 and a few projects are already allocated in different silos16:02
sil2100didrocks: should I ignore-conflicts? Or I shouldn't push that?16:03
didrockswell, don't check with me, but with upstream I guess :)16:05
sil2100didrocks: I didn't want to use this feature 'just like that' without consulting with you, as it's to be used only on priority things ;)16:07
didrockssil2100: if you asssess it's priority…16:07
Saviqdidrocks, you slytherin?16:09
didrocksSaviq: tssssssss16:10
didrocksah maybe :p16:10
Saviqsil2100, I know it probably doesn't work that way16:11
Saviqsil2100, but ideally the projects put into that silo would not get locked16:11
Saviqsil2100, it would be our responsibility to reconcile16:11
boikocjwatson: back16:11
sil2100Saviq: I'll ignore-conflicts, but mention that you'll have to rebuild and retest if the other silos get free16:14
Saviqsil2100, yes, of course16:15
sil2100Saviq: silo assigned, with the proper warning16:19
Saviqsil2100, thanks!16:21
Saviqkgunn, mterry, so we decided there is ABI breakage?16:22
gatox_lunchmandel, sil2100 that seems to be a left over that was to be used to add some ui components to the download manager, but it's not there yet, so removing the dependcy16:22
=== gatox_lunch is now known as gatox
sil2100gatox, mandel: ok, once it's in the branch, please rebuild and we'll retry publishing16:23
* sil2100 prepares for practice16:23
gatoxmandel, sil2100 removed16:23
gatoxand pushed16:23
sil2100gatox: thanks!16:24
psivaaogra_: i've made the jenkins job config change to install/remove the dep. pkges just before/after the tests now after doing a full a mako run. This should fix the messaging app test failures on manta and flo16:57
* ogra_ hugs psivaa 16:57
psivaaogra_: although, it could point that ofono-phonesim-autostart could have some issues when rebooting the phablet devices. not really sure17:00
ogra_we'll see, the test results for messaging can hardly get worse on the tablets :)17:00
psivaaogra_: ack, the latest runs succeeded when we actually install messaging-app-autopilot and run the tests straight away17:01
ogra_perfect !17:01
didrockskgunn: coming?17:02
didrockskgunn: as you have an item for Mir (qt event loop)17:02
kgunndidrocks: not today...i'm double booked17:02
kgunndidrocks: i think you're a little quick on the mir trigger for qt event loop right ?....not convinced mir has a play here...or have i missed more  info ?17:04
didrockskgunn: Saviq: can you update the bug with your infos?17:06
didrocksinfos17:06
didrocksinfo*17:06
didrocksfrom what I know we were waiting on a Mir patch17:07
Saviqdidrocks, am building now17:07
Saviqdidrocks, but that wasn't to fix17:07
Saviqdidrocks, but to test the theory17:07
Saviqdidrocks, I confirmed that the bug is between images 237 and 238, so Qt 5.217:08
Saviqi.e. http://people.canonical.com/~ogra/touch-image-stats/238.changes17:08
=== om26er_ is now known as om26er
imgbot=== trainguard: IMAGE 249 building (started: 20140320-17:15) ===17:14
Saviqdidrocks, q: so if I need no-change rebuilds of stuff due to abi break, what do I do in CI train?17:17
didrocksSaviq: empty MP17:18
Saviqdidrocks, ok, so the "additional source packages" are only for you knowledgeable people?17:18
didrocksSaviq: for direct upload to the ppa17:19
Saviqdidrocks, right, which I can't do, understood!17:19
cyphermoxdidrocks: robru: so, messaging-app is wiating for telephony-service on arm64, powerpc, and ppc64el; which is ftbfs on powerpc and depwait on the others17:21
robrucyphermox, what can we do?17:21
cyphermoxrobru: either 1) unblock it explicitly, which I would like to not do if we can fix the issue, or 2) go through the deps to unbreak stuff17:22
cyphermoxI'm looking into 2, to figure out what needs to be unbroken17:22
cyphermoxso telephony-service needs libusermetrics on arm64 and ppc64el...17:23
robrucyphermox, yeah, i like 2 too, but no clue17:23
cyphermoxand that's depwait waiting for valgrind17:23
robrucyphermox, its depwaits all the way down ;-)17:23
cyphermoxvalgrind just isn't being built for these arches for whatever reason17:24
cyphermoxI did try to start it in sbuild but I don; t remember the result17:24
cyphermoxrobru: didrocks: I'll look at that, if it's worthwhile, but perhaps we should just unblock it for now ^17:25
robrucyphermox, last time i hit this issue, instead of hard-coding arches, I just added a build-dep that was also arch-limited, and then it got unblocked through -proposed17:26
didrockscyphermox: thanks17:26
cyphermoxrobru: ideally we might actually want to try to build everything on all arches, if it's not actually impossible for reasonable reasons17:27
cyphermoxdidrocks: I'll unblock messaging-app fi you're okay with my assessment17:30
rsalvetididrocks: bug 129526617:30
ubot5bug 1295266 in ubuntu-ui-toolkit (Ubuntu) "qmlscene crashed with SIGSEGV in UCAlarmModel::clear()" [Undecided,New] https://launchpad.net/bugs/129526617:30
robrucyphermox, ok, something came up for me, I need to run to the store urgently. will be back within 30 min17:30
cyphermoxok17:30
didrocksrsalveti: do you think it's a blocker?17:31
rsalvetididrocks: probably not as it seems I was the only one that got the crash17:32
didrocksrsalveti: I think it's something to keep on the radar17:32
didrocksyeah17:32
rsalvetibut still good to track17:32
didrocksrsalveti: well, I won a new tab I guess :p17:32
rsalveti;-)17:32
didrockscyphermox: sure17:34
didrockscyphermox: I know that cjwatson did some valgrind hacking where it's not available on all archs17:34
Laneyhttps://code.launchpad.net/~cjwatson/libusermetrics/valgrind-optional/+merge/21156317:39
Laneyyou should get that in17:39
cyphermoxyeah17:40
cjwatsoncyphermox: so this is all in scrollback17:43
cjwatsoncyphermox: there's that libusermetrics change Laney just linked to, and there are two commits from boiko in other history-service and telephony-service branches which IMO ought to be pulled out and landed separately17:44
cjwatsonboiko: ^- do you agree with that?  If so could you please prepare appropriate branches?17:44
cjwatsonboiko: or do you want me to?17:44
cyphermoxyeah let's land those17:50
boikocjohnston: bill just sent a mail to didrocks and sil2100 about that17:51
boikocjwatson: ^17:51
boikocjohnston: sorry17:51
boikocjwatson: it is not worth the trouble17:51
boikocjwatson: I will just add that messaging-app MR to the silo landing-009 together with the MRs already there and we land when things start moving again17:52
cjwatsonwhy a messaging-app merge?  that shouldn't be needed to get the existing version in -proposed in17:53
cjwatsonI don't think we should be stacking up more there, we should be trying to keep -proposed as clear as possible17:53
cyphermoxyeah, and make the landing as small and self-contained as possible, there are enough regressions already17:54
cyphermoxcjwatson: should I unblock messaging-app in the meantime or should we keep it as a reminder to fix this stuff?17:55
robrucyphermox, back, need anything?17:56
cyphermoxrobru: not right this moment17:56
=== bfiller is now known as bfiller_afk
boikocjwatson: but then we will have to spend even more time solving conflicts on the branches that were already reviewed and tested17:56
sergiusenscyphermox, or robru can I bother you with a packaging review for lp:ubuntu-push ?17:56
cyphermoxyes17:56
boikocyphermox: we were doing small landings, but with the Qt5.2 switch things started piling up, and we can't spend all day long landing one MR at a time17:57
cjwatsoncyphermox: you can't unblock it17:58
cjwatsonI can possibly force it on the understanding that it's being fixed17:58
cjwatsonwe definitely shouldn't do robru's proposal of an arch-limited build-dep here though, not when we have a fix in sight17:59
robrucjwatson, ok17:59
=== alan_g is now known as alan_g|EOD
cjwatsonthat's sensible when we know it's hard17:59
=== plars changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: plars | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: -
cjwatsonforced for next run18:03
cjwatsonboiko: ^-18:04
boikocjwatson: thanks18:06
jdstrandI marked the apparmor line in Pending to 'yes' several hours ago. I planned on attending the meeting today, but another meeting ran over18:08
jdstranddo I need to do anything more to be assigned a silo, or do I need to formally ask?18:08
robrujdstrand, asking is always best, it gets our attention18:11
jdstrandok18:11
jdstrandmay I have a silo?18:11
jdstrand:)18:11
robrujdstrand, yep, on it18:12
jdstrandnote-- this silo is not a MP18:12
jdstrandrobru: ^18:12
robrujdstrand, but there's an MP?18:12
jdstrandso, right, I'm trying to define our process for apparmor18:12
jdstrandupstream releases tarballs18:12
jdstrandand we do source package uploads18:13
jdstrandI have a branch, apparmor-ubuntu-citrain, that represents what is in the archive now18:13
jdstrandI then ask people when the prepare a new source package to merge again it (using the contents of the new source)18:13
jdstrandthat we, we can review, add the checklists, etc18:13
jdstrandthe intention being, when I am assigned a silo, I would upload to it (or pocket copy in this case)18:14
jdstrandand then when we publish, I do the merge manually18:14
jdstrandperhaps there is a better way?18:14
robrujdstrand, if you list an MP in the MP list, citrain builds it.18:15
robrujdstrand, if you want to upload a source package, you need to leave the MP list empty, and list your source package name in the source package name list18:15
jdstrandah, so maybe I can just add it to the comments or something if people want to review it18:15
jdstrandah!18:16
* jdstrand adjusts18:16
jdstrandrobru: 'Additional source packages to land'?18:17
cyphermoxyeah, you can make it just a souce package to land18:17
jdstrandI think the word 'Additional' threw me18:17
cyphermoxthen we´ ll upload that to the citrain silo ppa18:17
cyphermoxand do testing there before syncing to the archive18:17
robrucyphermox, well, jdstrand can upload can't he?18:17
jdstrandnote, the package is actually already built in https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages18:18
cyphermoxbeing a lander yes18:18
jdstrandwe could in theory pocket copy, but if it is easier to upload, that's fine too18:18
cyphermoxnah you could copy too18:18
cyphermoxmaybe just make it rebuild the package to be sure18:18
jdstrandok18:19
cjwatsonif ubuntu-security-proposed can't build packages fit for the archive then we're all doomed18:19
* jdstrand adds to notes about how to do source package citrain uploads18:19
cjwatsonthat's already something we copy to the archive from, isn' tit?18:19
cjwatson*isn't it18:19
jdstrandit is18:19
cyphermoxyes18:19
jdstrandit doesn't have -proposed enabled18:19
cjwatsonso I don't think we should waste builder time on rebuilding it just 'cos18:19
robrujdstrand, ok sorry, you got silo 818:20
jdstrandrobru: why are you sorry, that is good news, no?18:20
jdstrandincidentally, I only ask about the pocket copies cause I don't know how the spreadsheet/process will all cope with a pocket copy18:21
robrujdstrand, oh, because it should have been done like 10 minutes ago, i just got a little distracted18:21
jdstrandheh18:21
jdstrandrobru: np! thanks18:21
cyphermoxjdstrand: it won't matter really18:21
robrujdstrand, you're welcome18:21
jdstrandso, shall I do the binary copy then?18:21
cyphermoxsure18:21
jdstrandhere goes nothing! :)18:21
cyphermox:)18:21
cyphermoxso we're just using this for testing the package really18:22
jdstrandyes18:22
jdstrandok, so spreadsheet say 'Silo ready'18:23
jdstrandI requested the pocket copy18:23
jdstrandhttps://launchpad.net/~ci-train-ppa-service/+archive/landing-008/ shows it in there18:23
jdstrandbut the status is pending (that's fine)18:24
cyphermoxyup18:24
imgbot=== trainguard: IMAGE 249 DONE (finished: 20140320-18:25) ===18:24
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/249.changes ===18:24
robruboiko, please clean silo 1418:31
jdstrandso, I don't need to press the Build button at all with source upload/pocket copy?18:32
jdstrandI test and when done, mark the box as testing done?18:32
boikorobru: doing it right now, thanks18:32
robruboiko, thanks18:33
robrujdstrand, what you can do is start a build job with the flag WATCH_ONLY, then the spreadsheet will get the right build status from the PPA18:33
seb128cyphermox, robru, can we get silos for l44&45 (desktop only changes)18:45
jdstrandrobru: ack, thanks18:46
cyphermoxsure18:48
jdstrandFinished: SUCCESS18:49
jdstrand\o/18:49
robruyay!18:49
robrucyphermox, are you doing seb's silos?18:50
kenvandineseb128, don't hog the silos, i want one too :)18:51
seb128kenvandine, 6 available, don't worry18:52
balloonsping asac; are you going to be around next week?19:01
seb128cyphermox, robru: ?19:04
robruseb128, yeah?19:05
seb128robru, can one of you give me silos? ;-)19:05
robruseb128, oh i thought cyphermox was doing it. ok, on it19:05
seb128robru, thank19:05
seb128s19:05
seb128robru, seems he's not, which is why I did a new ping ;-)19:06
cyphermoxI was19:06
cyphermoxbut please give me the time to log in and stuff19:06
seb128robru, ^19:06
seb128cyphermox, sorry, I didn't get that the "sure" was for me19:06
robrucyphermox, oh, well i just did l4419:06
seb128one each? l45 for cyphermox ;-)19:06
seb128robru, thanks19:06
robrukenvandine, what line do you want a silo for? is it ready?19:07
kenvandinerobru, 2219:07
kenvandinebfiller_afk, we're ready right?19:07
kenvandinerobru, yes, we're ready19:08
kenvandinei think it was blocked on gallery getting published19:08
kenvandinewhich is done now19:08
robrubfiller_afk, kenvandine : ok you guys got silo 14. i see bill is afk, want me to hit the build button?19:11
kenvandinerobru, any reason not to build?19:11
kenvandine:)19:11
robrukenvandine, nope ;-)19:11
kenvandinego for it19:11
cyphermoxseb128: 1519:11
kenvandinethx!19:11
robruwaiting for bill to get back just means testing is delayed19:11
robrukenvandine, you're welcome19:11
robrukenvandine, http://162.213.34.102/job/landing-014-1-build/35/console19:12
seb128cyphermox, thanks19:15
asacballoons: from what i can see, yes. why?19:22
* asac likes such open questions :)19:22
balloonsasac, I was hoping to put together a meeting to talk about images, regressions and our landing process :-) Some of what's being raised on the phone mailing list is worthy of discussion19:23
asacballoons: i surely can go on a call and listen if someone summarizes the points19:24
balloonsto frame it, it's not about the ci-train; rather our considerations for release blockers and our methodology on things19:24
asacballoons: if you could put together a summary of the key points made19:24
asacthat would help19:24
balloonsasac, perfect.. yes, I have a presentation to share..19:24
asaci think i got them all19:25
asacbut like to hear them in different words :)19:25
asacand maybe i missed them19:25
balloonsasac, haha..19:25
ogra_balloons, oooh +++++19:26
kgunnrobru: sorry if this is repeat, wifi weirdness at the house...could you reconfig silo4 for me ?19:36
thomirobru: cyphermox: Any idea what the status of landing our autopilot is? Did the image you were waiting for get made OK?19:37
robrukgunn, no repeat, no problem19:37
robruthomi, yeah so i can provisionally land it today, but i have to do a lot of my own testing with it19:37
kgunnno repeat? arg....stupid verizon router19:37
thomirobru: yay! Please let me know if there's anything I can do to help out. This is pretty critical for us now.19:38
robrukgunn, i see from here you disconnected briefly19:38
kgunnthanks...19:38
robruthomi, just help by writing code that doesn't regress ;-) but seriously I'm just going to enable the silo and do a bunch of testing and as long as we stay 100% green I'll publish it19:39
thomirobru: "writing code that does not regress"... You *do* know that that's what every programmer on the planet aims to do, right? And *none* of them achieve it 100% of the time. Having said that, we have a test process that takes a long time, to try and catch as many of those regressions as possible :)19:40
robruthomi, I know, I was kidding :-P19:40
thomiyeah, I know - sorry , gotta vent sometimes19:41
thomiI'm kind of fed up with the notion that released regressions are caused by lazieness or lack of skill19:41
thominot that you suggested that, mind you19:41
robrutrue19:42
t1mpare clock-app and/or music-app autopilot test flaky in image 249?19:48
=== bfiller_afk is now known as bfiller
robrut1mp, not that I'm aware of? didn't we just get 100% green in 248?19:57
robrukenvandine, hrm, just noticed merge conflicts in that build log. if you want to take that branch, resolve the conflict, and push your own branch, I can reconfig the silo with your new branch and rebuild. http://162.213.34.102/job/landing-014-1-build/35/console20:04
robrukgunn, ugh, sorry, i only just now noticed that my attempt at reconfiguring your silo failed. let me try that again20:05
kgunnrobru: thanks...i saw, but thot i'd be bugging you :)20:06
robrukgunn, no please, I'm highly distracted today, i could use some poking when I fall behind on things20:06
robru(distracted by unimportant things, like squirrels in my birdfeeder and bootstrapping a new laptop I just bought)20:07
robrukgunn, ok, silo 4 should be good to build now20:07
kgunnrobru: thanks man...damn squirrels20:08
t1mprobru: I have some failures with packages from a merge request, that's why I'm asking20:09
robrut1mp, not sure, sorry, i'm not super familiar with those components.20:09
t1mprobru: http://pastebin.ubuntu.com/7127039/20:10
t1mpok20:10
t1mpI'm testing for this MR - https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/ima-bug1288876/+merge/21133020:11
t1mpI thought you guys want to get that fix before promoting the image20:11
t1mpI'm not sure though - is https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1288876 a blocker?20:11
ubot5Ubuntu bug 1288876 in Ubuntu UI Toolkit "When clicking the header, the notes are not collapsed" [Critical,In progress]20:11
robrut1mp, i don't believe that's a blocker, at least that's not one of the ones i saw blocking image promotion20:12
robrut1mp, i'm just in the middle of running unity8 ap tests (loooong), will try clock app shortly20:12
t1mprobru: I'm running *all* app tests (and uitk and unity8). about 90min in total. When its done I can re-run the ones that failed to see if it is consistent20:13
t1mprobru: thanks :)20:13
robrut1mp, no worries20:15
robruhumm, just got a pass on unity8 but now the device seems frozen. not responding to touch20:15
kgunnrobru: hey that build in silo 4 just failed....strangely to me anyway20:18
kgunncan you take a peak20:18
kgunnor peek20:18
kgunnseems it wanted a src package it can't find to match the debian ver #20:19
robrukgunn, is this the first citrain landing of ubuntu-touch-session? it seems like the packaging is wrnog20:19
kgunnrobru: it might be20:19
robrukgunn, ugh, native package... hm20:21
robrukgunn, https://code.launchpad.net/~robru/session-manager-touch/packaging/+merge/212047 ok, so this would be my recommendation for packaging changes to get session-manager-touch through the ci train20:31
kgunnrobru: ok, do i just need to add that mp ?20:32
kgunnto the list of mp's or does it have to land first or something20:32
robrukgunn, well, it needs some input20:32
robrukgunn, because I'm changing it from a native package to a split one, that's somewhat controversial. also I renamed the source package name, people are going to be ruffled by that. so we need to identify the stakeholders and see what they say20:33
kgunnrobru: ok...so this silo is really only for testing...not landing...can i add that mp in the meantime ?20:36
robrukgunn, oh, sure. just add it to the start of the list before reconfiguring20:36
robruogra_, I guess you are the most relevant person to review: https://code.launchpad.net/~robru/session-manager-touch/packaging/+merge/212047 please don't hate me ;-)20:37
robrut1mp, yeah i just got one failure in clock app...20:39
robrumine's different though20:40
kgunnt120:54
t1mprobru: I got two, see https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/ima-bug1288876/+merge/211330/comments/50084320:54
t1mpit has a link to the full logs20:54
robrut1mp, sorry, forgot to paste mine, let me dig it from my terminal scrollbar20:56
robrut1mp, here's my failure: http://paste.ubuntu.com/7127287/20:57
robrut1mp, totally different tests. seems flaky i guess. i only ran it once -- did you retry yet?20:57
t1mprobru: ah yes, I didn't get clock failure. But kalikiana was also running all tests and he got the clock failure20:58
t1mpkalikiana: ^20:58
t1mprobru: I'm re-trying the music app test now20:58
t1mpkalikiana: did you retry the clock test?20:58
kgunnrobru: ok, this thing hates me....can you reconfig ?20:59
robrukgunn, you didn't copy the MP list into the reconfig job ;-)21:02
kgunnrobru: oh i feel stupid21:02
robrukgunn, nah, it's stupid that you have to copy&paste it by hand like some kind of peasant. we're hoping to improve this in a later version of citrain21:04
kgunnrobru: yeah...it still doesn't like the ubuntu-touch-session21:05
* kgunn laughed at peasant remark21:05
t1mphmm I got confused with all the tests.. I did get clock failures21:06
t1mpI'm re-running the wrong tests..21:06
* t1mp re-queued the clock tests21:07
robrukgunn, hmmm21:12
robrukgunn, i don't see my MP in that build log...21:13
robrukgunn, oh, your reconfig failed. let me redo it21:14
t1mprobru: I'm running clock tests again. they fail somewhere else now21:18
=== seb128_ is now known as seb128
robrut1mp, well that seems quite flaky then21:19
robrut1mp, i'm running other stuff (because I'm testing autopilot itself) and it seems fine elsewhere. i'll rerun clock app in a bit21:19
t1mprobru: it is long past EOD time for me so I step out now. I linked all the logs with clock-app failures here https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/ima-bug1288876/+merge/21133021:22
robrut1mp, ok cool. good night!21:22
t1mprobru: let me know if you report a bug for clock-app tests, I'll read it tomorrow. Otherwise I can report it tomorrow21:23
* t1mp off21:23
robruthomi, so I've been testing autopilot for like, 3 hours. it's looking really good. I expect to publish it in an hour or so21:42
thomirobru: wooo! that's great news, thanks21:42
robruthomi, you're welcome21:43
=== plars changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CITrain support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: -
plarsrobru: cyphermox: looks like 249 is still running, not much to report so far except that calendar-app appears to have 2 errors on mako22:03
cyphermoxrobru: didn't we assign 46 and 47 before? I thought we had?22:04
robruplars, thanks22:04
cyphermoxplars: thanks22:04
robrucyphermox, nah you're thinking of 45 and 4422:04
cyphermoxalright22:04
cyphermoxwell, I'll take care of them now22:04
cyphermoxI added l48, which is more indicator stuff22:04
veebersrobru: will the up-coming TRAINCON-0 affect assigning silos? i.e. I'll want to grab one today for autopilot release+1 so I can hit it in my morning next week22:07
=== kenvandine_ is now known as kenvandine
robruveebers, ehhhhhh.. in theory "no" but if there's lots of blocked landings there might be a silo shortage22:10
veebersrobru: ack, thanks22:15
robruveebers, i'll try to assign your next silo as soon as we complete the publishing of the current one22:17
veebersrobru: awesome, thank you22:20
robruveebers, are the MPs listed in the sheet already?22:22
veebersrobru: not yet. I'm getting things together and sorting out any merge conflicts22:23
robruveebers, ok cool.22:23
veebersrobru: I'll have something soon (as we can partly reconfigure silos ourselves now, right?)22:23
robruveebers, you can reconfigure yourself as long as you don't add any new packages. but don't reconfig 3 or we'll have to retest the whole thing22:25
veebersrobru: ack, I'm not going to touch 3 ^_^22:26
jdstrandrobru: apparmor testing completed and good. ok for me to publish? I assume I just need ACK_PACKAGING22:35
robrujdstrand, uhhh... how big of a change is this? do you promise no regressions? ;-)22:36
jdstrandit is a new upstream release. it is heavily tested on touch, desktop and server. FFe discussion happened with infinity. it is good22:37
robrujdstrand, ok, publish away then.22:37
jdstrandthanks22:39
jdstrandmerge and clean should be ONLY_FREE_SILO cause of the source package upload/pocket copy, correct?22:39
jdstrandrobru: ^22:39
robrujdstrand, hmm, i don't think so. just run merge & clean like normal, it won't merge anything because it has no MPs. should be fine22:40
jdstrandok22:40
robrubrb22:41
robruback22:42
robruthomi, veebers: cyphermox and I are a little concerned about the diff for upstart-app-launch. it looks like some zeitgeist-core stuff got reverted. Is that intentional, or a mistake?22:53
thomirobru: what? no!22:53
thomirobru: my branch changes two lines only22:53
robruthomi, http://162.213.34.102/job/landing-003-2-publish/51/artifact/packaging_changes_upstart-app-launch_0.3+14.04.20140318-0ubuntu1.diff sounds like a mistake then ;-)22:54
thomijust changes the name of the nev var that's set from QT_TESTABILITY -> QT_LOAD_TESTABILITY22:54
thomirobru: yes, I didn't do that!22:54
thomirobru: this is my MP: https://code.launchpad.net/~thomir/upstart-app-launch/trunk-fix-env-var/+merge/20871622:54
robrucyphermox, ohhh, i think I see what's happening. the revert is 0ubuntu3, so it would have been a manual distro upload that wasn't in trunk. that's why it got lost in the silo22:55
cyphermoxwell, you're missing 0ubuntu2 and 0ubuntu322:55
cyphermoxfor this change: https://launchpad.net/ubuntu/+source/upstart-app-launch/0.3+14.04.20140220-0ubuntu322:55
robrucyphermox, yeah, whoever did those didn't bother to sync trunk.22:56
cyphermoxwhich also shows up in the diff, and I kind of agree with xnox's change22:56
* thomi is totally lost :)22:56
cyphermoxI would rather not land this as it is, it's wrong to revert changelog like this22:56
robruthomi, sorry, basicaly xnox uploaded some changes direct to distro (short-circuiting citrain) and now citrain is really confused. it thinks you want to undo those changes. but you don't. so we need to re-sync22:57
cyphermoxthomi: so basically, what you'd need to do is take the diffs from 0ubuntu2 and 0ubuntu3 and apply them in the merge request or however else, on the branch, so as to be in sync with twhat's in the archive22:57
robrucyphermox, yes you're right, we just need to resync22:57
thomirobru: do I need to do anything, or will you guys take care of it?22:57
robruthomi, i can take care of it if you're not comfortable with this level of debian-fu22:57
thomiand, as an aside, how come changes are bypassing ci-train?22:57
thomirobru: thanks, I'll buy you a beer in Malta :)22:58
robruthomi, well, xnox is being a bad boy. shame on him22:58
robruthomi, haha, thanks22:58
robrucyphermox, ok, so other than those accidental reverts, any other concerns? i'll fix that then publish?22:58
cyphermoxpretty much22:59
cyphermoxlet me check what 0ubuntu2 is22:59
cyphermoxhttps://launchpad.net/ubuntu/+source/upstart-app-launch/0.3+14.04.20140220-0ubuntu223:00
cyphermoxyeah, if you get the diff for both these uploads, then you'd basically have no packaging diff except for a possible changelog entry23:00
kgunnrobru: i started to hit build again for the packcages that didn't show up...was wondering if you were up to something special there ?23:00
kgunnonly the ubuntu-touch-session & mir packages built23:01
kgunnbut not....the many others23:01
robrukgunn, oh sorry. i wasn't sure what the status of the silo was so I ran a build job to only build the touch-session package. i guess mir built from before.23:01
robrukgunn, if there's anything missing, by all means, rebuild the silo23:02
kgunncool....23:02
cyphermoxeh23:02
robruthomi, ok, sorry for the delay. i synced distro into trunk and now I'm rebuilding *just* upstart-app-launch (so we don't have to retest autopilot). should be ready to go soon here23:24
thomirobru: awesome! \o/23:32
kenvandinerobru, i don't know what's up with that merge conflict, i just grabbed his branch and tried merging trunk23:35
kenvandinesays nothing to do23:36
kenvandinei merged in my 2 branches he prereq'd on and it did something... but no diff23:36
kenvandinei commited them at lp:~ken-vandine/content-hub/peer_picker_ui23:36
robrukenvandine, can you push it all to fix_pending_check and i'll rebuild?23:38
robrukenvandine, oh, just saw "bzr help criss-cross" in the log. never saw that before. bzr kinda sucks at merging it seems23:45
kenvandinerobru, so i merged that into my quiet_logging branch23:46
kenvandinewhich was built off of peer_picker_ui branch23:46
kenvandineso you can just remove that branch from the config23:46
robrukenvandine, oh ok thanks23:46
kenvandineand i refreshed all the branches based on that23:46
* kenvandine crosses fingers23:46
kenvandinesucks to have so many branches queued up :(23:46
kenvandinesoooo much change23:47
kenvandinebfiller, ^^ i merged his peer_picker_ui branch into one of mine that was stacked on it and robru is going to reconfigure it23:48
kenvandinebfiller, hopefully that'll clear it up23:49
robrukenvandine, bfiller: ok fingers crossed! http://162.213.34.102/job/landing-014-1-build/37/console23:49
* kenvandine thinks it's beer thirty... goes to get a cold one23:49
kenvandinerobru, thx23:49
robrukenvandine, lol23:53
robruyou're welcome23:53
bfillerkenvandine: nice, Elleo and I did the same with peer_picker_ui and peer_details and we got further23:59
bfillerkenvandine: this criss-cross bzr stuff is a bit of a mystery23:59
kenvandineyeah23:59
bfillerkenvandine: we were guessing we'd end up with one big mamoth branch23:59

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