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

=== thomi_ is now known as thomi
=== Ursinha-afk is now known as Ursinha
imgbot=== trainguard: IMAGE 138 building (started: 20140718 02:05) ===02:04
imgbot=== trainguard: IMAGE 138 DONE (finished: 20140718 03:40) ===03:39
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/138.changes ===03:40
=== wgrant_ is now known as wgrant
sil2100o/07:14
sil2100This heat is killing me...07:14
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #133 promoted | Need CI Train help? Ping: sil2100, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
popeyhello! this is new! http://popey.mooo.com/screenshots/device-2014-07-18-083826.png07:38
sil2100Ooooh07:41
sil2100Since when do we have that?!07:41
popeydunno, only just noticed it07:41
popeyin proposed07:42
* sil2100 checks commitlogs07:42
Mirvthat's awesome, I've been waiting for that too :)07:45
sil2100Mirv: o/07:46
sil2100Mirv: I thought you're on holidays already :)07:46
sil2100ogra_: hmmm... I wonder why the changes file for 137 is empty - I guess it was the Mir image, right?07:46
jibelsil2100, popey the shutdown prompt comes from unity8 7.90+14.10.20140717.1-0ubuntu107:47
popeysil2100: the file was 403 initially, and 0 bytes long, guessing ogra's script failed07:48
sil2100jibel: oh, thanks ;)07:49
Mirvsil2100: after today :) just gave you a prenotice08:02
tvosssil2100, Mirv something wacky in the ci infrastructure: https://ci-train.ubuntu.com/job/landing-008-1-build/08:32
brendandpopey, https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/134233608:39
ubot5Ubuntu bug 1342336 in Ubuntu File Manager App "test_go_to_root/home_must_open_the_root/home_directory fails since mako #132" [Undecided,New]08:39
robrutvoss, nope, it's your stuff that's broken: https://code.launchpad.net/~vorlon/process-cpp/explicit-gcc-version/+merge/22656408:39
robruactual 404 ;-)08:39
cjwatsonlooks like a typo, should be https://code.launchpad.net/~vorlon/process-cpp/explicit-gcc-version/+merge/22659408:41
cjwatson(there was a previous version of the MP but that was 226569)08:41
robrumysterious08:42
robrutvoss, anyway ^ update that link & reconfigure, should work08:42
alan_gcihelp: I've a problem with mir-mediumtests-utopic-touch and mir-mediumtests-runner-mako which amounts to "dpkg ... --auto-deconfigure will help" - how do I get the scripts updated? (For an example see: https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/2109/console)08:53
sil2100tvoss: looking09:00
sil2100Ah, robru already took a look09:00
tvosssil2100, already fixed, thanks09:00
tvosssil2100, or better: understood09:00
sil2100robru: shouldn't you be like, sleeping? ;)09:00
brendandsil2100, https://bugs.launchpad.net/autopilot/+bug/132860009:00
ubot5Ubuntu bug 1328600 in Autopilot "Autopilot lacks support for large timestamps" [High,Confirmed]09:00
robrusil2100, what? it's only 2AM here...09:00
brendandsil2100, i'll look at the uitk issue and try and see if anything is wrong there. obviously there is an issue with autopilot too, but it doesn't explain why it started failing all of a sudden09:05
sil2100brendand: ok, thanks - yeah, I wouldn't suppose that so many should start failing because just of that AP problem09:42
sil2100brendand: but as we already inspected the changes, we didn't see anything landing that could have caused it09:42
sil2100But maybe we missed something09:42
cjwatsonplars: the test channel next week will be "ubuntu-touch/stable-staging-proposed"09:44
brendandsil2100, i found the calendar_app failures are reproducible09:54
brendandsil2100, i filed a bug for them: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/134391609:55
ubot5Ubuntu bug 1343916 in Ubuntu Calendar App "test_add_new_event_with_default_values & test_fill_form fail since mako #137" [Undecided,New]09:55
popeythanks brendand09:56
sil2100Oh09:56
sil2100brendand: thanks!09:56
camakosil2100, re-requesting a silo for row 13... Switched "Ready" row to "yes" but not sure if you guys received notification.09:57
sil2100camako: hi! We might have missed that, let me assign a silo for you09:58
camakosil2100, thanks!09:58
brendandsil2100, we could potentially work around the uitk failures in the tests. i'll talk to elopio about it when he's in09:58
sil2100camako: silo 10 for you! yw09:59
sil2100brendand: oh, work around? You mean, around the timestamp bug in AP?09:59
camakosil2100 :-) thanks09:59
brendandsil2100, yes10:00
t1mpsil2100: do you have a bug id for the timestamp bug?10:00
brendandt1mp, https://bugs.launchpad.net/autopilot/+bug/132860010:01
ubot5Ubuntu bug 1328600 in Autopilot "Autopilot lacks support for large timestamps" [High,Confirmed]10:01
sil2100t1mp: ^10:01
sil2100t1mp: it's an autopilot bug it seems10:02
t1mpbrendand, sil2100 thanks10:02
t1mpI have seen that bug for all UITK MRs yesterday10:02
asacfginther: ping me when on, s we can chat about dashboard10:03
alan_gcihelp: I've a problem with the jobs mir-mediumtests-utopic-touch and mir-mediumtests-runner-mako - how do I get the jobs updated?10:03
alan_gCurrently they use setup_branch: lp:~josharenson/+junk/mir-medium-test-runner-for-jenkins10:03
alan_gWhat I want is for them to use : lp:~mir-team/+junk/mir-medium-test-runner-for-jenkins10:03
alan_g(The latter adds a missing option to dpkg)10:03
bzoltansil2100: I do not know who to escalate, but no MR was able to land on the staging branch of the UITK because of this bug : https://bugs.launchpad.net/ubuntu-app-launch/+bug/132914110:03
ubot5Ubuntu bug 1329141 in Ubuntu Application Launcher "qmlscene crashed while running test_can_launch_multiple_applications" [Critical,Confirmed]10:03
sil2100bzoltan: hi! Yeah, I was also thinking about this one, we discussed it yesterday during the evening meeting10:04
t1mpbzoltan: so we have two blockers now, this is the other https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/132860010:04
ubot5Ubuntu bug 1328600 in Autopilot "Autopilot lacks support for large timestamps" [High,Confirmed]10:04
sil2100bzoltan: someone pointed out that it could be qtubuntu at one point, right?10:04
bzoltansil2100:  should I start pushing to the staging branch directly and land it?10:04
bzoltant1mp:  large timestamp? Like year and month in it? Wow... that is large10:05
t1mpsil2100: yes mirv hinted that it might be qtubuntu - https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141/comments/510:05
ubot5Ubuntu bug 1329141 in Ubuntu Application Launcher "qmlscene crashed while running test_can_launch_multiple_applications" [Critical,Confirmed]10:05
sil2100bzoltan: hm, you could do that, although I guess this would basically mean you'll have to test more before landing...10:05
sil2100ricmm: hi!10:05
sil2100ricmm: could you maybe take a look at the above bug? ^10:05
bzoltansil2100:  I do the full test suite anyway10:05
sil2100ricmm: we're not sure where the actual problem comes from, but some clues point into the direction of qtubuntu10:06
t1mpbzoltan: for example the timestamp bug can be seen here https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2383/?10:06
t1mpbzoltan: that result I got for *all* MRs yesterday10:06
bzoltant1mp:  geez10:06
Saviqcihelp hey guys, this job seems stuck in "recording test results" http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/479/console10:07
Saviqcihelp and this VM does not start http://s-jenkins.ubuntu-ci:8080/computer/ps-utopic-server-amd64-3/?10:07
t1mpbzoltan: indeed10:08
Saviqcihelp, also, I'd need ssh access to one of the utopic&&amd64 VMs please, gotta debug non-reproducible test failures10:09
psivaaalan_g: Saviq: i'll take a look at your questions one by one10:12
bzoltansil2100:  For us these bugs are showstoppers and have the highest possible severity I have seen so far in the UITK project. I can hack around them by creating a shadow staging branch where I merge all the MR branches and propose that branch for landing and then sync back to the staging ... but that would kill the whole point of the continuous integration and automatic testing.10:12
Saviqpsivaa, thanks10:12
bzoltansil2100:  we could not autoland on our staging for 72 hours ... from the point of the UITK there we are running in the 72snd hour of a Jenkins outage10:13
sil2100Crap :|10:13
sil2100bzoltan: the biggest problem with this qmlscene crash blocker is that we don't know where to escalate it exactly10:14
sil2100bzoltan: my first guess is ricmm, but not sure if that's the right path10:14
bzoltansil2100: the problem sound like a qtubuntu bug.10:15
sil2100ricmm: could you take a look at it as soon as possible? (just hope you're around)10:16
bzoltansil2100:  the real problem is that I do not think we can expect the autopilot tests of the apps and the uitk to be reliable on the device.10:16
sil2100bzoltan: with the current results, yes?10:16
bzoltansil2100:  not even talking about that a crashing qmlscene will be fatal for the users too10:16
sil2100bzoltan: yeah, that's why those 2 issues are currently our blocker10:16
sil2100*blockers10:17
sil2100bzoltan: I'll also try making sure the right people are working on it10:19
bzoltansil2100:  Thank you10:19
sil2100ogra_: is ricmm working today?10:20
ogra_sil2100, i think he is in the US, but i wouldnt see why not10:20
sil2100(i.e. did he take a holiday?)10:20
sil2100Ah, that would explain it10:20
psivaaalan_g: do you want to replace the setup branch for ever? (from lp:~josharenson/+junk/mir-medium-test-runner-for-jenkins to lp:~mir-team/+junk/mir-medium-test-runner-for-jenkins)10:27
alan_gpsivaa: that would be great10:27
psivaaalan_g: ok, i've done that and triggered a rebuild on the failed one10:31
alan_gpsivaa: thanks!10:31
cjwatsonsil2100: How's the citrain generalisation for ubuntu-rtm looking?10:37
sil2100cjwatson: didn't work on it yet today, let me finish that up later today once I'm done with the issue dashboard for landing purposes, as I'm almost done10:42
cjwatsonsil2100: Right, thanks.  I'm nearing the end of other work items I can do before we actually create it ...10:44
psivaaSaviq: i can't find the host where 'ps-utopic-server-amd64-3 is supposed to run on.. sorry10:45
Saviqpsivaa, ok, will have to wait for fginther10:46
psivaaSaviq: ack10:46
* sil2100 goes to prepare lunch10:55
=== MacSlow is now known as MacSlow|lunch
fgintherpsivaa, 'ps-utopic-server-amd64-3' is hosted on naartjie. It's failing to revert from its snapshot (seen in jenkins slave log) so its disk image is likely corrupt.11:29
fgintherpsivaa, I'll see if we have a usable backup for the image.11:30
psivaafginther: ack, thanks. i missed naartjie when cheking11:30
popeyballoons: can you help with updating tests for https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/NewEvent-Contact/+merge/223570 ? - it needs an updated test for adding contacts.11:31
=== MacSlow|lunch is now known as MacSlow
=== jibel_ is now known as jibel
=== renato is now known as Guest57300
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | CI Train Status: #133 promoted | Need CI Train help? Ping: sil2100, trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
ricmmsil2100: im here now13:09
sil2100ricmm: \o/13:09
sil2100ricmm: did you see that bug already? https://bugs.launchpad.net/ubuntu-app-launch/+bug/132914113:10
ubot5Ubuntu bug 1329141 in Ubuntu Application Launcher "qmlscene crashed while running test_can_launch_multiple_applications" [Critical,Confirmed]13:10
sil2100It seems to be a blocker for any UITK development13:10
ricmmwhat does that mean anyways13:10
ricmmdoes it make some specific branches fail?13:10
ricmmif so, which ones13:10
=== Guest57300 is now known as renato__
t1mpricmm: let me see13:17
sil2100ricmm: I think all branches fail from what bzoltan mentioned13:18
t1mpthere is another bug now that also makes the branches fail, so with the current MR we see the other bug13:19
t1mpthis is the other bug that blocks us now - https://bugs.launchpad.net/autopilot/+bug/132860013:20
ubot5Ubuntu bug 1328600 in Autopilot "Autopilot lacks support for large timestamps" [High,Confirmed]13:20
t1mpbut before that we didn't have autolanding for a few days because of the qmlscene crashes13:20
t1mpI'm not sure though if the qmlscene crash affected 100% of the MRs, but a lot (maybe 80%)13:20
t1mpeven changes where we only updated the docs13:20
t1mpricmm, sil2100 I think this is one where qmlscene crashed https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2109/?13:21
t1mpfrom this MR https://code.launchpad.net/~nik90/ubuntu-ui-toolkit/improve-header-api-docs/+merge/22611313:21
sil2100We also saw the qmlscene crashes in smoketesting13:22
t1mpit failed CI twice, and then autolanding, and then it passed autolanding after an empty commit.13:22
t1mpthis MR also has qmlscene crashes https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/noArchErrors/+merge/22566713:24
t1mpwe are pushing stuff to our staging manually today, that's why some newer MRs are now "Merged". But of course that is not the ideal way of working13:25
t1mp15:10:42 < ricmm> does it make some specific branches fail?13:28
t1mpricmm: if I would have to guess, I'd say about 80% of CI and autolanding runs failed (for all MRs, independent from what's changed)13:28
ricmmok13:29
ricmmcan you get me a reproducible case13:29
t1mpelopio: have you been able to reproduce the crash locally?13:33
t1mpbzoltan: ^?13:34
Mirvtsdgeos: Saviq: sil2100: one more update, check https://wiki.ubuntu.com/Touch/QtTesting (-> qt5-beta2) if you need to test Qt 5.3.1 (even though it's not going in before RTM) for some bug or such. I just now very quickly rushed it together to the extent that I've it running on my mako.14:06
Mirv+ desktop (Qt Creator works too)14:06
Mirvqtbase+qtxmlpatterns+qtdeclarative+qtwebkit is about "well done", everything else is ad-hoc rush packaging at the moment - but it works :D14:07
Mirvbzoltan: ^ managed to get Qt Creator running with 5.3.1 too if you want to test something so that you know if there'd be a potential fix to cherry-pick to our 5.3.0 for SDK purposes14:07
cjwatsonbfiller: Hi, do you think https://code.launchpad.net/~cjwatson/gallery-app/static-exiv2/+merge/227275 could be added to silo 1, if you're OK with it?14:13
bfillercjwatson: sure14:14
bfillercjwatson: I'll add it and rebuild the silo14:14
cjwatsonbfiller: Brilliant, thanks - the plan would then be to upload the click package to the store and get it onto images, drop libexiv2-12 from ubuntu-touch-meta, and then once calligra manages to build (currently blocked on a librevenge MIR) the whole transition should manage to land and silo 1 can be cleaned after that14:15
cjwatson(The .deb will still depend on libexiv2-*, so it'll still be part of that transition, but we should actually be able to land it all then)14:16
bfillercjwatson: getting this error when trying to build silo 1 with gallery: https://ci-train.ubuntu.com/job/landing-001-1-build/122/console14:43
bfillercjwatson: I checked force rebuild but still getting error14:44
t1mpelopio: hello14:56
t1mpelopio: can you read back here to where I highlighted you? I wonder whether you reproduced https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141 locally14:56
ubot5Ubuntu bug 1329141 in Ubuntu Application Launcher "qmlscene crashed while running test_can_launch_multiple_applications" [Critical,Confirmed]14:56
t1mpricmm started to have a look at the bug14:57
ogra_poor bug14:57
ogra_:)14:57
cjwatsonbfiller: The one you linked didn't have force-rebuild set; the build immediately after that has force-rebuild set and appears to be working14:59
cjwatsonbfiller: https://ci-train.ubuntu.com/job/landing-001-1-build/123/console14:59
bfillercjwatson: ah ok, thanks14:59
elopiot1mp: ricmm: I've seen the crash in my machine and my phone. But not with simple steps to reproduce, just by running the big toolkit suite or the unity8 applicacion life cycle suite multiple times.15:00
elopioI'll see if I can get a loop that launches qmlscene with a simple qml until it crashes to see how often it is.15:00
sil2100Damn...15:02
=== gatox is now known as gatox_lunch
bzoltanMirv:  cool. I will test it on Monday15:18
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
sil2100ricmm, t1mp: were you able to get to something?15:59
plarssil2100: I just killed my browser, be there as soon as I can16:03
kgunnis there a prob on manta with image # 138 ?16:10
ogra_could be16:11
* ogra_ doubts mantas actually get mooted more than once per month by regular devs16:11
kgunnogra_: i got endless google16:11
=== gatox_lunch is now known as gatox
ogra_*booted16:11
kgunnogra_: we've been diligent trying to test qtcomp on it16:12
ogra_(mine has a constantly dead battery )16:12
kgunnits consistently gotten worse in the virgin image lately16:12
ogra_(requiring me to charge it at least for 1h first)16:12
ogra_kgunn, http://ci.ubuntu.com/smokeng/utopic/touch/ surely agrees with you16:12
kgunnogra_: was just checking on that ;)16:13
ogra_137 and 138 definitely had probs16:13
ogra_though these devices get not properly charged (only via USB port) which is extra deadly for the manta16:13
ogra_i.e. the lab devices can be unreliable16:13
=== sil2100 changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | CI Train Status: #133 promoted | Need CI Train help? Ping: trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | 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.
cjwatsonbfiller: How does silo 1 look re testing?16:23
cjwatsonHoping somebody has time to look ...16:24
bfillercjwatson: haven't had time to test yet, but plan to do so later this afternoon16:25
cjwatsonok, cool, thanks16:26
=== Ursinha is now known as Ursinha-afk
robrukenvandine, need the merge URLs in column F16:36
=== Ursinha-afk is now known as Ursinha
kenvandinerobru, how's that look?16:39
robrukenvandine, looks like system-settings conflicts with silos 4 and 6... you're going to have to coordinate with mterry and kgunn about that16:40
mterrykenvandine, hello!16:40
mterrykenvandine, if you want to land quickly, go ahead, don't worry about silo 416:41
kgunnkenvandine: just let us know when you land we can rebuild 616:41
robruwell that was easy ;-)16:41
robrukenvandine, ok you got silo 1816:42
robrukenvandine, people.canonical.com/~platform/citrain_dashboard/#?q=kenvandine has the silo status and quick links to the jenkins build jobs16:42
kenvandinethx everyone :)16:43
robrukenvandine, you're welcome!16:43
barryrobru: i'll assign myself a silo for row 3116:44
robrubarry, ok ;-)16:44
barryrobru: using my vast experience as a button pushing monkey sheriff16:45
robrubarry, http://bit.ly/1lcoYV316:45
barryrobru: priceless! :)16:46
barryrobru: anyway, i'm off to lunch.  will check on it later16:46
robrubarry, bon appetit!16:47
kenvandinerobru, do i need to enter any info to start the build?16:47
robrukenvandine, oh yeah, you need to click the 'build' link at that dashboard URL I gave you, and then that loads the jenkins job, which you have to click 'Build' to make it go. but you have to click it twice, because the first time will just log you in and won't trigger the build16:48
kenvandineah16:48
kenvandinethere we go :)16:49
=== Ursinha is now known as Ursinha-afk
=== rvr is now known as rvrOff
=== Ursinha-afk is now known as Ursinha
pmcgowankenvandine, jonas' merge failed again on the about page tests, something about dbus failing to connect17:36
kenvandinesigh17:37
robrufginther, is jenkins having some networking issues? at least one silo can't seem to upload to the PPAs. https://ci-train.ubuntu.com/job/landing-017-1-build/103/console and https://ci-train.ubuntu.com/job/landing-017-1-build/102/console different tracebacks, but both related to dput failing connect to launchpad to upload.17:37
pmcgowankenvandine, they passed last time17:38
pmcgowanhe fixed something for the background page should have nothing to do with it17:38
* kenvandine looks17:40
kenvandinepmcgowan, interesting.. that's the same failure i was seeing running them on my device the other day17:42
kenvandinebut they didn't fail in CI17:42
kenvandineto rule out flaky tests, i just triggered a rebuild17:44
pmcgowankenvandine, seems odd, all accesses to the system dbus17:45
robrufginther, nm, seems transient, retrying the build fixed it17:47
elopioricmm: I've commented the qmlscene bug with a script that will get you a crash.17:48
elopiorobru: once the spreadsheet says my silo is ready to build packages, how do I jump to the next state?17:50
robruelopio, visit http://people.canonical.com/~platform/citrain_dashboard/#?q=elopio and click 'Build', which opens the jenkins job, then on that page click 'Build' twice (once to log in, once to actually trigger it)17:51
elopiorobru: got it. Thanks.17:52
fgintherrobru, good, I could find anything not working from what I could check18:01
fginthers/could/couldn't/18:01
robrufginther, hehe, thanks for checking18:08
pmcgowankenvandine, you need help testing the silo?18:25
kenvandinepmcgowan, yes please18:26
kenvandinei tested call waiting and trying to test the wifi ids change now18:27
kenvandinebut i'm not seeing it18:27
pmcgowanwhats the wifi id change kenvandine?18:29
kenvandineincluding extra info in whoopsie reports18:29
kenvandinei see it now that i read the full MP18:29
pmcgowanoh18:29
kenvandinesome text changed18:29
kenvandinebut i can't check it18:29
pmcgowankenvandine, is it the location info checkbox?18:38
kenvandineyes18:38
pmcgowanhmm I cant check it18:38
kenvandineme either18:39
pmcgowanseems its not enabled18:39
kenvandinei get the haptic feedback18:39
kenvandineso must be enabled18:39
pmcgowankenvandine, I dont understand the code there18:44
kenvandinei'm also not getting sound playback in the sound panel18:45
kenvandinewhich i'd assume might be the revert apparmor policy branch18:46
kenvandinelanguage one looks good18:46
pmcgowansigh18:47
pmcgowankenvandine, the change to initialize the ringtone so it doesnt scroll works18:48
pmcgowanbut the revert did not18:48
kenvandinei assume18:49
kenvandinesince i hear no playback18:49
pmcgowankenvandine, that change seems to not install the bad profile, but I dont think it deletes it if its there?18:49
kenvandinealthough i'm not familiar with the problem that hack was trying to fix18:50
kenvandineoh... maybe that's the problem18:50
kenvandinebut that'll be a real problem anyway18:50
pmcgowanright18:50
pmcgowanso a reflash will work, but not an update18:50
kenvandinepmcgowan, maybe we should drop some of these branches from the silo and give it another go?18:53
kenvandinerobru, is that what "reconfigure" lets me do?18:53
robrukenvandine, yep, just update the spreadsheet first18:53
pmcgowankenvandine, yes drop those two18:54
pmcgowanthe others seem ok to me18:54
kenvandinerobru, do i update it on the landing-018 tab?18:54
kenvandinei guess not18:54
robrukenvandine, nope, on the Pending tab. the silo tab is just a readout basically18:54
robruexcept when it isn't, sigh18:54
pmcgowankenvandine, so that revert18:56
kenvandinerobru, so it reads the branches out of the spreadsheet?18:56
pmcgowankenvandine, I wonder if it works with an image update?18:56
robrukenvandine, yeah, the jenkins reconfigure job will access the spreadsheet to determine what branches go in the silo.18:57
kenvandinepmcgowan, not sure, lets ask the experts on monday18:57
robrukenvandine, in CI Train we're really heavily abusing the spreadsheet, pretending it's a db.18:57
pmcgowankenvandine, I am wondering if we should leave it in18:57
kenvandinei just want to get some of this pile of branches landed18:57
kenvandinepmcgowan, but how can we test that?18:57
pmcgowankenvandine, we cant I think18:58
pmcgowankenvandine, if we get an image update we will know18:58
pmcgowanI bet it works, as would a reflash18:58
pmcgowanjdstrand, about?18:58
pmcgowankenvandine, worst case it does nothing and we need a second fix18:59
kenvandinewell i'm wondering if that sound playback works without that revert19:00
pmcgowanno it doesnt19:00
kenvandineoh19:00
robrubfiller, can you approve the merges in silo 11?19:00
pmcgowanand I manually fixed it yesterday and heard it work19:00
kenvandinebugger... now i've removed that branch :)19:00
pmcgowanwith a comand jdstrand gave me19:00
kenvandineah, i forgot to build though19:01
jdstrandpmcgowan: ?19:01
* kenvandine adds again19:01
pmcgowanjdstrand, the revert in https://code.launchpad.net/~laney/ubuntu-system-settings/revert-apparmor/+merge/22722519:01
bfillerrobru: checking, must have missed some19:01
pmcgowanwill that apply on a system update? as it does not on package install19:01
pmcgowanseems it stops doing something at install, but does not fix the issue with apt update19:01
jdstrandpmcgowan: what do you mean it doesn't apply?19:01
jdstrandoh, you mean the file is not removed19:02
pmcgowanjdstrand, will a system update remove the offending policy19:02
pmcgowanright19:02
jdstrandhonestly, I'm not sure19:02
jdstrandcause I don't know how the image is put together19:02
pmcgowanit must I think19:02
bfillerrobru: done19:03
jdstrand/etc/apparmor.d is ro19:03
robrubfiller, published!19:03
pmcgowanjdstrand, so is everything that gets updated19:03
pmcgowanI vote we leave that branch in19:04
pmcgowankenvandine, ^^19:04
jdstrandI know, was was saying that is a good thing. so if the stuff that puts the image together is built from debs19:04
jdstrandand the debs don't contain it19:04
pmcgowanexactly19:04
jdstrandthen it shouldn't be there19:04
kenvandinepmcgowan, ok, reconfiguring again19:04
pmcgowanI commented on the diagnostics mp19:05
kenvandinepmcgowan, thx19:05
pmcgowanI gotta eod early, talk to you later19:05
kenvandinehave a great weekend!19:05
pmcgowanyou too19:05
barryrobru: my build failed ^^ which isn't totally unexpected, but i'm missing a button (or don't remember how) to retry the build19:14
robrubarry, ok, depends -- do you have new commits to upload, or is it a transient failure you want a no-change retry?19:15
barryrobru: the latter19:15
barry(sometimes udm dbus just times out for reasons we've never been able to track down)19:15
robrubarry, ok, then you need to click through to the PPA, and find the ppa build job and click retry there (citrain isn't even involved in that)19:15
robruwell, once you do that, do a WATCH_ONLY citrain build job so that citrain notices when the new rebuild completes19:16
barryyeah, there's no retry button.  must be some other permission issue going on19:16
robrubarry, you're looking here? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+build/619526519:16
robruI see the retry button, not sure why you don't19:16
barryrobru: yeah, me neither19:18
robrubarry, ok, retried it for you19:18
barrywhat team are you in that i'm not in? :/19:18
barrythanks19:18
robrubarry, probably ppa service team19:18
robrubarry, https://launchpad.net/~ci-train-ppa-service19:18
robrupester asac for access to that19:19
barrycould be.19:19
barryyeah, will do19:19
barryor slangasek since he's also an admin19:20
robrubarry, anyway, now run the jenkins build job, but check WATCH_ONLY, and then you'll get nice things like a queuebot ping when the new rebuild is done19:20
robrualright, I gotta run for lunch, brb!19:23
charlesogra_, this actually landed earlier this week but iirc you were asking about it:19:29
charlesnow when you dismiss an alarm, the audio stops as soon as the popup dialog goes away19:29
* barry waves to slangasek 19:42
* slangasek waves19:42
barryslangasek: so, you might not have the scrollback19:42
slangasekok, apparently the new window being opened was correct, and I had fallen out of the channel :P19:42
barry<barry> robru: my build failed ^^ which isn't totally unexpected, but i'm19:43
barry        missing a button (or don't remember how) to retry the build  [15:14]19:43
barry 19:43
slangasekbut at least there's http://irclogs.ubuntu.com/2014/07/18/%23ubuntu-ci-eng.html19:43
barryah yes19:43
slangasekwhich is out of date19:43
barryheh19:43
barrysorry for the upcoming crappy paste19:43
barry<robru> barry, ok, depends -- do you have new commits to upload, or is it a19:43
barry        transient failure you want a no-change retry?  [15:15]19:43
barry<barry> robru: the latter19:43
barry<barry> (sometimes udm dbus just times out for reasons we've never been able19:43
barry        to track down)19:43
barry<robru> barry, ok, then you need to click through to the PPA, and find the ppa19:43
barry        build job and click retry there (citrain isn't even involved in that)19:43
barry<robru> well, once you do that, do a WATCH_ONLY citrain build job so that19:43
barry        citrain notices when the new rebuild completes  [15:16]19:43
barry<barry> yeah, there's no retry button.  must be some other permission issue19:44
barry        going on19:44
barry 19:44
barry<robru> barry, you're looking here?19:44
barry        https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+build/619526519:44
barry<robru> I see the retry button, not sure why you don't19:44
barry<barry> robru: yeah, me neither  [15:18]19:44
barry<robru> barry, ok, retried it for you19:44
barry<barry> what team are you in that i'm not in? :/19:44
barry<barry> thanks19:44
barry<robru> barry, probably ppa service team19:44
barry<robru> barry, https://launchpad.net/~ci-train-ppa-service19:44
popeyʘ‿ಠ19:44
barry<robru> pester asac for access to that  [15:19]19:44
barry 19:44
barry<robru> barry, anyway, now run the jenkins build job, but check WATCH_ONLY,19:44
barry        and then you'll get nice things like a queuebot ping when the new19:44
barry        rebuild is done19:44
barry 19:44
barryslangasek: ^^^19:45
slangasekrobru: so you're agreed that the best interface for this (for the time being) is for people to click the retry button directly in the ppa?  I have no problem adding barry to the team, since he knows better than to bypass the train to upload to the ppa; but I don't want to add lots of people generally without training, and figure that "retry the build" is a thing it would be useful to be able to do19:45
slangasekbarry: popey says: private paste ;)19:46
popey19:46
slangasekrobru: maybe this is enough of a corner case that I should not worry about it, though19:46
barrypopey: you are so iconic19:46
barryyay.  failed again.  so it's a separate issue that udm sometimes times out, and i'll be getting together with mandel on monday to discuss.  of course, local builds don't fail :/19:48
slangasekok19:50
barryslangasek: thanks :)19:52
robruslangasek, actually, for a while I was just doing jenkins rebuilds, which results in having the package re-uploaded. The personification of a very large number told me that doing that was very wasteful and the PPA retry build button was strongly preferrable.19:57
* barry is back19:57
slangasekrobru: right, exactly :)19:57
=== Ursinha is now known as Ursinha-afk
robruelopio, please approve the merges in silo 9 then I can publish20:03
elopiojhodapp: can you please top-approve them?20:04
robrukenvandine, hah, you published yourself, you sneaky core dev you.20:04
kenvandinerobru, aren't i allowed to? :-p20:04
robrukenvandine, yup, just wasn't expecting it20:04
jhodappelopio: got the links handy again?20:04
kenvandineugh20:05
robrukenvandine, no, that's me20:05
elopiojhodapp: one second20:05
robrukenvandine, because I published at the same time you did20:05
kenvandineoh... hehe20:05
kenvandineok20:05
robrukenvandine, your publish job ran fine20:05
elopiojhodapp: I think this is the only one that's missing the approval20:06
elopiohttps://code.launchpad.net/~brendan-donegan/mediaplayer-app/remove_scene_select_test/+merge/22707120:06
kenvandinerobru, and when do we do the merge & clean?20:06
elopiorobru: with the top-approval is enough, right?20:06
slangasekplars, fginther: where does the config logic live for the jenkins jobs that generate the source packages for silo uploads?20:06
robruelopio, no, I have to publish after the merges are top approved. it's not automatic20:06
robrukenvandine, after the package hits the release pocket20:06
kenvandineok, i assume you'll do that?  i'll probably be eod by then :)20:07
robrukenvandine, so there's this script that polls the archive for that and pings us once it's ready to merge, but it's broken right now. i'm looking at fixing it20:07
robrukenvandine, yeah no worries20:07
jhodappelopio: done20:07
fgintherslangasek, I believe it's in lp:cupstream2distro, let me narrow it down20:07
kenvandinerobru, cool thx!20:07
elopiorobru: ready for you20:08
slangasekfginther: ok.  It came to my attention last weekend that the chroots are being updated in-line as part of each source package prep, and have not been updated since utopic opened; we could save a lot of clock time on jenkins jobs by making sure these base chroots were updated routinely20:08
robruelopio, jhodapp : uh, guys? https://code.launchpad.net/~brendan-donegan/mediaplayer-app/remove_scene_select_test/+merge/226863 this merge in the silo is superceded. did you want to maybe put the new merge in place and rebuild?20:09
jhodappelopio: ?20:10
robruor did you just miss when you were trying to click approved?20:10
jhodapprobru: something changed20:10
jhodappelopio: yeah, it has conflicts against trunk20:11
robrujhodapp, elopio: alright, well I'm gonna need you guys to find the new mp / sort out the conflicts, update the MP link in the spreadsheet, reconfigure, rebuild, retest, then I can publish.20:12
jhodapprobru: definitely... elopio: let me know when you want me to look again20:13
fgintherslangasek, this appears to be the script to deploy the jobs: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/view/head:/citrain/manual/setup-citrain20:13
slangasekfginther: thanks for the pointer20:13
robrufginther, hm? that's just the one that creates the jenkins jobs from the templates. it doesn't make the chroot. I don't know where that got done, maybe manually20:14
robruslangasek, ^20:14
fgintherslangasek, I suspect you just want a new job to update the chroot daily. Which should just be a matter adding a new job to refresh to do just that20:14
fgintherugh, redundant20:14
slangasekfginther: ah, adding new jenkins jobs; this sounds like a task for someone who knows something about jenkins :)20:15
fgintherrobru, I don't think you want to generate a new chroot all of the time. I think it's enough to just update them20:15
robrufginther, right, but that script you linked neither creates nor updates the chroots, that's handled somewhere else, but I don't know where.20:16
elopiorobru: wow, I think we were close :)20:16
robruelopio, yeah, not sure how that superceded merge slipped in there, or how it even built with merge conflicts.20:17
elopiorobru: it was me who missed added the original one instead of the superceded. Sorry.20:19
robruelopio, no worries20:19
=== josepht 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.
fgintherrobru, ok, so it's probably a 2 part task then, 1) create the script to update chroots if needed, 2) create jenkins job to call script20:20
robrufginther, yeah that sounds reasonable, except I don't have the first clue where those chroots are stored, what command will update them, etc. are we using pbuilder? i don't even know20:21
kenvandinemterry, kgunn: system-settings has been published, you can rebuild now20:21
robrumterry, kgunn nooooo20:21
mterryI'm getting mixed messages  :)20:22
robrukenvandine, the builds pull from trunk, you can't build until the silo is cleaned.20:22
robrupublishing isn't enough20:22
fgintherrobru, it uses cowbuilder which I believe behaves just like pbuilder for the purpose of upgrading20:22
robrukenvandine, rather to be more clear, you can't rebuild the other silos until the first silo has been merged.20:22
barryi don't know any details about the chroots, but here's the script i use to keep my local chroots up-to-date: http://bazaar.launchpad.net/~barry/+junk/repotools/view/head:/chup20:24
robrubarry, thanks20:24
=== Ursinha-afk is now known as Ursinha
kenvandinerobru, ah... ok thx20:26
elopiorobru: launchpad says there's a conflict, but I can merge that branch with trunk without problems.20:26
robruelopio, the warning about the merge conflict could be stale then. sometimes launchpad doesn't update the diff.20:27
robruelopio, at any rate, I can't publish that silo until all the merges are top-approved. so either approve that merge or replace it with one that is.20:27
elopiorobru: I updated the line on the pending tab of the spreadsheet with the right MP20:31
robruelopio, ok you should be able to run the reconfigure job20:31
elopiowhich is not yet top-approved anyway. jhodapp, you just left your approve comment here: https://code.launchpad.net/~brendan-donegan/mediaplayer-app/remove_scene_select_test/+merge/22707120:32
elopioPlease do it on the top.20:32
robrujhodapp, yeah, we like you on top.20:32
elopio:D20:32
elopiook, reconfiguring.20:33
jhodappelopio: can't, it has merge conflicts according to LP20:33
elopiojhodapp: I've just merged it with trunk here and there are no conflicts.20:34
elopioI'm not sure how to tell launchpad to refresh.20:34
elopiojhodapp: oh, you should have permissions to resubmit.20:34
jhodappelopio: yeah that's odd, it doesn't show any conflicts in the diff either20:34
jhodappelopio: k, resubmitted for you20:35
elopiothat should clear it. I would have to reconfigure again, but that's fast.20:35
robrujhodapp, elopio: ok but if you've resubmitted Yet Another MP, you need to make sure the newest MP is in the spreadsheet and reconfig again20:35
robruyeah20:35
elopioit still says there are conflicts.20:36
elopiolaunchpad is drunk20:36
bfillerrobru: could you please reconfigure silo 16? I added history-service20:36
robrubfiller, done20:38
bfillerrobru: cheers20:38
robrubfiller, you're welcome20:39
elopiorobru: if we ignore launchpad, will it merge fine when you publish?20:39
robruelopio, i imagine so... it doesn't merge in launchpad, it downloads trunk, downloads the branch, merges them, then pushes. so if there's no conflict it should work fine20:39
elopiojhodapp: sounds good? ^20:40
jhodappelopio: worth a shot though I'd kind of like to know why it says there's a conflict20:41
elopiojhodapp: there used to be a conflict on debian/changelog on barry's branch.20:42
elopiobut he solved it.20:42
jhodappelopio: it's just kind of weird20:44
elopioI agree. But I tried merging the three to trunk, and there are no conflicts. Also merge trunk with the three in order.20:46
elopiooh, the resubmit needs a commit message.20:57
tvossslangasek, charles seems like the silo is good to go for testing20:58
tvosskgunn, ^20:58
charlestvoss, ack20:58
charlestvoss, 8?20:58
tvossslangasek, charles, kgunn could you guys let me know your results?20:58
tvosscharles, yup20:58
kgunnyep20:58
charlesyes20:58
tvosskgunn, charles, slangasek just sent a mail21:00
Laneyis there a general way to get ci train to substitute the version it's about to release?21:32
Laneyin this case it's for a .maintscript file21:32
kgunntvoss: looks good21:34
robruLaney, not sure what you mean? can you just write the .maintscript to parse the version out of the changelog? the built package will have the changelog.21:35
Laneyno21:36
LaneyThe advice from dpkg-maintscript-helper(1) is to specify current-version~, but I don't know what the current version is going to be21:37
Laneyguess I could just upload :-)21:37
robruLaney, you should be able to predict the current version, since it's just upstream+14.10.2014MMDD-0ubuntu121:38
robruperhaps with a .1 in there if it's your second build of the day21:38
robruusing UTC time21:39
Laneyhow do I know what MMDD are going to be?21:39
barryrobru, slangasek third time's the charm: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+build/619526521:39
LaneyI think there's some magic thing for symbols files21:39
robruLaney, right now in UTC. you're going to put the MP in a silo and build it right now, yeah?21:39
Laneythat's a similar case21:39
robruLaney, there is a magic thing for symbols, but it isn't hooked up for maintscripts21:40
Laneynod21:40
robruLaney, how specific does the version have to be? Can you pick a MMDD that is greater than what's currently in the archive, but lower than what the next release will be?21:40
robrubarry, cool, gonna publish then?21:41
LaneyMaybe...21:41
barryrobru: the dashboard hasn't caught up yet, but after that... much testing first!21:42
robrubarry, ah, it polls on a 5min interval, should be done soon21:42
barrycoolio21:43
sil2100robru: just to make sure - did you fix the issue already?21:43
robrusil2100, oh yeah, sorry. you deleted one too many lines, brought it back and redeployed, it's working now. forgot to email you21:44
sil2100Since I see that for some unknown reason  the check-publication-migration script is missing a line21:44
sil2100Yeah21:44
sil2100Thanks ;)21:44
robrusil2100, thought you'd be gone by now ;-)21:44
sil2100o/21:44
robrusil2100, have a good weekend21:44
sil2100I go now then ;)21:45
robruLaney, wait21:46
robruhahaha21:46
* Laney wibbles21:46
robruLaney, just looking at the citrain code. it iterates over the files in debian/ looking for 0replaceme, but it skips files that don't contain 'symbols' in the name21:46
robruLaney, would be trivial to remove that check and do that substitution in all files21:46
robruLaney, although if I drop that check it'll make a changelog entry saying it updated symbols, might need a little more finesse than just dropping the check21:47
Laneydoes it replace with just the upstream version?21:48
robruLaney, yes it seems to replace with the upstream version21:48
LaneyI need the full version, although I guess that's always just -0ubuntu121:48
robruLaney, yeah21:48
robruLaney, you should be able to do 0replaceme-0ubuntu121:49
robruLaney, want me to make this change? shouldn't be hard.21:49
Laneyrobru: That'd be nice, then we can try it out Monday21:50
LaneyCan't think of any possible unintended consequences21:50
robruLaney, and if so, should I bother to check for "maintscript" in filename, or just do it for all files? do you envision any file under debian/* where you'd want a literal 0replaceme? it won't be escapable.21:51
LaneyIt's possible you'd want this in maintaner scripts too so I don't think I'd whitelist21:51
robruLaney, ok, I'll tinker and deploy something shortly21:52
LaneyProbably best to deal with any bad stuff as it comes up, because I can't really think where it might atm21:52
Laneycool, cheers21:52
robruelopio, jhodapp ok now just approve that last merge ;-)21:56
robrumterry, kgunn: ok now you guys can rebuild your system settings21:58
jhodapprobru: cool...elopio, which MR is it?22:01
robrujhodapp, https://code.launchpad.net/~brendan-donegan/mediaplayer-app/remove_scene_select_test/+merge/22739722:01
jhodappthanks22:01
robrujhodapp, you're welcome22:02
jhodapprobru: that makes me nervous that LP still says merge conflicts...I've not seen it wrong before22:02
robrujhodapp, that error doesn't even make sense. This merge doesn't even touch debian/changelog22:03
kgunnta22:03
jhodapprobru: right, just sayin :)22:04
jhodappelopio: robru: approved22:06
robruLaney, alright, I made that change and deployed in production, we'll find out soon if it explodes or not ;-)22:13
cjwatsonLaney: The maintscript doesn't need to match exactly; a lower bound is sufficient22:13
cjwatsonI would just put today's date in, and bump it if somebody else lands the package before you do22:13
robruLaney, as an added bonus, now when replacing 0replaceme, the changelog it generates will mention the specific filename changed, rather than just 'debian/*symbols' as it used to22:13
robrucjwatson, hah, too late! we support 0replaceme in in maintscripts now ;-)22:14
cjwatsonI mean, if there's more automation, great, just worth understanding what the real constraints are too ...22:14
Laneycjwatson: Yes I know22:17
Laneyrobru: cheers I'll try it out next week22:28
robruLaney, you're welcome22:28
robrucjwatson, still around? need an archive-admin ack on some new binary packages https://ci-train.ubuntu.com/job/landing-012-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scope-click_0.1+14.10.20140718.1-0ubuntu1.diff22:33
cjwatsonhuh, I thought we were having a call to talk about the design of that on Monday, so seems kinda premature22:34
robrucjwatson, dunno, blame alecu and mhr322:34
alecucjwatson: as I mentioned on the email thread, we're landing what we have so far; the call is to discuss ways to prepopulate that db, and any possible change.22:36
cjwatsonrobru: as an archive admin I have no objection; as a click developer I'm not so sure, but I guess this is unwindable22:36
cjwatsonso go ahead22:37
cjwatsonalecu: ok22:37
alecugreat, thanks.22:37
robrucjwatson, alecu thanks22:37
cjwatsonnot around from here on though :)22:38
alecuhave a great weekend :-)22:38
cjwatsonta22:38
cjwatsonI'm sure I'll enjoy working on RTM bits in spare moments ;-)22:38
bfillerrobru: need another reconfig on silo 1622:59
bfillerplease22:59
robrubfiller, done: https://ci-train.ubuntu.com/job/prepare-silo/1086/console23:00
bfillerrobru: thanks :)23:00
robrubfiller, you're welcome23:01
bfillerrobru: if I'm only removing a package from the silo (history-service) do I still need to rebuild the whole silo before releasing?23:01
robrubfiller, nope, just need a WATCH-ONLY build (and for me to delete the package from the ppa)23:02
bfillerrobru: ack23:02
robruwhich, it's not in the ppa, so you're good ;-)23:02

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