/srv/irclogs.ubuntu.com/2014/07/21/#ubuntu-ci-eng.txt

robrucjwatson, Chipaca: https://ci-train.ubuntu.com/job/landing-009-1-build/120/console looking good now, sorry for the hassle there00:04
Chipacarobru: thanks!00:51
Chipacai guess build 120 was wonky in some way too?00:53
robruChipaca, hum, looks like it failed to upload for some unrelated reason. but at least the original problem is fixed. I tried a FORCE_REBUILD in the hopes that it was just a version number issue (force rebuild does a version bump and has a chance of working...)00:55
robruChipaca, yeah, build 121 looks like it's going: https://ci-train.ubuntu.com/job/landing-009-1-build/121/console00:56
Chipacayep, watching it with bated breath :)00:56
Chipacaactually, scratch that, i'm going to catch some sleep00:57
robruChipaca, goodnight!01:00
robruChipaca, ah, looks like you got a test failure there01:11
imgbot=== trainguard: IMAGE 141 building (started: 20140721 02:05) ===02:04
imgbot=== trainguard: IMAGE 141 DONE (finished: 20140721 03:35) ===03:34
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/141.changes ===03:34
veebersrobru, trainguards: Any chance anyones around? :-)05:25
robruveebers, oh hey05:45
veebershey robru, do you ever sleep? :-)05:46
robruveebers, haha, not even 11PM here... ;-)05:46
veebersrobru: :-) I just wanted to check in, 2 things. I've _finally_ marked autopilot release as good to go05:46
robruveebers, I see that, I was wondering ;-)05:47
veebers2nd, I have a libautopilot-qt release setup, I released too late that thomi bottom approved but not top approved before he EOD. I'm hoping you don't mind assigning the silo for it as is so I can get the testing phase underway (as it takes ~3-4 hours)05:48
robruveebers, yeah for sure, we changed citrain so that you only need top-approval to publish, not to build05:48
veebersrobru: ah nice. Thanks for that :-)05:49
robruveebers, thank sil2100, he made that change ;-)05:49
veebersrobru: Do I need to fire off the build or is that done automatically now days?05:49
robruveebers, ah, you still need to kick the build I think05:49
veebersrobru: cool will  do so05:49
robruveebers, not sure if I'm comfortable publishing that autopilot silo, sil should be up soon to look at that.05:50
veebersrobru: ack, no worries05:50
robruveebers, alright, I'm going back to the TV. have fun!05:50
veebersrobru: Thanks again, much appreciated o/05:51
robruveebers, you're welcome!05:51
robruveebers, ^^ you know how to fix that? ;-)05:59
veebersrobru: heh, your supposed to be watching tv. I was waiting for sil or someone to come online to check, but I'm pretty sure that's its because I screwed up in one of my ppas05:59
veebersrobru: i.e. https://launchpad.net/~veebers/+archive/ubuntu/tmp-autopilot-qt-non-visual05:59
veebersthat version should have a ~veebers1 or something after it06:00
robruveebers, huh, that's weird, it shouldn't be getting versions from random PPAs, it should be just looking at what's in the archive.06:00
robruveebers, https://launchpad.net/ubuntu/+source/autopilot-qt yeah that same version is in distro06:01
veebersrobru: that's what I thought, but I pulled trunk and the version in the change log is '1.4+14.04.20140312-0ubuntu2'06:01
veebersrobru: oh, bad assumption on my part then06:01
robruveebers, ah, xnox made an upload. you gotta take this diff: https://launchpadlibrarian.net/175664192/autopilot-qt_1.4%2B14.04.20140312-0ubuntu2_1.4%2B14.04.20140312-0ubuntu3.diff.gz and just push it direct to trunk, then rebuild in the silo.06:02
veebersrobru: does that mean someone pushed directly to arc. . .06:02
robruveebers, yes ;-)06:02
veebersrobru: ah awesome, thanks for the heads up. So I should push that to trunk, not create a MP with those changes?06:03
* veebers looks at the diff06:03
robruveebers, yeah, when people make direct archive uploads, there's no real point to bother with MPs, it's already too late for that. so just push it to trunk and then the build can proceed.06:03
veebersrobru: awesome, I owe you one06:04
robruveebers, hehe, no worries! ok, out for real this time ;-)06:04
Chipacarobru: yes, test failure. Digging into it after I've had my coffee.07:34
xnoxChipaca: hmmm, yes coffeeeee that's what i need!07:53
=== cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #133 promoted | Need CI Train help? Ping: cjwatson, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
cjwatsonsil2100: I won't make the landing meeting today - will be cycling into town, meeting doko to work in a café for the morning08:01
sil2100cjwatson: oh, let mvo_ sheriff today, as it seems he'll be off on Friday so he preferred starting today - if possible08:01
cjwatsonoh?  ok08:01
sil2100Oh, doko in the UK? My my!08:02
cjwatsonI'll let mvo_ take the topic once he's around08:08
=== mvo_ changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #133 promoted | Need CI Train help? Ping: mvo_, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
sil2100Go away heat..!08:12
=== renato is now known as Guest23306
xnoxsil2100: nice and cool overcast here =) we've had boiling hot heat last week though.08:22
sil2100I hope it'll be the same here, I *need* coolness!08:23
seb128xnox, you mean like 25°C? ;-)08:23
sil2100psivaa: hm, what's up with mantas in our latest images?08:23
sil2100psivaa: and I saw some mako tests didn't finish?08:23
psivaasil2100: mantas are both down in adb.. probably dead without charge. i've askes IS to take a look08:24
psivaasil2100: mako health check was still running and i rekicked unity8 tests because we only had 20 unity8 tests (instead of 53) due to a 'string exception'08:25
xnoxseb128: well we actually did have 31 last week.08:28
seb128xnox, nice ;-)08:28
cjwatsonmvo_: ta08:31
mvo_cjwatson: no problem08:31
tvossdavmor2, ping08:42
davmor2tvoss: wassup,  location got good testing last week.  Location found me in seconds on the campsite never failed to amaze me :)08:43
psivaabrendand: http://pastebin.ubuntu.com/7829158/08:46
asacbzoltan: uitoolkit is really bad in dashboard?08:57
ogra_asac, yea08:57
asacdid that thing got landed?08:57
bzoltanasac: nopez08:58
asacogra_: what caused this?08:58
bzoltanasac: ogra_: there was not even a single successful Jenkins job for the UITK for a week. Jenkins is busted badly08:59
ogra_asac, i thought sil2100 discussed that with bzoltan on friday08:59
ogra_asac, we would fix it if we knew :P08:59
ogra_asac, brendand did some research as well as the AP guys08:59
asachttp://ci.ubuntu.com/smokeng/utopic/touch/mako/131:20140715:20140712/9061/09:00
asacthat one is good09:00
ogra_yes09:00
asac132 as well09:00
ogra_133 too09:00
ogra_(we promoted it)09:00
asac134 too09:00
asac135 started09:01
ogra_right, as i said, it is being investigated09:01
asacnoone tried to figure out what caused this on 135?09:01
ogra_it is being looked at since it started09:02
sil2100asac: we're looking at it since it started, and we know more or less what causes it09:02
sil2100asac: and the fun thing is that most of the failures are not caused by any particular landing09:02
bzoltanasac: my previous landing was on last Tuesday09:03
sil2100asac: but caused by a timestamp issue in autopilot that just started happening because the date changed (got big enough)09:03
sil2100Which is very funny09:03
sil2100And there's the qmlscene crash, but it's actively being looked at09:03
asacsil2100: the date changed?09:04
ogra_well, today it turned into system-compositor and unity8 crashing09:04
ogra_davmor2, are you running 133 (devel) constantly somewhere ? i see frequent session restarts09:05
ogra_(once a day at least)09:05
brendandsil2100, apparently we can workaround it in uitk09:06
ogra_sil2100, ugh, i just relaoded the dashboard ... seems the indicator-location crash is back in the four tests09:06
sil2100ogra_: yeah, saw that, it's a promotion blocker so I suppose we need to poke tvoss again ;)09:07
sil2100ogra_: as charles needed some input from tvoss to identify09:07
ogra_yup, tie him up in a corner til he has fixed it09:07
tvossdavmor2, great @location. So can I ask you to give silo 8 a spin?09:28
bzoltansil2100: asac: sorry for the delay... this is one of the bugs what blocks the UITK tottaly - https://bugs.launchpad.net/ubuntu-app-launch/+bug/132914109:32
asacbzoltan: seems thgey want a unity8.log09:34
asacmirv not on today?09:34
ogra_nope09:35
bzoltanasac:  he is on holiday for two weeks09:35
ogra_two weeks vacation09:35
asacSaviq: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141 ... something for your team?09:35
asacqtubuntu09:35
asacseems leo has attached a good repro instruction09:35
asacso gerry could get the log himself easily09:36
bzoltanasac: and this is the other one -> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/132860009:41
* ogra_ wonders if that also happens if you just run with a POSIX or C locale 09:44
ogra_(and default to UTC)09:44
bzoltansil2100: may i get a silo for the line28, please?09:47
sil2100mvo__: ^09:51
mvo__sure09:52
sil2100asac: we already had ricmm and greyback looking at this bug, waiting for them to proceed09:52
mvo__bzoltan: could you please set it to "ready" (column I)09:52
bzoltanmvo__: Ahh... thanks.09:53
mvo__bzoltan: :) this part will ensure  the trainguard s get a ping from the bot09:54
mvo__bzoltan: you have the silo now09:54
asacsil2100: well, greyback asks for a log09:56
asacsil2100: while there are repro instructions... so if he has priority on it, he culd just run and get that log on his own09:56
davmor2tvoss: will do09:57
tvossdavmor2, thank you09:57
davmor2sil2100: looks like manta never completed the update, stuck on the google logo it was the update it was installing before D'oh I'll plug it into the pc and reboot it and see what happens09:58
tvosscjwatson, can I get your vote here? https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/22751109:58
tvosscjwatson, had to take over Steve's MP to explicitly specify the dbus-cpp version to build against09:58
cjwatsonlgtm10:06
cjwatsonbut fix whatever ps-jenkins doesn't like :)10:06
cjwatsonoh, that's just newest dbus-cpp being unavailable, ok10:07
sil2100davmor2: ouch10:07
tvosscjohnston, thanks10:08
tvossdamn10:08
tvosscjwatson, thanks :)10:08
Saviqsil2100, greyback didn't really look at that bug, ricmm did you (re: bug #1329141)10:08
Saviqasac, ↑10:08
SaviqI'm running the steps now, 5 mins in, no crash10:08
sil2100We were poking ricmm hard about this one on Friday10:09
asacSaviq: awesme10:10
asacthanks10:10
asacsil2100: ricmm was sprinting last week; this week he is busy too... have you checked that this regression was caused by an upload of qtubuntu?10:11
davmor2sil2100, ogra: okay so adb seems to be working, nothing in /var/crash where is the best place to look next or who is the best person to talk to about what they mighty need,  Been on the google logo for about 12 minutes according to uptime10:15
sil2100asac: we checked, but there was no qtubuntu upload when this started happening, but it might have been a hidden issue caused by something else - when the crash started happening we landed a fix for a blocker in unity-system-compositor, but we weren't able to exactly find any relation... that's why ricmm was pointed to as the main person that could know more10:16
=== Ursinha-afk is now known as Ursinha
asacsil2100: kk10:22
mvo__sil2100: I'm at lunch now - just to let you know :)10:22
asaclets see if saviq finds something too10:22
ogra_davmor2, sounds like the container doesnt start then10:25
cjwatsonsil2100: How's the RTM stuff going?10:30
camakocihelp: we have the same failure on three different MPs on the mir/0.5 branch... All on armhf... any ideas?10:46
asaccamako: where is such an example?10:47
camakoasac, https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2114/console10:49
davmor2ogra_: mtp keeps restarting10:49
ogra_well, does the caontainer run ?10:49
ogra_*container10:49
ogra_(mtp only reacts to property changes)10:49
ogra_sounds like it is restarting (and thus settiing/unsetting the property)10:50
ogra_davmor2, pastebin the oputput of /system/bin/logcat -d ... and syslog10:51
davmor2ogra_: http://paste.ubuntu.com/7829641/10:52
ogra_there you go10:53
ogra_https://code-review.phablet.ubuntu.com/#/admin/projects/10:53
ogra_err10:53
ogra_W/libEGL  ( 2071): eglTerminate() called w/ 1 objects remaining10:53
ogra_E/libEGL  ( 2071): validate_display:263 error 3001 (EGL_NOT_INITIALIZED)10:53
ogra_(paste error)10:53
ogra_talk to the Mir guys10:54
ogra_davmor2, i'm surprised you dont see the display flashing actually ... seems to restart and die several times10:55
davmor2ogra_: no solid on the google logog10:55
davmor2-g10:55
ogra_yeah10:55
davmor2ogra_: and there is syslog http://davmor2.co.uk/~davmor2/syslog11:00
ogra_Jul 21 10:03:41 ubuntu-phablet kernel: [   32.623884] mali mali.0: state save latency exceeded, new value 1346833 ns11:01
ogra_Jul 21 10:03:42 ubuntu-phablet kernel: [   33.060695] init: lightdm main process (2060) terminated with status 111:01
ogra_Jul 21 10:03:42 ubuntu-phablet kernel: [   33.060784] init: lightdm respawning too fast, stopped11:01
ogra_graphics driver dies ... and then it tries to respawn the container over and over (which causes the adb/mtp restarts)11:02
Saviqsil2100, asac, https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141/comments/1511:03
ogra_davmor2, so thats either an android update ... (wait for rsalveti to show up) or a Mir issue11:03
asacSaviq: awesome11:04
asacyes for fixing both sides :)11:04
sil2100Saviq: o/11:04
asacis this random tmp thing a new feature?11:04
asacso who is fixing the underscore thing?11:05
asactedg: ^^11:05
davmor2ogra_: will do :) /me curses rsalveti for daring to not be online when I have issues that need diagnosing :D11:06
ogra_yeah, these americans ... sleeping all day11:06
Saviqasac, I'm looking into UITK11:07
Saviqasac, it's not new, it's just... random ;)11:07
* sil2100 needs to lay down for a moment11:08
asacSaviq: hmm. started with build 13411:08
asacso maybe we have multiple issues here ... one that is random11:08
Saviqasac, something probably changed there11:08
asacone that is repro11:08
Saviqasac, but the quick solution is still valid11:08
asacyeah11:08
Saviqasac, and then we can investigate11:08
asacthis one sounds sensible11:08
asacSaviq: uitk is creating the randomstring?11:09
asacnot ual?11:09
Saviqasac, yes11:09
asacsh ok11:09
asacsh11:09
asacah11:09
asac:)11:09
Saviqasac, UITK creates a fake app11:09
asacbzoltan: ^11:09
asac13:02 < Saviq> sil2100, asac, https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141/comments/1511:09
bzoltanasac: Saviq: let me check that out11:10
Saviqbzoltan, tests/autopilot/ubuntuuitoolkit/fixture_setup.py:8411:12
Saviqbzoltan, doesn't look like you can easily tell it to not use underscores...11:14
bzoltanSaviq: yes11:14
Saviqmaybe we can rename it after it's created11:15
bzoltanSaviq: I hate all these modern libs ... :)11:18
Saviqbzoltan, it did discover a real bug, though ;)11:24
bzoltanSaviq: :D how true11:24
ogra_bugs ? there are no bugs !11:25
ogra_they are just features in camouflage ...11:25
ogra_(or was that the other way round ?)11:26
sil2100;D11:27
ogra_davmor2, so looking at the test results manta seems to have started failing with 137 .... which at the same time was shipping the new Mir 0.511:40
ogra_davmor2, would probably good to confirm that it works with 136 and breaks with 13711:41
davmor2ogra_: will do, playing catchup on correspondence at the minute.11:41
davmor2ogra_: 136 is working12:04
ogra_davmor2, so 137 should fail :)12:04
davmor2ogra_: installing it now12:05
brendandsil2100, the messaging-app failure is reproducible by the way12:41
tvossdavmor2, ping12:45
davmor2ogra_: 137 is broken on manta12:46
ogra_davmor2, great, thanks ! so it is in fact the Mir update i guess12:46
ogra_tell #ubuntu-mir to fix it ;)12:46
davmor2tvoss: sorry bunch of manta tests and Lunch back now, silo 8 is next on the list12:47
tvossdavmor2, awesome, thank you :)12:47
tvossdavmor2, the sooner, the better12:47
tvossdavmor2, quite some components in there12:47
* sil2100 is at lunch still12:48
davmor2tvoss: is there some instructions then so I know everything is installed? Or should it all be covered from and dist-upgrade?12:48
sil2100davmor2, ogra_: could you just overview what's the manta status? Is it completely broken since 137?12:48
tvossdavmor2, I would propose citrain device-upgrade 812:48
ogra_sil2100, yeah, the graphics driver falls over with the new Mir it seems12:49
sil2100ogra_: but didn't we get some test runs in smoketesting for manta that were ok?12:49
ogra_not since 13712:50
sil2100uh12:54
sil2100Damn, we should REALLY look at non-mako platforms everyday12:55
sil2100Since I missed this for instance12:55
sil2100psivaa: in case I forget about this, could you maybe make sure we at least look if all our platforms had all tests running?12:55
ogra_manta is difficult lbecause it never charges enough in the lab12:57
psivaasil2100: ack, will do. that. not sure if i'll be having enough time to do that before the landing meeting though.. I guess i could do it after the meeting12:58
tvossdavmor2, and the silo contains packages built with a new toolchain. So testing instructions as "simple" as: "test everything"12:59
rsalvetiogra_: mir 0.5 also broke the hammerhead image: bug 134319813:21
rsalvetiso yeah, it'd be good to test such landing on more devices (not necessarily hammerhead)13:21
rsalvetibut at least mako, flo and manta13:21
rsalvetiops, wrong bug13:21
rsalvetibug 134553313:22
ogra_no bot ?13:24
rsalvetivacation maybe13:27
ogra_ah, yeah, its summer in the northern hemisphere13:29
ogra_summer vacation then ...13:29
mvo__sil2100, Chipaca: hm, when I try to publish landing-009 I get: "2014-07-21 13:30:32,492 ERROR Some merge requests are not yet approved. Please review all merges and re-run the build job"13:31
Chipacamvo__: hm? wha?13:31
Chipacado I have to +1 something?13:32
mvo__Chipaca: yeah, very odd, let me look over the branches13:32
sil2100Yeah, it means there's a branch that's not yet Approved13:32
mvo__Chipaca: https://code.launchpad.net/~chipaca/ubuntu-push/the-push-automatic/+merge/227420 is in state "needs review", someone needs to set it to approved13:33
* Chipaca approves13:34
Chipacathere13:34
oSoMoNsil2100, hey, can silo 12 be published, please?13:36
mvo__Chipaca: thanks, its happier now, looking over the debdiff of the debian changes (https://ci-train.ubuntu.com/job/landing-009-2-publish/44/artifact/packaging_changes_ubuntu-push_0.49+14.10.20140721.1-0ubuntu1.diff) I can see e.g. changes in what looks like a already released debian/changelog stanza. is this on purpose or a accident?13:36
mvo__oSoMoN: I can publish it if everytihng is ready and tested13:36
sil2100mvo__: ^ can you take a lookie once you're free? ;)13:36
oSoMoNmvo__, it’s ready and tested indeed, all it needs is publication13:37
Chipacamvo__: it might be? can you point me at the line?13:37
mvo__Chipaca: the bits after "@@ -11,6 +64,10 @@"13:37
mvo__oSoMoN: thanks! publishing now13:38
mvo__Chipaca: there is also a "+  [ John R. Lenton ]\n[Samuele Pedroni]" at the beginging of the changelog, but that could be a merge artifact, not sure if you can do much about it13:39
oSoMoNmvo__, thanks13:40
mvo__Chipaca: other than that the debian/* changes look fine13:42
Chipacamvo__: sorry, was in a meeting and couldn't focus on this and that at the same time. What artifact are you referring to when you say "@@ -11,6etc"?13:44
* Chipaca is in a maze of diffs, all different13:44
Chipacamvo__: i saw the [john]\n[samuele] thing, wondering if it's worth fixing -- last couple of merges the names were stripped out anyway13:46
Chipacamakes reading the changelog harder, but eh13:46
Chipacadammit, you pointed me *at* the diff13:48
* Chipaca reads that13:48
Chipacamvo__: that seems like a bad merge, possibly our side of things13:49
mvo__Chipaca: yeah, the [joh]\n[samuele] is just costmetic, the other one is more important to not add entries that are not really valid :)13:49
Chipacamvo__: those same lines (different wording) are in the right changelog13:49
Chipacamvo__: i need to fix the branch, and re-build. Give me a few.13:51
mvo__Chipaca: no problem, just let me know when you are ready and I'm happy to click the right button13:51
fginthercamako, looking at the scripts in lp:~mir-team/+junk/mir-medium-test-runner-for-jenkins and the console log. Those tests are getting stuck here: exec_with_adb_user "/sbin/initctl stop unity8"13:52
fginthercamako, and then the build timesout out waiting for that to return13:53
=== psivaa is now known as psivaa-afk
davmor2tvoss: there is a regression in mediascanner, it is not collecting artwork/showing the music title for an age http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150018.png  this then became http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150207.png just before the screen blanked so 45-55 seconds.14:03
tvossdavmor2, ack, let me look into it14:04
tvossdavmor2, is that an otherwise unknown regression?14:06
davmor2tvoss: let me double check, I think previously it showed the title and the music notes in a blank tile if it didn't know or until it updated14:07
davmor2tvoss: yeap like this http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-21-150837.png  note the title only appears on the one at the front but you get the idea of what I'm used to seeing while it refreshes.14:10
davmor2tvoss: which is what is happening now for a group of say 20 or so at a time with the screen nearly blanking on each group14:11
tvossdavmor2, ack14:11
sil2100geh, I feel bad today...14:15
ogra_xnox, do you do the meta upload too (for indicator-transfer) ?14:21
xnoxogra_: no, merge only.14:23
xnoxogra_: not that urgent to land.14:23
=== barry` is now known as barry_
=== barry_ is now known as barry
tvossdavmor2, mediascanner2 rebuilding in silo14:28
davmor2tvoss: nice14:30
=== psivaa-afk is now known as psivaa
Chipacamvo__: done14:41
Chipacaqueuebot: you so slow lol14:41
mvo__Chipaca: thanks, on it14:42
=== greyback is now known as greyback|away
tvossdavmor2, should be upgradeable14:55
cyphermox_ChickenCutlass: seb128: brendand: let's land ubuntu-system-settings for the bluetooth updates today hopefully...14:56
cyphermox_brendand: I've updated the manual tests document14:56
seb128cyphermox_, no14:56
ChickenCutlassyes let's land asap14:56
cyphermox_seb128: any other things you'd like to land in u-s-s?14:57
seb128cyphermox_, there is a landing we just put in the landing queue and I'm reviewing your changes and have needs fixing comments coming14:57
cyphermox_ok14:57
cjwatsonbfiller: How's silo 1 looking?14:58
bfillercjwatson: I commented in the landing sheet14:58
bfillercjwatson: ready to go from my perspective, just wanted clarification of steps. Typically we release the silo then generate the click from trunk once it's merged14:59
cjwatsonbfiller: We can't in this case, circular14:59
bfillercjwatson: right14:59
bfillercjwatson: should I manually merge to trunk then generate and upload click?15:00
cjwatsonbfiller: Can't go on trunk until it's in utopic, can't reach utopic until we unblock the exiv2 transition, can't unblock that transition until we have this in the store15:00
davmor2tvoss: got it now let see what happens15:00
bfillercjwatson: shall I upload the version that I built in jenkins?15:00
cjwatsonbfiller: Couldn't we release this to utopic-proposed, and then generate the click package from ~ps-jenkins/gallery-app/utopic-proposed?15:00
cjwatsonOr from something equivalent15:01
cjwatsonAt least that way it's clearly on track15:01
bfillercjwatson: that sounds like a plan15:01
davmor2tvoss: that looks better :)15:01
tvossdavmor2, awesome15:01
bfillercjwatson: can you take care of that and ping me once it's in proposed and I can generate the click and upload15:02
cjwatsonbfiller: Hm, important to make sure versions are correct I guess15:02
cjwatsonbfiller: the utopic-proposed branch has slightly fewer revisions than trunk does due to translation updates automatically committed to trunk15:03
cjwatsonbfiller: So maybe a manual merge to trunk would be safest, so that it correctly comes out as revision 1017 ...?15:03
bfillercjwatson: that works15:04
cjwatsonsil2100: ^- do you see any problems with this plan?15:04
=== greyback|away is now known as greyback
sil2100cjwatson, bfiller: I didn't backlog everything, but we could wait for it to get to utopic-proposed and then force merging it to trunk (as if it was released) and roll out a click package from trunk?15:05
cjwatsonRight, that was the plan15:05
sil2100cjwatson, bfiller: so just using CI Train for that15:06
cjwatsonbfiller: OK, I'll go ahead and release this to -proposed15:06
cjwatsonsil2100: Oh, for the merge as well?15:06
sil2100cjwatson: yes, you can force the merge and clean to merge the change even though it didn't reach the destination yet15:06
sil2100We do that for some SRUs15:06
sil2100If we know that it's in -proposed and passed all verifications for bugs, we allow merging it in already15:07
cjwatsonI guess so - we just need to make sure not to build gallery-app again until the transition's done15:07
sil2100Ok15:07
sil2100Indeed15:07
cjwatsonWhich is now a matter of hassling the security team until they review an MIR15:07
seb128cyphermox_, ok, commented with a list of need fixing15:09
seb128cyphermox_, I didn't code review, just played with it a bit15:09
cjwatsonargh some more blockers have appeared15:09
seb128cyphermox_, but commenting anyway if you want to start working on fixing some of the issues15:09
cyphermox_seb128: sure15:09
cjwatsonhate hate hate15:09
sil2100brendand: btw. any luck with the autopilot timestamp thingie?15:09
tvossdavmor2, do you keep on testing?15:10
davmor2tvoss: yeap lot to test, Everything :)15:10
tvossdavmor2, lol15:10
brendandsil2100, i'll talk to elopio about working around it. that's the only option at the moment15:11
balloonssil2100, I was just asking about that :-) I pushed a workaround for the toolkit tests at least on friday15:11
davmor2meh never noticed that before me files a bug for the teams to unify on names.15:11
Laneyseb128: you took out the test fixes?15:13
seb128Laney, what where?15:13
LaneyI thought I saw them in the uss landing15:13
cyphermox_seb128: sounds like your bluetooth is broke too15:13
sil2100balloons: hi! For the timestamp problems? :)15:13
seb128Laney, which ones?15:14
Laneyoh wait15:14
balloonssil2100, yes..15:14
seb128Laney, silo 004 has it?15:14
Laneyline 31 is another one15:14
Laneygot confused15:14
sil2100hmmm15:14
seb128cyphermox_, "too"?15:14
sil2100balloons: we still have tons of failures, so I thought we didn't have any workarounds for that one15:15
balloonssil2100, it hasn't landed but it works. I'll work on getting the sdk team to review15:15
seb128Laney, silo 004 is good for you then?15:15
sil2100Oh15:15
davmor2sil2100: in the lack of a popey for confirmation can you quickly drag down the network indicator no the name mobile settings click on it and then tell me the name of the section it takes you too please15:16
cyphermox_seb128: part of the issue seems that your bluez may not have started properly15:16
Laneyseb128: just wanted to check if the replaceme worked15:16
sil2100balloons: how many failures does it fix?15:16
seb128Laney, let me know if it does ;-)15:16
Laneyseb128: looks right15:17
seb128great15:17
cyphermox_seb128: wait, scratch that, that's the remote device15:17
balloonssil2100, it will allow the UITK to pass again. thomi rejected my change to AP to fix everything ;-) Looks like it's harder than my proposed fix15:17
sil2100davmor2: hm, I would have to re-flash my phone, can you wait for that?15:18
davmor2sil2100: it's possible in any image so that shouldn't be an issue unless you flashed android back on it ;)15:18
sil2100Ah, oh!15:19
ogra_yay, statically linked gallery-app15:20
ogra_\o/15:20
ogra_cjwatson, so theoretically we should be ablke to unseed exiv2 now15:20
sil2100davmor2: I clicked Cellular settings and it takes me to the Cellular section15:20
sil2100davmor2: when clicking on Wi-Fi settings it takes em to Wi-Fi15:21
davmor2sil2100: ah it is a recent change then that's why I didn't see it before, I wonder if it is english GB as language setting from the welcome screen15:22
davmor2sil2100: I see mobile settings instead of cellular and then it takes me to the cellular page in the settings app15:23
cjwatsonogra_: Right, I know, just waiting for a couple of other things15:23
sil2100Oh, ok, well... my image is quite outdated so maybe it changed now15:23
cjwatsonogra_: Do we normally silo ubuntu-touch-meta or just upload directly?15:23
ogra_just directly15:23
ogra_onyl if it is a bunch of packages that also live in a silo we use silos for it15:24
davmor2brendand: what do you see in network indicator mobile settings or cellular settings?15:24
ogra_single additions/removals dont really need a silo15:24
brendanddavmor2, Mobile settings15:24
cjwatsonogra_: OK.  We shouldn't unseed this until after the new gallery-app is in the store, but I can deal with it after that.15:25
davmor2brendand: and did you pick English_GB when setting up the phone?15:25
ogra_cjwatson, great, thanks !15:25
cjwatsonogra_: (Note it's not entirely statically linked, it just statically links that one library, for now)15:25
ogra_yeah15:25
brendanddavmor2, yes. because i speak english, and i'm in the uk15:25
ogra_i saw the code change15:25
cjwatsonSomebody owes me the hour of my life I spent figuring out how to do that in cmake15:26
davmor2brendand: I'm click on mobile settings and see where it takes you :)15:26
sil2100ogra_: ok, so I don't feel to well today, could you lead todays meeting? I'll compose an e-mail later on, there's just some small things to discuss today anyway15:26
sil2100ogra_: just that there's progress on the UITK front15:26
brendanddavmor2, to Cellular page in u-s-s15:26
davmor2brendand: So not the Mobile page then ;)15:27
sil2100ogra_: btw. how's the manta situation? Did the Mir guys mention anything?15:27
ogra_sil2100, right, i think thats our major issue today15:27
brendanddavmor2, nope15:27
ogra_sil2100, yeah kgunn has put the right people on the task15:27
ogra_it is all handled fine15:27
brendanddavmor2, probably because there's no such thing :)15:27
sil2100ogra_: as mentioned above, with UITK we have both issues almost done, at least well identified... the UITK autopilot issues are worked-around by balloons, waiting for release, and the qmlscene crash is identified and worked on a fix15:28
sil2100ogra_: kalikiana has a fix for the crash even15:28
ogra_cool !15:28
sil2100Or workaround rather!15:28
sil2100https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/noScores/+merge/227541 <- it's EVIL but I guess that in this case I could even accept it ;)15:29
* sil2100 goes to lay down for a while15:29
kalikianaI figured we'd want to avoid rewriting the whole way to pick unique filenames and possibly hitting other corner cases :-)15:31
brendandsil2100, did balloons submit a workaround for the uitk failures?15:31
brendandsil2100, i didn't see anything15:31
balloonsbrendand, https://code.launchpad.net/~nskaggs/ubuntu-ui-toolkit/fix-1328600/+merge/227394.. MP's go to staging for them, so they might be a bit hidden15:32
balloonsbrendand, elopio pointed out there's one more test to update, so I'll do that now so it passes15:33
=== gatox is now known as gatox_lunch
tvossslangasek, ping15:58
slangasektvoss: hi16:00
brendandsil2100, stuck in another meeting16:00
tvossslangasek, so davmor2 finished his testing :) all good \o/16:00
slangasektvoss: huzzah16:00
tvossslangasek, with that, we can walk through all the mps again and see if they are all top-approved before finally publishing :)16:01
slangasektvoss: why do we need to do that?16:01
tvossslangasek, not sure that all are top-approved and I thought the publishing step would fail if they were not16:02
tvossslangasek, https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/22751116:02
tvossthostr_, you marked https://code.launchpad.net/~charlesk/indicator-datetime/make-gcc-version-explicit/+merge/224467 as "Needs fixing"?16:04
thostr_tvoss: IIRC that was about the gcc or g++-4.9 string.... charles ^^^16:05
charles...?16:07
* charles looks16:07
tvossslangasek, there is a merge conflict here: https://code.launchpad.net/~vorlon/media-hub/explicit-gcc-version/+merge/22656716:08
charlesthostr_, you approved with a LGTM, then marked 'needs fixing' without comment...16:08
thostr_charles: yes, because later I detected something wrong.... at least that's what I remember16:09
slangasektvoss: merge conflict> yes, someone appears to have been manually creating changelog entries ;)16:09
thostr_charles: can you quickly check the gcc string?16:09
slangasektvoss: FWIW, I don't believe there's any technical reason that top-approval should be required for publication16:10
cjwatsonNo technical reason but citrain makes you override it if not, and it seems generally sensible to get it16:10
tvossslangasek, okay ... would be great to have them top-approved to merge&clean as soon as possible :)16:10
tvossslangasek, sorry for the changelog thingy :)16:10
charlesthostr_, tvoss, the changes are the same as in the other indicator-make-gcc-version-explicit MPs...16:11
tvossslangasek, can you fix in your branch?16:11
slangasekyes, fixing16:11
charlesthostr_, I don't understand what you mean, I don't see a problem in the diff16:11
tvosscjwatson, could you revisit: https://code.launchpad.net/~thomas-voss/pay-service/explicit-gcc-version/+merge/22476316:13
slangasektvoss: fixed16:13
tvossslangasek, thanks16:13
charlesthostr_: it would have been better to add an explanation when marking as "Needs Fixing" ;-)16:13
seb128kenvandine, Laney: can you help testing the settings in silo 004?16:13
seb128I don't have a sim to run that part of the testplan16:13
tvossslangasek, would you mind top-approving here: https://code.launchpad.net/~thomas-voss/platform-api/explicit-gcc-version/+merge/22751116:13
tvoss?16:13
thostr_charles: yeah....16:13
LaneyI don't have one with any credit16:13
Laneyis that required?16:13
kenvandineseb128, sure16:14
seb128Laney, not sure, in fact we don't even touch that panel in this landing, so not sure we need to test it at all, still would be good to just see if you can connect to your carrier16:14
cjwatsontvoss: You don't seem to have addressed my comments16:15
tvosscjwatson, let me re-read16:15
cjwatsonI had two different comments both of which are still problems AFAICS16:16
thostr_charles: or, it was the dh auto configure thingy...16:16
thostr_charles: that didn't set the compiler env?16:16
tvosscjwatson, okay, let me see16:16
kenvandine85457716:17
kenvandinewhoops16:17
kenvandineseb128, what needs testing?16:23
seb128kenvandine, just install, restart settings, check that things seem to work fine (including update date in about panel)16:23
seb128kenvandine, not sure we need to run the full testplan since we didn't do much changes (mostly about panel for the update timestamp and test bugfixes)16:24
tvosscjwatson, updated https://code.launchpad.net/~thomas-voss/pay-service/explicit-gcc-version/+merge/22476316:24
kenvandineok, nothing SIM specific :)16:24
seb128no16:24
tvossslangasek, quick dinner, back after16:28
=== Ursinha is now known as Ursinha-afk
cjwatsontvoss: thanks, approved16:31
robruLaney, hey, did you build anything with that 0replaceme yet? Let me know how that works for you...16:31
Laneyrobru: yeah, u-s-s in 004 has it, seems to have worked!16:31
robrusweet16:32
kenvandineseb128, yay... sounds!16:32
kenvandineseb128, looks good to me16:32
robruogra_, has anything big landed during your shift? should I kick an image before publishing autopilot?16:32
sil2100robru, ogra_: the meeting finished?16:32
robrusil2100, yep16:33
robruwas short16:33
sil2100robru: ah, I'll be pushing my second (better!) approach to auto-m&c today probably, so watch out when you redeploy ;)16:33
sil2100If I find enough strength for that16:33
robrusil2100, heh, take it easy, you're no good to us dead from heat stroke! ;-)16:34
seb128kenvandine, thanks, to me too16:34
seb128Saviq, +1 from the settings side16:34
Saviqseb128, anything I should still look at in there?16:35
Saviqseb128, run autopilot?16:35
seb128Saviq, no, it's fine, we tested it enough between us I think16:36
Saviqseb128, ok cool, just running u8 now16:36
Laneyseb128: it seems fine to me16:37
Laneyseb128: we should put some more vertical spacing in I think16:37
Laneythe rows under 'System' look too close to me16:38
bfillersil2100: regarding gallery, let me know when the -proposed merges to trunk so I can generate a click from trunk16:38
=== gatox_lunch is now known as gatox
bfillersil2100: or if I need to run merge and clean16:39
sil2100bfiller: ah, let me take care of that ;)16:41
sil2100robru: thanks ;p16:41
* sil2100 is a person of winter16:41
sil2100I like sun and summer, but not when it's hot!16:41
sil2100bfiller: ok, it's now merged in trunk16:43
seb128Laney, yeah, feel free to mp a change for that16:43
Laneywill do16:43
bfillersil2100: thanks!16:44
sil2100ogra_,davmor2: do we have a bug for the dead mantas?16:47
davmor2sil2100: rsalveti does for the hammerhead and it is a similar issue so should fix both as I understand it16:48
sil2100Can anyone throw me a bug number? ;)16:49
sil2100For teh e-mail16:49
robrukgunn, ^ bug number for that manta issue?16:52
kgunnrobru: lp: 134553316:52
robrusil2100, ^16:53
sil2100Thank you!16:54
=== alan_g is now known as alan_g|EOD
=== retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | CI Train Status: #133 promoted | Need CI Train help? Ping: mvo_, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
robruSaviq, seb128, Laney: just did a big autopilot landing, I guess I'll wait for that to migrate, kick an image, and then publish silo 417:30
Saviqrobru, ok17:31
tvosscjwatson, slangasek can I get your votes here?17:44
tvosshttps://code.launchpad.net/~charlesk/indicator-datetime/make-gcc-version-explicit/+merge/22446717:44
slangasektvoss: what are we voting on?17:47
bfillerpopey, cjwatson: new version of gallery-app uploaded to store if you could approve popey18:08
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: robru | CI Train Status: #133 promoted | Need CI Train help? Ping: robru, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
tvossslangasek, just a review please :-)18:16
=== Ursinha-afk is now known as Ursinha
imgbot=== trainguard: IMAGE 142 building (started: 20140721 19:15) ===19:14
robrustgraber, ^^ did you land any changes to queuebot recently? not sure why it's double-pinging about new landings.19:24
robruI suppose if people edit the description field after marking ready: yes it would double-ping. hrm19:24
stgraberrobru: haven't changed anything but yeah, I'd suspect someone editing the description after setting it ready19:24
tvossslangasek, ping19:27
tvossslangasek, seems like we have a build error for media-hub after I triggered a rebuild to match the latest version in the MP: https://launchpadlibrarian.net/180424031/buildlog_ubuntu-utopic-amd64.media-hub_1.0.0%2B14.10.20140721-0ubuntu1_FAILEDTOBUILD.txt.gz19:27
robrustgraber, can I get a core dev ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff19:29
kgunnfginther: did you help camako turn on autolanding for mir0.5 branch ? or do i need to manual merge ?...its ok either way, i'm just shepherding a critical fix thru19:34
stgraberrobru: sorry, I'm busy and on vacation at the moment.19:35
fgintherkgunn, the problem was not resolved. I found the bit of test code that is causing the problem, but camako must have been offline or unable to respond to debug it further19:35
robrustgraber, ah sorry, didn't know19:36
robrustgraber, sign off IRC :-P19:36
robrukenvandine, can I get a core dev ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff19:36
stgraberrobru: I never sign off IRC because I use IRC for way more than just work stuff :)19:36
kgunnfginther: no worries, i'll do it19:37
=== Ursinha is now known as Ursinha-afk
tvossslangasek, would be great if you could fix the build error and trigger a rebuild for media-hub. I could ask davmor2 for a more focused round of testing tomorrow morning before finally publishing19:41
tvossrobru, ping19:45
robrutvoss, pong19:45
tvossrobru, hey there :) silo8 is almost good to go and I would like to avoid a resync to trunk19:45
tvossrobru, could you make sure that silo 8 takes the lock on the packages in it?19:45
tvossasac, ^19:46
robrutvoss, oh ok19:46
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: robru | CI Train Status: #133 promoted | Need CI Train help? Ping: robru, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it!
robrutvoss, so I'm taking lunch in an hour, but my official EOD isn't until 5 hours from now, and I'll probably even be around a bit after that, so just ping me when you're ready to publish19:51
tvossrobru, I will EOD now, kinda late here19:51
tvossrobru, would be great if you could hand over the information to the next shift :)19:52
robrutvoss, oh, so you're aiming to publish tomorrow?19:52
tvossrobru, yup19:52
robrutvoss, ok19:52
tvossrobru, thanks a lot19:53
robrutvoss, no worries!19:53
=== Ursinha-afk is now known as Ursinha
slangasektvoss: media-hub> right, looking; however, why do we think another round of testing is needed?20:34
imgbot=== trainguard: IMAGE 142 DONE (finished: 20140721 20:45) ===20:44
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/142.changes ===20:44
slangasektvoss: also, this media-hub build failure is clearly unrelated to the gcc change; is someone else likely to be working on fixing it?20:55
slangasekjhodapp: are you by any chance looking at the media-hub FTBFS introduced by the new gst?  Don't want to step on your toes, and we need to get https://code.launchpad.net/~vorlon/media-hub/explicit-gcc-version/+merge/226567 landed for g++4.920:58
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #133 promoted | Need CI Train help? Ping: robru, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does. Silo 8 is incoming! Don't release anything that conflicts with it!
* robru -> lunch21:07
jhodappslangasek: no I'm not21:11
kgunnrobru: hey, sorry to double pester behind the bot...but its a hot one, can i get a silo for the mir fix ? line 3222:41
robrukgunn, sorry, was on lunch, can assign now22:53
robrukgunn, you got silo 4, and building: https://ci-train.ubuntu.com/job/landing-004-1-build/145/console22:55
kgunnthanks!22:55
robruyou're welcome!22:56
robruinfinity, cjwatson: anybody around for a packaging ack? https://ci-train.ubuntu.com/job/landing-013-2-publish/62/artifact/packaging_changes_ubuntu-download-manager_0.7+14.10.20140721-0ubuntu1.diff22:58
infinityrobru: Looking.23:01
robruinfinity, thanks!23:01
infinityrobru: Looks reasonable to me.23:03
robruinfinity, thanks!23:03
infinityrobru: That symbol version should be higher, but if, as stated, nothing really uses this yet anyway, meh.23:03
robruah ok23:03
infinityrobru: But, actually, please fix that.23:04
robruinfinity, oh i hit publish already23:04
infinityrobru: That new symbol should be 0.7+14.10.2014072123:04
infinityrobru: Oh.  Well, ask them to fix it in trunk. ;)23:04
robruinfinity, or it could be 0replaceme ;-)23:04
robruinfinity, ok23:04
infinityrobru: It's harmless to get it wrong when there's no danger of partial upgrades happening, but it's also a nice changelog for when symbols were added.23:05
infinityrobru: (Basically, what that symbols file means is that if a package starts using that symbol, it will depend on libthing (>= old-version) when it should depend on (>= version-where-symbol-appeared))23:06
robruinfinity, ahh i see23:07
robruI'll prep a branch to fix that23:07
infinityrobru: Looking at the small amount of context there, I suspect they're bumping upstream version when they change the API, so those could be simplified to "0.4" and "0.7" etc, rather than the whole ugly version string.23:09
infinityrobru: At least, in that case, we went from 0.6 to 0.723:09
infinityrobru: Which would have the nice side effect of making this sort of thing more backportable, should that be needed in the future (ie: 0.7+14.04 is << 0.7+14.10, but both are >> 0.7)23:11
infinityProbably not neede for this specific package, but worth thinking about.  Symbol versions should reflect upstream changes, except in the really weird case where a Debian patch adds a symbol.23:12
robruinfinity, technically the +14... is part of the upstream version number, but the line is blurry when we're the upstream.23:13
infinityrobru: Right, in the Debian sense, foo+release+date is the "upstream" version, but in the upstream versus daily release sense, I'd contend the real upstream version there is just 0.723:14
infinityOr, at least, from the POV of symbol versioning.23:14
infinityTHe rest is muddier. :P23:14
robruinfinity, so you want to see it like this? http://bazaar.launchpad.net/~robru/ubuntu-download-manager/utopic-proposed/revision/31623:15
infinityrobru: Yeah.  Realistically, the +foo should be stripped from all of them, so it's more obvious what we're going for there (and even as a subtle reminder that API additions should be bumping that version).23:16
infinityCause tracking API/ABI changes by a datestamp could well lead to madness (see above argument, re: backportability)23:16
robruinfinity, it's not *really* a datestamp though. it's version by upstream + by distro release series before the datestamp bit.23:17
infinityWe won't backport any of this from U to T, but we may well see backports and forward ports between U and V.23:17
infinityrobru: Right, it's a date twice, though.  Just one happens to be an Ubuntu version. ;)23:17
infinityrobru: The point is that a dependency of >> 0.7+14.10 is wrong, if 0.7+14.04 can also satisfy it, and the obvious choice is 0.723:17
infinity(Same for the 0.4, etc)23:17
robruah, ok23:18
infinityrobru: I doubt it matter at all for this specific thing (yet), if it'll generally only exist in system images, but best practices and all, and it may well be abused by apt later (ie: when it ends up on my desktop some day).23:19
infinityAnd making apt's life easier on partial upgrades by not forcing it to sort out upgrade ordering it doesn't need to is always a win.23:19
robrucool23:20
slangasekjhodapp: pushed a fix for the gst-induced FTBFS to lp:~vorlon/media-hub/explicit-gcc-version.  Do you prefer that I separate this out into a separate branch for review?23:25

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