/srv/irclogs.ubuntu.com/2014/10/02/#ubuntu-ci-eng.txt

robruQueuebot, nooooooooooooo00:25
bfillerrobru: I need a silo for line 94 please01:18
bzoltan1rsalveti: I used to use the `gdbus call --session --dest com.canonical.UnityGreeter --object-path  --method com.canonical.UnityGreeter.HideGreeter|grep -v '\(\)'` to hide the greeter... it does not seem to do the job. Do you know what should I use instead?01:21
rsalvetibzoltan1: hm, no idea, mterry might know01:22
bzoltan1rsalveti: he is not around. ogra_ gave me this line... I need to unlock the screen and kill the greeter after resets between AP tests01:23
rsalvetirobru: any idea ^?01:23
bzoltan1rsalveti:  the best kept secret of the CI :) is how the CI dash does things ... I am positive that nobody is unlocking the screen and typing passcodes manually there :) So there is a CI approved way to do. It would be cool to share those lines with the pubic.01:29
rsalvetibzoltan1: yeah, I know ogra_ was involved with that, maybe plars has any idea01:29
bzoltan1rsalveti:  for me that shell function used to work -> http://pastebin.ubuntu.com/8476271/ But not anymore.01:30
plarsbzoltan1: rsalveti: you want to use /usr/share/unity8/unlock-device from unity8-autopilot01:51
plarsit's made to be pulled onto the adb host and run from there01:52
plarsotherwise, if you just want the dbus call, you should be able to run:01:53
plarsadb shell "gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter && echo Greeter unlocked"01:53
bzoltan1plars: Thanks I prefer the dbus call... I do my own reboots :)01:53
plarsbzoltan1: actually, that looks the same as what you were running I think01:53
plarsbzoltan1: we have seen it fail a few times if it's done too soon, what's it returning for you?01:54
bzoltan1plars:  it looks similar to my script, but it is not the same01:54
bzoltan1plars: I would not use the `adb reboot; sleep 5; adb wait-for-device`01:55
bzoltan1plars:  that is unreliable...01:55
plarsbzoltan1: the sleep is more than enough to ensure that we don't return from wait-for-device before the reboot01:56
plarsbzoltan1: or were you referring to something else?01:56
bzoltan1plars: sometomes... but 10 sec is safer01:57
plarsbzoltan1: I've never seen that part of it fail so far, really we could probably even get away with less01:57
plarsbzoltan1: the part we have problems with is that if it fires too soon after boot, sometimes it can't make the dbus call yet01:58
bzoltan1plars:  I run my reset like 100-200 times a day when I do... weekly.01:58
plarsbzoltan1: mterry just landed a change that loops it a few times if it fails though01:58
bzoltan1plars: I think I stick to my script with the right dbus call :)01:58
plarsbzoltan1: feel free to propose an improvement to it if you have something that works better :)01:59
bzoltan1plars:  according to my experience there is no sure way... I have to tune my script  every week.02:00
bzoltan1plars:  Things change all over without much notice and tools fail without any meaningful error... so it is a continuous fight :)02:00
bzoltan1plars:  so that dbus call takes away the Greeter. But does it take away the password lock too?02:06
plarsbzoltan1: yes02:07
bzoltan1plars:  cool, thank you02:07
imgbot=== trainguards: IMAGE 265 building (started: 20141002 02:10) ===02:09
bzoltan1plars:  I am still lobbying :) for releasing the CI validation tools via the CI train to the archive. Make it pass all the QA standard what other packages pass and offer a tool what developers can apt-get install and use02:22
plarsbzoltan1: that script is part of unity8 - it already goes through the landing process same as everything else02:31
robrursalveti: sorry nope, i just do train stuff, dunno about messy device stuff like greeters ;-)03:05
robrubfiller: utopic 203:09
imgbot=== trainguards: RTM IMAGE 77 building (started: 20141002 03:10) ===03:09
bzoltan1robru: the clock app fails with the stock RTM image but all green on the CI dash.03:14
bzoltan1robru:  also the dialer_app tests are flaky03:19
rsalvetirobru: just configured silo 8 and can't build: https://ci-train.ubuntu.com/job/ubuntu-landing-008-1-build/82/console03:28
robrursalveti: weird. click IGNORE_STEP for now03:37
robrubzoltan1: no idea03:37
robrursalveti: hm that's odd... still digging03:42
rsalvetirobru: hm, also failed03:44
robrursalveti: the thing is I just refactored that code, and now it makes no sense to me. I need to review the old code to see how badly I broke it i guess.03:44
rsalvetibut differently03:44
robrursalveti: that one's a legitimate failure though, isn't it? ;-)03:45
rsalvetioh, need to put force rebuild03:45
robrursalveti: well wait03:46
robrursalveti: the trunk branch is really missing that revision from distro.03:46
robrursalveti: make sure you check that before you just wantonly revert it03:46
rsalvetirobru: yup, no worries, that is as expected03:46
rsalvetinot landing this until my other landing migrates properly03:46
robrursalveti: right http://launchpadlibrarian.net/186327488/ubuntu-touch-session_0.108%2B14.10.20140926.1-0ubuntu1_0.108%2B14.10.20140929-0ubuntu1.diff.gz you need to push this to trunk ;-)03:47
rsalvetirobru: can't yet because it's waiting on another silo to be cleaned03:47
rsalvetiguess I can actually03:47
rsalvetibut the clean step from the other silo might fail03:47
rsalvetiwhich is fine I guess03:48
robrursalveti: why would the clean step fail? wouldn't it just merge the branch?03:48
rsalvetirobru: migration is blocked as pulse still needs to be accepted03:48
rsalvetiI just wanted to go ahead and start my other landing, but yeah, the changelog entry is still missing until the other silo gets merged03:49
rsalvetilet me try something different03:49
robruah03:49
imgbot=== trainguards: IMAGE 265 DONE (finished: 20141002 04:00) ===03:59
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/265.changes ===03:59
Mirvmorning04:09
robruMirv: morning!04:11
Ursinhaman, "morning" means I should go to bed :)04:12
robruUrsinha: haha. it sure means I shouldn't be working... not quite bedtime though04:13
Mirvrsalveti: if you're still there, you could possibly ack this addition of a single symbol to platform-api: https://ci-train.ubuntu.com/job/ubuntu-landing-007-2-publish/lastSuccessfulBuild/artifact/packaging_changes_platform-api_2.5.0+14.10.20141001.3-0ubuntu1.diff04:13
bzoltan1Wow, I got full OK from the gallery tests with the UITK silo.04:17
Mirvbzoltan1: it's been some time since I've seen full OK from gallery locally..04:18
Mirvnice04:18
bzoltan1Mirv:  yes, I am surprised too :D The UITK landing tests look good04:19
imgbot=== trainguards: RTM IMAGE 77 DONE (finished: 20141002 04:20) ===04:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/77.changes ===04:19
bzoltan1Mirv:  but the camera app hangs .. is there a special trick to make that run? Maybe robru knows...04:20
robrubzoltan1: i dunno nuthin bout nuthin04:20
bzoltan1robru: dude :) that is a perfect line before saying EOD04:21
robruEOD04:21
robru;-)04:21
robru(EOD 3.5 hours ago)04:21
bzoltan1LOL04:21
bzoltan1I EOD'd 8 hours ago and woke up 3 hours ago...04:22
rsalvetiMirv: why the bump from 2 to 5?04:23
rsalvetiI wonder if we shouldn't also bump the other files we have in there04:23
rsalvetiops, 3 to 504:23
Mirvrsalveti: it looks like they forgot the bump the last time they bumped the version to 2.4.0..04:24
rsalvetiright04:24
rsalvetiseems fine from the MR04:24
rsalvetiMirv: +104:24
Mirvthanks.04:25
Mirvbzoltan1: I know no special trick for camera, it used to run ok04:26
robrursalveti:  my fix for that bug you saw just landed in production04:26
Mirvcamako: (if you are around) are you planning Mir 0.8.0 landing soon or slightly later? mzanetti kgunn etc would probably like to know whether they can land their QtMir + QtUbuntu also to rtm now that it's landing to utopic04:27
bzoltan1Mirv: running like `/bin/sh -e /usr/bin/phablet-test-run -r 0000 -s JW024063 -p camera-app-autopilot camera_app` does nothing ... Failed to connect to Mir: connect not called04:27
rsalvetirobru: nice, hot fix in production04:27
rsalvetithat's how we roll :-)04:27
kgunnMirv: i know camako said there was a stopper for mir0.8 promotion04:27
Mirvrobru: any idea where queuebot went? it was active 45mins ago, no totally silent despite me doing things.04:28
robrursalveti: oh no, this one went through code review! ;-)04:28
Mirvkgunn: ok. I can then at least assign silo for mzanetti.04:28
rsalvetirobru: awesome04:28
robruMirv: yeah stgraber says his server is kernel panicking every 10 minutes, so queuebot is more or less offline. before you woke up it was freaking out and spamming the channel a bit04:28
Mirvrobru: oh, ok.04:28
Mirvoh yeah, scrolling a bit further, a suspiciously _lot_ of queuebot activity :)04:29
robruMirv: but not like the spamming we saw before, it was behaving normally in the sense that it would start up, and then ping everything as if it was new, and then the server crashed, and then it would reboot, restart, ping everything, etc04:29
robru"behaving as well as could be expected from a server that crashes every 10 minutes"04:29
ToyKeepercyphermox_: Any idea if the two critical indicator bugs for rtm-024 (indicator-network, urfkill) are still present?  (network indicator crashes and doesn't restart, wifi toggles disappear when wifi disabled)05:45
ToyKeeperThe bug report doesn't indicate any fixes yet, and if the silo enables a new critical bug (even if it's in some other component), it can't land until the fix is included too.05:50
bzoltan1trainguards: is here a QA eng available to check and sign the UITK in the silo14?06:14
ToyKeeperbzoltan1: There might be soon.  The other two silos in queue are blocked.06:16
ToyKeeperkgunn, mzanetti: On that note, what test plan is relevant for silo rtm-011?  Nothing is linked.06:17
bzoltan1ToyKeeper:  all right, thanks. Then I carry on with the QtC work06:17
ToyKeeperkgunn, mzanetti: I'm heading to sleep soon, so could you add the test plan info to the spreadsheet for whoever picks it up next?06:18
ToyKeeperbzoltan1: I think a faster uitk testing method may have been worked out, but I don't recall if that matter ever came to a conclusion.  I hope it did, so we can get that tested and landed faster.06:20
bzoltan1ToyKeeper:  That would be awesome. My tests took only about ~24 hours this time... but the base is not really good. The stock image has too many failures06:21
ToyKeeperbzoltan1: I think the most bang for the buck with UITK is in manual exploratory testing, which would be both faster than re-running AP and more likely to catch visual glitches which don't affect the function.06:25
bzoltan1ToyKeeper:  that is exactly I was suggesting from the beginning. Simple re-running the AP tests on a most likely different base image (I tested on three images in 24 hours) does not make much sense in my view. But as you said, good eyes can catch things.06:27
ToyKeeperI just don't recall a final decision about it, and am at the end of my day.  I'll try to get it at least started though.06:27
bzoltan1ToyKeeper: So I am happy for the change06:27
bzoltan1Mirv:  I got a funny question... I am preparing the -gles package .. Now as the UITK is built in the RTM silo, I expect that the debian/watch file should contain different PPA URL. Is that correct?06:29
bzoltan1trainguards: I would like to ask for a reconfig of the rtm14 silo, i just added there the -gles package.06:34
ToyKeeperIn that case, perhaps I shouldn't start on it.06:36
ToyKeeperIf the contents of the silo changed just now, wouldn't that invalidate the previous test results?06:37
bzoltan1ToyKeeper: absolutely  not... I am adding the -gles package06:39
bzoltan1ToyKeeper:  that has nothing to do with the UITK package I tested. It is a package for the emulator... what is not tested by anybody for any landing06:40
ToyKeeperOh, okay.06:40
bzoltan1ToyKeeper: actually it is something what is a real issue... at some point we should start testing the emulator images too06:41
ToyKeeperHaha, yeah.  As soon as the emulator itself is reasonably stable.  :)06:41
Mirvbzoltan1: you're correct, it should be of the style http://ppa.launchpad.net/ci-train-ppa-service/landing-020/ubuntu-rtm06:47
bzoltan1Mirv:  I used this "https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-014/+files/ubuntu-ui-toolkit_([^-]*)\.orig.tar.gz"06:48
bzoltan1Mirv:  I can still change06:49
Mirvbzoltan1: maybe that's correct... we'll see. reconfigured.06:50
Mirvor sorry, not yet06:50
Mirvchanges in the prepare jobs06:50
Mirv"Please ask the trainguards to reconfigure this silo for you." I _am_ a trainguard :)06:50
Mirvoh, right, there it is06:51
Mirvbzoltan1: now reconfigured06:51
bzoltan1Mirv: :D06:51
bzoltan1Mirv: ehh https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-014-1-build/25/console06:59
Mirvbzoltan1: unsynced changelog vs https://launchpad.net/ubuntu-rtm/+source/ubuntu-ui-toolkit-gles07:02
Mirvpsivaa: btw the clock app qmlscene was a duplicate bug #137634607:05
ubot5bug 1376256 in qtorganizer5-eds (Ubuntu) "duplicate for #1376346 libedataserver crashed with signal 5 in clock-app" [Medium,Confirmed] https://launchpad.net/bugs/137625607:05
Mirvbut the mediascanner one was potentially a newly filed07:05
Mirvanyway, neither is upstream Qt crasher but apparently in our components07:05
bzoltan1Mirv:  does it mean that I need to change the previous entry in the changelog? So it will pull from the RTM distro...07:16
Mirvbzoltan1: probably yes07:17
bzoltan1Mirv:  all.. right. I try that07:17
bzoltan1Mirv:  it seems that the trick works.. thanks07:20
Mirvgood!07:20
brendandsil2100, red alert, we got a true blocker yesterday07:29
brendandsil2100, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/137650007:29
ubot5Ubuntu bug 1376500 in thumbnailer (Ubuntu) "[regression] thumbnails and image previews displayed wrong" [Critical,Confirmed]07:29
sil2100brendand: ugh, that in ubuntu-rtm?07:34
sil2100Right, rtm07:35
tsdgeoswho do i need to bribe to get some nodes for http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/ ?07:44
tsdgeos' All nodes of label 'utopic&&amd64' are offline '07:44
Mirvsil2100: at least that wasn't "isolated bug fix" but went through QA07:46
Mirvtsdgeos: cihelp, probably07:47
tsdgeosMirv: if there was someone called cihelp :D07:47
sil2100hah ;)07:52
sil2100tsdgeos: cihelp is a key-word that all CI team members get pinged on07:53
tsdgeosic07:53
vilatsdgeos: O_o /me looks07:54
brendandMirv, no i would have extra pissed off it is was an 'isolated bug fix'07:57
davmor2Morning all07:59
sil2100brendand: I just poked Satoris, not sure when he starts his day though08:04
vilatsdgeos: weird, the node appears to be up but jenkins fails to connect to it, I'll escalate08:08
tsdgeosvila: tx08:09
Mirvsil2100: what's your current damage report? I mean in terms of recovering from injuries..08:12
Mirv"hull intact" etc08:12
sil2100hah ;)08:12
davmor2sil2100: did I set the day thing right on those tags age still say N/A08:13
sil2100It's better, it's not swollen anymore08:13
sil2100But I still have problems moving it so I'm wearing a stabilizer08:14
sil2100davmor2: hm, I thought those were correct, let me re check08:14
davmor2sil2100: what this teach you about doing martial arts incorrectly ;)08:15
sil2100I think everyone took our previous exercises a little bit too seriously08:16
sil2100;)08:17
sil2100davmor2: ok, fixed, we both filled in bad tags yesterday - it's suppsaosed to be lt-date- not lt-age-08:17
davmor2sil2100: hahaha08:18
mzanettisil2100: hey ho :) could I have a silo for spreadsheet line 42 please?08:20
sil2100mzanetti: looking!08:20
sil2100mzanetti: it's a sync from utopic now, right? Only unity8?08:21
mzanettisil2100: yeah08:21
mzanettisil2100: wait, let me make sure which ones08:21
mzanettisil2100: yep, only unity808:22
sil2100mzanetti: hm, unity8 already seems to be configured for ubuntu-rtm in silo 1108:22
sil2100mzanetti: I'll assign a silo but make sure you land rtm/11 first08:23
sil2100mzanetti: as the packages in the new silo I'll assign will include the version from rtm/11 as well, so we first need to +1 the previous silo before proceeding08:24
Mirvsil2100: ok. hopefully getting better and better soon.08:26
mzanettisil2100: ah... that's why08:26
mzanettisil2100: ok... I can also wait... but rtm seems to start being 3 silo releases behind utopic08:26
mzanettisil2100: but we have > 10 approved branches in unity8 again, so I'd need to get going with that too soon08:27
sil2100mzanetti: ok! Let's poke QA today to make sure it gets signed off as soon as possible08:27
mzanettibrendand: hey, could you prioritize silo rtm/11 a bit please?08:27
sil2100davmor2, brendand: can you (or anyone else) sign off rtm/11?08:27
brendandmzanetti, no test plan08:32
brendandmzanetti, otherwise it probably would have been signed off already08:32
sil2100psivaa: hey! You online today?08:37
mzanettibrendand: added the test plan link08:39
brendandmzanetti, you didn't think about running any of the indicator- test plans?08:42
mzanettibrendand: hmm... doesn't really change the indicators itself. only the ui for it.08:43
mzanettibrendand: unity8 test plan contains verification of the ui08:44
mzanettibut if you're worried, feel free to do some more checks08:44
Mirvsil2100: he e-mailed that he'll be later on08:44
brendandmzanetti, ok but keep in mind the testing is not only to verify the fixes work but also to check for regressions08:44
mzanettibrendand: yeah sure... but if that silo introduces regressions its the ui not connecting to them, or rendering some labels wrong in there... still covered by the unity8 test plan08:45
brendandmzanetti, ok just making sure - some people are not so careful08:47
chihchunquestion: how do I push a new package version to the image?08:54
chihchunhttps://wiki.ubuntu.com/citrain/RTMLandingApproaches # really confusing08:56
* popey gives up08:58
sil2100chihchun: let me get back to you in a moment08:58
chihchunsil2100: #1351092 and #1334495 are fixed in fonts-android 1:4.3-3ubuntu2, but I see fonts-android 1:4.3-3ubuntu1 in current image09:00
dbarthhi trainguards; i've unblocked branches in silo 14 for landing09:02
brendandpstolowski, hey - you tested the last mediascanner landing right?09:04
sil2100chihchun: ok, so generally the RTMLandingApproaches is a document for people that already know the CI Train landing process and just want to know how to land the same stuff in ubuntu-rtm09:05
sil2100chihchun: did you use the CI Train before?09:05
pstolowskibrendand, i tested last mediascanner-scope landing09:05
Mirvdbarth: ok!09:05
Mirvsil2100: robru: we'd btw need a feature to mark a silo "test silo" so that anything conflicting with only that is allowed to be prepared09:05
pstolowskibrendand, (not the mediascanner)09:06
Mirvsil2100: robru: considering my Qt silo now conflicts with half the world09:06
chihchunsil2100: No, I did not. and the issue has been fixed in ubuntu package, I don't need to do a new MP09:06
ogra_ricmm, could you top approve https://code.launchpad.net/~ogra/phablet-tools/fix-phablet-shell-without-local-key/+merge/236696 ?09:07
sil2100chihchun: ok then, let me take a look at this09:10
chihchunsil2100: thanks09:10
sil2100chihchun: ok, so I see that the new utopic images already have the ubuntu2 in them - all we need to do is sync up this package to RTM09:11
sil2100chihchun: do you have an ubuntu-rtm enabled device?09:12
chihchunsil2100: right, I have a nexus409:12
sil2100chihchun: does it have an image from the ubuntu-rtm channel installed?09:12
sil2100Or is it devel-proposed?09:12
Mirvpstolowski: MP not approved, can't publish https://code.launchpad.net/~unity-api-team/unity-scopes-shell/department-doesnt-go-away/+merge/23177409:13
Mirv(top-approved)09:13
sil2100chihchun: anyway, I'll fill in a sync landing for you - this will generate a PPA for ubuntu-rtm where the packages will be available for testing09:14
chihchunsil2100: yes, I have r67, 20141002 image on it. (ubuntu-touch/ubuntu-rtm/14.09-proposed)09:14
sil2100Excellent09:14
pstolowskiMirv, ah, it is now09:17
ogra_mvo, iirc that came from your meta upload ... https://lists.launchpad.net/ubuntu-phone/msg10035.html ... any idea about it ?09:18
brendandpsivaa, but you know it had mediascanner and thumbnailer in that silo right?09:18
brendandpsivaa, sorry09:18
sil2100chihchun: ok, so now https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-021 has the fonts-android version for your testing09:18
brendandpstolowski, ^09:19
chihchunsil2100: where should I report my test result?09:19
sil2100chihchun: once you test those packages, please go to the spreadsheet, find your landing (it's currently row number 68, but you can find it by your nickname), scroll the sheet to the right and switch 'Testing pass?' for this column to 'Yes (#image_no_you_tested_on device_name your_nickname)'09:21
sil2100chihchun: after that the rest belongs to us and QA, so you're free09:21
Mirvpstolowski: thanks, published.09:22
psivaasil2100: sorry dint know you'd lead the meeting back today. so i emailed Mirv in the rush to go out09:22
Mirvpsivaa: and I didn't notice sil2100 wasn't included :)09:23
psivaa:)09:23
pstolowskibrendand, i know nothing about that, sorry09:24
brendandok that's kind of a problem09:25
chihchunsil2100: all done, thanks09:28
mvoogra_: I am just the uploader, its "bzr log -r 248" committer: Jamie Strandboge <jamie@ubuntu.com>09:29
mvo  merge from David Barth: Let apparmor protect access to the OA APIs09:29
ogra_oh, ok09:29
sil2100psivaa: ah ;) No worries!09:29
ogra_dbarth, ^^09:29
ogra_dbarth, see https://lists.launchpad.net/ubuntu-phone/msg10035.html for context09:29
sil2100chihchun: thanks! Now just we need to wait for QA to sign it off and it'll be in ubuntu-rtm09:30
dbarthreading09:33
dbarthok, i noticed that yesterday with mardy09:34
dbarthmardy: ^^ that same permission error; so the fix is to explicitely specificy the applicationid when making calls. right?09:34
mardydbarth, ogra_: I'll comment on the bug report, as well as to the ML09:42
ogra_mardy, merci :)09:42
brendandsil2100, i almost forgot there's something i needed to talk to you about09:51
sil2100Wazzup?09:52
brendandsil2100, silo 19 has qml pre-compilation fixes, we think it will be high impact so when it lands we want it to land alone09:53
brendandsil2100, you think you can arrange that?09:53
sil2100Oh, finally that big landing!09:53
sil2100brendand: sure thing, I also see that Mirv is set as one of the landers so I'm sure he'll additionally have a look at that09:54
ogra_lets make sure to have a standalone image for it09:58
bzoltan1brendand:  Do you think you can take the UITK release candidate?10:02
mzanettisil2100: hey, when you have a minute, please assign me a utopic silo for row 6910:02
brendandbzoltan1, i'll put it next in the queue10:03
ogra_how would people think about a remote execution feature for phablet-shell ? like: http://paste.ubuntu.com/8478233/10:04
bzoltan1ogra_: I would use it10:07
seb128do you people know what happened to get glib updated in the rtm serie?10:07
bzoltan1brendand: thank you. The logs are at the same place. The link is in the sheet10:07
ogra_seb128, havent checked excuses yet10:07
seb128ogra_, excuses?10:07
seb128we wanted to get it updated but qa needed to approve it I think10:08
ogra_seb128, seems colin didnt move it over to rtm-proposed yet10:08
brendandogra_, what benefits would it give over adb shell?10:08
seb128is that still blocked?10:08
ogra_seb128, oh, wait ... glib ? not glibc10:08
seb128ogra_, https://launchpad.net/ubuntu-rtm/+source/glib2.010:08
seb128right10:08
ogra_heh, sorry ... (we're trying to land glibc too atm)10:08
seb128http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=glib10:08
seb128that one ^10:09
seb128is it blocked? can we do anything to unblock it?10:09
seb128it's an important fix for wakeups issues10:09
ogra_seb128, spreadsheed line 19 ..10:10
ogra_hasnt been set to "testing done" yet10:10
ogra_QA qill only be notified about it if that has happened10:10
ogra_*wil10:10
ogra_l10:11
seb128Laney, ^ should we do that?10:11
bzoltan1brendand:  I explained to ToyKeeper that the silore configuration  is not relevant for the QA because it was needed to get the -gles package built too10:11
ogra_seb128, i assume the testplan: "test ALL the things" might be a bit time consuming though :P10:12
seb128ogra_, not sure how you want to test base libraries10:12
ogra_me neither10:12
ogra_but at least describing how to test the bugs you aim for to be fixed are gone might be helpful10:13
Laneytesting done where?10:14
ogra_Laney, the K column on the spreadsheet10:14
Laneyokay, I thought that was for QA to do10:15
Laneyseb128 did some testing10:15
LaneyI don't know how to check for the wakeup problem10:15
seb128I run my krillin with that version for a few days without issues10:15
Mirvsil2100: brendand: I'm just a lander helper there, but yes it's a high impact landing and requires super extra care. not sure about ETA though.10:16
Laneyseb128: can you fill in image number please ;-)10:17
davmor2Laney: No the developers run their testplan and mark it tested, we then grant it in the needs QA sign off10:17
seb128Laney, urg, I don't remember, I think it was 7110:17
Laneyheh10:17
seb128let me reinstall it on the current image10:17
seb128so we can put the current number there ;-)10:17
* Laney wibbles at davmor2 10:18
davmor2Laney: take those pants off your head and pencils out of your nose, you don't fool anyone :P10:19
ogra_Laney, note that if you put in "test all the things" someone might take that literally and run all AP tests (which is a several hour process) :)10:19
ogra_i know that ToyKeeper does that in such cases10:19
Laneyogra_: I don't mind, it's not expected to break anything10:19
* ogra_ usually points to the bugs and how to check they are gone in the test plan 10:19
ogra_Laney, no, but it takes QA time and will make the landing slow10:20
Laneywell it's not an isolated upload just for that fix10:20
* brendand grumbles check for regressions too...10:20
Laneywe just took the upstream release which contains it10:20
ogra_sil2100, any idea on what vacation the bot is today ?10:24
sil2100hmmm10:25
sil2100ogra_: I think it's just slacking off, we should fire it!10:25
ogra_++10:25
davmor2ogra_: tomorrow it is uniting with all the other bots10:25
ogra_lol10:25
LaneyTag der queuebotten einheit10:26
sil2100But yeah, I guess we need to poke stgraber about it10:26
Mirvsil2100: ogra_: the machine running it reportedly crashes every 10 minutes, so it's essentially gone for now10:33
john-mcaleelymorning all10:33
john-mcaleelysil2100, ogra_ new device tarball available10:34
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141002-d5938d7.tar.xz10:34
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-20141002-d5938d7.changes10:34
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/device_krillin-testresults-20141002-d5938d7.ods10:34
john-mcaleelyany chance of a davmor2 or brendand QA pass? ^10:34
brendandjohn-mcaleely, as long as we're going to have the results in spreadsheet form can we keep it in the google doc?10:35
john-mcaleelybrendand, have a look at the google doc :-)10:35
sil2100\o/10:36
bzoltan1Mirv:  the QtC from the silo6 is well tested and good to go... it has a fix what could be important to important people :D10:38
Mirvbzoltan1: ok, I'll publish it as soon as the arm64/etc builds are fully ready10:40
brendanddavmor2, are you busy with something else?10:41
davmor2brendand: bisecting the trust-store crash10:42
ogra_john-mcaleely, oh, i see two lovely fixes there :D10:43
john-mcaleelyogra_, only two :-)10:43
brendanddavmor2, can we let the developers do that and you pick up the device tarball?10:43
davmor2brendand: location crashing is definitely just 76+ trying to find when truststore crash happened now10:43
ogra_well, the otherse are a nice icing :)10:43
john-mcaleelyha!10:43
john-mcaleelyoh, the change in disk space will be latent unless you flash_tool install the release. I'll send mail on that topic once the release is up on s-i.u.c10:46
looldavmor2: could you check syslog for aa errors?10:46
looldavmor2: since the main difference seems to be apparmor10:46
davmor2lool: done it yesterday with jdstrand  no issues relating to location directly10:46
lool:-/10:47
davmor2lool: exactly10:47
looldavmor2: there was no simultaneous device tarball update, was there?10:47
looldavmor2: any satellite crashed in your backyard between #75 and #76?10:47
davmor2lool: no the device tarball is only available now, and the custom tarball did touch anything in here, but custom didn't land and ToyKeeper confirmed that location service crashed for her in 76 too10:48
davmor2s/tarball did/tarball did not10:49
davmor2brendand: I already have 73 flashing so I'll try that and then leave it with lool for the trust-store crash, and then test the device tarball on current10:50
davmor2lool so image RTM73 has trust-store crash10:54
davmor2lool: no I need to get on with some other stuff10:55
davmor2now even10:55
davmor2john-mcaleely: I get permission denied on the ods doc10:56
john-mcaleelydavmor2, doh10:58
john-mcaleelydavmor2, please retry10:58
davmor2john-mcaleely: yay11:00
davmor2lool just to confuse matter 77 with the device tarball I'm testing and location is working again but trust-store still crashes on it's initial run11:13
sergiusenssil2100: so today, there's no difference from doing a utopic or rtm first landing?11:25
sil2100sergiusens: what do you mean?11:25
sergiusenssil2100: well, robru was telling me you were working on something to make it just one atomic thing11:26
sil2100sergiusens: yeah, I didn't work on it yesterday because of a sick day so I'm one day late in the schedule11:26
sil2100So for now it's still the same as before11:27
thostr_sil2100: any idea what's wrong with silo 11? it seems to be building for days...?11:32
sil2100thostr_: looking11:32
thostr_sil2100: the log says it's building since 26.9.!11:33
sil2100thostr_: ouch, well... this is iterating into infinity, as urfkill started being unbuildable for 3 platforms with the introduced changes11:34
sil2100thostr_: I aborted the build, but this needs to be resolved anyway11:35
bzoltan1brendand:  any news about the UITK landing?11:35
thostr_sil2100: nice... just wondering why none of the landers noticed...11:35
sil2100cyphermox_: hey!11:35
thostr_and this is blocking others silos11:35
sil2100cyphermox_: what's up with silo 11? Is making urfkill unbuildable for those 3 architectures wanted?11:36
sil2100thostr_: yeah, I guess we, the LT, should have also noticed, but we can't keep track of all individual silo contents11:36
sil2100Though, this one we should have noticed11:36
sil2100thostr_: thanks for noticing!11:36
thostr_sil2100: well, I think it should have been noticed by landers... I mean, when I press the build button I really want ot have it build ASAP. anyway11:37
=== chihchun is now known as chihchun_afk
cwaynedavmor2: ping11:54
davmor2cwayne: so the custom tarball sucks without location dude :(  I'm testing a device tarball now tough and the location seems to be working there so lets get that landed and I'll try the custom again after that and hopefully we will be rocking then11:56
davmor2cwayne: but it was looking pretty good except for the scopes that didn't load properly because of the lack of location :)11:58
cwaynedavmor2: but that's not the custom tarball's fault :(12:00
davmor2cwayne: no but the broken scope become more obvious now they become front and center12:01
cwaynebut it's really not a broken scope, its a scope that requires location but not getting it12:02
cwaynebut anyway, im fine to get it in after device tarball :)12:02
brendandbzoltan1, someone is looking at it now12:13
brendandbzoltan1, remember the trello board :)12:14
ogra_brendand, i thought that was supposed to be linked from the spreadsheet12:15
brendandogra_, i did to - look at sil210012:15
brendandogra_, it's in the topic though12:15
* ogra_ loks at sil2100 12:15
ogra_*looks12:15
sil2100It was on the spreadsheet some time ago, ugh12:15
ogra_brendand, he looks like evry day ... just with that thing around his wrist12:15
sil2100brendand: re-added12:16
sil2100That thing on my wrist is irritating - looks cool but is uncomfortable as hell12:17
ogra_heh12:17
davmor2sil2100: then stop doing martial arts badly, lesson learnt ;)12:18
davmor2sil2100: this is the problem with martial arts when it goes wrong it hurts like hell, I broke me little finger cause it got caught up wrong doing a roll for gods sake :) You think your wrist support is annoying try a cast :D12:21
sil2100hah ;)12:22
* sil2100 goes for lunch12:23
sil2100No way I'm cooking with this hand, we'll eat something outside12:23
cwaynedavmor2: man im pretty sure i would break everything if i tried martial arts12:23
davmor2sil2100: wow that ambitious unless you have snails outside12:24
davmor2cwayne: man you'd be fine12:24
cwaynedavmor2: nah, im pretty sure i'm like made of glass or something, I broke my pinky finger badly last year just playing catch with my brother12:25
cwaynelol12:25
davmor2hahaha12:25
* ogra_ would recommend a ball instead12:27
cwaynelol12:28
cwaynebut he's so fun to throw12:28
ogra_heh12:28
bzoltan1brendand:  ahh.. of course. I see victor opened it12:28
cwaynedavmor2: btw, i've started this up if you think it could be helpful for tracking.. it's basically what you told me you test anyway + like 2 things :) https://docs.google.com/a/canonical.com/spreadsheets/d/1j9dQyiHLj5w6udh8Ixp3VfOF7C8ZGYaUYz65wx9TxyM/edit#gid=012:50
cwaynedavmor2: so installing with a --wipe, I am now able to reproduce not getting location13:01
cwayneand it does suck :/13:01
* lool goes wiping his krillin then13:04
davmor2cwayne: told you so ;)13:06
cwaynedavmor2: you were right :)13:06
cwaynealthough it isn't my fault at least :P but it does certainly ruin the scope experience13:06
looldavmor2: still we dont know exactly what caused the regression, there was no location-service related landing between 75 amd 7613:07
davmor2john-mcaleely: I have run everything on your spreadsheet and that is all good, including headset13:16
davmor2john-mcaleely: I'm just running a quick smoketest now and then I think it is good to go13:17
john-mcaleelydavmor2, sounds good13:17
sil2100davmor2: I don't like eating snails13:37
zsombibrendand: ping13:44
brendandzsombi, hello13:46
zsombibrendand: zoltan is away, so in case you have sthing for the toolkit, I'll be here for an hour still13:48
kenvandinesil2100, can  you tell what's wrong with line 71 on the spreadsheet?  says circular dependency?  and there's a request ID, but it isn't in a silo13:52
sil2100kenvandine: hm, let me check13:53
sil2100kenvandine: ok, fixed - something broke and there was an invalid formula in column O13:54
kenvandinethx13:54
=== Ursinha changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Please inform robru of all build failures today.
davmor2john-mcaleely, sil2100: device tarball is good14:04
ogra_yay14:04
sil2100yay!14:04
sil2100john-mcaleely: push it o/14:04
ogra_john-mcaleely, are we there yet ?14:04
sil2100davmor2: then the custom tarball, right?14:04
john-mcaleelysil2100, sure?14:04
looldavmor2, cwayne: How does one track landing of a custom or of a device tarball?14:04
loolcause I have some updates to land there too14:05
davmor2lool: you talk to cwayne and john-mcaleely14:05
sil2100john-mcaleely: I guess so - ogra_, brendand: any objections?14:05
ogra_lool, custom -> cwayne, device -> john-mcaleely14:05
looland for utopic?14:05
davmor2lool: there isn't one14:05
ogra_the android package for device ...14:05
looldavmor2: there is!14:06
looldavmor2: or do you mean no process?14:06
* john-mcaleely my hand is hovering above an 'enter' key...14:06
ogra_lool, cwayne again :)14:06
ogra_john-mcaleely, ohhhh, the suspense !14:06
john-mcaleelylool, one reads the tea laves14:06
john-mcaleely(for device tarball)14:06
davmor2lool: I meant tarball, it's in the package as ogra_ says :)14:06
loolah right14:06
sil2100john-mcaleely: pressit!14:06
john-mcaleelypressed, sil2100 davmor2 ogra_ brendand  - new device tarball pushed14:07
davmor2john-mcaleely: Don't make me come down there and press it for you :P14:07
john-mcaleelylool, ^ there you go - live feedback on progress :-)14:07
davmor2cwayne: do you need to do anything to have it pull in the device tarball on your version?14:08
looljohn-mcaleely: :-)14:14
cwaynedavmor2: shouldn't14:15
=== boiko_ is now known as boiko
alecutrainguards: ping. I'd like to ask about bug # 1376445, where a change in signon-apparmor-extension broke online accounts as used from the click scope and some other places14:41
alecuhttp://pad.lv/137644514:42
ubot5Launchpad bug 1376445 in signon-apparmor-extension "Addition of signon-apparmor-extension causes token lookup problems" [High,In progress]14:42
cwayneif you're asking to revert it, +1 from me too14:42
alecutrainguards, cwayne: I'd like to find out how did it land (I suspect not thru a silo), and how we can prevent those kind of breakages in the future14:43
alecuat least, I'd like to make sure that landings for online accounts are triggering QA in dependent projects, like our scopes14:44
alecumardy: dobey: I'd like your ideas on that too ^14:45
dobeyalecu: require QA approval and ensure QA tests the appropriate things, when new packages are requested to be added to the ubuntu-touch seed, before the change is actually made, as i don't think ubuntu-meta lands through CI train14:47
dobeymoving ubuntu-meta to CI train would probably be a major annoyance for everything other than ubuntu-touch though14:48
* Ursinha watches the conversation and makes notes14:48
alecuUrsinha: feel free to throw ideas too, I'd like to understand how this is happening, and how to prevent it.14:51
Ursinhadobey: that's an interesting use case14:51
Ursinhaalecu: I'm learning the process as well so I can suggest improvements :)14:51
dobeyUrsinha: indeed14:51
Ursinhadobey: how does that work in that case? the package is pushed to archive directly and then you have to QA it?14:52
Ursinhaas you say that doesn't land through citrain14:52
Ursinha*said14:52
dobeyUrsinha: well, ubuntu-meta is just a meta package; the package that caused the breakage was already in the archive. what caused the breakage was it being added to the seed, and thus instaleld on the image.14:54
=== oSoMoN_ is now known as oSoMoN
dobeyUrsinha: so i think when there is a request to add a new package to the ubuntu-touch seed, QA should first install that package on a device, and then run through appropriate test plans to ensure things don't break; then they sign off and it can be added to the seed14:55
cwayne+114:55
dobeyand i'm guessing this problem happened, beacuse we aren't doing that (if we are doing that, then i guess the wrong tests were run, or at least, not enough tests were run)14:56
Ursinhadobey: oh, I see the problem package-wise..... do we have more of these, a significant number of metapackages that we care about on the phone side?14:58
dobeyUrsinha: i don't think so. afaik ubuntu-touch is the only metapackage we really care about on the phone side14:59
Ursinharight14:59
dobeycjwatson would know better than me if there are others though14:59
Ursinhadobey: I'll think about it on the train/airline side, thanks for the info15:00
sergiusenssil2100: Mirv can I get a slo for 77?15:00
sil2100Ah, crap, right... no queuebot15:01
sil2100sergiusens: sure15:01
Ursinhasil2100: what happened with queuebot?15:01
sil2100Ursinha: stgraber's machine has problems right now, so queuebot has no where to work on - we've been already discussing moving it to somewhere public15:01
=== gatox_ultra is now known as gatox
Ursinhasil2100: oh yeah, you know you have my +1 on that :)15:02
dobeyUrsinha: sure. i'm not sure we want to stick ubuntu-meta in the ci train process completely though; as that would add a bunch of needless process for the rest of ubuntu when managing server/desktop images and such.15:02
Ursinhadobey: not completely, as you said it would be a lot of trouble and the goal is to facilitate, not the other way around15:03
Ursinhadobey: I was more considering the tracking part, having maybe a "partial" request where the building part is done outside the train but we still get to track and request QA input15:03
Ursinhasomething along these lines15:04
robrubfiller: your build failure is caused by a comma in the space-separated packages list, fixed it for you and building: https://ci-train.ubuntu.com/job/ubuntu-landing-002-1-build/76/console15:04
cwaynebut so while fixing process in the future is great, we also need to fix the immediate problem :)  should we revert that addition? or wait for a fix?15:04
cwayneit breaks all my scopes that use OA..15:04
bfillerrobru: oh thanks, I hadn't seen that yet15:04
dobeycwayne: i was hoping mardy would get the fix in which i suggested on the mailing list15:04
Ursinhabot being dead makes me sad15:04
dobeyUrsinha: don't be sad. it's only the beginning in bot's new afterlife15:05
UrsinhaLOL15:05
cwaynedobey: https://code.launchpad.net/~mardy/signon-apparmor-extension/lp1376445/+merge/23688215:06
cwaynenot in a silo yet that i've seen15:06
dobeycwayne: well, jenkins doesn't like it :)15:07
cwaynenoticed that :)15:07
dobeyoh15:08
dobeythat's because coverage isn't working in jenkins for some reason, but it's trying to build with coverage15:08
dobeythe tests apparently passed15:08
sergiusensbrendand: do critical bugs get QA signoff preference?15:14
brendandsergiusens, i would hope all silos are fixing critical bugs at this stage15:15
sergiusensbrendand: well some of us only have high bugs in our lists ;-)15:15
sergiusensI would bet not thought15:16
sergiusenseasily checked in the PPA changelog15:16
dbarthtrainguards, can i have a silo for line 78 please; thank you15:17
rsalvetijezz15:21
ogra_lovely15:21
sil2100Let the poor guy talk all he wants15:30
sil2100queuebot: we're happy to see you too15:30
sil2100dbarth: ok! Let me check if anyone was faster than me15:30
dbartheh15:34
dbarthso, who wins? ;)15:34
sil2100dbarth: I did ;) Silo should be yours15:35
sil2100elopio: hi! Do you know if there is any progres related to gallery and calculator utopic failures?15:44
sil2100elopio: the ones with $HOME issues15:44
Ursinhasil2100: where is the bot running now?15:45
elopiosil2100: we started a long discussion to find the right way to solve it15:45
elopiohttps://bugs.launchpad.net/ubuntu-app-launch/+bug/137642315:45
ubot5Ubuntu bug 1376423 in Ubuntu Application Launcher "There is no easy and future-proof way of starting an app in a clean environment" [Undecided,Invalid]15:45
sil2100Ursinha: I think it's still at Stephane's15:45
elopiofor now, things point to create a new user, and that's something that will take time to implement properly.15:46
elopioso now we need to see if we add a new patch to fix it for the moment.15:46
Ursinhasil2100: got it15:47
looltrainguards, Mirv: FYI, I've repurposed the dbus-cpp + l-s rtm silo / landing request to include more packages and do a single bigger location related landing15:49
loolhowever I need to land translations first15:50
looltrainguards, Mirv: woudl you mind killing line 25 ?15:51
loolkgunn: hey, how's the utopic landing of trust-store going?15:53
kgunnlool: i am just now testing it15:53
kgunnhope to be done w/in 30 min15:53
loolkgunn: cool; mind pinging me when it's in?15:53
kgunnlool: will do15:54
sil2100lool: oh, ok, so completely freeing line 25, yes?15:54
loolsil2100: yes15:54
loolsil2100: I've merged into the first landing for l-s15:55
loolsil2100: if I read this correctly, there's no silo15:55
sil2100lool: just to make sure - you mean the rtm landing from tvoss, right?15:55
loolsil2100: yes15:55
=== chihchun_afk is now known as chihchun
kgunnlool: hey do you know much about trust-store ?15:59
loolkgunn: not much; the concepts and have poked a bit16:01
loolkgunn: I saw there was a comment on the top crasher that this could possibly be fixed by a random branch, but I kind of doubt it16:02
kgunnlool: so his official test plan filters down the testing, and it passes....but if i run the full suite i see a couple of failures....16:02
kgunnaltho, those aren't called out in his test plan16:02
kgunnso...hmmmm16:02
kgunnreverting to virgin image to try16:02
sil2100geh16:11
sil2100Firefox died16:12
sil2100One final try16:12
sil2100Ok, that's no use, my connection to google services is too terrible16:12
sil2100ogra_: could you lead the meeting in my stead?16:12
ogra_sil2100, sure16:12
sil2100Since I can't even get hangouts to open now16:12
sil2100...aaand I can't even close the tab, great16:13
ogra_sil2100, not sure you had anything you wanted to bring up specifically ... we shortly talked about the systemsettle issues ...16:19
pstolowskitrainguards, what should I do with line 55 (see my comment in line 81)? i basically need the hotfix to land in utopic first, then 55 should have all the fixes listed previously in #54/#55, plus the hotfix16:19
robrupstolowski: i don't understand what you're trying to do16:21
pstolowskirobru, a few MPs just laned in utopic, but we discovered an issue and need to land one more MP in utopic. then we want to copy utopic package into rtm (so, all the MPs from #55 + the hotfix)16:23
robruright, so just do that exactly how you described it, then? I don't understand what the problem is16:24
pstolowskirobru, shall #55 still list all MPs, plus the new one? or just the new one?16:24
robrupstolowski: no, 54 already landed, it's done. 55 can't have any MPs because it's a sync. I gave you silo utopic 1 for line 81, build test & land that one, and then when you do the sync it'll pick up everything together16:26
kgunnlool: i want to check something but have to step away for an hour...sorry to be a hold up on trust -store but wanna be sure16:27
pstolowskirobru, ack, thanks16:28
loolkgunn: ok16:30
robrupstolowski: you're welcome16:30
dbarthhey, i'm trying to see which rtm image oxide 1.2.4 will be in16:36
bzoltanbrendand: I missed the last few hours. Is there any news about the UITK QA tests?16:42
ogra_dbarth, is it in the rtm archive already ?16:53
=== gatox is now known as gatox_lunch
imgbot=== trainguards: IMAGE 266 DONE (finished: 20141002 17:00) ===17:00
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/266.changes ===17:00
davmor2cwayne, sil2100, ogra: so let it roll I think, everything opens, everything seems to work, location works which was the big issue before I'm happy17:03
cwaynedavmor2: did it add the extra favorites too?  (if you'd ever touched them it won't unless you do a fresh flash)17:03
cwayneneato17:05
popeymy unity just crashed in 26617:05
cwayneso sil2100 am i good to push?17:05
popeydied completely17:05
sil2100cwayne: yeah, I guess that's a +1!17:05
sil2100robru, slangasek: not sure if I'll be able to join todays hangout ;/ I seem to have issues with the internet, or at least with accessing google17:05
robrusil2100: try chromium? it seems to work better for hangouts17:15
robrusil2100: oh I need to coordinate with you: so I'm done hacking the build job (for now). are you still working on the publish job?17:16
sil2100Yeah, but I have problems with connectivity in overall, I'm dropping packets to google.com17:16
robruhm17:16
sil2100robru: not yet, but I'm almost done!17:16
davmor2popey: why did you kill it you are meant to cherish it and nurture it like it is a small child, not kill it ;)17:17
sil2100Still writing tests for the new bits17:17
cwaynesil2100: davmor2: pushed, thanks guys17:17
cwaynenow there will probably be a new one on monday :P17:18
robrusil2100: cool, no worries. I do need to get on the publish job sooner or later, but it can wait ;-)17:18
dbarthogra_: it's in ubuntu-rtm yes17:24
dbarthogra_: https://launchpad.net/ubuntu-rtm/+source/oxide-qt17:24
brendandbzoltan, let me check17:28
brendandbzoltan, is it urgent to land today?17:29
bzoltanbrendand: would be nice17:31
bzoltanbrendand: so we can sync the trunk tomorrow and it could land on an rtm image17:32
dobeyare the lines in the spreadsheet for syncs from one distro to the other supposed to include the MP lines now as well?17:34
sil2100dobey: no, no MPs needed there17:38
dobeythat's what i thought. i saw a couple that had MPs listed there though17:39
sergiusensfginther: any reason http://s-jenkins.ubuntu-ci:8080/view/click/job/account-polld-ci/ is not running?17:39
sil2100dobey: yeah, we usually clean those up before assigning17:41
sil2100What the heck17:58
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: s-jenkins need to be restarted. Please inform robru of all build failures today.
fginthersergiusens, We need to bounce s-jenkins. the trigger jobs were stopped a little while ago to stop incoming work18:01
sil2100slangasek, robru: I'm trying to connect right now18:01
sil2100Ffffff18:03
sil2100slangasek, robru: ok, quick modem reset18:04
sil2100brb18:04
AlbertA2trainguards: can I get a silo for line 84?18:04
robruslangasek: meeting?18:06
=== gatox_lunch is now known as gatox
fginthersergiusens, s-jenkins is up again, that job should start soon18:26
=== fginther changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Please inform robru of all build failures today.
sergiusensralsina_: ^18:26
sergiusensfginther: thanks18:26
ralsina_fginther: thanks18:27
kgunnOoo ooo ^ silo rtm11 ready to publish!18:40
sil2100!18:45
sil2100kgunn: publishing :)18:45
kgunnlool: ok...so sorry, so many interupts...but yeah, looks like those same tests are failling in the virgin image18:51
kgunnso i'm gonna say this tests ok18:51
kgunnno regression18:51
sil2100o/18:57
kgunnrobru: line 59 on the sheet actually that one ^ silo003, can you set me up an rtm sync ?19:02
kgunnthanks19:02
AlbertA2trainguards: can I get a silo for line 84?19:09
sergiusensrobru: can we setup a sync of http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-022 to utopic?19:10
robrukgunn: you got rtm2319:12
kgunnthanks19:13
robruAlbertA2: utopic 1219:13
robrusergiusens: utopic 16, and congrats on being the 2500th silo assigned19:14
robrukgunn: you're welcome19:15
thostr_can I get a silo for line 81?19:16
robruthostr_: utopic 1719:17
thostr_robru: thanks. then another one for line 82? this is for fixing the blocker about the broken picture thumbnails19:19
robruthostr_: yeah build the utopic one first, the sync can come after19:21
thostr_robru: ok19:21
cwaynekgunn: any reason for line 67 to not have a silo yet? would love to test many of those branches..19:41
kgunncwayne: it's up next in fact.... robru if you have a spare ^19:41
kgunnrobru: also, in row 29 "small unity8 fixes" can get an rtm silo now that silo11 is cleared out19:43
robrukgunn: ok, row 67 got 1919:43
robrukgunn: line 28 you mean? 29 landed19:46
kgunnrobru: which ever has the title "unity8 small fixes"19:46
robruright19:46
robrukgunn: i'll have to get back to you on that one, spreadsheet is imploding19:47
kgunnrobru: np :)19:47
robrukgunn: ok utopic 1119:49
bregmais it imploding or exploding?19:49
bregmasideploding19:50
robrubregma: definitely an implosion, it's collapsing under its own weight. it may have enough mass to achieve a singularity19:50
bregmamore likely just collapse into a neutronsheet, or maybe even a brown dwarf19:50
kgunnbregma: lol19:51
* kgunn now has to imagine implosion vs http://www.youtube.com/watch?v=jdn8gQkHyHI19:52
tedrsalveti, Are you going to land the indicator-sound branch for the profiles?20:00
tedrsalveti, Want to rebase a couple branches on that, it would be easier if it was in trunk :-)20:00
cwaynefginther: so could I try to build clicks with click-buddy on s-jenkins? (i.e. will it be installed at all on those machines)20:01
fginthercwayne, I'll get back to you shortly20:02
cwayneok thanks :)20:02
ToyKeeperLaney, seb128: So, the glib silo (rtm-015) needs some sort of test plan, and confirmation via testing that it actually fixes the bug it's supposed to fix.  Probably also a means of retesting the wakeups in the future to detect regressions.20:06
alecuthat sounds wrong... line 84 is building on silo rtm-2620:10
ToyKeeperLaney, seb128: On the desktop it's usually okay to pull new revs from upstream without much testing, especially early in the release cycle, but the phone is much more strict (especially this close to release).20:10
seb128ToyKeeper, not sure what would be a test plan for that "run the phone, make sure it keeps working as before"20:11
seb128ToyKeeper, no need to give a speech on how the phone is stricter than the desktop20:11
ToyKeeperseb128: A good start would be "here's a way to measure wakeups before/after the change".20:11
seb128ToyKeeper, no idea how to do that, you would have to ask to the people who filed the bug20:12
seb128ToyKeeper, we got an update from upstream that fixes the issue, but no idea how to reproduce it20:12
ToyKeeperseb128: Do you have a link to the bug?20:14
ToyKeeperseb128: QA can't sign off until the changes are testable and documented in a test plan or AP test suite or unit test or performance test somewhere that it won't be forgotten.20:16
seb128ToyKeeper, ok, feel free to keep the phone eating power through wakeups then, your call20:17
seb128that update is coming from upstream and fixing things20:17
seb128even if we don't have specific steps to trigger the issue20:17
alecuseb128: ToyKeeper: I think we are all a bit exhausted with deadlines20:18
ToyKeeperseb128: You could ask jfunk for an exception.20:18
alecuseb128: but I understand that it's our job as landers to test the silos to make sure they fix the things that they are supposed to fix. That includes finding out how to test it, to try to make QA's life easier20:18
seb128alecu, well, I don't know how to make a testplan for a lib like glib20:19
seb128it's used by most processes on the phone20:19
seb128so it's basically "use the phone, run all the tests"20:19
seb128which is what we wrote on the landing ask20:19
alecuseb128: I wouldn't know how to do that too. But it sounds to me that there must be a way to test that specific thing that's being fixed20:19
ToyKeeperIt is indeed difficult to test core libs.  It at least needs a way to test the specific issue it's fixing though.20:19
seb128well, I don't know how to reproduce/test it20:20
seb128I just can say the update includes an usptream fix20:20
ToyKeeperCan you find out how to test it?20:20
kenvandineToyKeeper, i've improved the updates portion of the settings test plan20:20
ToyKeeperkenvandine: Sweet, thanks!20:20
seb128ToyKeeper, I guess, but I don't have the free slots for that20:20
seb128ToyKeeper, so either we take the fix or not, your call20:20
kenvandineToyKeeper, it's still one scenario, but more thorough20:21
kenvandinei'll add more for install all/pause all along with landing fixes for  bugs in those :)20:21
ToyKeeperkenvandine: I should be ready to start on that as soon as I have my phone reflashed and the silo installed.20:22
seb128ToyKeeper, one corresponding bug is https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/130813020:22
ubot5Ubuntu bug 1308130 in indicator-messages (Ubuntu) "indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist" [Low,Confirmed]20:22
seb128ToyKeeper, you can maybe ask cking to help since he reported the issue?20:22
ToyKeeperseb128: QA is a tiny team and doesn't have enough cycles to write the tests for everyone else's changes.  QA is mostly making sure the dev teams are doing proper testing.20:26
robruok, spreadsheet statuses restored.20:27
seb128ToyKeeper, right, well other teams are also small and might not have the resources to write tests for every bugfix backported from other upstreams20:27
seb128ToyKeeper, so we have the choice to test for regressions and test the fix, knowing it likely fix the issue and doesn't create new one or just reject it because it has no proper testcase and keep a blocker bug in the rtm20:28
seb128ToyKeeper, I'm not the one who asked uploads to be gatekept by the qa team there, just trying to help getting issues resolved20:28
ToyKeeperseb128: I'll see if cking can help, but for now it's blocked pending tests (from cking, seb128, or Laney) or an override.  It's not actually my call.20:28
seb128ToyKeeper, nor mine20:28
pmcgowanToyKeeper, do you know how the daily power test results are done20:29
pmcgowanthats the reference in the bug20:29
ToyKeeperpmcgowan: No, sorry, I'm not really involved in the performance testing.20:30
pmcgowanToyKeeper, seems the test plan is to run that on the silo, who would know?20:30
thomipmcgowan: are you referring to the battery discharge tests, as documented on the RTM readiness report? or something else?20:34
thomipmcgowan: oh wait, I see now, sorry, ignore me :D20:34
thomiI'm pretty sure that's cking's baby20:34
pmcgowanrobotfuel, we have a fix for https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130 in a silo and want to run the daily power tests to validate it20:37
ubot5Ubuntu bug 1308130 in indicator-messages (Ubuntu) "indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist" [Low,Confirmed]20:37
pmcgowanif that makes sense20:37
pmcgowanrobotfuel, the fix is a new glib in silo rtm-15 and QA here was unsure how to test it20:38
jfunkpmcgowan: not to be pedantic, but it seems everyone is unsure how to test it20:39
jfunknot just QA ;)20:39
robotfuelpmcgowan: okay all the power tests take more than a day, due to lack of resources, but we should be able to tell from the screen off quiet and the screen on quiet tests.20:39
pmcgowanjfunk, fair enough :)20:40
pmcgowanrobotfuel, would you validate that or can you tell us/ ToyKeeper how to do it20:41
kgunnted: yo, you gonna land that silo that has unity8 in it very soon ?20:41
kgunnlike tonight ?20:41
robotfuelpmcgowan: I can do that, I'll talk to toykeeper20:42
pmcgowanrobotfuel, awesome thanks20:42
ToyKeeperkenvandine: Sorry, it's looking like your silo might be delayed a bit.  :(20:42
tedkgunn, 13?20:42
kgunnted: yeppers20:43
tedkgunn, No, that's just an integration silo, mterry's branch isn't finished in there.20:43
kgunnted: ah-ha...good, so i can proceed20:43
kenvandineToyKeeper, problems? or did something else jump in front of me in line? :)20:43
tedkgunn, Yes20:43
pmcgowanToyKeeper, kenvandine oh heck, I didnt mean to do that20:43
mterryted, kgunn: sorry!  working on it, but i've got weird issues with it20:43
kgunnmterry: no prob, just trying to clear out some of our backlog20:43
mterryted, also, you might want to reconfigure/rebuild that silo from latest chagnes20:43
tedkgunn, Sorry, it says "ignore this branch" in the spreadsheet, it just doesn't carry over well.20:44
mterryslightly smoother now20:44
ToyKeeperkenvandine: Depends on if we find a way to test glib soon.20:44
kgunnyeah i was on dashboard20:44
tedmterry, Cool, I'll rebuild.20:44
robotfuelpmcgowan: it might be good to send an email to cking to ask him to test the silo tomorrow morning, he has some special equipment to measure power consumption.20:44
mterryted, only sticking point now is that it takes a bit for some of the menu content to regen20:44
kenvandineToyKeeper, haha... pmcgowan was bugging me about when it would land... now he's bumping me down in the queue :)20:45
pmcgowanrobotfuel, thats fine with me20:45
pmcgowanrobotfuel, mind emailing him?20:46
robotfuelI'll send an email20:47
robotfuelpmcgowan: ^20:47
pmcgowanthanks robotfuel20:47
ToyKeeperI'd definitely prefer if cking could do it, since he has the tools and background for it and it seems no one else does.20:47
pmcgowanthats fine20:47
pmcgowanToyKeeper, he can test if it fixes the issue but not if there are side effects I'd say20:48
pmcgowanbut maybe also some of that20:48
ToyKeeperpmcgowan: Definitely.  I'm planning to do the daily image test on it as a system-wide sanity check.20:49
pmcgowangreat20:49
brendandrobru, can you make the spreadsheet behave please?21:06
brendandrobru, we keep getting duplicate cards i suppose because it's flicking back and forth between the QA sign-off state21:07
robrubrendand: http://38.media.tumblr.com/tumblr_lyjjr8cbwp1r34qiso1_500.gif waving my magic wand just for you buddy21:08
brendandrobru, but seriously, this only started happening in the last couple of days21:11
robrubrendand: oh did it? funny I must have been hallucinating for the last 6 months then because the spreadsheet is *CONSTANTLY* reverting state and generally throwing away critical information.21:14
robrubrendand: you're a total nutjob for wanting to write code that integrates with this. just delete it.21:14
robruthe spreadsheet is going away anyway so you'll need to write new code to read from the new thing anyway21:14
asacanyone knows if this glib landing can be backed out?21:22
asacLaney: is it an abi bump etc.?21:23
robruasac: the glib landing isn't even in RTM21:25
fginthercwayne, click-buddy is installed on the armhf boxes, but it's the trusty version21:28
cwaynefginther: ah, hm, any idea how different they are?21:28
sergiusenscwayne: only misses the --allow-untrusted for installing on target21:29
asacrobru: i see a silo here: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=21:30
fginthersergiusens, thanks, I was getting ready to read through bzr logs21:30
asacrobru: let me rephrase, i wondered if the landing intend is something that can be backed out in case we land it21:30
asace.g. abi bump etdc.21:30
sergiusensfginther: much easier to grab the debs for each and compare the included click-buddy with a diff :-)21:30
fginthercwayne, installing to the target wouldn't be useful here, there are no devices attached :-)21:30
robruasac: oh I have no idea how easy that would be to revert. i thought you thought it was landed already and wanted to back it out21:31
fginthercwayne, sounds like it should work, if there are problems we can investigate21:32
asacrobru: no, just want to figure what risk we can take to understand how we go about bootstrapping a formalized glib testplan21:36
cwaynefginther: sergiusens: excellent :) i'll try it out21:36
robruasac: ah, ok. not sure, better ask Laney then, sorry21:37
cwaynefginther: /tmp/hudson6281116677040042202.sh: 2: /tmp/hudson6281116677040042202.sh: click-buddy: not found21:39
cwayneoh the armhf boxes21:39
cwaynefginther: actually still seeing that on calxeda21:41
cwayneah it works on calxeda-pbuilder, but doesnt have the right framework :/21:42
LaneyWhat do you want to know?21:43
LaneyThere's no ABI break, that would be madness in the case of glib and you'd definitely know about it.21:43
cwaynesergiusens: where do the click frameworks actually come from?21:48
cwaynei.e. which package21:48
asacLaney: just to give you context (without implying anything at this time), the way we bootstrap landing gate testplans is that the landers start a pretty simplistic testplan that captures what they think is reasonable to protect us from majority of regressions we might encounter (after all the component owner knows best how his component is used in stack and what parts are a bit flaky and hence what hotspots in the stack we might21:50
asacLaney: then if we find regressions in image testing after landing, we improve the gate smartly (aka learning testplan rather than a blank "test all"); since glib never did landings before, our knowledge about how a smart testplan looks like is very constrained and since we cannot afford any big risk, we can only really do that in this way if we are sure we can get rid of a regression coming out of it through a backout.21:50
asacif we canot backout there are two choices: a) nothing changes for lander and we just frontload the QA image testing on the silo; b) land a cherry pick fix so we can back out21:52
LaneyCan you show me one for a base library?21:52
asacLaney: depends how you define base libraries. good set of what you consider base libraries are in the same situation as glib because they were always direct uploaded by core-devs which means that we have no organically grown testplan (which is really unfortunate given the level of risk averseness we have at this point where customers constantly expect better deliveries)21:54
asacso i would like to use glib to maybe figure how we can do that as i expect there might be other libraries coming21:55
asacat even more unfortunate times21:55
asacanyway, there are components that are deep in the stack that have test plans grown organically21:55
asaclet me find some21:55
asacLaney: given the nature that we grow as we go and start small, stuff that is stable usually doesnt need full testing. so https://wiki.ubuntu.com/Process/Merges/TestPlan/platform-api is pretty much something central is still reasonable21:57
asacLaney: other extreme is uitk which broke everything here and then over time, so we run basically all APs etc. on it21:58
asacLaney: https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit21:58
asacI cannot remember glib breaking stuff here and then.21:58
asacso i think its pretty stable21:58
asacthere were glitches that broke everything at once, but those would have been caught by just running a single AP test21:59
asacand boot system21:59
asacand do something like using systemsettings or so21:59
asacanyway, the whole thing is that we start with something the lander feels gives him some level of confidence in a formal manner so we can learn over time and tweak, improve etc.21:59
asacLaney: https://wiki.ubuntu.com/Process/Merges/TestPlans/22:00
asacthere are loads of testplans under that22:00
asacimo you guys are most familiar with glib and know which areas are rock solid22:00
asacand which areas are causing grief22:01
asac(a few years back i would have suspected that the gio part is flaky so i would have probably checked if there is anything very basic i can do to exercise that that part works)22:01
=== robru changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Please inform robru of all silo assignment/reconfigure failures today.
asacotherwise, just think how glibt is used and which main submodules are used by which app in our touch stack22:01
asacso lets say gio is used by app X, just say: start app and see that X works22:02
fginthercwayne, I believe this error is caused by not having the necessary schroots (which makes sense as these machines have none)22:03
asactell me what you think we could do that makes sense. as i said would really much would like to use this to understand what we would do in case another base library comes even later during our product crunch22:03
cwaynefginther: makes sense22:04
asacLaney: looking at the bug and that its marked low prio we can also continue talking about this on monday (tomorrow is pub holiday)22:04
Laneyasac: Alright, well we can talk about this in the team tomorrow and see what we think.22:06
asacLaney: thanks. just repost the lines i wrote. as i said its something new. so far we only dealt with base libraries taht are under heavy development22:06
asacby ourself22:06
asaclike uitk22:06
asacso folks automateically believe that all these base libraries need to have everything run at the gate automatically22:07
asacbut i dont think thats the case for the parts in our stack that are super stalb22:07
asacbut we have no data besides the incidential "all broken firedrills" due to big glitches that can happen on those22:07
asacimo we should just apply what we always do. you guys think what would be a good start and then se how this evolves over time22:08
asacand as long as we can backout the risk of not knowing things is bearable22:08
LaneyThere's a lot of random stuff in the stack that is actually pretty mature software22:08
asacjust land early in day and if there is a regression, back it out, figure if there is a smart stitch to protect etc.22:08
asacLaney: exactly22:09
LaneyI think that if you have this feeling about a change you want to make then a very heavyweight process is going to feel like quite a drag22:09
asacLaney: so i am sure if we start light, we will protect from the bit glitches and we wont have a big testplan22:09
asacLaney: what i describe above is very lightweight. its just writing up whatever you feel are reasonable test steps that help you feel confident that all will be good22:09
asacanyway, run that through team22:10
asacand lets chat monday22:10
Laneyk, thanks for info22:10
loolkgunn: sorry, so what' the plan WRT trust-store? is this delayed to tomorrow?22:12
looltrainguards, would you mind assigning a silo for line 68 (roaming location-service fix); this one needs a separate PPA while it's being tested by HERE folks22:20
loolhopefully tomorrow morning if I can get a silo now  :-)22:20
robrulool: utopic 322:27
loolrobru: ty22:28
robrulool: you're welcome22:28
kgunnlool: i landed in utopic, and marked it ready for qa in rtm23:28
loolthanks23:28
looltrainguards, any free silo for utopic / line 74?23:29
robrulool: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=location-service how many location-service silos does there need to be, exactly?23:30
loolrobru: the ubuntu-rtm one should be gone...23:31
robruhttp://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=location-service even also ubuntu ;-)23:31
loolrobru: 17:54 < sil2100> lool: oh, ok, so completely freeing line 25, yes?23:31
lool17:54 < lool> sil2100: yes23:31
lool17:55 < lool> sil2100: I've merged into the first landing for l-s23:31
loolrobru: not sure why it's still there23:31
loolrobru: silo 3 is for HERE to test (roaming) and the other one I thought I could land, I've tested the branch successfully yesteryda, but the fix is insufficient23:32
robrulool: well those are rows 11 and 39, surely 25 is not location-service23:32
loolrobru: speaking of the rtm one23:32
loolrobru: it used to be line 2523:32
robrulool: well it's not clear to me whether you want to free row 11 or 3923:33
loolrobru: none of these23:33
robrulool: which is the silo which should not be assigned?23:33
loolrobru: sorry let me start afresh23:34
loolrobru: there was one rtm landing WIP, we gave up on it and repurposed it; it's now the accunulated location related landings23:34
loolso just 1 in rtm, and that's ok23:34
loolbut finishing some utopic landing firsts23:34
robrulool: except that there are two rtm silos assigned for location-service23:35
loolrobru: hmm this silo 020 is completely new to me23:35
looland I am not sure it will land happily in rtm23:35
robrulool: well you'll have to coordinate that with camako then23:36
robrulool: more to the point, the two utopic silos you have are not just 'small fix part of mir landing' or whatever. you have two silos for location-service already. are you sure you can't roll this new one into one of the existing ones?23:37
loolrobru: I dont mind23:37
loolrobru: we could I guess; just not sure either of them will be stuck23:37
loolrobru: you see, the startup fix seemed to work but doesn't; am I supposed to take it back?23:38
loolor fix it?23:38
loolbut that might take some time23:38
looland the other one is ready to land too, it was just waiting for another landing to complete23:39
robrulool: the problem with having three simultaneous silos for a package like this is that a) there are only so many silos, so other people can't get theirs, and b) whichever one publishes first forces the other two to rebuild, which is time consuming and wasteful23:39
robrulool: so if there's any way you can merge the requests I'd appreciate that.23:40
robrubrb23:40
looloh actually I can do simpler23:40
loolsnif, or so I thought23:42
robrulool: ok, I mean if you really insist on a third silo I can do it, but I'd prefer not to23:45

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