/srv/irclogs.ubuntu.com/2014/11/06/#ubuntu-ci-eng.txt

=== ribru is now known as robru
robruhurr durr i'm a shurr01:32
Mirvmorning again04:48
robruMirv: oh hello! I *just* merged some experimental stuff into production, so watch out for weird failures. I'll stay up for a bit to revert it if anything goes wrong, just ping me04:52
robruMirv: builds were tested in preprod but publishing and cleaning is totally untested and may explode04:53
robruindeed I've broken cleaning. excellent!04:54
robrutedg: false alarm, I'm breaking stuff04:55
Mirvrobru: ok :)04:55
robruheh, check-publication-migration is working ;-)05:01
Mirvrobru: publishing seems to be working, too05:01
robruMirv: oh sweet05:01
robruMirv: ok I'm gonna try to fix cleaning instead of reverting everything...05:02
robruMirv: but if I can't fix it in an hour then I'll revert and try again tomorrow05:02
Mirvsounds good05:02
Mirveh, that's not true though ^05:03
Mirvit's not yet anywhere, the keyboard05:04
Mirvthe rsync line looks correct so I'd expect it to appear soon though05:04
Mirvyes, now it appeared05:06
Mirvrobru: but the check-publication-migration failed there ^. it's still pending https://launchpad.net/ubuntu-rtm/+source/ubuntu-keyboard/0.99.trunk.phablet2+14.10.20141104~rtm-0ubuntu105:06
robrushit05:07
robrudamnit05:09
robruI didn't really touch check-publication-migration though.05:09
robruoh, I did tinker with a function that check_publication_migration calls. damn. ok I'm loading with debugging statements!05:11
robruhm05:19
robruok well i've fixed merge & clean05:20
robruMirv: ok I think I fixed check_publication_migration as well, but silo rtm 6 now really is published so it's tough to say. let's keep an eye on that...05:20
robruhmmm05:22
robruwut05:24
robrucihelp did citrain jenkins just get rebooted or something? strange anonymous job termination plus I got logged out just seconds after submitting a job05:25
robruoh well that's good at least ;-)05:25
robruMirv: ok check_publication_migration is fixed ^05:26
robruI like how check_publication_migration's default thing is to claim all packages are migrated in the event of an error. "oh something broke? all packages are migrated!!"05:26
robruugh05:27
Mirvrobru: ok, great!05:27
Mirvnice defaults05:28
Mirva bit like these "Error! Success!" of the past05:28
robruMirv: yeah it's the same old architectural deficiency shining through various cracks05:29
robrutedg: ok sorry for the highlight spamming there, your silo was successfully merged & cleaned despite that strange signal 15 message there. I confirmed your trunk branch has the right stuff in it ;-)05:30
robrusweet this is looking really good.05:54
robruMirv: ok I'm gonna land this05:54
Mirvrobru: sure, all seems good now so far05:56
robruMirv: ok I'll be around for a little bit, but if anything explodes, just run the deploy job with DEPLOY_PROD_REVISION set to -3 to get it back to a known working state. -2 will put it into a state where syncs don't work06:44
Mirvrobru: everything seems still fine, although I'm only playing with the qt silo atm07:31
Mirvprobably there will be no reason to deploy the older version07:32
robruMirv: yeah dunno, my last branch also seemed fine but then some corner car came up that was broken. The train is a fickle mistress07:33
robru*case07:34
Mirvthat she is07:36
popeyMirv: when you get a moment could you please upload  http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calendar_0.4.534_all.click - I think balloons may have tried last night, but I don't see it in the store.07:51
tvossgood morning07:56
Mirvpopey: calendar uploaded09:01
popeythanks Mirv09:05
sil2100Damn, I feel like a zombie09:06
ogra_hmm, unity8 is still freaking out in topbefore/after everywhere09:09
* Mirv has loads of crashes in /var/crash from playing around for the morning09:10
Mirvor had, rather, just reflashing09:10
ogra_we have only 3 in smoke-testing09:10
ogra_my volume overlay comes up at the very top of the screen again (covering the panel)09:12
ogra_this happens every other image to me ... totally random09:12
popeyogra_: on krillin? not seen that here09:14
ogra_popey, yeah, on krillin, i showed it to john-mcaleely at the sprint ... it was gone for a while but now i have it randomly back after every other OTA09:16
ogra_havent seen it for at least three images though09:17
ogra_hah, fun09:23
ogra_now it is gone09:23
ogra_(i disconnected my BT speaker)09:24
sil2100We still didn't get the CPU-load-fixes in, right?09:25
tvosssil2100, nope, one part of them is on the way in rtm 909:26
sil2100brendand, davmor2: for QA, how many people do we have now in the EU timezone? Just 2 people?09:27
sil2100tvoss: thanks :)09:27
* Mirv bootstrap flashed latest vivid, stares at spinning Ubuntu logo09:27
brendandsil2100, 409:28
* Mirv waits for the step 1 from the new QA plan to be implemented (only release images to -proposed that boot & run unity8)09:28
evrobru: it ran out of space09:28
brendandMirv, ?09:28
evSee #is-outage09:28
evAnd https://bugs.launchpad.net/ci-train/+bug/138996809:29
ubot5Error: ubuntu bug 1389968 not found09:29
brendandMirv, oh vivid. pfff09:29
Mirvbrendand: it was discussed during the sprint that there should be a gatekeeper that non-booting images wouldn't be released. I assume that would make sense (when it's available) on vivid too.09:29
Mirvbrendand: ;)09:29
brendandMirv, it would indeed09:29
Mirvbrendand: how much before you wanted this "rtm-022 ping"? there's something to test there now, I just find it a bit hard to test with the unity8 crashes and scope unreliability in general.09:30
brendandMirv, whenever you're ready to test it09:31
sil2100ev: hey! I'll comment on that in a minute09:31
evThanks sil210009:31
Mirvbrendand: I'm ready to test it in the sense that lorn could use feedback on the bug whether there's an improvement or not. I did get music scope image downloads over 3G, but I also had problems that I don't know if they are related to the qtbase or the unity8 problems.09:33
john-mcaleelyogra_, did we decide it was a difference with OTA vs clean flashes?09:34
ogra_john-mcaleely, iirc we firstly did but then discovered someone else who had OTAed and didnt see it09:35
ogra_and set the bug to incomplete09:35
sil2100davmor2: ping! Meetong09:35
john-mcaleelycjwatson, I need to ask for updates to system-image.u.c, so it takes different tarballs for rtm & vivid09:38
john-mcaleelycjwatson, I've tried to find that file you sent me at the sprint in my logs09:38
john-mcaleelycjwatson, but have failed to find it :-(09:38
brendandSaviq, i was testing silo 4 yesterday09:49
Saviqbrendand, yes, I know you did not like the indicator syncing09:49
Saviqbrendand, we're looking into it now, all else fails I'll pull the relevant changes from silo 409:50
brendandSaviq, thanks. i also felt like it was crashing more often, but they were the same crashes as usual, not new ones09:54
Saviqbrendand, I think the qtubuntu-media fix only landed later than when you were testing09:54
brendandSaviq, well i don't think i had landed yet09:56
Saviqor even..09:56
alan_gcihelp in the transition to vivid mir-ci seems to have lost some builds: specifically mir-mediumtests-utopic-touch has no vivid equivalent. Before: https://jenkins.qa.ubuntu.com/job/mir-ci/2008/console, after: https://jenkins.qa.ubuntu.com/job/mir-ci/2022/console. What's going on?09:57
popeystupid webcam09:58
* Mirv flashes vivid 909:58
davmor2popey: you should have a warning "May contain flashing images" as your lower 1/3 ;)09:59
popeyheh09:59
popeyyes!09:59
imgbot=== trainguards: IMAGE 11 building (started: 20141106 10:05) ===10:04
cjwatsonjohn-mcaleely: http://paste.ubuntu.com/8849582/10:06
cjwatson(that's nusakan:/srv/system-image.ubuntu.com/etc/config)10:06
john-mcaleelycjwatson, thanks10:07
vilaalan_g: looks like the mir-mediumtests-vivid-touch doesn't exist, will ping fginther10:17
alan_gvila: thanks10:18
evrobru, sil2100, Ursinha-afk: public service announcement: if you move files around in lp:cupstream2distro's citrain directly, do be sure to update the jenkins charm and/or lp:ci-train10:24
evas this has broken the production deployment10:24
pstolowskibrendand, hello, fyi the topblocker bug from #50 has been tested by us and is ready for qa sign off10:27
john-mcaleelycjwatson, here's how I think it should look http://paste.ubuntu.com/8849746/10:27
john-mcaleelycjwatson, there are now 3 tarballs available for system-image.u.c: utopic, ubuntu-rtm-14.09, master (vivid)10:28
john-mcaleelycjwatson, right now, all three are identical, and contain what is in the single lookup now10:28
john-mcaleelycjwatson, I believe I need to publish separate updates today for vivid & ubuntu-rtm10:28
john-mcaleelycjwatson, does the update make sense to you?10:28
evrobru, sil2100, Ursinha-afk: this is also why while having a remote branch that production pulls from gives you flexibility, it's a fundamentally broken approach as it's all too easy to get out of sync when things aren't carefully coordinated. Tar'ing up the code and making that part of the deployment fixes this.10:35
evobviously not blaming you guys for any of this - it's a creation you've inherited - but I want to make sure we take the right lessons from it10:36
evfix cowboy'ed onto production. jacekn is working on doing an upgrade-charm to pick up the real fix in the jenkins charm10:39
cjwatsonjohn-mcaleely: I'm at a conference right now.  Could you please mail me a diff (*not* the whole new file)?10:41
john-mcaleelycjwatson, sure10:41
popeyogra_: vivid 10 on mako known broken?10:43
ogra_popey, ask Mirv and davmor2 :P10:43
ogra_they showed it in the meeting10:43
davmor2popey: yeap ogra_ is meant to be fixing it though10:44
ogra_popey, i triggered 11 (see above) to make sure we are not missing anything from the android update, 11 might or might not work10:44
davmor2ogra_: fix it faster10:44
ogra_:P10:45
popeykk10:45
davmor2ogra_: no faster not more sarcastically :P10:45
ogra_haha10:45
sil2100ev: ACK10:45
ogra_heh11:11
ogra_the bootchart for vivid 10 looks interesting11:11
ogra_http://people.canonical.com/~ogra/ubuntu-phablet-vivid-10.png11:11
ogra_looks like media-hub is in a crashing loop .... tearing down unity8 with it11:11
Mirvpopey: I went back to 9 to test qt11:12
popeyta11:12
popeywill revert11:12
tvossogra_, do you have the new device tarball?11:18
ogra_tvoss, where ? krillin ? yes, since yesterday11:18
Ursinhaev: understood, but not sure if files were moved around, robru was working on changing relative/absolute paths in the code, I wonder if that broke things?11:19
tvossogra_, the one that is required for https://launchpad.net/ubuntu/+source/media-hub/2.0.0+15.04.20141105.1-0ubuntu111:22
tvossogra_, also: got crash file for media-hub?11:22
ogra_tvoss, note the above is vivid on mako ... that should have the changes in the new android package11:23
ogra_and yes, i have crashes11:23
Ursinhaev: if you are talking about bug 1389968, then the problem seems to be that the charms weren't updated to reflect how setup_citrain gets parameters (not that files were moved around), but your point still stands -- thanks for pointing that out11:23
ubot5Error: Launchpad bug 1389968 could not be found11:23
tvossogra_, did you upload them, yet? oops idea would be helfpul11:23
tvosss/idea/id11:23
ogra_tvoss, https://errors.ubuntu.com/oops/5bdbf2a4-65a4-11e4-80e5-fa163e525ba711:23
tvossogra_, ouch, somehwere in android11:25
ogra_yes11:26
ogra_ricmm, ^^^11:27
ogra_(oh, i think he is flying today)11:27
ogra_we might have to wait for rsalveti11:27
imgbot=== trainguards: IMAGE 11 DONE (finished: 20141106 11:30) ===11:29
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/11.changes ===11:29
ogra_tvoss, ^^ looks like hybris simply had not migrated for image 1011:29
ogra_11 should boot11:29
ogra_Mirv, popey ^^^^11:31
popeydammit, 9 just finished ☻11:31
popeyhuh, no volume overlay when changing up/down11:32
davmor2popey: but now you can ota to 1111:32
popeyya11:32
Mirvogra_: thanks.11:33
* popey updates11:36
popey111 is good11:42
popeyer, 1111:42
popeygot a bit excited there11:42
ogra_haha11:45
john-mcaleely+10011:45
brendandpopey, nope that never landed in vivid11:50
brendandpopey, as i found out yesterday11:50
evUrsinha: already fixed :)11:53
evUrsinha: what broke it was renaming files, yeah11:53
evbut what's more fundamentally broken is that this production environment references a remote bzr branch that can change underneath it11:53
evit really should've been that the code got bundled with the deployment11:54
evand requests were made to webops for further updates11:54
Ursinhaev: got it11:54
davmor2brendand, sil2100, ogra_: Mako vivid 11 has buttons not swipe http://people.canonical.com/~davmor2/buttons.png12:13
brendandsil2100, isn't stuff meant to land in vivid first?12:14
brendandSaviq, ^12:14
Saviqbrendand, davmor2, it's the telephony service that needs adapting12:14
Saviqand yeah, they did not land it in vivid yet12:15
Saviqwe did our part12:15
davmor2Saviq, brendand: it hasn't landed in RTM either this is buttons too12:15
brendanddavmor2, well no - i'm testing that now12:16
sil2100davmor2: yeah, it's silo 4 that has that actually12:16
ricmmogra_: so no breakage? :)12:16
ricmmslow migration bots ;)12:16
ogra_ricmm, yeah, just out-of-sync12:16
Saviqdavmor2, it's in silo12:17
Saviqso yeah, the telephony bit landed in rtm, not in vivid, unity8 bits the other way round12:18
* davmor2 blames ogra_ obviously for vivid 10 being broken ;)12:19
ogra_yeah, my hybris fiddling broke everything12:19
brendandSaviq, so what about silo 4 then?12:20
Saviqbrendand, dednick pung you somewhere, will come here shortly12:20
brendandSaviq, i didn't get anything12:20
dednickbrendand: hi12:21
brendanddednick, hello12:21
Saviqfight!12:21
Saviq;)12:21
Saviq/food12:21
ogra_food fight ?12:21
Saviqogra_, you kinky you12:21
ogra_:D12:21
dednickbrendand: pinged you on touch awhile ago. nevermind :)12:21
dednickbrendand: i've tried out silo 16 but can't get the sound out of sync? what are your steps?12:21
brendanddednick, sound?12:22
dednickbrendand: kgunn said the flight mode and sound settings in system settings were stll getting out of sync with indicators12:22
brendanddednick, the problem i have is that flight mode toggles back and forth when you switch it on12:23
Saviqbrendand, ah, that's an indicator-network issue12:23
dednickbrendand: i think it's because of the backend12:23
brendandSaviq, is there a fix pending for it?12:24
Saviqbrendand, we tell it "go to flight mode", a second or so later we check the value, but it's still "no flight mode", then another second after that it comes back with "yeah, I turned flight mode on"12:24
brendandSaviq, it looks crappy though12:25
Saviqbrendand, it does, I agree, and no I don't think there's a fix, but then that's required for the switches to remain in sync12:25
SaviqWellark, so, indicator-network taking a long time (like multiple seconds) to acknowledge flight mode setting, what can be done?12:26
kgunnSaviq: dednick ....but with silo 16, i can toggle flight mode quickly and get it to "stick" seemingly12:26
Saviqkgunn, I think it depends on your setup, basically the network indicator is waiting for urfkill (?) to say "yeah, you're in flight mode"12:27
Saviqand it's switching hardware about that might take some time I think12:27
dednickkgunn: the indicators and settings use a differnt method to working the flight mode. i think something is getting screwy somewhere in the backend12:27
john-mcaleelyso, does 'rtm silo 9' have a pair for (I'm guessing) vivid?12:27
john-mcaleelyand how would I find out?12:27
john-mcaleelyrsalveti, ^ ?12:28
kgunnjohn-mcaleely: grep the sheet for landing-00912:28
john-mcaleelyoh, are the numbers the same on both distros?12:28
Saviqno12:29
kgunndednick: also, for sound, if i select silent mode...the little speaker+sound wave icons stays...12:29
john-mcaleelykgunn, no luck :-(12:29
Saviqtvoss, is there a vivid silo for what rtm 9 is?12:30
Saviqjohn-mcaleely, but also, that silo looks like a sync, meaning that is already *in* vivid12:30
brendanddednick, i can get the sound toggles to be out of sync here too12:30
john-mcaleelyaha. interesting.12:30
john-mcaleelySaviq, thanks12:30
Saviqjohn-mcaleely, if you look at http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=00912:30
brendanddednick, without the silo12:30
Saviqjohn-mcaleely, it says "spreadsheet row 62"12:30
john-mcaleelyit does indeed12:30
dednickbrendand: yeah.. that's what the silo fixes12:30
Saviqjohn-mcaleely, you can then go to https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&pli=1#gid=012:31
brendanddednick, ok12:31
dednickkgunn: do you mean the icon?12:31
Saviqjohn-mcaleely, and see how the silo is set up, it says "sync:ubuntu,vivid" there, meaning it simply picked all the packages up from vivid12:31
kgunndednick: yep gimme a sec...will video12:31
Saviq/reallyfood12:32
john-mcaleelySaviq, aha, thanks. makes some sense.12:32
john-mcaleelyunping rsalveti  :-)12:32
dednickkgunn: i dont think silent mode is connceted to an icon. it doesnt change if i change in indicators either.12:33
dednickunless you mean the really annoying icon which pops up in the system settings page.12:34
kgunndednick: then how the heck is a user supposed to glance at phone and see he's on silent mode ? :P12:35
kgunnsholdn't the icon change to a speaker+'X' instead of sound waves12:35
dednickkgunn: hehe. yeah, well it should. bug in indicator-sound i guess12:35
brendandkgunn, so i really don't want to land this unless i hear that either a fix is imminent (like in a silo almost ready for sign-off), or that this is the desired behaviour for RTM12:37
kgunnbrendand: it might be that we're not the ones to fix it12:44
dednickkgunn: hm. so apparently "mute" and "silent mode" are not the same things...12:44
Saviqbrendand, kgunn, dednick, we could pull the sync branch from the silo and come up with a proper fix afterwards, but that will mean breakage, as opposed to visual awkwardness12:44
Saviqdednick, yeah, but we don't do <|× for either ;)12:45
Saviqso def. a bug in indicator-sound12:45
dednickSaviq: pull the u8 sync branch you mean?12:45
Saviqdednick, yes12:45
kgunnSaviq: breakage how ?12:45
dednickSaviq: no breakage. will be same as before12:45
Saviqkgunn, same breakage we have now I mean12:46
kgunn:)12:46
Saviqso we're getting out of sync, with dednick's branch we're in sync, but visually awkward12:46
dednickright. so the indicator will just be wrong.12:46
=== alan_g is now known as alan_g|lunch
kgunndednick: but it's eventually right12:46
dednickya12:46
kgunni mean it does correct eventually12:46
Saviqkgunn, with dednick's branch, not without it12:46
kgunn(but awkward indeed)12:46
kgunnSaviq: got it....12:47
Saviqso yeah, IMO it's better to be correct but awkward vs. wrong12:47
Saviqbrendand, ↑?12:47
kgunnman Saviq said it better....that's what i tried to say to brendand y'day12:47
dednickworth noting that i dont think the settings corrects itself :/12:47
Saviqdednick, not before your branch in silo 16 that is?12:49
dednickSaviq: silo16 doesnt add autocorrecting.12:49
dednickSaviq: the USS branch i mean12:49
dednickwith the timer thingy12:50
Saviqdednick, should it?12:50
dednickSaviq: well, for the same reason we have done in u8.12:50
kgunndednick: so i'm on silo 16....and system-settings seems to follow12:51
kgunneven eventually12:51
kgunnhmmm dednick this seems way better than last night (flight mode toggling)12:53
kgunnah...cause i installed ofono sim stuff12:54
kgunnfaster than a real radio12:54
dednickkgunn: https://bugs.launchpad.net/indicator-sound/+bug/139006712:55
ubot5Ubuntu bug 1390067 in The Sound Menu "Silent mode does not change the icon to the mute icon (or like)" [Undecided,New]12:55
dednickkgunn: yeah, that would do it. probably works every time as well...12:55
Mirvboiko: bfiller: https://code.launchpad.net/~boiko/history-service/save_timestamps_utc/+merge/240337 not approved, ready for publishing otherwise13:01
Saviqbrendand, so, just to restate: with silo 4 we're correct, but awkward, without it we're wrong (in what the indicator shows), so if you ask me it's still better13:01
boikoMirv: oups, I think I will wait for bfiller to approve it13:01
Saviqand that's the only two choices we have right now13:01
* sil2100 lunch o/13:07
Saviqbrendand_, looks like your connection's flaky today13:09
Saviqbrendand_, brendand, so, just to restate: with silo 4 we're correct, but awkward, without it we're wrong (in what the indicator shows), so if you ask me it's still better13:09
Saviqbrendand_, and that's the only two choices we have right now13:09
Mirvwhy do I have ~80 systemd-logind process on my mako... vivid I guess13:10
mdeslaurogra_, bzoltan, cjwatson: https://codereview.qt-project.org/#/c/99054/13:10
mdeslaurogra_, bzoltan, cjwatson: please also fix this issue: https://bugreports.qt-project.org/browse/QTCREATORBUG-1333913:11
Mirvand why does the mirscreencast stall all the time13:12
tvossSaviq, yup, the changes landed to vivid last night13:12
* Mirv wants an oracle to answer all his questions13:12
Mirvcjwatson: do things break if I CI Train would try to sync 5.3.2-2 of qtimageformats _with binaries_ from landing PPA, while 5.3.2-2 is in proposed already without binaries (because build dependencies not matched)? with 5.3.0, I removed the synced packages from PPA right before publishing and let them build in the archive, which was a bit slow.13:15
=== boiko_ is now known as boiko
tvossrsalveti, around?13:20
Mirvcore-dev question also here, if anyone up for acking a single liner for vivid: https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_1.1.1311+15.04.20141102-0ubuntu1.diff13:20
brendand_Saviq, it needs to be passed by product management/design then. if that's the final behaviour they prefer to have then so be it13:22
sil2100Mirv: ogra_ can you take a look at Mirv's question reg. packaging ^ ?13:23
Saviqkgunn, ↑13:24
ralsinatrainguards pretty please a silo for row #70?13:26
rsalvetitvoss: yes13:26
ralsinaoops, trainguards meant row #5613:26
Mirvralsina: rtm-00613:27
ralsinathx Mirv!13:27
=== mandel is now known as mandel|lunch
=== chihchun_afk is now known as chihchun
Chipacacan somebody translate https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-006-1-build/86/console to human? what do we need to do?13:35
MirvChipaca: your rtm bzr branch https://code.launchpad.net/~ubuntu-push-hackers/ubuntu-push-qml/rtm does not match what's actually in rtm at the moment https://launchpad.net/ubuntu-rtm/+source/ubuntu-push-qml13:36
brendand_kgunn, did you say yesterday that when you used dednick's silo that the flight mode toggle worked normally?13:36
ChipacaMirv: is this checking versions, or actual branches?13:37
ralsinaMirv: That's because this is my first time landing this to rtm after vivid opened13:37
MirvChipaca: versions13:37
Chipacaralsina: ^13:37
ChipacaMirv: thanks13:37
ralsinaso I need to dch and change the version?13:37
Mirvralsina: preferably you should dget the rtm archive version and make sure the rtm branch matches that content exactly, and parse the meaningfulness of any delta. most probably it's just the last changelog entry not being rtm mangled in the bzr.13:38
ralsinaack, thx Mirv!13:38
kgunnbrendand_: define normal... :) i was trying to say what saviq said13:38
kgunnthat is, it is correct behavior however "visually awkward" b/c the ui is checking to be in sync with what the backend acgtually does13:39
kgunnwhereas...before these silos, the ui would reflect incorrectly what the state of the backend is13:39
kgunnbrendand_: think of it as bad visual design with silos, we're using toggle & icons to be both for theuser to input desire & reflect the current state13:40
* Mirv is sad not being able to publish UITK13:40
brendand_kgunn, so one problem is that if you toggle the switch on > off > on13:40
brendand_kgunn, then it ends up in off13:41
brendand_kgunn, the ui shouldn't do what the backend says, the backend should do what the ui says13:41
brendand_kgunn, anyway i'm not going to make the call on this, somebody from product management/design should13:42
kgunnbrendand_: i don't think you understand...the ui has to reflect what the backend state is, e.g. you turn off flight mode, but it takes 10 seconds to get out of flight mode13:42
kgunnand what it failed to get out of flight mode completely13:43
kgunnhow would the use know that ?13:43
kgunncan't just redraw the ui and hope for the best...b/c that is exactly the original bug13:43
kgunnso if i follow your argument, you should mark the top blocker invalid13:43
sil2100Can't we have an intermediate state?13:45
brendand_kgunn, so the TOPBLOCKER refers to switches getting out of sync in general13:45
sil2100Like, after switching the flight mode, disabling the button until we get confirmation from the backend or wait some timeout (in case that fails)?13:45
* olli waives13:46
brendand_kgunn, not specifically flight mode13:46
brendand_olli, hey13:46
ollihow can I help13:47
brendand_olli, there's an attempted fix for a TOPBLOCKER which makes the flight mode switch behaviour very obviously broken looking from a user point of view13:47
sil2100olli: hello! btw. can I send out a draft e-mail for proof-reading in a moment? :)13:47
brendand_olli, kgunn and Saviq's argument is that it's necessary to ensure correct behaviour13:48
brendand_note i said broken *looking*13:48
ollibrendand_,  iwas reading the backscroll13:48
kgunnsil2100: yes, we need an intermediate state really...but with 1 day to go that's rough13:49
sil2100kgunn: true...13:49
kgunnnot to mention it's more than ui...it'd be a whole new meta state to perpetuate throughout13:49
Saviqolli, basically, what happens: user taps flight mode, the indicator starts doing things; the UI then asks "is flight mode on?", and gets "no", so it switches back; then backend says "dude, flight mode is on now", and it settles on On13:49
ollibrendand_, I haven't seen it myself... but doesn't it improve the state where the button state was pointless as it was out of sync?13:49
Saviqolli, yes, it does, it's actually correct, but visually awkward13:49
* kgunn takes video to avoid explaining like 10 times today :)13:50
rsalvetijohn-mcaleely: yeah, the changes for vivid already landed :-)13:50
rsalvetijohn-mcaleely: so feel free to just push the vivid tarball13:51
rsalvetiogra_: thanks for building 11, 10 was indeed out of sync13:51
brendand_olli, out of sync with what? the system state, or out of sync between the indicator and system-settings?13:51
rsalvetiit got the new android tarball, but not latest hybris13:51
ollibrendand_, the situation on #14013:51
olliwhere iirc the indicator is out of sync with pretty much everything easily13:52
brendand_olli, depending on exactly what issue you're taking about, i believe there were some ofono fixes to eliminate the chance of that happening13:53
kgunn...i'm totally pushing for an actual indicator alert with "dude, flight mode is on now"13:53
brendand_olli, if you mean when it gets permenantly out of sync, rather than temporarily13:53
brendand_kgunn, if you look at the way android does it then it almost instantly turns off wifi and bluetooth, but takes a little for cellular13:54
brendand_kgunn, when turning off at least13:54
Saviqbrendand_, don't get me wrong, the indicator service should just go "yes, flight mode is on" straight away, and, if failed (?), come back with "oh dude, I failed"13:54
kgunnyeah13:55
ollishould have, would have, could have... I think the question is...13:55
kgunnbrendand_: we're not arguing we're done and dusted....we're saying what we're wanting to land is "better" than broken13:55
Saviqbrendand_, which needs fixing in the network indicator service or urfkill at least13:55
brendand_olli, do you have an exact bug number for the issue you're thinking of? is it this one? https://bugs.launchpad.net/indicator-network/+bug/133671513:55
ubot5Ubuntu bug 1336715 in unity8 (Ubuntu RTM) "[TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings" [Critical,In progress]13:55
olliwhat's worse... the previous state of the system or the current13:55
Saviqright13:55
kgunnbut we need time to add design into the mix for a meta-state/transistion for radios and sucj13:55
kgunnsuch13:55
brendand_olli, well not current - it hasn't landed yet13:56
kgunnSaviq: crap, how do i get this ofono meego sim off my phone now :P13:56
Saviqkgunn, uninstall it13:56
kgunni removed ofono-phonesim-autostart but that no help13:56
Saviqkgunn, uninstall ofono-phonesim13:56
Saviqkgunn, and reboot13:56
kgunndid13:56
ollibrendand_, intended current13:56
Saviq-phonesim, too, or just -autostart?13:57
kgunnmy bad...13:57
kgunndoing phonesim (no autostart now)13:57
brendand_olli, personally i think the previous was better but there appears to be a specific bug i wasn't aware of13:57
Saviqbrendand_, that's where we disagree, you could end up with flight mode permanently saying "yes" when it was, in fact, not enabled13:58
kgunnexactly...rude surprise for user13:58
Saviqand then if you toggled, it would say "no", but was actually getting enabled Oo13:58
brendand_Saviq, i know that was possible in the past, but i do believe a fix was landed to ofono to make that extremely unlikely13:59
brendand_Saviq, i'll do some testing on the base image13:59
ollibrendand_, to me the improvement was a combination of both bugs14:00
brendand_tvoss, btw lets get your silo landed, it works beautifully here14:00
brendand_olli, i think the new behaviour will be extremely confusing for the user because there can be a significant period where the toggle state is not what it's going to be soon in the future14:02
brendand_olli, so they look at it and go "didn't i just switch that on?"14:03
cjwatsonMirv: that won't be allowed.  you could upload 5.3.2-2build1 to the relevant silo though14:03
tvossbrendand_, it is set to testing done, awaiting qa14:04
dbarthtrainguards: hello, can i have a new silo for line 68 ?14:04
brendand_kgunn, olli, Saviq - it just feels like we are swapping a big issue that happens rarely with a minor issue that is obvious and always there14:06
Saviqit was happening to me all too often...14:06
Saviqolli, so yeah, your call, I can back that change out from the silo and give ourselves a few more days to straighten it all out14:06
ollibrendand_, talking to Joe atm14:07
olliI am inclined to take the fix14:07
ollibut then I might be biased, so getting a 2nd opinion14:07
=== josepht changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: josepht | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
brendand_olli, have you seen the new behaviour?14:07
ollichecking it out with KG14:09
brendand_Saviq, so the bad behaviour you're right is not *that* hard to reproduce, but it does only seem to occur in 'abnormal' use14:13
fgintheralan_g|lunch, vila, I've restored the missing job, apologies for missing this the first time through14:14
=== alan_g|lunch is now known as alan_g
ollibrendand_, I think unreliable state is worse than visually confusing14:14
pmcgowanogra_, you about?14:15
olliat least it heals itself14:15
alan_gfginther: no worries - it made CI a *lot* faster14:15
vilafginther: thanks14:15
brendand_olli, if that's your final decision, ok14:15
ollibrendand_, still awaiting feedback from Joe14:17
ollias I said, I could be seen as biased14:17
bfillersil2100: can you republish rtm 5, merges are now approved14:18
sil2100bfiller: o/14:18
brendand_olli, i'm just preparing for the inevitable, which is that this lands, then someone notices it in the sanity/regression testing and makes a fuss about it. then i need to say that it landed in silo 4 and i tested it - to which the response will be 'why did you allow that?'14:18
brendand_olli, better to say 'because product management decided that was the preferred behaviour given the constraints'14:19
ollibrendand_, totally understand your position14:19
sil2100bfiller: done o/14:20
bfillersil2100: thank you14:20
WellarkSaviq: sorry, was not paying attention to freenode for a while14:20
Wellarkso, what's the problem?14:20
WellarkSaviq: actually, let's move to #ubuntu-touch14:20
brendand_olli, fwiw the issue with flight mode getting stuck is not something that i regularly hear mentioned in testing14:20
brendand_olli, i'm sure there will be a flood of people mentioning this on the mailing list once it lands14:21
brendand_if it lands14:21
Saviqbrendand_, olli, Wellark is having a look at fixing it indicator-sid14:26
Saviqe14:26
Wellarkworking around!14:26
Wellarkthe indicator is not broken strictly speaking14:27
Saviqnothing is, strictly speaking14:27
Saviqolli, brendand_, kgunn, let's back out that commit from the silo, land it and give ourselves some time to fix it proper with no visual artifacts?14:27
olliSaviq, talking to ben/joe/pat atm14:28
WellarkSaviq: well, the whole indicator framework is broken by (technical) design, but that's another discussion14:28
Saviqalways14:28
kgunnSaviq: brendand_ dednick ok, so decision is to land this "improvement" but then fix issue in ota114:44
kgunnolli: ^14:44
kgunnthat's per prod management aka board of elders14:45
ollistahp14:45
ollikgunn, is accelerating my midlife crisis14:45
kgunnbug has been updated to include ubuntu-ux for design of meta state14:45
* kgunn imagines olli as sort of mace windu on jedi council in his role on board of elders14:46
john-mcaleelyok, so when we need one, I have a device tarball ready to publish for silo9 + rtm14:48
john-mcaleelysil2100, ^14:48
sil2100john-mcaleely: thanks for the info! Victor is  testing the silo 9 right now14:49
sil2100john-mcaleely: is the device tarball required for silo 9 to work correctly?14:49
sil2100Since we need to make sure Victor is aware14:49
sil2100brendand_, davmor2: ^14:49
john-mcaleelysil2100, it is. and victor was just hassling me for the right permissions. so I think he's away14:49
john-mcaleelyaway? aware.14:49
brendand_kgunn, ok i'm satisfied(ish) ;)14:50
sil2100;)14:50
sil2100olli: ;)14:50
ogra_olli, wanna buy my porsche ? its not red though14:52
olliogra_, 911?14:52
ollilightly used?14:52
ogra_(you could make kgunn pay half of it if he is the reason for the crisis)14:52
* olli eyeballs brother in laws dirt bike atm14:53
ogra_olli, nah, i'm not getting manager salary ... 944S2 well used :)14:53
olliheh14:53
* olli just bought an family car... with 8 seats...14:54
ogra_heh, yeah, thats what you get being a father14:54
sil2100olli: you have a porsche? ;)14:56
sil2100I mean, ogra_ ^14:56
ogra_yep14:56
ogra_old one ...14:56
ogra_(well, i have three, but only one that drives :) )14:57
sil2100What kind? Out of curiosity, might snatch it from you if it's good enough14:57
* cwayne is jealous14:57
brendand_olli, one last thing - can we have a bug raised and tagged for OTA1 to track the UI fix?14:57
sil2100...;)14:57
brendand_olli, i'd like to point the team to it14:57
ogra_sil2100, http://de.wikipedia.org/wiki/Porsche_944#mediaviewer/File:Porsche_944_rear_20080130.jpg14:58
ogra_but in white14:58
cjwatsonjohn-mcaleely: OK, so I'm fine with your patch and can apply it; looks like all those URLs have identical contents right now so it shouldn't cause a new image number to be generated14:58
sil2100ogra_: oh, looking nice!14:59
cjwatsonsil2100: Are you OK with me going ahead and applying John's patch to the system-image config to use different URLs for the device_krillin tarball for utopic/vivid/14.09?14:59
ogra_since i dont need to drive to work every day i considered cars are just for fun which made me buy it :)14:59
ogra_(and its a lot of fun :) )14:59
sil2100cjwatson: I should be fine, as it's not something that would break any workflow - but to which URL will it change?15:00
* sil2100 lacks context about the change15:00
cjwatsonsil2100: http://people.canonical.com/~jhm/barajas/device_krillin.tar.xz -> http://people.canonical.com/~jhm/barajas/{utopic,master,ubuntu-rtm-14.09}/device_krillin.tar.xz15:01
cjwatsonif you'll excuse the brace-expansion there15:01
sil2100ogra_: hah, indeed! I'm still looking for a garage - once I do that I want to buy a motorcycl actually15:01
john-mcaleelycjwatson, sounds good - the same contents was my aim :-)15:02
sil2100cjwatson, john-mcaleely: then a big +1 on that!15:02
ogra_sil2100, cool ...15:02
brendand_olli, i can raise the bug if you're tight for time15:02
ogra_pmcgowan, i'm back now15:02
* ogra_ finds it funny that once he leaves IRC during a workday for 30min the ping hell breaks lose 15:03
cjwatsonjohn-mcaleely,sil2100: ok, that's applied now15:03
brendand_kgunn, or maybe you can raise a bug giving an idea of what the intended fix is?15:03
john-mcaleelycjwatson, thank you!15:04
kgunnbrendand_: design already updating bug 133671515:05
ubot5bug 1336715 in unity8 (Ubuntu RTM) "[TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings" [Critical,In progress] https://launchpad.net/bugs/133671515:05
brendand_kgunn, so you're using a different task in the same bug?15:06
Saviqtvoss, jhodapp, om26er, there's a q-m conflict between silos 2 and 915:07
brendand_kgunn, it's a different bug now so to me that's starting to get a bit messy. but whatever you prefer15:07
Saviqtvoss, jhodapp, om26er, I don't think 2 can land before 915:07
Saviqas it would bring with it commits that are in trunk that are not yet in rtm (and are being synced in silo 9)15:07
tvossSaviq, ack15:08
brendand_kgunn, either way confirm for me if you're going to stick with adding a task there or raise a new bug, i want to link to the right thing15:08
Saviqjhodapp, also, in general, we try to land to vivid first, or at least have a silo into vivid before we land into rtm15:08
kgunnSaviq: should we do a new bug ? or keep the one ? indicator out of sync15:08
om26erSaviq, hmm, ok. So how can we "stop" 2 from landing ?15:08
om26erdo you know ?15:08
Saviqom26er, yeah, don't test it! ;)15:09
kgunndesign supposed to update the existing one...hate to move it15:09
om26erSaviq, I already did, I need to change it back to needs QA sign-off15:09
jhodappSaviq, indeed, though vivid wasn't open when we first tried to land it15:09
om26erSaviq, or not, I missed that with another silo.15:09
Saviqjhodapp, but now it is...15:09
jhodappSaviq, yep, although it doesn't really matter which you land in first15:10
Saviqwe're in a huge mess of stuff landed in one of {rtm,vivid} now :/15:10
Saviqjhodapp, kinda does15:10
kgunnbbiab15:10
Saviqjhodapp, because if you land in rtm, your trunk will then get ~rtm in the changelog15:10
jhodappSaviq, yeah, our team was targeting rtm first for a while, so again not something I just randomly decided15:10
Saviqjhodapp, ok, seems process is all over the place, contrary to the landing team's recommendation, then :|15:11
Saviqbut that's why we have the conflict problem now15:11
jhodappSaviq, the landing process wasn't working well for a while15:11
Saviqjhodapp, being the person who lands roughly 20-30 MPs a week, I must disagree ;)15:12
Saviqthe only problem was utopic being closed, but that's an exception15:13
jhodappSaviq, point noted :)15:13
ogra_Saviq, there was some agreement that phonedations should be allowed to land in rtm first as an experiment15:13
Saviqogra_, oh ok, IMO the experiment failed ;P15:14
ogra_experiment failed obviously :)15:14
Saviqbecause *first* became *only* almost15:14
ogra_yeah15:14
rsalvetiit was only like that when utopic was closed15:15
rsalvetior in freeze, depending on the package15:15
brendand_kgunn, Saviq - any decision about the bug?15:18
rsalvetiqtubuntu-media against trunk and scopes agains the rtm branch15:20
rsalvetilanding madness between 2 distros15:21
ogra_well, things should still have gone to -proposed for utopic in that case15:21
ogra_and afaik the plan was that vivid gets utopic-proposed synced on opening15:22
rsalvetiright, but landing first on rtm was not causing issues from that perspective15:23
rsalvetidepending on the project, it's fine to have both landings and land it first on rtm15:23
rsalvetiproblem is not having the landing for utopic/vivid15:23
Mirvah, ken published the uitk now finally15:24
MirvI guess the core-dev application would be a good idea some year after all15:25
Mirvogra_: wow!15:25
Mirvogra_: looks like fun indeed!15:25
sil2100Mirv: I'm thinking the same thing ;)15:25
sil2100Saviq: yeah, regarding that - we're now trying to see how many things we're missing in vivid that landed in ubuntu-rtm15:26
sil2100And it's not super easy15:26
Saviqsil2100, you'd think the landers knew ;)15:27
Mirvoh, right, that migration check is broken in ci train15:27
sil2100Mirv: migration check..?15:27
Mirvsil2100: robru updated ci train code, and when he ended in the morning (his night) it all seemed pretty good to me but the migration check probably would still need a bit of fixing. good enough anyway that no need to revert the revert of the revert.15:28
sil2100o_O15:29
Mirvsil2100: ci train told vivid 010 would have migrated, while it has not15:29
sil2100Mirv: ok, let's make sure there's a bug for that and assigned to robru then!15:29
Mirvsil2100: filing15:30
ogra_sil2100, so not sure you saw the other discussion ... bug 1387214is currently our worst blocker and needs fixing before final golden master ...15:30
ubot5bug 1387214 in system-image (Ubuntu) "file corruption on touch images in rw portions of the filesystem" [Critical,Triaged] https://launchpad.net/bugs/138721415:30
sil2100ogra_: thanks, this looks serious indeed15:32
sil2100ogra_: we'll tag it as [TOPBLOCKER] asap as well15:32
* sil2100 adds it to the list for LT15:32
Mirvbzoltan: Text conflict in po/ubuntu-ui-toolkit.pot when trying to m&c, looking at solving manually15:49
Mirvbzoltan: sil2100: merged UITK manually, there was .pot file change directly in trunk that had only its comment headers that needed fixing15:52
sil2100Mirv: thanks! I think there's not much other choices when that happens...15:53
john-mcaleelyincoming device tarball, for vivid channels:15:55
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/master/device_krillin-20141106-4f167c4.changes15:55
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/master/device_krillin-20141106-4f167c4.tar.xz15:55
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/master/device_krillin-testresults-20141106-4f167c4.ods15:55
john-mcaleelysil2100, ^ do you want to QA sign of that? (vivid  only device tarball)15:55
john-mcaleely(I assume you do)15:55
brendand_john-mcaleely, he's not getting it even if he wants it :)15:56
john-mcaleelyha15:57
john-mcaleelywell, krillin vivid is broken without it15:57
john-mcaleelyso maybe I should just push it?15:57
sil2100john-mcaleely: it's for vivid, right?15:58
john-mcaleelysil2100, yes15:58
ogra_oh, shiny15:58
ogra_more log quietening \o/15:59
sil2100john-mcaleely: I think this can go just as it is, as we don't do sign-off for QA15:59
* ogra_ likes that !15:59
sil2100(only if QA wants that)15:59
john-mcaleelyok, so ogra_ is now a good time to push a new vivid tarball?15:59
ogra_john-mcaleely, sure ...15:59
john-mcaleelyogra_, sil2100 pushed.16:00
john-mcaleelyshould be, lucky-for-some, 13 when it lands16:00
john-mcaleelyrsalveti, ^ hybris sync for vivid/krillin landing16:00
rsalvetijohn-mcaleely: great16:01
brendand_john-mcaleely, if there's absolutely 0 chance it could impact RTM then just land it16:01
john-mcaleelybrendand_, noted. good job, because I just did :-)16:02
popeyplars: i lost the link to those scripts for doing local ci.. do you have the lp link handy?16:05
plarspopey: lp:ubuntu-test-cases/touch16:05
popeyaha! thanks!16:06
ogra_john-mcaleely, erm ... so why did my rtm krillin just get an update notification ?16:13
ogra_for image 147 ....  o_O16:13
ogra_sil2100, did we have a custom tarball today ?16:14
sil2100ogra_: hm, no, I don't think we did16:14
john-mcaleelyinteresting ogra_16:14
sil2100john-mcaleely, ogra_: did the device tarball get published already?16:14
sil2100Oh, maybe that's what cjwatson mentioned earlier?16:14
ogra_sil2100, i understood what john published was vivid only16:15
cjwatsonI just applied a patch to change URLs; at the time I did so the resulting contents should've been identical16:15
john-mcaleelyogra_, so you do16:15
cjwatsonBut I know John was intending to change them shortly afterwards16:15
john-mcaleelyogra_, darn. cjwatson any idea why that ended up in rtm?16:15
cjwatsonThe point of the URL changes was so that we could update vivid without changing utopic or 14.0916:15
cjwatsonno16:15
ogra_description": "ubuntu=20141106,device=20141106-4f167c4,custom=20141104-399-18,version=147",16:15
cjwatsonSomebody not at a conference will have to debug that16:15
ogra_and "description": "ubuntu=20141106,device=20141105-4a6bca7,custom=20141104-399-18,version=146",16:16
john-mcaleelyI know at least one reas16:16
john-mcaleelyon16:16
john-mcaleelylooks like it might have been me16:16
ogra_146 looks like what cjwatson describes16:16
ogra_it is identical to 14516:16
ogra_147 looks like a new device tarball16:16
john-mcaleelyogra_, interesting - it seems to be a mixture16:17
cjwatsonI hadn't expected the patch I applied to result in a new image number since the contents were identical, but I guess import-images might have noticed the change and tried; an extra identical image shouldn't have been a problem16:17
john-mcaleelythe device_krillin.build has been touched by me here:16:17
ogra_cjwatson, yeah, no worries, that should be fine16:17
john-mcaleelyhttp://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin.build16:17
ogra_the device tarball that was intended for vivid only is wrong though16:18
john-mcaleelybut the tarball next to it has not16:18
john-mcaleelyah16:18
john-mcaleelymy mistake16:18
cjwatsonThe config looks right.  http://paste.ubuntu.com/8853786/ FWIW16:18
john-mcaleelyln foiled me16:18
cjwatsonHa16:19
ogra_john-mcaleely, so just take the old tarball and bump the version ?16:19
ogra_to replace the wrong one16:20
john-mcaleelyogra_, yeah. doing it now16:20
robruev: when you say 'fix cowboyed into production' what exactly did you do?16:23
john-mcaleelyogra_, sil2100 cjwatson sorry about that16:24
john-mcaleelyover keen use of ln when setting up three copies of the same file to start with16:24
john-mcaleelyall now broken to unique files16:24
john-mcaleelyand for rtm & utopic, I've bumped the revision, and linked the correct tarball16:25
john-mcaleelyso new builds, I assume, but fixed ones16:25
sil2100john-mcaleely: no worries, glad it's fixed now16:26
john-mcaleelyas ever: zero chance of impact, where zero takes non-zero values :-)16:27
sil2100hah ;)16:28
Saviqbrendand_, are you still waiting for something from us re: silo 4?16:29
brendand_Saviq, no - i'm kind of hoping silo 9 will land at the same time because i had a gut feeling 4 on its own was making the unity8 crasher slightly more common, but i'll land it tonight regardless16:31
brendand_thanks kgunn for filing the new bug16:31
Saviqbrendand_, ok thanks16:32
* ogra_ upgrades to 14816:35
ogra_heh, with that the flashing only flashed my screen (and rebooted)16:35
=== mandel|lunch is now known as mandel
brendand_john-mcaleely, my my16:39
davmor2robru: he got a cowboy call Fix and pushed him into production, ev is like that16:39
brendand_john-mcaleely, i should always remember what 'zero chance' really means :)16:39
john-mcaleelybrendand_, :-)16:39
davmor2brendand_: you didn't believe a developer did you, that was mistake number one ;)16:40
davmor2john-mcaleely: would that be why my phone took forever to boot and say 14.10 on my ota testing then?16:41
john-mcaleelydavmor2, hrm. for 147, yes16:42
john-mcaleely147 never existed16:42
john-mcaleelyor shouldn't :-)16:42
tvosstrainguards, can I get silo for line 71?16:50
sil2100tvoss: o/16:56
tvosssil2100, o/16:56
sil2100tvoss: with pleasure, this is one of the recently approved bugs for ubuntu-rtm as well16:57
sil2100(and I like the idea you land it first to vivid016:57
sil2100)16:57
bfillersil2100: need a silo for line 70 as well16:57
sil2100bfiller: sure thing, the same thing here - assigning, just make sure that the same fix gets into vivid as well16:58
bfillersil2100: will do16:58
tvosssil2100, ack16:58
popeylanding call?17:00
sil2100davmor2: meetong17:02
sil2100plars: same here ^17:02
davmor2trying to login in17:02
dbartho/ if there is a vivd silo available for line 6817:02
dbarththanks ;)17:02
davmor2sil2100: Trying to join the call. Please wait...17:03
robruMirv: what symptoms did you observe in check-publication-migration during your shift? I thought I fixed that...17:12
balloonsping joespht .. is something up with core apps jenkins?17:14
plarssergiusens: I never saw any new ubuntu-device-flash or phablet tools for trusty in the ppa yet...17:15
sergiusensplars: yeah, I thought I'd ping you before doing that (it's for trusty, right?)17:17
plarssergiusens: yes17:17
popeyplars: http://paste.ubuntu.com/8854525/ what am I doing wrong here?17:22
popeyit just hangs at that point and the phone is in recovery mode17:22
ollisil2100, Saviq, kgunn, so do we have the u8 and tvoss' silos come through now?17:24
plarspopey: no idea, it's just doing ubuntu-device-flash at that point. The scripts don't have any control over what udf does internally17:24
sil2100olli: they're in QA :)17:26
sil2100olli: so the status is:17:26
sil2100olli: the u8 silo is basically signed-off, but it's waiting on tvoss's silo, since brendand_ suspected that u8 actually makes the crashes appear more frequently17:26
sil2100olli: while the tvoss silo fixes those completely17:27
olliare they good for rtm17:27
ollior just vivid?17:27
sil2100olli: so brendand_ wants to wait for silo 9 to finish the sign-off to make sure that both of them land in the same moment17:27
sil2100olli: that's for RTM now, I think those landed in vivid already17:27
ollik17:27
sil2100olli: anyway, ETA is today still17:27
olligood17:27
ollisil2100, what else are you expecting to land for the Fri image?17:28
john-mcaleelysil2100, you'll need to ping me to land silo9, so you can get a device tarball17:28
sil2100john-mcaleely: sure :)17:30
sil2100olli: there's one more silo with telepathy-ofono which we need17:31
sil2100The others are not super required17:31
balloonsfginther, is there something up with the core jenkins? No pages seem to be loading for me17:38
balloons*community core apps jenkins17:38
fgintherballoons, please ping the vanguard josepht17:42
balloonsfginther, aye, I did, just didn't get anything bug..17:42
* balloons patiently waits17:43
fgintherballoons, ohhh17:43
robruurgh wtf17:43
fgintherballoons, should be back now. the jenkins process appeared to be wedged17:45
robrubzoltan: yeah sorry shit's broken right now, gimme a sec17:49
fgintherballoons, sorry about the run-around. Will see if we can handle this better in the future.17:50
balloonsfginther, no worries. It was just really impactful so I felt the need to ping you17:51
balloonsthanks17:51
evrobru: I came up with a diff to the jenkins charm and asked webops to deploy that to the production jenkins instance17:51
evthen committed that17:52
evI'll follow up to your email tomorrow. Running out of time today17:52
evto be clear, I'm not trying to blame anyone for this, just mention that it's shining a light on how our architecture/process is wrong - we shouldn't be referring to an external branch that can change at any time from a production service17:53
evcode deployments should be bundled with the charms themselves17:53
evbut all things for us to carve out a story for17:53
robruev: thanks, no worries, I'm not feeling blamed, and I agree that citrain is essentially a case study in "what not to do". I'm looking forward to ditching it and appreciate your help17:55
ev:)17:55
evI am responsible for much of this mess, so do know I feel equally invested in its improvement17:55
robruev: oh really? this whole time I've been blaming a certain frenchman...17:56
evhahaha17:56
robruMirv: sil2100: I have a hotfix for check-publication-migration, it's in production already, just waiting for it to automerge into trunk17:59
=== alan_g is now known as alan_g|EOD
bfillerrobru: would you mind deleting vivid silo 27 and allocating vivid silo for line 7318:06
pmcgowansil2100, are the commit logs generated automatically, there seems to be a long lag between an image being installable and the log being available18:08
ogra_pmcgowan, well, it uses my changelogs as input ... mine get generated/linked only 5min after an image was built18:08
sil2100pmcgowan: they're generated automatically on a remote host, but they're not synced to any public place automatically - my machine does it currently18:09
pmcgowanok thanks18:09
robrubfiller: sure18:09
sil2100pmcgowan: there is a ticket for an automatic copy to people.canonical.com, but I didn't have time to push people on moving that forward18:09
pmcgowansil2100, thanks18:09
* ogra_ guesses we need a landing team sprint some day ... with only the focus to move all our tools away from our home desktops :P18:09
pmcgowanogra_, where are your logs?18:09
pmcgowan+118:09
ogra_http://people.canonical.com/~ogra/touch-image-stats/rtm/18:10
ogra_one level up there is devel (vivid)18:10
sil2100ogra_: hah, my scripts are running on a canonistack instance!18:10
ogra_and there are archives too18:10
robrubfiller: ok you got 7 now18:10
sil2100ogra_: so that's not on my home desktop ;)18:10
bfillerrobru: cheers18:10
robrubfiller: you're welcome18:10
ogra_sil2100, hah18:11
pmcgowansois the 148 I just got actually 145? so confused18:11
ogra_pmcgowan, before you start to wonder, these changelogs are only rootfs changes ...18:11
ogra_so all custom tarball or device tarball uploads generate nothing18:11
sil2100pmcgowan: basically, yes ;)18:12
ogra_pmcgowan, yes, 146 was 145 renamed when colin made a change on tehserver config ... 147 was a wrongly landed device tarball, and 148 was the reversion of that tarball ... which gets you back to 145 with shiny new version number18:13
pmcgowanpooooof18:13
pmcgowanhead exploding18:13
ogra_lol18:13
ogra_yeah, better stick to sil2100's executive summary18:14
sil2100hah ;p18:15
=== josepht changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: None
josephtballoons: sorry, I must've missed your ping18:33
josephtballoons: my highlight didn't catch it :) 12:14 < balloons> ping joespht .. is something up with core apps jenkins?18:35
balloonsjosepht, ahh fun!18:35
balloonsyou should remember to turn off those ignore balloons settings whenon vanguard :p18:36
ogra_pmcgowan, i think i saw somone else with bug 1390170 yesterday18:38
ubot5bug 1390170 in ubuntu-system-settings (Ubuntu) "Two system updates notifications shown" [Medium,New] https://launchpad.net/bugs/139017018:38
popeyplars: omg... it was a dodgy usb cable!18:39
ogra_pmcgowan, ah, that was seb12818:40
pmcgowanogra_, yeah thats a first for me18:40
=== chihchun is now known as chihchun_afk
pmcgowannow getting 0 or 2 it seems18:40
ogra_so he can confirm your bug :)18:40
ogra_iirc there was already some log collecting going on with Chipaca18:40
seb128ogra_, pmcgowan, yeah, just commented on it, Chipaca said it was an indicator bug, the push helper log suggest it send a clear order to the indicator and that seems to fail18:41
Chipacapmcgowan: if you've got that again, talk with larsu18:41
Chipaca(larsu agreed it's a bug, asked for a way to reproduce, or a crash)18:42
seb128Chipaca, larsu said the warning in the messaging log was a bug right?18:43
seb128we have no proof that the "didn't clear" issue was the same one18:43
Chipacawell, we have push asking for a clear, the clear not happening, and a warning in the log about a delete out-of-bounds error18:44
seb128well, maybe the way push ask for the clear is buggy?18:44
seb128the indicator didn't change for a while and we never had clear failing18:44
pmcgowanis there a messaging log I should grab?18:44
seb128pmcgowan, cf my command on the bug18:45
seb128comment even18:45
Chipacayes, which is why i asked larsu, and his response was that it shouldn't ever happen18:45
seb128k18:45
seb128is there any way we can "emulate" the situation?18:45
seb128would make easier debugging18:45
Chipacaseb128: i don't know how the situation comes about18:47
Chipacaonce it's in there, it's easy enough to see the failure18:47
Chipacajust call ClearPersistent on the right endpoint18:47
Chipacasee it return 0 (as if there were nothing in the indicator)18:47
Chipacahmmm... well, that's only after the first. so no.18:47
Chipacaseb128: i don't know of one.18:47
seb128I guess the question is "do we have a script that do 'add entry, clear, add entry'" the same way that's done in the scenario logged in those logs18:48
Chipacaseb128: i can give you a command that does "clear, add entry" and you can call it repeatedly18:48
seb128Chipaca, that would be a start ;-)18:49
seb128then I can see if I can get the indicator to print that warning again18:49
seb128pmcgowan, note that the dup doesn't happen all the time, I got it once this week18:49
seb128just got an update notification and it's not duplicated18:49
pmcgowanseb128, this is the only time I ever saw it18:49
pmcgowanI added a coupe logs around the time18:50
ogra_pmcgowan, but you usually dont wait til two images have built18:50
ogra_today we actually had two really close in succession ... we rarely have that18:50
pmcgowanogra_, thats true, although 147 had downloaded already18:51
rsalvetisil2100: ogra_: john-mcaleely: we can land silo rtm 9, but we need to coordinate it with the device tarball18:54
rsalvetihow to proceed?18:54
john-mcaleelyI think sil2100 had a cunning plan earlier18:55
ogra_rsalveti, once the silo migrated we switch off the s-i auto-importer18:55
john-mcaleelyor possibly ogra_ did18:55
ogra_once the rootfs is built and the tarball is in place, we switch it back on18:55
rsalvetialright, let me publish it then18:55
plarspopey: hah!18:56
sil2100rsalveti, ogra_, john-mcaleely: right, we publish silo 9, silo 4, ogra_ disables the auto-importer and we kick a new image18:56
ogra_ah, i forgot about 418:57
ogra_that was so tiny ... easily missed :P18:57
sil2100Would be best to have 4, but brendand said it's signed-off too18:58
sil2100I mean, it was just waiting for silo 918:58
sil2100...and that telephony silo18:58
sil2100brendand: ping ^18:58
rsalvetiargh, having issues publishing it18:58
sil2100uh18:58
rsalvetithat was after doing a watch only build18:59
sil2100hmmm18:59
rsalvetisil2100: no idea of what is going on in there19:01
rsalvetican't publish19:01
sil2100rsalveti: will try looking into that as well19:01
robruslangasek: sil2100: meeting? https://plus.google.com/hangouts/_/canonical.com/landing-team?authuser=119:01
ogra_just dput :P19:01
sil2100rsalveti: strange, CI Train doesn't find those packages at all19:05
rsalvetinice19:07
sil2100rsalveti: even though the backend has that configured19:07
sil2100hmmm19:07
sil2100Maybe the state got lost on the jenkins instance19:07
sil2100Let me take a look there19:07
rsalvetialright19:08
sil2100robru: hmm... you might need to look into that yourself ^19:15
sil2100robru: since it seems that before doing watch-ppa for silo 009 citrain doesn't seem to copy the .dsc files for watch-ppa anymore19:15
sil2100So it doesn't recognize those19:15
sil2100robru: did you test your changes for source uploads?19:15
sil2100robru: might not be caused by your changes, but as we relied on paths there, I suspect it might19:23
robrusil2100: hm, I guess I forgot to test source uploads. I made sure mps and syncs were working though. they all copy the dscs into the right place. Ok I can take a look at that now. :-/19:39
sil2100robru: thanks! :)19:42
sil2100ogra_: and still no archive link for my e-mail ;/19:42
ogra_the last two days it was pretty fast19:42
robrursalveti: sorry are you in a hurry to publish? I really need to take lunch...19:43
slangaseklool: interesting... why does spreadsheet line 18 have a testing sign-off from you against an RTM image for an Ubuntu silo?19:44
ogra_robru, the next image build waits for it ..19:44
robrursalveti: if you're in a hurry just binary-copy the packages. but please don't free the silo, I need to poke at it.19:44
robruogra_: ugh it will not be quick to fix. can you just binary copy the packages from the silo to distro?19:44
ogra_i'll leave that to ricardo, but yeah19:45
ogra_get your lunch19:45
ogra_:)19:45
robruok, brb19:45
rsalvetirobru: I can give you some time, no worries19:47
rsalvetias long we have people around that knows what needs to be done with the device tarball19:47
ogra_rsalveti, well, can you find someone else to coordinate the image then ? i dont want to do an all-nighter19:48
rsalvetiogra_: let me just publish that by hand then :-)19:49
ogra_:)19:49
ogra_thanks :)19:49
brendand-nexus5sil2100 did you hear anything about 9 yet?19:53
rsalvetilanding as we speak19:54
brendand-nexus54 and 17 will join it then19:54
ogra_if they can19:55
rsalvetiogra_: robru: alright, just manually copied all packages from silo 919:55
ogra_great19:55
rsalvetisilo 4 is still waiting QA to sign it off it seems19:56
ogra_lets hope the other silos dont need that too19:56
ogra_rsalveti, brendand-nexus5 gave that hours ago ...19:56
ogra_not sure why the spreadsheet isnt updated then19:56
rsalvetiright, looking at the spreadsheet19:56
rsalvetishould I publish both now then?19:57
brendand-nexus5ogra i did not. I was waiting for 919:58
Ursinhaslangasek, sil2100: I've requested access for both of you, it's not an RT but bootstack support instead -- unfortunately only the person that filed the request can see it20:00
UrsinhaI'll update you once they update the request20:00
sil2100brendand-nexus5: so, we seem to have a train issue20:01
sil2100brendand-nexus5: once robru investigates, we might have it released20:02
brendand-nexus5sil2100 - :/20:02
sil2100robru: if it takes too long, please soft revert the change and publish silo 9 and 420:02
sil2100Those are crucial for our images20:02
rsalvetialready manually published silo 920:04
ogra_sil2100, we can just copy-package the others too i guess20:04
ollisil2100, jhodapp do you guys know if this is in flight?20:05
ollihttps://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/138193020:05
ubot5Ubuntu bug 1381930 in unity-scopes-api (Ubuntu RTM) "[TOPBLOCKER] 7digital previews do not play in the scope" [Critical,Fix committed]20:05
ogra_sil2100, rob seems to only need the stuff to stay in there for investigation20:05
jhodappolli, should be, Saviq's team is working to land that20:05
rsalvetiwe just landed a few changes to qtubuntu-media20:06
rsalvetiwonder if we need to rebase it20:06
rsalvetior land it first on vivid20:06
rsalvetijhodapp: we can safely land https://code.launchpad.net/~jhodapp/qtubuntu-media/fix-1381930/+merge/240327 on vivid, right?20:06
jhodapprsalveti, yes20:07
rsalvetilet me create a silo for that one20:07
sil2100Ok, so make sure that silo 4 and the telephony changes land as well20:08
sil2100And do the image kick20:08
robrursalveti: sil2100 ogra_ other than 9, are the other urgent silos source uploads, syncs, or mps?20:08
sil2100robru: not sure if 4 is not mixed20:09
rsalvetiseems we need 4 and 1720:09
rsalveti14 is also ready to go20:09
sil2100ogra_: and still no archive entry of my e-mail...20:10
sil2100Ok, I need to AFK now, see you tomorrow20:10
sil2100ogra_: I'll keep my eyes opened for that and post when I see it20:10
sil2100o/20:10
rsalvetiogra_: robru: will try landing 4 and 17 then20:11
jhodappquite the backlog of things to land :)20:11
rsalvetiSaviq: https://code.launchpad.net/~unity-team/unity8/rtm-14.09-staging/+merge/240664 is not yet approved20:11
om26erralsina, Hi!20:13
rsalveti17 is in, can't publish 4 though20:13
rsalvetiuntil the MR is approved20:13
rsalvetikgunn: ^20:13
robrursalveti: wtf? 9 is a sync silo, I specifically tested that, it was working yesterday!20:13
om26erralsina, I am trying to test silo for bug 1384855 -- I am not sure what was the issue exactly ?20:13
ubot5bug 1384855 in Ubuntu Push QML "clearPersistent is passing a string list instead of multiple strings to push-client" [Critical,Triaged] https://launchpad.net/bugs/138485520:13
ralsinaom26er: there was a bug that caused a push-client crash when a certain function was called.20:14
ralsinaom26er: nothing used that function before so noone noticed. The suggested test is adding the crashing call on startup of the hello app. If you can start it and push-client doesn't crash, it's fixed20:14
kgunnrsalveti: thanks...hmmm which MR20:15
* kgunn goes to look20:15
om26errsalveti, so no potential of regression then, you are just fixing an API that nothing was using before  ?20:16
rsalvetikgunn: https://code.launchpad.net/~unity-team/unity8/rtm-14.09-staging/+merge/24066420:16
olliSaviq, is this in flight?20:16
ollihttps://bugs.launchpad.net/dialer-app/+bug/137804320:16
ubot5Ubuntu bug 1378043 in unity8 (Ubuntu RTM) "[TOPBLOCKER] Phone is getting locked during a call" [Critical,In progress]20:16
robrursalveti: ogra_ oh ok I see what's happening, i changed the code to save certain files in a different place, this silo was assigned before the change so the files are in the wrong place. I can fix this live in production without any code changes20:17
kgunnrsalveti: ok, approved just an oversight20:17
kgunnolli: we're all good20:17
ollikgunn,20:17
olli?20:17
kgunnolli: oops, nvmd20:18
kgunnlemme read20:18
om26erralsina, oops that message above was for you :) wrongly sent to ricardo.20:18
kgunnrsalveti: we're still good on the approval topic tho20:18
om26errsalveti, mis-typed :)20:18
rsalvetialright, 4 just got published20:18
kgunnolli: that bug isn't us20:18
ralsinaom26er: exactly, just fixes that API, noone uses it yet, telegram will after this lands20:18
kgunnchicken20:18
ralsinaom26er: no regression possible at all20:19
rsalvetirobru: ogra_: guess we just wait them to hit release, trigger a new image and copy the device tarball20:19
rsalvetiogra_: is that something you can take care of?20:19
ollikgunn, it has an rtm u8 task20:19
om26erralsina, cool.20:19
robrursalveti: right, well now there's this: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-009-2-publish/23/console20:19
kgunnolli: my bad...i see he added a chicken branch for u820:20
rsalvetiwtf20:20
ogra_rsalveti, thats why i'm still here, we need to stop the auto-importer20:20
kgunnolli: yes, it was part of the mega load20:20
robrursalveti: version bs. did you binary copies get accepted? seems like you were uploading versions 14.10 when 15.04 was already in rtm20:20
ogra_(to have everything be imported together)20:20
kgunnso silo420:20
pmcgowankgunn, which has landed already? i cant reproduce it20:21
rsalvetirobru: silo 9 was fine, did a binary copy and it worked fine it seems20:21
kgunnpmcgowan: actually...silo4 rtm is _just_ now landing20:21
kgunnonly landed on vivid 2 days ago20:21
robrursalveti: oh wait, I think I'm reading the log backwards. I think it's just complaining that it found your manual uploads already at the destination and it didn't expect that20:22
rsalvetirobru: right, that would make more sense :-)20:22
pmcgowankgunn, it was merged on the 20th, seems it must have landed before now20:23
pmcgowananyway I cant see the issue occur20:23
kgunnpmcgowan: on trunk20:23
robrursalveti: ok ignore the errors coming from silo 9, it's confused. once the packages are in destination we can just free that20:23
kgunnwe've got 2 branches20:23
kgunnalready20:23
robrursalveti: I'll check other silos for this same problem and pre-emptively fix those20:23
rsalvetialright20:23
pmcgowankgunn, I guess I am concerned as the bug seems fixed, so whats the MR for20:24
pmcgowanChickenCutlass, you around?20:24
kgunnat any rate, bug updated20:24
kgunnpmcgowan: you're right...it was in the last mega load (end of sprint week)20:25
pmcgowankgunn, oh good20:25
pmcgowanthanks20:25
kgunnsorry, thot it was this one20:25
kgunni just see big silo, i think it's this one :D20:25
pmcgowanyou and your big silos20:25
Ursinharobru: are these bugs we are introducing with our changes? or only bugs our changes are uncovering?20:26
rsalvetiI just landed so many things I'm scared20:26
rsalvetilol20:26
* kgunn wants a tshirt that says "unity8: we've got big silos"20:26
rsalveti10 packages + new device tarball20:26
Ursinhakgunn: hahaha20:26
ollikgunn, so https://bugs.launchpad.net/dialer-app/+bug/1378043 this one is fix released then20:27
ubot5Ubuntu bug 1378043 in Ubuntu UX "[TOPBLOCKER] Phone is getting locked during a call" [Critical,Fix committed]20:27
olliwondering why it wasn't cleaned up20:27
rsalvetiisn't this part of the one that is just landing?20:27
kgunnolli: i think actually it was linked after the bot ran ?20:27
robruUrsinha: a little bit of both20:27
ollihm20:27
kgunnor the bots semi-reliable20:27
ollikgunn, mind updating the status?20:27
robrursalveti: ok same issue fixed in 2 other silos, initial guess is that's all of them, will double check now20:28
kgunni did, hit refresh ?20:28
kgunnolli: ^20:28
olligood boy20:28
ollithx!20:28
rsalvetiwtf20:28
rsalvetilol20:28
* kgunn sits up and pants20:28
olli:)20:28
* ogra_ looks for bleach to get these pics gone20:29
robruUrsinha: so the thing is, there is just a literal truckload of code that accesses files using relative paths, and depends on the cwd being set correctly somewhere else in the code. In most cases you can just change the relative path to an absolute path and it's fine. but some bits of the code were so obscure that I literally was not able to trace back from20:30
robruthe relative path to the previous call to os.chdir to figure out what directory it was supposed to be in. so I just hardcoded 'ok these files live in the silo root dir now', and that's great when you assign a new silo from scratch, but unfortunately existing silos had those files in bizarre subdirectories that I didn't expect. so I had to just dig in the20:30
robruserver and move those files into their new canonical path in order for the new code to find those20:30
ogra_rsalveti, is 009 completely in ?20:32
rsalvetiogra_: yes20:34
ogra_great, let me kick of a rootfs then ... will john-mcaleely be around later to push the tarballl ?20:34
john-mcaleelyhe will ogra_20:34
ogra_yay20:34
ogra_:)20:34
john-mcaleelyhow long do you think?20:35
john-mcaleely(before I do my bit)20:35
ogra_45min for the rootfs or so ...20:35
ogra_max 1h20:35
john-mcaleelyok, I'll return to a beer for a while then :-)20:35
ogra_https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/20:36
ogra_:)20:36
john-mcaleelyhow many times can I hit reload?20:38
john-mcaleely:-)20:38
ogra_heh, try DOSing the server ;)20:38
ogra_the estimated times are really just rough guesses20:38
ogra_armhf usually takes longer20:38
imgbot=== trainguards: RTM IMAGE 149 building (started: 20141106 20:40) ===20:39
davmor2ToyKeeper: ^ one for you to review on sanity when it builds I think :)20:39
asaci guess we could parse the backlog of the imgbot and use the times to get real data on how long it takes20:40
ogra_asac, well, thats combined times of s-i and rootfs20:40
ollikgunn, mind having a look at https://bugs.launchpad.net/ubuntu-ux/+bug/138474920:40
ubot5Ubuntu bug 1384749 in ubuntu-ui-toolkit (Ubuntu) "[TOPBLOCKER] Detected X,Y coordinates for touch event on text field is off" [Critical,In progress]20:40
ogra_the url above has the plain rootfs20:40
asacogra_: guess thats what we really care about, no?20:40
ogra_asac, indeed20:41
kgunnolli: doing20:41
asac"time to final image"20:41
ogra_asac, though john waits to upload the device tarball at tthe right time20:41
ogra_for that tthe rootfs build time is the measure20:41
asacoh an "alley oop" basically20:41
davmor2asac: from experience 1:30-2hours20:41
asacnice move20:41
asaclol20:41
ogra_asac, right ... coordinated device tarball and silo landing ... so we spare one broken image20:42
asacyeah alley-oop :)20:42
ogra_right, 1:30 -2h ... this time it will take longer because i'm driving the s-i importer manually20:42
asacguess we should think about how to make infra smarter so doing what we try to do is less of a stunt20:43
kgunnolli: so wrt bug, my understanding is, there's really nothing to be done from our end20:43
asacl8tr20:43
ogra_at some point we need one s-i server per project20:43
ollikgunn, can we remove the tasks then20:43
ogra_then its gets easy20:43
kgunnolli: the related mir bug could be considered an "enhancement"20:43
kgunnolli: ack20:43
ChickenCutlasspmcgowan: yes20:49
pmcgowanChickenCutlass, we closed that bug we were discussing20:50
pmcgowanwhere the phone locked on a call20:50
ChickenCutlasspmcgowan: right cool20:50
ChickenCutlasspmcgowan: that should have been fixed with the last big unity upload20:50
pmcgowanyep20:50
ToyKeeperAh hah, I *did* hear a beep somewhere.21:05
ToyKeeperasac: It might be hard to get data from IRC logs, since imgbot hasn't been very reliable lately.21:05
ToyKeeperAnyway, I'll get the 149 testing going soon after it finishes building.21:05
ogra_yeah, sorry for that21:05
ogra_(imgbot)21:06
bfillerrobru: could you publish rtm14 when you get a chance? thanks!21:18
robruogra_: is it safe to publish rtm14 yet? how's that image build going?21:25
ogra_robru, just go ahead, it is in the final stages21:26
om26errobru, do you know when does the next rtm build will happen ? i.e. 14921:26
ogra_om26er, in the works :)21:27
john-mcaleelyogra_, page says built. do I push yet?21:27
ogra_john-mcaleely, yeah, go ahead21:27
om26erogra_, as in building ? great!21:27
ogra_well, more as in"being-hand_puzzled-together"21:28
ogra_:)21:28
john-mcaleelyogra_, next puzzle piece slid in21:28
john-mcaleelyogra_, tarball pushed21:28
ogra_awesome ... firing the importer back up21:29
john-mcaleelythis will be 149, right?21:30
ogra_thats what the bot said, yes :)21:30
ogra_and the importer runs again ...21:31
ogra_~30min now, then we are done21:31
john-mcaleelynice21:32
ogra_plars, the 146 krillin tests seem to hang in address_book21:34
ogra_(or at least the dashboard does)21:34
plarsogra_: I'll take a look21:46
ogra_thx21:46
ogra_importer done ... should show up any minute21:51
plarsogra_: argh, 147 is up now I think... so the one I just started will pull that21:53
plarsoh, no it's getting 146, we're good21:53
plarsogra_: it seems that device went offline in the middle of the run and the job timed out. I'm curious to hear what state the device ended up in21:54
imgbot=== trainguards: RTM IMAGE 149 DONE (finished: 20141106 21:55) ===21:54
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/149.changes ===21:54
john-mcaleely\o/21:54
asac1:15h21:55
* john-mcaleely upgrades impatiently21:55
asacnot too bad21:55
ogra_go wild hapy testing :)21:55
plarswe skipped 147 and 148?21:55
ogra_asac, well, that was hand driven ... check the bot notes tonight with the auto-build ... thats mpore realistic21:55
asachand driven should be slower in average, no?21:57
ogra_wow ... what a changelog21:57
asacanything unexpected in that changelog?21:57
ogra_asac, not necessarily ... the different cron jobs are not all in sync ... so you have dealays ... i actually never measured the difference21:57
ogra_s/you have delays/you can have... /21:58
asacright. cron can only go so far. better is trigger driven :)21:58
asachehe21:58
asacso is this image potentially the best ever?21:58
* asac checks for update21:58
ogra_the compononets surely are21:58
john-mcaleelyunquestionably21:58
ogra_dont ask about the whole ;)21:58
john-mcaleelyjust booted for me21:59
asacthe components alone are not worse a lot; what counts is the melting pot of all in one unique awesome experience that is more than just software :)21:59
john-mcaleelywhat else could go wrong?21:59
ogra_right, but we dontn know how well all of them interact :)21:59
ogra_you only see that in the full image at the end :)21:59
ChickenCutlassogra_: not seeing 149 when I check for  updates22:02
ChickenCutlassogra_: does it take a little while22:02
ChickenCutlass?22:02
robruChickenCutlass: in my experience it's available as soon as the bot pings about it, but maybe that's no longer the case (I haven't tried recently)22:04
ChickenCutlassrobru: that’s what I thought — systems settings saying nothing there.22:04
ChickenCutlassanyway22:04
ChickenCutlassI will wait22:04
rsalvetiat least ubuntu-device-flash already found 149 here22:05
ogra_ChickenCutlass, tell Chipaca22:05
Chipacahello hello22:05
ChickenCutlassogra_: I am manually checking as well22:05
ogra_the system-settings updater too22:05
Chipacadrat22:05
ogra_ChickenCutlass, ah, then you most likely trashed the data for Chipaca22:05
Chipacagoodbye goodbye22:05
ogra_heh22:06
ChickenCutlassogra_: I rebooted and now its there22:06
ogra_ChickenCutlass, i have it flashing here22:06
ChickenCutlassweird22:06
ogra_when i had that last i saw a hanging system-image process22:06
ogra_check the next time22:06
ChickenCutlassok22:06
ogra_well, it boots ...22:08
ogra_hmm, registering my SIMs seems to take quite long22:08
ogra_ah, now it has both22:09
john-mcaleelyworked for me - hit update after the bot announced it. now enjoying it...22:09
ToyKeeperI wonder why xchat stopped pinging me when imgbot says something, but I still get notifications when someone mentions the word "imgbot".  Odd.22:09
ogra_yeah22:10
ogra_matching "=== trainguards" should get you all bot pings though22:11
robrubfiller: 17, 14, and 1022:37
bfillerrobru: nice22:37
dobeythere's still no way for jenkins to build click-packaged projects without having debian/ right?22:56
robrudobey: correct, jenkins does not build click packages. If you put in a debian/ directory it'll build you a deb22:57
dobeyi think jenkins does build click packages22:58
dobeyhttps://jenkins.qa.ubuntu.com/job/generic-click-builder-vivid-armhf/12/?22:58
dobeyat least, that looks like a click package to me22:58
dobeybut it looks like in the console output, that it's using dpkg stuff to install the necessary dependencies, to build the thing22:58
rsalvetirobru: hey, line 51 is not reflecting the reality in there23:53

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