/srv/irclogs.ubuntu.com/2015/01/12/#ubuntu-ci-eng.txt

imgbot=== IMAGE 63 building (started: 20150112-02:10) ===02:10
imgbot=== IMAGE RTM 191 building (started: 20150112-03:10) ===03:10
imgbot=== IMAGE 63 DONE (finished: 20150112-03:25) ===03:25
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/63.changes ===03:25
imgbot=== IMAGE RTM 191 DONE (finished: 20150112-04:15) ===04:15
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/191.changes ===04:15
bzoltanrobru: if you still here :) Mirv will not be around for three weeks05:57
robrubzoltan: ah but sil should be back today ;-) what's up?06:21
bzoltanrobru:  his family income per capital just got reduced by about 27%06:24
robrubzoltan: I hope that's a euphemism for "having a child" because otherwise that sounds like a really shitty pay cut...06:25
bzoltanrobru:  as his manager I can ensure that his pay did not change :D06:26
robrubzoltan: who are we talking about? I thought steve was sil's manager?06:27
bzoltanrobru:  Ohh ... Mirv is reporting to me06:30
robruah06:30
robrubzoltan: so what can I do for you? I don't see anything to do in the dashboard06:30
bzoltanrobru:  nothing right now :) I just informed you. I will have two landings today .. both vivid and RTM... hopefully. The silo1 in both. But RTM needs QA signoff and the vivid needs some testing06:52
robrubzoltan: OK, I'm eoding now, but sil should be around shortly to publish stuff06:53
sil2100Morning07:33
=== sil2100 changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: -
tvossgood morning07:58
tvosstrainguards, could someone reconfigure the silo for line 30 in the spreadsheet?07:58
sil2100tvoss: sure!08:18
sil2100Reconfiguring08:18
tvosssil2100, welcome back and a happy new year :)08:18
tvosssil2100, thanks08:18
sil2100tvoss: thanks :) Is that silo 20 that you want reconfigured?08:18
tvosssil2100, silo 10 it is08:19
tvosssil2100, should become an rtm silo08:19
sil2100Ah, so it's line 21 then08:20
sil2100tvoss: hm, ok, so in this case we need to free this silo and re-assign it, as only this way we can change the target series08:21
sil2100tvoss: is that ok?08:21
tvosssil2100, sure08:21
sil2100tvoss: ok, reassigned - just be aware that you already have a location-service rtm silo in 00508:30
tvosssil2100, thank you08:30
Saviqtrainguards ↑ indeed, please do :)08:50
sil2100o/08:50
sil2100Love RTM fixes :)08:50
sil2100Saviq: assigned08:52
Saviqsil2100, o/ welcome back!08:53
Saviqsil2100, the spreadsheet doesn't look good (yet?)08:56
sil2100hmm, the spreadsheet never looks good! And it's really slow08:57
Saviqok let's see if it gets up to speed soon08:57
sil2100I would decrease the update timers a bit, but now that we have more silos than before it might again just die and race a lot08:58
* ogra_ yawns09:08
Saviqogra_, welcome back :)09:09
ogra_hey hey ... happy new year :)09:09
ogra_sil2100, looks like the last system-settings upload broke 120 tests on RTM09:11
sil2100Happy new year indeed09:13
sil2100ogra_: when was the system-image upload?09:14
sil2100Damn, my commitlogs are broken again, crap09:14
ogra_bah09:19
brendandsil2100, ogra_ - hey long time :)09:19
ogra_yeah, 4 weeks :)09:19
ogra_feels like it was last year though09:20
brendandogra_, it was :)09:21
ogra_:)09:21
=== chihchun is now known as chihchun_afk
sil2100Ah... I see why commitlogs broke, of course09:27
sil2100Out of disk space again...09:27
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
tvosstrainguards, can I haz silo for line 52, please?09:59
sil2100tvoss: sure! We have a meeting now, so will assign once it's over09:59
tvosssil2100, thx09:59
sil2100tvoss: wow, another location-service silo? ;)10:10
tvosssil2100, yup10:10
tvosssil2100, got some fixes staged, landing one by one10:11
sil2100hm, btw. I still don't see this bug as approved by the product team10:11
sil2100I'll assign it but make sure you push them to review it10:11
pstolowskitrainguards, hello, may i ask for reconfiguring of silo rtm 11 (added MP from another project, my attempt to reconfig failed)10:15
pstolowski?10:15
sil2100pstolowski: sure thing :)10:23
sil2100pstolowski: reconfigured10:24
pstolowskisil2100, thanks!10:25
popeydavmor2: have updated http://pad.ubuntu.com/MusicAppManualTesting for latest tests for search10:31
davmor2popey: yeah it'll be me testing latter on I'll give you a ping after lunch when I start on it10:32
popeydavmor2: awesome, thanks. If you see I missed any test cases let me know and I'll add them. want to make it as comprehensive as possible.10:35
davmor2popey: will do10:36
popeyta10:36
sil2100zbenjamin, bzoltan: I'm trying to assign a silo for you right now but seem to be encountering some problems, in the middle of debugging those now11:31
sil2100Ah11:32
sil2100Ok, see the problem11:33
sil2100zbenjamin, bzoltan: could anyone of you re-submit and re-approve the https://code.launchpad.net/~binli/qtcreator-plugin-ubuntu/lp1409596/+merge/246089 merge? Currently it's targetting lp:ubuntu/qtcreator-plugin-ubuntu which is not your trunk, it's the distro branch11:34
brendandsil2100, can you get me the last version of system-settings?11:34
brendandsil2100, i'll try reverting it now11:34
zbenjaminsil2100: ok11:34
sil2100brendand: you mean, you want the last working (non broken) version of u-s-s?11:35
brendandsil2100, well just the previous version11:36
sil2100brendand: well, it seems there have been multiple releases since image #186 when autopilot broke11:36
sil21000.3+15.04.20141211~rtm-0ubuntu1 is the version pre-#186, I can fetch you the packages for that11:37
brendandsil2100, ok11:37
sil2100brendand: http://paste.ubuntu.com/9717897/11:38
zbenjaminsil2100: i changed line 53 to target the correct version11:39
zbenjaminsil2100: uh something is wrong11:41
zbenjaminsil2100: we remove that mp11:41
zbenjaminsil2100: i completely removed it now11:41
=== MacSlow is now known as MacSlow|lunch
bzoltanzbenjamin: sil2100: let's just reject that MR ..11:50
zbenjaminbzoltan: i just set it to "needs fixing"11:51
zbenjaminbzoltan: and removed it from the lnading11:51
sil2100zbenjamin, bzoltan: so you don't need it in this landing?11:52
sil2100Ok, let me assign then now11:53
zbenjaminsil2100: no it can wait till its fixed11:53
zbenjaminsil2100: thx :)11:54
sil2100yw :)11:55
davmor2popey: just signed into instagram and facebook on 191 I photos for both :)12:24
popey12:24
popey#191?12:24
* sil2100 goes to lunch12:47
davmor2popey: latest rtm image12:47
popeyhm12:49
popeydavmor2: Dispatching search: "com.canonical.scopes.instagram_instagram" "" ""12:51
popeyfile:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool12:51
popeyi get that in my unity8-dash.log12:51
davmor2popey: one for cwayne when he gets up then12:52
popeyyeah12:52
popeythanks for checking12:52
davmor2popey: no worries moving onto Music app after Lunch12:52
popeyta12:52
rsalvetiogra_: happy new year :-)12:52
popeyChinese new year already? ☻12:52
ogra_rsalveti, same to you !13:00
=== alan_g is now known as alan_g|lunch
cwaynedavmor2: changelog sent :)  sorry if its late, was a bit sick friday :/13:01
=== greyback_ is now known as greyback
popeycwayne: *pounce*13:02
davmor2cwayne: poor excuse ;)  I can look at it latter :)13:03
popeycwayne: http://people.canonical.com/~alan/screenshots/device-2015-01-12-130210.png13:03
popeycwayne: Dispatching search: "com.canonical.scopes.instagram_instagram" "" ""13:03
popeycwayne: file:///usr/share/unity8/Dash/CardTool.qml:179:38: Unable to assign [undefined] to bool13:03
popeyi do have an account setup, but it doesnt seem to work13:03
cwaynepopey: that's an old version, if you go into system settings -> accounts -> instagram, is the scope checked off to grant access?13:06
popeycwayne: scope not listed13:06
popeycwayne: I'm on the very latest image13:06
popeycwayne: http://people.canonical.com/~alan/screenshots/device-2015-01-12-130616.png13:07
cwaynelatest promoted or latest -proposed13:08
cwaynealso, what does account-console list show13:08
cwaynei think this is another instance of stuff getting borked when i had to move the account-plugin into the same click to make sure that it could get into the store13:08
popeyi am on proposed13:09
popeyubuntu-touch/ubuntu-rtm/14.09-proposed13:09
cwaynepopey: try running this then rebooting: adb shell "sqlite3 /home/phablet/.config/libaccounts-glib/accounts.db \"UPDATE Services SET provider='com.canonical.scopes.instagram_instagramaccount' WHERE provider='com.account.plugin.instagram_instagram';\""13:14
popeyhmmm13:16
popeynice13:28
popeycwayne: that fixed it, thank you13:28
cwaynepopey: np13:39
=== alan_g|lunch is now known as alan_g
=== MacSlow|lunch is now known as MacSlow
=== karni is now known as karni-afk
jdstrandcwayne: hey and happy new year :) fyi rtm silo 010. we'll need a custom tarball regeneration14:43
sil2100o/14:53
=== chrisccoulson_ is now known as chrisccoulson
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: -
ollia15:05
cwaynejdstrand: happy new year to you as well :)  when do you expect silo 10 to land?  we were about to land a custom tar, but if yours is imminent we can hold off til later today/tomorrow to coordinate15:09
sil2100brendand: how's the system-settings AP investigation going?15:16
brendandsil2100, interestingly...15:17
sil2100brendand: is it still reproducible in the previous u-s-s version?15:17
brendandsil2100, yes. the working theory now is the regression is in some package that is installed by the test. maybe autopilot itself15:17
brendandsil2100, so we need to look at dates/times15:18
sil2100http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/186.commitlog <- this is what landed in #186, so I suspect it's one of those packages that caused it15:18
brendandsil2100, what changed between the time it last worked and the time it started failing15:18
sil2100There's an UITK change in this image, but the description seems unrelated, hm15:19
jdstrandcwayne: I've been waiting for QA signoff since last... thursday?15:20
jdstrandcwayne: I was told that qa should do it sometime today15:20
jdstrand*by* sometime today15:20
cwaynehm, ok15:23
cwaynedavmor2: sil2100^ i think we should probably then hold off on custom until that lands15:23
sil2100jibel, brendand, davmor2: ^ ?15:23
cwayneotherwise you'll have to do custom twice :)15:23
pmcgowanQA page says silo 10 passed15:24
pmcgowanjdstrand, ^^15:24
jdstrandoh, I just checked the spreadsheet a few minutes ago...15:24
jdstrand(the landing spreadsheet)15:25
jibelsil2100, jdstrand rvr tested it15:25
jdstrandthe landing spreadsheet still says 'QA needs to sign off'15:25
jdstrandbut, that's fine15:25
jdstrandcwayne: looks like it passed. I guess you can regenerate?15:25
cwaynejdstrand: well, is it in the image/archives yet?15:26
jdstrandcwayne: no. that's right, I forgot, you need it there first15:27
jdstrandso, if someone tells me to push it, I will15:27
davmor2jibel: I wonder if rvr is having the issue I have sometimes you change the spreadsheet to passed it looks to change for you but the sync to actually change the sheet is dead so it never gets updated except locally,  I of course blame ogra_ for that ;)  \o/ so glad ogra_ is back :)15:29
sil2100jdstrand: is that rtm silo 10?15:29
jdstrandsil2100: it is15:29
sil2100jdstrand: hm, it's not set to tested done by QA yet on the spreadsheet, right?15:30
sil2100Or are my eyes just wrong?15:30
davmor2rvr: you tested silo10 right?15:30
jdstrandsil2100: you are right and so are mine. others said it was tested by qa on some other list15:30
sil2100ygh15:30
jibeldavmor2, don't get me started on spreadsheets please15:30
sil2100davmor2, jibel: yeah, sometimes the spreadsheet times out and doesn't save the change...15:31
pmcgowanjdstrand, sil2100 I think rvr just forgot to mark it https://trello.com/b/AE3swczu/silo-testing15:31
brendandsil2100, i need to get the old autopilot package for system-settings, where would that be?15:31
jdstrand(rvr, btw, thank you for testing)15:31
sil2100brendand: hm, hmmm15:31
sil2100brendand: wait a moment15:32
davmor2sil2100: yeah I'm guessing that is what has happened here as the silo is in the passed section of the trello board15:32
sil2100brendand: that's actually a valid question15:32
sil2100brendand: ah, crap!15:32
sil2100brendand: ok, let me give it to you15:33
jibelbrendand, you can find all the version here https://launchpad.net/ubuntu-rtm/+source/ubuntu-system-settings/+publishinghistory15:33
sil2100brendand: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-002/+build/6635435/+files/ubuntu-system-settings-autopilot_0.3%2B15.04.20141211%7Ertm-0ubuntu1_all.deb15:33
jibelbrendand, select i386 for the autopilot tests15:33
bfillersil2100: could you rebuild rtm silo 2 with different version numbers. The maliit-framework that is getting synced is a lower version number than what's in rtm already https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-00215:39
sil2100bfiller: let me take a look at that and try dealing with it15:42
sil2100Sadly sometimes that happens...15:42
bfillersil2100: thank you15:42
sil2100bfiller: yeah, I'll fix that, since it's a common issue with the current train15:43
cwaynejdstrand: which version of a-e-u would i need for generating the new cache?15:44
alex_abreutrainguards ubuntu-rtm silo 15 is a FP, I got confused flagging the line above as ok15:59
alex_abreu^^15:59
sil2100alex_abreu: ACK15:59
alex_abreusil2100, thx16:00
=== chihchun is now known as chihchun_afk
sil2100oSoMoN: hey! The sync request of webbrowser-app - does that carry fixes for the current milestone?16:08
oSoMoNsil2100, it’s not been formally approved yet, it’s more of a request to allow testing to verify what would happen if we were to backport trunk to rtm16:10
rvrpmcgowan: jdstrand: Right, sorry, I forgot to mark it16:12
sil2100oSoMoN: ok, so I'll assign a silo but leave a comment about that16:12
sil2100Oh, ok, nevermind16:12
oSoMoNsil2100, I just added a comment to make it explicit, thanks16:12
sil2100Comment there ;)16:12
sil2100Thanks!16:12
jdstrandcwayne: 1.2.4016:15
jdstrandcwayne, sil2100: let me know when to push it and I will16:15
cwaynejdstrand: i'm ready whenever you guys are16:15
sil2100rvr: did you mark it as ready? Can we land it? Just double confirming16:16
=== karni-afk is now known as karni
jdstrandsil2100: 10:12 < rvr> pmcgowan: jdstrand: Right, sorry, I forgot to mark it16:16
jdstrandcwayne: do you have someone from qa who is tasked with testing your new custom tarball already?16:17
jdstrandbasically, I don't want to push it and then the custom testing/push lags16:17
sil2100jdstrand: then it's all fine for me for releasing it, cwayne would that slow you down or can we release?16:18
rvrsil2100: I found a problem with silo 6 + silo 0 + silo 10, although I think it's only a matter of silo 6 (ciborium).16:20
cwaynesil2100: if we have people to test custom + spanish custom in ~30 minutes so that we dont have a long first boot im good16:21
sil2100davmor2: are you busy now?16:21
davmor2sil2100: what?????16:22
sil2100davmor2: we needz ze custom tested in ~30 minz!16:22
sil2100Will you have time then?16:23
* jdstrand notes he has not pushed anything16:23
jdstrandI can push at a time that is convenient for cwayne and qa16:23
davmor2sil2100: No I'll be in a meeting in 30 minutes I can test after the meetings and tea though16:23
sil2100What a coincidence, I'll be in a meeting in 30 minutes as well16:24
sil2100alex_abreu: hey! Can you make sure all merges in silo 008 are approved?16:31
alex_abreusil2100, sure16:31
sil2100alex_abreu: tell me when I can re-publish the silo16:35
alex_abreusil2100, ok you can16:36
sil2100brendand: any luck on the investigation? Do you think this should block our promotion plans for today?16:42
brendandsil2100, yeah, reverting the autopilot package fixes it16:42
brendandsil2100, but there's nothing we can do about that now. blocking the promotion won't achieve anything16:43
* sil2100 checks the diff16:43
sil2100brendand: yeah16:43
cwaynesil2100: jdstrand: so what's the deal?  would davmor2 and rvr be able to test the customs16:45
sil2100cwayne: yeah, after our landing meeting in 15 minutes davmor2 should still have some time I suppose16:45
cwaynesil2100: we'd need someone to test spanish too, at least a brief check -- we need to keep them in sync16:49
* davmor2 blames ogra_ for all file corruptions now, you just keep lining up jobs to blame you for :P16:49
jdstrandsil2100: so, should I push it now then?16:50
sil2100rvr: you around for some time still, right?16:51
rvrsil2100: One hour or so16:53
sil2100jdstrand: ok, so please push it if you can :)16:53
jdstrandok, I'll do it in just a moment16:54
sil2100davmor2, rvr: once jdstrand releases his silo, could you take a look at the custom+spanish_custom tarballs?16:55
rvrsil2100: I can take a look, but can't promise I'll finish today16:56
davmor2sil2100: NO :P :D16:56
rvrjdstrand: Seems the issue I found is known and not related to the silos16:57
jdstrandcwayne: ok, pushed ^16:59
cwaynejdstrand: thanks17:00
jdstrandnot sure when the spreadsheet or the dashboard will be updated...17:00
bzoltansil2100: I would like to execute an experiment. I would like to see how the latest UITK Vivid landing (silo1) behaves with the RTM image. May I ask for a silo with the same MR just for build and test? So not to land, but to run the tests and see all the builds.17:01
sil2100bzoltan: hm, ok, we can do that, we just need to make sure it's commented everywhere that it's not meant to be landed then17:02
sil2100ogra_: hey! Will you make it for the meeting?17:04
bzoltansil2100: I will make a branch and will not top approve it ... so it will not land and I will change the control file, so it can not accidentally land ... plus add DO NOT LAND in every possible comment field.17:04
ogra_sil2100, yeah, justfinishing up the snappy one ...17:04
sil2100ogra_: ACK17:04
ogra_(gimme a few)17:04
cwaynejdstrand: sil2100: ah, wed need a rootfs with the new a-e-u right17:05
jdstrandcwayne: yes17:05
jdstrandthat should be coming (1.2.40 is in -proposed atm: https://launchpad.net/ubuntu-rtm/+source/apparmor-easyprof-ubuntu/1.2.40)17:06
sil2100davmor2: meetong17:07
cwayneogra_: sil2100: ^ can we get an rtm rootfs kicked off once 1.2.40 is in 14.0917:08
ogra_i guess we can17:08
=== plars changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: -
brendandkenvandine, sil2100 - here's a bug for tracking the issue: https://bugs.launchpad.net/ubuntu-rtm/+source/ubuntu-system-settings/+bug/140980917:13
ubot5Launchpad bug 1409809 in ubuntu-system-settings (Ubuntu RTM) "Autopilot tests fail due to system settings not being able to start" [Undecided,New]17:13
kenvandinebrendand, thanks17:14
jdstrandogra_, sil2100 (and cwayne): https://launchpad.net/ubuntu-rtm/+source/apparmor-easyprof-ubuntu shows 1.2.40 is in release17:15
jdstrand(fyi)17:15
cwaynejdstrand: thanks, kicking custom now17:16
ogra_check if rmadison agrees ;)17:17
ogra_(obviously does)17:17
pstolowskiqa, hey, what is the deadline for current wave of rtm fixes (for having them tested in silos)?17:32
davmor2sil2100, jibel: emulator is good but some apps have been removed so I have had to invalidate the one test for now, and modified the downloaded app for ebay so that one could pass.  So it is as good as it ever is17:35
cwaynesil2100: davmor2: rvr: so assuming an RTM rootfs has been kicked, I think the custom image to test will be 27017:35
davmor2cwayne: thanks17:35
rvrcwayne: Is there a new image for custom-proposed-es?17:36
rvrI was flashing 4317:36
cwaynervr: there will be with the new rootfs, it would be 4517:37
rvrcwayne: Ok17:37
cwaynervr: the scopes will be the same in 43 and 45, so if you want to test the OOBE on 43 then all that would need to be checked on 45 is that the cache was updated17:37
cwaynei've got to go run some errands, so all please shoot me an email if there's any questions17:39
sil2100davmor2: \o/17:42
sil2100davmor2: thanks!17:42
sil2100jibel: so, any final words before we promote?17:42
jibelsil2100, +1 to promote17:42
sil2100jibel: it's 188, right?17:43
jibelsil2100, krillin/rtm/188 is what we tested17:43
sil2100ogra_: could you promote rtm 188 for krillin and its counterparts for mako and emulator? :)17:43
jibelsil2100, mako 157 and the rest is 15117:43
sil2100The spanish might be also needed to be promoted, right?17:43
ogra_sil2100, sure, gimme a bit17:43
sil2100But not sure if it got tested well enough17:44
jibelyes17:44
bzoltansil2100:  ^ this is my experimental silo request17:52
sil2100bzoltan: I love the big caps-lock warning!17:52
bzoltansil2100: :D17:52
sil2100;)17:53
ogra_=== IMAGE RTM 13 promoted ===18:06
ogra_that is: krillin 188, mako 157, emulators 15118:06
ogra_jibel, which es image should i promote ?18:06
jibelogra_, 13718:07
ogra_thx18:07
ogra_=== IMAGE RTM.es #7 promoted ===18:09
ogra_(krillin 137 as above)18:09
sil2100ogra_: thanks! :)18:09
=== alan_g is now known as alan_g|EOD
bzoltansil2100:  would you please reconf the rtm silo1018:11
sil2100bzoltan: sure18:20
sil2100ogra_: is emulator image promoted as #13 as well? Or as #12?18:20
ogra_sil2100, oh, right, yeah, emulator is one behind18:21
rvrogra_: Is es-proposed-customized still building?18:24
ogra_rvr, i dont think anything is building atm18:25
sil2100bzoltan: done ;)18:25
sil2100Ok, I'm off outside now, bbl18:25
rvrcwayne: No image 45 then? :-/18:25
ogra_rvr, es-proposed-customized is nothing we build, thats solely cwayne's thing i think18:26
rvrogra_: Ah, ok18:26
rvrI'm hitting [F5] on that channel compulsively :)18:27
ogra_44 is from 1h ago apparently18:27
ogra_do you expect anything newer ?18:27
rvrYup, cwayne specifically mentioned 4518:27
ogra_ah, k18:28
tedgtrainguards, can I get vivid silos for lines 59, 60 and 61 please?18:28
robrutedg: on it18:30
tedgrobru, Great, thanks!18:30
robrutedg: well row 59 will need to be not blank before I can assign it18:31
tedgHmm, not blank for me…18:31
robrutedg: rows 60 and 61 got 8 and 1318:32
robrutedg: weird, just refreshed the spreadsheet and line 59 showed up. weird sync glitch I guess18:32
tedgrobru, Okay, whew, I couldn't figure out anything else to do to it :-)18:33
robrutedg: line 59 got silo 16 ;-)18:33
tedgrobru, Cool, thanks!18:34
robrutedg: worst case, reload the spreadsheet, if the row was missing, re-enter the data. it happens sometimes.18:34
robrutedg: you're welcome!18:34
* tedg wonders if 2015 will be the year the spreadsheet dies18:36
davmor2cwayne: 2015/01/12 18:38:02 Flashing version 269 is still trying to be downloaded :(18:38
robrutedg: I would guesstimate we are a month away from killing the spreadsheet. it's happening, just slowly.18:38
robruor rather, "it's happening, just constantly fraught with setbacks and distractions."18:39
davmor2tedg: also robru lies ;)18:39
tedgdavmor2, So there's no setbacks and distractions? ;-)18:40
* tedg will not miss the spreadsheet18:40
tedgOkay, packages building, device reflashing, lunch!18:41
robrutedg: you and everybody else! (not missing the spreadsheet, that is, not lunch)18:44
robrubfiller: silo 1718:45
cwaynewait so was there a new rootfs18:55
cwayneogra_: ^18:56
robruslangasek: sil2100: Ursinha: I vote we cancel our meeting now as there's not much to discuss (I'll send an email update shortly with some staging instance details)19:00
robruunless anyone disagrees...19:01
cwaynedavmor2: ^19:02
slangasekrobru, sil2100, Ursinha: well maybe sil2100 wants to say happy new year to everybody? :)19:03
slangasekbut I'm ok to cancel if you all agree there's nothing to discuss19:03
robruslangasek: aha, already did say happy new year at that other meeting 2 hours ago ;-)19:04
slangasekheh19:04
sil2100Happy New Year!19:07
sil2100;)19:07
sil2100No, I'm fine with skipping, I just got back like 10 minutes ago anyway19:07
robrusil2100: k, great.19:08
robrusil2100: I'm still working on the staging bringup. I fixed SSO but now there's some firewall issue stopping it from working. once I get a successful build out of it I'll email those instructions on how to use it.19:08
cwaynesil2100: was there a new rootfs kicked? if not we can just do the custom test tomorrow morning19:13
slangaseksil2100: Šťastný nový rok19:14
davmor2sil2100: ogra_ talk to us please19:15
sil2100davmor2: hey!19:15
sil2100cwayne: no new rootfs was kicked19:15
davmor2sil2100: cwayne so tomorrow am then right?19:16
sil2100We didn't have a new image yet, there will be an auto-build later at night19:16
davmor2sil2100: that'll be too late for anyone to test though at a guess19:16
sil2100We wanted to have the custom landed so that the new image doesn't have any issues19:16
sil2100We could theoretically disable the cronjob and just kick the image manually tomorrow once the custom is tested...19:17
sil2100robru: ugh, ok, thanks!19:17
davmor2sil2100: custom needs the new rootfs to be tested though19:17
sil2100davmor2: can you test it with changes from a silo?19:19
davmor2sil2100: how many silos have landed?19:19
sil2100For RTM it might have been only one silo landing today19:19
sil2100davmor2: since if we have a new rootfs (a new image) built during the night, this would mean some users will get long boot times, right?19:20
davmor2sil2100: well there is the 3 that meant that silo 10 could land and then I think there were one or 2 so that is 4-5 and then that has to be installed after the custom tarball image has been installed19:21
davmor2not sure how well that would work19:21
sil2100davmor2: hm, why so many silos? Today there was only this silo landing, and we have a rootfs with all the others already19:22
davmor2sil2100: silo 10 depended on 006 and 001 and then there is any that have passed today19:24
sil2100davmor2: yeah, but none of those landed yet, only silo 1019:25
sil2100So do we need to land 006 and 001 along with the tarball?19:26
davmor2sil2100: so I'm around for 30 minutes, and by the sound of it if the app armor fix isn't in place it will take 10 minutes to boot the image after I have bootstrapped on the image to test that has the tarball in place19:27
davmor2sil2100: the problem we have is that cwayne has been waiting for the new rootfs to build so he could trigger the tarball and we test image 270, we can test 269 and install all the ppa's but that kinda defeats the object,  so it looks like this will get tested in the morning now by the sound of it :(19:31
sil2100Ok, then there was some miscommunication here then19:32
sil2100hm, so I would actually prefer everything happening at once19:32
sil2100So maybe let's disable the cronjob for today, what do you say?19:33
davmor2sil2100: what does cancelling the cronjob do though?19:34
davmor2sil2100: you can build the new rootfs and then we just test the new 270 image in the morning19:34
davmor2sil2100: we need the app-armor fix in place so that the custom image doesn't take a week to boot unless I'm misunderstanding cwayne19:36
cwaynerighto19:36
davmor2sil2100: so as I see it we can cancel the cronjob, do a manual build first thing tomorrow your time, which should finish when I get online I can then test the new 270 image and a few hours latter you can release that done.  The other thing we could do is remove the ota tag from the build that we make so that cwayne can build on it but users don't upgrade to it19:39
cwayneso i've got the custom tar all set davmor2 since it's in the archive19:41
cwayneso if you cancel the cron and do it early UK time, you guys can start testing as soon as a rootfs is done19:41
davmor2sil2100: ^19:42
sil2100hm, ok19:44
sil2100So then I misunderstood it, I thought it's actually the other way around19:44
sil2100Then we don't need to disable the cronjob as, if I understood davmor2 and cwayne now, releasing the custom tarball would cause the long boot times19:45
sil2100If that's the case, then let's leave everything as it is and take care of the custom tomorrow morning19:45
davmor2sil2100: wilko19:45
cwayneno no no19:46
cwaynethe rootfs will cause the long boot times19:46
cwaynethe custom will fix it19:46
sil2100Ok, so it's as I thought19:46
sil2100davmor2: ^19:46
cwaynebut the custom is already built, so it can be tested as soon as the rootfs is done19:46
cwaynei.e. doesn't need to wait for my morning19:46
davmor2head is spinning now19:47
sil2100Yeah, but it's best if those two are done with as short delay as possible, so let's disable the cron and do the rootfs build and custom testing on davmor2's morning19:47
sil2100ogra_: hey! Could you disable the cronjob for building rtm images for today? :)19:47
davmor2sil2100, cwayne: right so we need to test what is there now which is 269? then retest that the new rootfs doesn't break it when the 2 converge?19:48
cwaynedavmor2: we could do that, since 269 has the scopes changes19:49
cwaynebut 270 will have the properly aligned cache19:49
davmor2cwayne: but 270 doesn't exist unless it just hasn't build yet19:50
cwayneright19:50
cwaynethat will be the new rootfs with the proper apparmor19:50
davmor2cwayne: and we can't build a new rootfs without releasing it, which will mean people have issues with boot times, for several hours until we can release the tarball that fixes it19:51
sil2100ogra_, slangasek: if anyone of you could disable the cronjob for ubuntu-rtm it would be awesome19:51
* sil2100 needs to EOD now19:51
sil2100o/19:51
slangasekok19:51
davmor2sil2100: night19:51
slangasekogra_: ^^ done19:52
kenvandinebrendand, so the tests passed for you with ubuntu-system-settings-autopilot=0.3+15.04.20141211~rtm-0ubuntu1 ?19:52
kenvandinebrendand, i got 96 failures with that version19:52
davmor2cwayne: so I'm assuming we will need to test what is there now, when that passes we then get ogra to work his magic and land the new rootfs and custom at the same time so there users never get a slow image19:53
cwaynedavmor2: yeah, we could pre-test what is there now, or wait and test it all at once19:54
cwayneim fine either way19:55
davmor2man this is harder than it needs to be I'm sure of it ;)19:56
kenvandinebrendand, but to even get that far, i had to install python3-evdev, which i think should be a depends somewhere19:56
kenvandineweird, python3-autopilot depends on python3-evdev20:01
kenvandinebut python3-evdev didn't get installed20:01
* kenvandine scratches head20:02
kenvandinebrendand, the second try i only had 4 failures with that old version, rather flaky :/20:29
kenvandineand my less_flaky branch didn't seem to help20:29
bfillerrobru: mind reconfiguring rtm silo 20 - I added a new package to sync20:37
robrubfiller: done20:38
bfillerrobru: thanks20:38
robrubfiller: you're welcome!20:38
dobeycihelp: what's the best way to get jenkins to run the test builds on an MP after it's already run a failed autolanding job?22:08
fgintherdobey, I don't quite understand. do you have a specific example?22:12
dobeyfginther: https://code.launchpad.net/~dobey/pay-ui/fix-card-cancel/+merge/24622322:12
dobeyfginther: it was set to approved before jenkins ran the standard MP test builds, and i set it to needs review to prevent it from landing (because it wasn't quite ready yet). now i'd like to get jenkins to run the normal MP test jobs for it, and hand the click that is built from that off to QA for testing, so they can approve it and we can land and release to the store22:14
fgintherdobey, ah ok. I can't remember if this will still be tested by a ci job or not... Regardless, I can manually trigger one.22:16
dobeyfginther: ok, please trigger on then. thanks :)22:17
plarsfginther: dobey: did you try reapproving it as the message there suggests?22:17
plarsfginther: shouldn't that cause it to retest?22:17
dobeyplars: i don't want to approve it yet22:18
fgintherplars, that's to re-try landing it. but that goes further than what dobey wanted22:18
dobeyright22:18
plarsgotcha22:18
fgintherdobey, it's building now22:18
dobeythanks!22:19
bfillerrobru: is there a way to rebuild syncevolution on rtm silo 20? Seemed it didn't get rebuilt when I rebuilt the silo after adding libsythesis22:54
robrubfiller: yeah in the build job you can specify to only build syncevolution22:59
bfillerrobru: I did a force rebuild of everything and it didn't get rebuilt22:59
bfillerrobru: but I'll try that23:00
robrubfiller: oh, look at the job, it's depwait23:00
bfillerrobru: but the dep should be there now23:00
bfillerseems to be anyway23:00
robrubfiller: hm, not sure why, but the most recent build job only uploaded the one thing, not both23:01
bfillerrobru: going to stop the build and just try to rebuild syncevolution23:02
robrubfiller: yeah, try that. if that doesn't work, try deleting the package from the PPA and then trying the build again.23:03
robrubfiller: or, you probably don't have perms to delete packages from the ppa. so if it fails again just ping me and I'll poke at it23:04
bfillerrobru: yeah looks like it needs to be deleted, the log says it's already there so not trying to upload it again23:05
robrubfiller: ok one sec23:05
robrubfiller: wait is this a no-change rebuild?23:06
bfillerrobru: yes23:06
robrubfiller: I may be able to rebuild within the PPA without touching train stuff, hang on23:06
robrubfiller: scratch that I botched it. ok, deleted, trying the upload again: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-020-1-build/61/console23:09
bfillerrobru: thansk23:13
robrubfiller: you're welcome23:13
robrubfiller: looks like you need to version bump. https://launchpadlibrarian.net/194662361/buildlog_ubuntu-rtm-14.09-amd64.syncevolution_1.5~rtm-0ubuntu2_MANUALDEPWAIT.txt.gz it wants ">= 3.4.0.47.5" but v "3.4.0.47.5~rtm-0ubuntu2" is actually less. I recommend changing the packaging so that it says >= 3.4.0.47.5~ that should work23:30
bfillerrobru: not sure how to do that - it's just a sync from vivid. can we tweak the rtm version numbers that get appeneded?23:32
robrubfiller: sure can't! ;-) I'm afraid this means you'll need to branch for RTM and then change this from a sync to an MP.23:32
bfillerrobru: ran into something similar this morning that sil fixed with maliit23:33
robrubfiller: oh really? how similar? can you show me some logs? Because neither sil nor I have any ability to deploy code changes in production at the moment, so it's literally  not possible to turn off the ~rtm version munging.23:35
robruunless he manually uploaded the package or something.23:35
bfillerrobru: he may have, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-00223:35
bfillerrobru: the version of maliit-framework has the ~rtm at the end now23:35
bfillerafter the ubuntu version23:35
robruindeed that package was manually uploaded by him23:36
robruhmmm23:36
robrubfiller: ok gimme a minute I'll poke at this. grumble23:37
robrubfiller: wow, ok, just discovered my GPG key expired a month ago, gonna need some time to make a new one and get it in keyservers so I can upload to the PPA.23:50
bfillerrobru: nice! thanks for help23:51

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