/srv/irclogs.ubuntu.com/2014/09/08/#ubuntu-ci-eng.txt

imgbot=== trainguards: IMAGE 232 building (started: 20140908 02:05) ===02:05
imgbot=== trainguards: RTM IMAGE 23 building (started: 20140908 03:05) ===03:05
imgbot=== trainguards: IMAGE 232 DONE (finished: 20140908 03:45) ===03:45
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/232.changes ===03:45
imgbot=== trainguards: RTM IMAGE 23 DONE (finished: 20140908 04:15) ===04:15
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/23.changes ===04:15
=== robru changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
Saviqtrainguards, can I please have a reconf on silo 1907:01
Saviqadded qtmir-gles there07:02
robruSaviq: I'm not here, but ok ;-)07:02
Saviqrobru, yeah, you should *not* be here07:02
Mirvhmm :)07:02
robruMirv: ah, you're here. ok I got this one but I'm really not here ;-)07:02
Mirvrobru: when you're not really here, you should really really not be here :)07:03
robruMirv: who are you talking to? I don't see anybody here.07:03
Mirvexactly07:03
bzoltanMirv:  have you heard anything about how to (a) disable the edges intro and (b) how to unlock the screen remotely?07:26
Mirvbzoltan: a) like, other than phablet-config edges-intro --disable? b) maybe see http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh07:30
bzoltanMirv: the `phablet-config edges-intro --disable` does not do the job, so yes a working solution would be cool07:31
Mirvok, I'll keep my ears open07:32
bzoltanMirv:  for the unlucking ... WOW, if that works then I am saved :)07:33
Mirvbzoltan: for a), it's nowadays apparently as simple as... adb shell "sudo dbus-send --system --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts/User32011 org.freedesktop.DBus.Properties.Set string:com.canonical.unity.AccountsService string:demo-edges variant:boolean:false"07:33
Mirv;)07:33
Mirv(from http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/287)07:33
brendandbzoltan, hello - do you have results from you tests for silo 12 landing?07:36
bzoltanbrendand:  that is the 28.08 lanidng for RTM, right?07:38
brendandbzoltan, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-01207:40
bzoltanbrendand:  geez, that is an archaeological finding :) I have flipped the tested switch last week. I still have the logs. Do you need me to check something?07:45
brendandbzoltan, no i just want to have the logs for comparison07:46
=== tvoss is now known as tvoss|test
=== tvoss|test is now known as tvoss
Mirvrobru: "AttributeError: 'bool' object has no attribute 'isdigit'" https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-007-1-build/25/console08:11
bzoltanMirv:  Do you know what does this mean: $ adb shell "gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter && echo Greeter unlocked"08:12
bzoltanError connecting: Cannot autolaunch D-Bus without X11 $DISPLAY08:12
seb128bzoltan, that it can't connect to the session bus I guess08:14
seb128bzoltan, try to adb shell; su - phablet; <command>08:14
tvossbzoltan, running as root?08:15
bzoltanseb128: tvoss: with new adbd all my commands are run as phablet. but I can try to force08:15
ogra_bzoltan, thats a bug with cgroups that mterry works on since a few days08:15
Mirvbzoltan: I wonder if that one hasn't been updated to the new world similar to the provisioning08:15
seb128bzoltan, could be that the env is wrong/doesn't include the dbus session08:16
ogra_the env is definitely wrong, you need the sudo wrapper, but even then it wont work08:16
ogra_logind doesnbt hand out proper sessions due to the cgroups issue08:17
seb128ogra_, hasn't the cgroup bug fixed by desrt/slangasek in systemd-s on friday?08:17
seb128"debian/patches/0001-cgmanager-stop-doing-async-calls.patch:08:17
seb128    cgmanager: stop doing async calls; fixes a race condition on login.08:17
seb128    Thanks to Ryan Lortie <desrt@desrt.ca>.  Closes LP: #1365095."08:17
ubot5Launchpad bug 1365095 in systemd-shim (Ubuntu-rtm 14.09) "Greeter not asking for pin code in image 11 (krillin)" [Undecided,New] https://launchpad.net/bugs/136509508:17
ogra_dunno, i have seen mterry and hallyn discuss into the (european) nige08:17
seb128k08:17
seb128I though that was ^08:17
ogra_*nite08:18
seb128but maybe there is another issue still08:18
ogra_well, you definitely still need the sudo wrapper08:18
Mirvdbarth: the syncing seems broken in yet new other way, I'll help your silo manually in a bit08:18
ogra_adb shell <command> doesnt have the full env08:18
bzoltanMirv:  seb128: ogra_: when I manually adb shell in and execute the command then the screen get unlocked08:18
seb128bzoltan, what ogra_ said08:18
bzoltanseb128: I just have read... so ogra_, what is the trick?08:19
ogra_(i have been looking into that over the weekend, might be i can fix it in adbd)08:19
ogra_bzoltan, wrap the gdbus command in "sudo -u phablet -i" as usual08:19
bzoltanogra_:  OK, I try that08:19
pete-woods(apologies for the spam, I edited the description)08:21
bzoltanogra_: works now, thank you08:21
davmor2Morning all08:27
seb128dbarth, ^ no no no for that rtm settings silo08:29
seb128dbarth, we have settings in sile 015 and are trying to land that to rtm for a week, don't hijack it with your version08:29
seb128Mirv, ^08:30
Mirvseb128: noted08:30
seb128https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-015/+packages08:30
seb128get that to land first please08:30
seb128that should be good, just need qa verification08:30
Mirvwill do that08:31
seb128thanks08:31
seb128should we clear 007 out meanwhile to avoid errorS?08:31
seb128it's going to need to be rebased on top of what is 015 anyway08:31
Mirvyeah, I'll clear it too, the current build has no use08:31
seb128or well, is that a sync of current utopic u-s-s?08:32
seb128because then that would be fine, but it would required a new round of testing, so we should still land 015 which has been tested already08:32
Mirvogra_: meeting?08:32
ogra_Mirv, i wish i could, firefox doesnt let me :P08:34
brendandseb128, hey - silo 15 seems to have issues08:36
seb128brendand, shrug08:36
seb128brendand, which ones?08:36
brendandseb128, wizard crashes, and sim cards can no longer be unlocked08:36
brendandat least. still more testing to do08:36
seb128brendand, settings have nothing to do with sim unlock08:36
seb128are you supposed you tested settings only?08:37
Mirv(running with watch_only since it had wrong status)08:37
brendandseb128, i have only upgraded the system-settings packages08:37
seb128brendand, the way we work is a bit weird btw, that update fixes at least 15 bugs and some important rtm ones, and we block on those fix on one potential issue08:37
seb128block those fixes on*08:38
seb128brendand, that "can't unlock sim" looks like it could be the systemd issue fixed in friday08:38
seb128brendand, anyway, as said, settings don't do sim unlock, so if you found a bug it's not with settings08:39
seb128brendand, it's more likely a random one which is already there in the image08:39
brendandseb128, it works before installing the packages08:39
seb128brendand, that shouldn't count as a settings blocker08:39
seb128you got lucky08:39
brendandseb128, several times08:39
seb128it might work on another try who knows08:39
seb128you got lucky several times08:40
seb128what I can tell you08:40
brendandseb128, alternatively - you're wrong08:40
seb128brendand, settings don't have sim unlock code, they are not involved in that08:40
seb128shrug08:40
seb128k, I give up, do whatever you want with settings08:40
Mirvactually we can't do any ubuntu-system-settings rtm landing because any new sync from utopic silo would include the landing-rtm-015 silo changes anyhow, so any QA signoff will depend on the rtm-015 changes being testably regression free.09:03
Mirvdbarth: ^ so your location settings landing might take some time to reach rtm until the previous u-s-s rtm landing is agreed by QA09:04
seb128Mirv, brendand has issues with settings anyway, so it looks like it's not ready to land09:05
seb128brendand, btw having a bug report of those specifics issue would help09:05
brendandseb128, i'm just going to confirm (again) what's going on09:05
dbarthMirv: ok, noted09:10
pete-woodsthanks for the allocation :)09:17
Mirvpete-woods: you're welcome :) we just had 0 silos free so I didn't do that earlier.09:19
pete-woodsMirv: have you seen weird build failures like this before? https://launchpadlibrarian.net/184302130/buildlog_ubuntu-utopic-amd64.libusermetrics_1.1.1%2B14.10.20140908-0ubuntu1_FAILEDTOBUILD.txt.gz09:24
pete-woodsmy diff for this change is totally insignificant (just adds the X-Ubuntu-Use-Langpack: yes line)09:25
Mirvpete-woods: ogra_: that problem pete is seeing is because of that not-done-by-me qtxmlpatterns upload. we probably need to revert it.09:27
ogra_Mirv, ouch ...09:27
Mirvpete-woods: thanks for letting us know, we just noticed in the meeting that a new qtxmlpatterns had been uploaded by mitya57. I assumed it was ok since we hadn't had error reports, but now we did09:29
Mirvnothing wrong with the new upstream version otherwise, but Qt is just very strict about numbers...09:30
pete-woodsno problem :)09:30
MirvI pinged him on #ubuntu-devel now, there's either a revert option or faking the module version option09:30
pete-woodswell I'll just be happy to build my package :) will follow along to see when it's resolved09:31
brendandseb128, so the bug is reproducible by installing the silo and then resetting the device09:33
brendandseb128, on utopic it's not reproducible - at least not on mako09:34
seb128brendand, can you describe "the bug"09:35
brendandseb128, i'll file it09:35
seb128thanks09:35
jodhMorning - can someone help me get upstart 1.13.2-0ubuntu1 into the rtm branch?09:37
brendandseb128, until then, when you click on the unlock button, indicator-network just seems to reload itself09:37
seb128brendand, k, your are speaking about the SIM unlock on boot?09:39
seb128brendand, that doesn't make much sense to me, settings are not running at this point and none of their code is used by unity8, the code involved should be unity8 and indicator only09:40
seb128brendand, I hope somebody figure it out though09:40
brendandseb128, it doesn't seem to happen if the wizard doesn't run, so maybe that leaves something in a bad state09:40
seb128brendand, that would be and is more likely than having settings involved09:43
jodhMirv: Hi - could you add a "sync: ubuntu,utopic,upstart" to the CI spreadsheet? I don't have write access and we need the latest utopic upstart in Touch for the "UAL with CGroups" landing (line 4 in the s'sheet)09:53
Mirvjodh: sure, but add where exactly? line 4 is the utopic landing10:01
Mirvjodh: or do you mean add a new upstart rtm landing for syncing from utopic?10:02
Mirvyes, I think you mean that10:02
jodhMirv: yes, a sync of the latest upstart in utopic which is a pre-requisite for line 4 actually working :)10:02
ogra_bzoltan, with my latest android-tools upload the sudo wrapping shouldnt be necessary anymore (once it landed in all images)10:04
ogra_(it wont do any harm either to keep it though)10:04
Mirvjodh: ok it will shortly start building at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-007/+packages . line 63 on the spreadsheet.10:05
jodhMirv: thanks very much!10:05
ogra_Saviq, are you landing https://code.launchpad.net/~unity-team/unity8/new-adbd/+merge/233684 somewhere ?10:11
Saviqogra_, yeah, silo 1910:11
Saviqogra_, but need to fix a sh$tload of ap tests that assumed there's no password10:11
ogra_Saviq, see above ... adbd should be fixed now ... while it wont do harm it also shouldnt be absolutely necessary anymore10:11
robruMirv: erk, looking10:11
Saviqogra_, yeah, k10:12
ogra_Saviq, (might make sense to verify it though ... but i think it shoudl "just work")10:12
Saviqogra_, kk10:12
robruMirv: looks like you freed the offending silo. I'm happy to blame sil for this, amazingly this bug is not in a part of the code that I've been hacking on ;-) if you see that again, try freeing the silo and then reassigning it, sil made some changes to the silo config format, silos that were assigned prior to friday may be incompatible with code that sil10:19
robrulanded on friday.10:19
ogra_ogra@styx:~/Devel/branches/phablet-tools$ adb shell "gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter && echo Greeter unlocked"10:24
ogra_()10:24
ogra_Greeter unlocked10:24
ogra_ogra@styx:~/Devel/branches/phablet-tools$10:24
ogra_yay !!!10:24
ogra_GGRRR did anyone elses krillin touchscreen get super sensitive in the recent images10:26
ogra_i cant even scroll in news weballs without having it open unwanted links all the time10:26
ogra_*webapps10:26
ogra_this is unusable !10:28
popeyogra_: ooh, i noticed that at teh weekend. have you got a bug for it?10:28
ogra_funnily there is no issue in the G+ app ... but in all news apps i tried10:28
popeyyeah, same10:28
ogra_popey, nope, only noticed it on sat and thought my display was to dirty or something10:29
popeyheh, ok, I'll confirm if you bug it.10:29
popeyguessing oxide?10:29
ogra_but it persists (and feels like it got worse, though probably i'm just easier to annoy now)10:29
ogra_popey, we didnt have oxide updates in rtm10:29
ogra_i think ...10:29
* ogra_ checks 10:29
ogra_i assume its the device tarball10:30
ogra_http://people.canonical.com/~ogra/touch-image-stats/rtm/21.changes thats all that landed on the weekend10:30
brendandseb128, here's a twist10:36
brendandseb128, i can reproduce it in utopic without the silo installed... but only on krillin :/10:36
seb128brendand, utopic already has the changes though, no need of a silo10:37
Mirvrobru: thanks for looking! a sync specifying a package worked, but then we postponed the whole landing. good to know, that workaround, makes sense that there was a format change.10:40
brendandseb128, well yes - i suppose that statement is a bit redundant10:43
brendandseb128, but i've tested the same thing on both krillin and mako with utopic and it only fails on krillin10:43
seb128brendand, k, fun10:43
ogra_yay10:45
ogra_gra@styx:~/Devel/branches/phablet-tools$ adb shell "gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter && echo Greeter unlocked"10:45
ogra_()10:45
ogra_Greeter unlocked10:45
ogra_ogra@styx:~/Devel/branches/phablet-tools$10:45
ogra_works on rtm fine as well :)10:45
=== MacSlow is now known as MacSlow|lunch
Saviqcihelp, this jobs looks stuck, 'innit http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako/4375/console ?11:00
Saviqso do the next two ones... /me worried that's what plars reported about devices getting stuck :|11:00
ogra_what devices are these ? makos ?11:01
ogra_(on krillin there was a udev rule from the device tarball that broke a shipped rule for adbd, which made the devices come up as offline, fixed on sat. devices that booted with the broken image might go stuck ... this is krillin only though)11:03
psivaaSaviq: ogra_: these devices are not offline. could be some other issue11:07
ogra_yeah, not that then11:07
ogra_its only krillin utopic anyway, mako and rtm should be fine11:08
davmor2Mirv: for some reason RTM silo 008 says it doesn't need QA sign off.  Yes it does and looking at the description there is more than one fix so it is all lies.  Also the telephony service isn't building11:12
bzoltanogra_:  have you guys hit this bug  with the CI testing  -> https://bugs.launchpad.net/gallery-app/+bug/1363190 It is a silent killer. You will not even notice that the flashing fails...11:14
ubot5Ubuntu bug 1363190 in gallery-app "Gallery APP autopilot tests pollutes the file system" [Undecided,New]11:14
psivaaSaviq: ogra_: so http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako/4375/console is not stuck, but it took a bit of time at one stage. they are progressing now11:21
ogra_yay11:21
ogra_good to know11:21
Saviqpsivaa, oh ok thanks11:22
Saviqoof11:22
Mirvdavmor2: bfiller has written there ": these are isolated bug fixes don't need QA signoff". and I've written that telephony-service failed to build11:27
Mirvprobably because of some media related landing missing from rtm11:27
davmor2Mirv: my concern is that we were told all rtm silos needed QA approval and now we see one that says it doesn't need it, so now we are wondering how many of these things are getting through11:32
Mirvdavmor2: the policy was that isolated bug fixes can go in without QA approval, but that 90% of landings would need the approval. better defining what's an isolated bug fix would help.11:33
davmor2Mirv: okay I'll chase it up with jfunk latter11:34
Mirvdavmor2: see line 58/59 for another example. I think I haven't seen others lately.11:34
Saviqtrainguards, I can get silo for line 29 please11:39
MirvSaviq: with pleasure. how's the utopic silo testing looking?11:47
SaviqMirv, had to fix a lot of autopilot because of the adb change (we didn't support pinlocked tests until now)11:48
SaviqMirv, so that's building now11:48
Saviqor built actualy11:48
Saviq+l11:48
Saviqso am testing now11:48
MirvSaviq: ok, cool11:51
=== MacSlow|lunch is now known as MacSlow
=== iahmad_ is now known as iahmad
=== om26er is now known as om26er|afk
ogra_Mirv, do you have anything pending for a new image ? i would like to trigger a build (that should hopefully help with screen unlocking in the lab)12:22
=== om26er|afk is now known as om26er
Mirvogra_: feel free to fire, I'm not holding my breathe on anything specifically12:26
ogra_heh, ok12:26
ogra_triggered12:26
asacMirv: see -touch for your help12:29
asacmterry: so i think we might wnt to move the systemd-shimd source packag efrom utopic in the system-setting silo?12:30
asacmterry: do we also need li8ghtdm?12:30
mterryasac, no12:30
asacmterry: no for putting it into the same silo?12:31
asacthink would help if it really fixes the problem that the system-settings silo bounced12:31
=== iahmad is now known as iahmad|afk
ogra_woudl be good if someone who has the issue could confirm that first though12:31
ogra_(that systemd-shim actually fixes the SIM unlocking)12:32
asacright12:32
asacdavmor2 is at lunch12:32
asacbut given that mterry fixed the same issue12:32
asaci am sure it does12:32
ogra_before you pile up more stuff in that poor silo12:32
asachttps://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/136509512:32
ubot5Ubuntu bug 1365095 in systemd-shim (Ubuntu-rtm 14.09) "Greeter not asking for pin code in image 11 (krillin)" [Undecided,New]12:32
asacogra_: that silo currently onlyhas system-settings12:32
ogra_asac, with a bunch of MPs though12:32
mterryasac, well...  I am not sure that they are the same root problem yet12:32
asacright, but if those depend on this one then they should go in together to avoid duping QA12:33
asacmterry: ok. let us know12:33
asacMirv is chcecking whty the shim silo didnt ubild12:33
asacMirv: uscan warning: In watchfile /tmp/tmp6IdJ2a, reading webpage http://people.gnome.org/~desrt/ failed: 500 Can't connect to people.gnome.org:80 (timeout)12:33
asachmm. it cant find the orig it seem12:34
ogra_yeah, that cant work12:34
asacs12:34
asacguess it should come from ubuntu archive12:34
asacmabye that thing was stuck in proposed?:12:34
ogra_no12:34
ogra_i saw it enter the utopic image12:34
asacogra_: when? before the silo failed?12:34
ogra_must be in the utopic archive proper12:34
Mirvasac: if you say -touch, then I discuss at -touch :) I copied it now manually.12:34
ogra_asac, yes12:34
asacMirv: thanks12:34
imgbot=== trainguards: IMAGE 233 building (started: 20140908 12:35) ===12:34
asacMirv: yeah, i just thought as we continued we might wanna go back here. sorry12:35
asacfor me its one tab away though :P12:35
asachehe12:35
asacright next door12:35
ogra_asac, 7-3 was an upload, didnt go though silos in utopic12:35
ogra_(systemd-shim 7-3 that is )12:35
asacogra_: sure, but could have been stuck in proposed when wee tried the silo for rtm12:35
asachttps://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/6/console12:35
asacogra_: it was siloed for rtm after12:35
asacbut anyway, we got it in now :)12:36
ogra_asac, silo buildds behave slightly different to distro builders ...12:36
* ogra_ got bitten by that on the weekend with android-tools too12:36
asacogra_: its not in the buildds12:37
asacits before... check the log12:37
asacbut doesnt matter now :)12:37
* asac still believes that the silo build was attempted when it was still in proposed and the jenkins doesnt take source origs from proposed12:37
cjwatsonis the theory here that the silo might have built against a package from -proposed?12:39
ogra_asac's theory is, yeah12:40
cjwatsonthat would be anomalous as silos are not normally configured to build against -proposed12:40
ogra_i think the copy-package would have copied the orig.tar.gz in any case12:40
cjwatsoncopy-package does not concern itself with such details :)  but the publisher would republish that when it runs12:41
cjwatsonif bzr-builddeb is relying on the .orig.tar.gz being in the archive already, then it may have to wait a publisher cycle12:41
asacno ... i said that the silo upload through the jenkins job might have been tried when the package wasnt in proper archive yet12:42
asachence we get the weird "cannot download orig tarball" failyure12:42
asachttps://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/6/console12:42
asacbut *shrug*12:42
cjwatsonIMO the problem there is that the version is wrong12:42
ogra_asac, the "silo upload" is a manual script call ...12:43
cjwatsonThis isn't a package that has its upstream maintained by ci-train, so surely it should be 7-3~rtm or similar, not 7~rtm-312:43
ogra_which essentially does something similar to a dput ... which in turn i would expect to have uploaded the orig tarball12:43
* asac desnt know and leaves it to the smart folks12:43
cjwatsonI seem to remember somebody mentioning that bug/misfeature/whatever here recently12:43
ogra_yeah, i think lukasz was looking into that on friday12:44
cjwatsonwe could just do a source copy instead though, right?12:44
asacyeah i see the version now12:44
asacdefiitely bogus12:44
cjwatsonunless this is a cherry-pick12:44
asaccjwatson: Mirv alreadu uploaded manually to the silo now12:44
cjwatsonok12:44
asaci think the ci train source copy feature is what failed here initially12:45
asacbut guess the version mangling is really bogus still there12:45
cjwatsonif it's doing version mangling it's not a copy ... :)12:45
asacyeah12:45
asacso i am not sure :)12:45
cjwatsonhave to admit I haven't used the sync feature yet; for ubuntu/landing-003 / ubuntu-rtm/landing-003 I just used copy-package since I could12:45
MirvI did copy-package now12:45
asachard to remember who did what there ... thought they used the sync: feature12:45
asacMirv: will the silo status figure that it got fixed?12:46
asaci mean here: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=12:47
ogra_if it was a dput it will ... with the next watch_only build12:47
ogra_(which you can only do after the packages have built ... be patient :) )12:48
asacheh12:48
cjwatsonyou can do it a bit before and it'll wait12:48
Mirvasac: yes, it just requires watch_only build that can't be done right away. it's now running.12:50
asaccool. thx12:50
* ogra_ thinks the last android-tools fix is the grossest hack he has ever done ... bt it makes things work 12:51
ogra_Sep  8 14:50:32 ubuntu-phablet sudo:  phablet : TTY=pts/38 ; PWD=/home/phablet ; USER=phablet ; COMMAND=/bin/bash -c /bin/bash -cl env12:51
ogra_(thats the log output of "adb shell env"12:51
ogra_)12:51
ogra_(see the COMMAND) ...12:52
boikorsalveti: hi, is the QMediaPlayer's audio role stuff already in RTM (or close to land at least)? telephony-service is failing to build on the RTM silo13:17
boikorsalveti: https://launchpadlibrarian.net/184207757/buildlog_ubuntu-rtm-14.09-amd64.telephony-service_0.1%2B14.10.20140905~rtm-0ubuntu1_FAILEDTOBUILD.txt.gz13:17
jibelboiko, it's in silo 11. I'm testing it.13:21
boikojibel: ah, nice!13:21
john-mcaleelyhi. I have a new device tarball I'd be interested in publishing today, if possible13:22
john-mcaleelyis someone able to give it a QA pass?13:23
boikoMirv: would it work if after rsalveti's silo 11 is landed, I trigger a rebuild of telephony-service? I didn't know there was code in telephony-service not landed on RTM yet13:23
john-mcaleelyogra_, ^ (as person running the landing meetings...)13:23
ogra_john-mcaleely, perhaps davmor213:23
ogra_depends how swamped he is ... looks like he is alone13:24
john-mcaleelydavmor2, something you could do today? (brendand did the honours on friday)13:24
john-mcaleelyogra_, understood13:24
rsalvetiboiko: yeah, would work after a rebuild13:25
rsalvetiboiko: didn't yet land because silo 11 is still to be tested13:25
davmor2john-mcaleely: Yeap I can do that, currently looking at a silo so I could do with it not conflicting with that.  Any idea on when you would like to land it13:25
rsalvetifrom my experience it takes a few days for the rtm stuff to be signed13:25
john-mcaleelydavmor2, it is worth doing, if I can land it before cob (~6pm) UK today13:26
john-mcaleelydavmor2, otherwise, it can wait13:26
boikorsalveti: ok, I'll just leave my silo sitting there waiting, would you mind giving me a heads up once silo 11 lands?13:26
rsalvetiboiko: sure13:27
boikorsalveti: thanks13:27
john-mcaleelydavmor2, http://people.canonical.com/~jhm/barajas/device_krillin-20140908-d8c11f3.tar.xz13:29
john-mcaleelydavmor2, simply download, and use --device-tarball with your favourite ubuntu-device-flash command to test13:29
davmor2john-mcaleely: no worries I'll give it a go asap13:29
john-mcaleelydavmor2, I'll ping you in a bit and see if I get lucky on your capacity :-)13:29
cyphermoxMirv: hey13:32
cyphermoxMirv: I'm seeing mtp as landed in the spreadsheet, and no longer in any silo, but apparently not in ubuntu-rtm13:33
asacogra_: Mirv: how are the landings for the rtm proposed blockers going?13:38
asaci think all but one had an MP according to sils mail on friday13:38
ogra_let me check his list13:39
asacogra_: its the four bugs i cut and forwarded to ue-leads with you CCed13:40
asacas you were appopinted the driver13:40
ogra_nobody told me :P13:40
asac** Sometimes input breaks and only edges are responsive13:41
asachttps://bugs.launchpad.net/bugs/1295623 => Merge requests present -> It should land soon, it's next in the unity8 queue.13:41
ubot5Ubuntu bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress]13:41
asac** Seekbar tests are skiped only on nexus 4 and 513:41
asacogra_: it was in the mail by sil13:41
asachttps://bugs.launchpad.net/bugs/1359040 => Merge requests present -> Is this really a blocker? Comment needed.13:41
ubot5Ubuntu bug 1359040 in mediaplayer-app "Seekbar tests are skiped only on nexus 4 and 5" [High,In progress]13:41
ogra_asac, yes, i see it13:41
asacogra_: so please ensure we dont pick up too risky landings while we try to get that13:41
asace.g. push back on crazy folks :)13:41
ogra_the seekbar stuff is really ignorable13:41
asacSaviq: when is landing of bug 1295623 scheduled?13:42
ubot5bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress] https://launchpad.net/bugs/129562313:42
ogra_but yeah, fix wouldnt hurt (four tests that should be skipped arent ... we tend to simply ignore their results ... purely cosmetic)13:42
Saviqasac, am testing now13:42
ogra_this one is definitely important13:42
Saviqasac, unless you mean the bug itself, then it landed around the time we started doing the phone ;)13:42
asac15:40 < ogra_> the seekbar stuff is really ignorable13:43
asac15:41 < asac> Saviq: when is landing of bug 1295623 scheduled?13:43
ubot5bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress] https://launchpad.net/bugs/129562313:43
asac15:41 < asac> ogra_: wll, we have an MP for that i read13:43
asac15:41 < asac> so why not get it in and get it off our worry list13:43
ogra_asac, no idea why it is on that at all13:43
jibelrsalveti, I tested silo 11, ran the testplan of pulseaudio and tried music player/mediaplayer/webbrowser with alarms and alert (incoming calls, incoming messages). All works fine, is there anything else to verify?13:44
asacogra_: wll, we have an MP for that i read13:45
asacso why not get it in and get it off our worry list13:45
rsalvetijibel: nops, that's it13:45
asac15:44 < asac> ogra_: well, sure that QA didnt like it and wants to get this resurrected13:45
asacogra_: well, sure that QA didnt like it and wants to get this resurrected13:45
asacdamn flaky connection13:45
asacoops :)13:45
* asac doesnt understand when irssi reposts stuff after disconnect and when not13:46
ogra_asac, answered your mail13:46
ogra_i didnt get tthat i was explicitly CCed ... evo just showed it in the thread13:46
asacogra_: anyway, i think that one is wihtelistable if we have the unity part13:46
mterryasac, phew had some laptop troubles -- in case you are still wondering, looks like the systemd-shim fix solves the SIM PIN problem13:48
tedgrobru, So I deleted the status on line 50, but I'm not sure if that was the right thing to do :-) It's fixed.13:48
ogra_mterry, right, it simply didnt land in rtm yet13:49
mterryogra_, sure...  Though note that the bug can still be reproduced on the latest utopic images until the next spin13:50
ogra_mterry, already spinning ;)13:50
mterryogra_, and there was some question on whether the bugs were the same root cause13:50
ogra_mterry, with an adbd fois for your un lock issue too btw ;)13:50
ogra_*fix13:50
mterryogra_, why don't we just land the unity8 branch?13:50
asacmterry: nice one13:51
mterryogra_, that's been approved for like a week13:51
asacdavmor2: can you do a joint tesating of 015 and 016?13:51
asacdavmor2: seems they going in together will fix the SIM PIN problem13:51
asacdavmor2: and that will then clear the path for location landing13:51
asacthanks!13:51
Mirvboiko: yes, but please ask someone with ppa rights to trigger the rebuilds in there directly13:51
asacjibel: ^13:51
Mirv13:51
davmor2asac: right okay so I'll actually need 016 to finish building then I can13:52
asacdavmor2: wait ... finish?13:52
ogra_mterry, it hasnt been approved13:52
asacdavmor2: its just dashboard brokenness13:52
asacdavmor2: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-016/+packages13:52
ogra_mterry, i just commented on it a few mins ago13:52
asacthey are buitl!!13:52
boikoMirv: ah because the sync: thing is broken already, right?13:52
asacMirv: ^ seems the dashboard didnt pick up that we directly uplaoded13:52
asacMirv: ignore... seems it did13:52
asacdavmor2: so all seems ready13:52
Mirvcyphermox: hmm, maybe some publishing went wrong because of the cu2d code refactoring13:53
ogra_mterry, seems it was merged with a giant other change that isnt 100% ready13:53
davmor2asac: ah package built now yeap no worries13:53
cyphermoxMirv: should I just do the copy?13:53
Mirvboiko: yes, the sync is no more there13:53
boikoMirv: ok, got it, thanks13:54
asacmterry: Saviq: maybe we cna cherry land this input fix?13:54
Mirvasac: regarding blockers, the big qtmir/unity8 landing is still being prepared by Saviq. mediaplayer-app blocker fix is approved to land.13:54
asacanyway, will not micro manage those :) ... lets hope we get the input landed13:54
asacMirv: cool. you think qtmir/unity8 is realisitc today/early-tomorrow?13:55
mterryogra_, woah...  someone took it and made lp:~unity-team/unity8/new-adbd which is enormous...13:55
Saviqasac, I replied already13:55
Saviq<Saviq> asac, am testing now13:55
asacah13:55
asacthanks13:55
asacyeah had reconnects here13:55
asacsorry13:55
jibelrsalveti, music doesn't stop when music player is closed, but I think that's an existing bug.13:55
rsalvetijibel: yeah13:56
Saviqmterry, yeah, what we forgot about is the adb change also made it that there's always a password..13:56
Mirvcyphermox: it'd probably need qa signoff so another silo. can you sort it out with robru? I need to flee13:56
mterryogra_, you just went ahead and added an automatic "sudo -u phablet -i"?!  I asked for that and you said no  :-(13:56
cyphermoxthere was already a signoff13:56
cyphermoxrobru:  ^^13:56
mterrySaviq, I thought our autopilot ran with a lightdm mock though?13:56
Mirvare there any other trainguards about before robert in 2h? I can't stay longer than this 10h today alas :(13:57
Saviqmterry, remember what our lightdm mock is these days? ;P13:57
mterrySaviq, no I mean the real mocks, the ones we use for qmluitests and such13:57
Saviqmterry, nope13:57
Saviqmterry, we only did the LD_PRELOAD thing, which doesn't seem to work any more13:58
Saviqmterry, if you can fix it better, feel free13:58
mterrySaviq, well -- depends on whether we feel running autopilot via mocked lightdm is a "real" test or not13:58
mterrySaviq, we'd need LD_PRELOAD and QML_PLUGIN_PATH13:59
mterrySaviq, for just the lightdm plugin13:59
Saviqmterry, yeah, let's go with my approach for now (I used the dbus unlock call)13:59
Saviqmterry, and if we decide we want it different is when we'll have a look at this again13:59
ogra_mterry, i said i wouldnt know if i can get it to work (we tried multipe times before)13:59
ogra_mterry, i got it to work now though14:00
mterryogra_, \o/14:00
ogra_mterry, with a gross gross hack though :)14:00
ogra_but it works at least14:00
mterrySaviq, gotcha, that's fine.  I just had remembered us using the mocks for AP so I didn't even consider having to fix them past the unlock-device script14:00
davmor2asac, Saviq: so it looks like the no keyboard on initial boot is in place still but more important on reboot you get no unity8 dash just a black screen with the loading animation.14:00
Saviqdavmor2, bug #136261914:01
mterryThe keyboard on initial boot bug isn't fixed?  /me scratches head14:01
ubot5bug 1362619 in unity-scopes-api (Ubuntu RTM) "unity8-dash hangs in scopes backend" [Undecided,Confirmed] https://launchpad.net/bugs/136261914:01
Saviqdavmor2, and I don't think the keyboard fix from mterry landed14:01
davmor2mterry: this is before the silo14:01
mterryah14:01
ogra_mterry, "adb shell env" output in auth.log : Sep  8 14:50:32 ubuntu-phablet sudo:  phablet : TTY=pts/38 ; PWD=/home/phablet ; USER=phablet ; COMMAND=/bin/bash -c /bin/bash -cl env14:02
ogra_mterry, like inception ;) shell in shell in sudo ...14:02
mterryogra_, heh14:02
Mirvdbarth: mp approvals... ^14:02
davmor2mterry: need a fresh install system was getting messy and I wanted clean results14:02
Saviqmterry, TBH we shouldn't be using any mocks in ap tests if possible, the lockscreen tests should probably be moved to QML ones anyway14:02
dbarthMirv: yup, spotted :/14:03
mterrySaviq, well in theory I agree, but handling unlocking via system password is tricky.  Not sure the dbus unlock is much cleaner than a mock, but at least it's using real code14:03
asacdavmor2: in silo or in general?14:03
asacdavmor2: i had this problem of no dash loading on krillin this morning14:03
asacbut also a couple days ago14:03
asacrebooting fixed it14:03
davmor2asac: rebooting indeed does fix it14:04
mterrySaviq, it'd be nice if there was a clean way for the unity8 AP test to be passed the system password14:04
mterry*phablet password14:04
asacdavmor2: right. but i saw it for a week or so from time to time on krilin... never on n414:04
Saviqmterry, well, we should have integration tests that actually test setting/unsetting the password, locking/unlocking the shell, but I don't think unlocking with pin/pass should happen every time...14:04
asaci mean.. getting an animation like starting an app forever14:04
* asac thought a few times it would be great if he could kill the dash just like an app :)14:05
asacthrough the right edge animnation14:05
mterrySaviq, well yeah -- ideally we could set / unset the password via the AP test  :)14:05
Saviqmterry, which would not be a unity8 ap test, but a high-level platform one14:05
Saviqmterry, but yeah, with the adb change right now there's no way to test unsetting the pass, as that will lock you out of the phone ;)14:06
mterrySaviq, eh, only high level because of the password thing.  Everything else would likely be local to unity8.  But sure, however we get it done14:06
ogra_asac, "restart unity8-dash" in the terminal app works fine14:06
Saviqmterry, unless you waited for the adb connection again, as the test really happens on the phone still14:06
ogra_asac, generally it shouldnt hang or crash indeed :)14:06
asacogra_: yeah, but its tempting to just shoot it in teh right edge aninmation if it doesnt accept input anymore :)14:06
asacogra_: hehe... true14:06
asacbut then most apps shouldnt need to be killed either14:06
asacbut we allow it anyways14:07
asaclike phone, mesasging etc.14:07
ogra_they hog memory14:07
ogra_even if they dont run14:07
asacnot with lifecycle14:07
ogra_sure they do14:07
asaclifecycle with swap them out if there is not enough mem14:07
ogra_a sigstopped app wont free its ram14:07
asacit first is sigstopped14:07
ogra_only once it gets OOM killed it will14:07
asacthen it gets serialized and killed14:07
asacright14:07
asacso in general there shouldnt be a need to kill them14:08
asaconly to fix dysfunctional apps14:08
asacthats hte only valid use case we have in theory forl killing imo14:08
ogra_not really14:08
asacwhy not really?14:08
ogra_i wouldnt want to have to scroll through the list of apps i have started since i got the new phone14:08
asacogra_: ok thats a user experiennce challenge then14:09
asaccould be sorted by least recently used14:09
asachehe14:09
ogra_if you make them unremovable in the edge swipe things will pile up and the edge switpe will become less useful14:09
asackind of true i guess14:09
asacthink maybe after not using them for like 2 days they could get hidden14:09
asacor only last 10 apps shown14:10
asachehe14:10
ogra_that might actually work14:10
ogra_until that arm64 phone with 4GB ram comes out and you want to have 20 to stay open :)14:11
asacbut guess the "kill because app is buggy" isstill a valid use case especially since we have random 3rd party apps in store14:11
ogra_yeah14:11
asacbut that use case also exist for dash :)14:11
asachehe14:11
ogra_which it shouldnt though14:11
ogra_system stuff needs to be rock solid14:11
asacwell it shouldnt for any of our key apps14:11
asaclike phone and messaing14:11
ogra_and shell :)14:12
asacterminal?14:12
ogra_lol14:12
asacah the shell14:12
ogra_well, that needs more love first14:12
asacindicators and friends14:12
ogra_right14:12
ogra_not terminal-app14:12
ogra_currently close to unusable on krillin ...14:12
* ogra_ goes back to hack on pam before the standup 14:13
* asac goes coffee14:14
imgbot=== trainguards: IMAGE 233 DONE (finished: 20140908 14:15) ===14:15
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/233.changes ===14:15
ogra_whee, exciting ...14:15
cyphermoxrhuddie: hey14:16
cyphermoxrhuddie: do you agree we can close https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1273629 ?14:16
ubot5Ubuntu bug 1273629 in bluez (Ubuntu) "HSP fails on Ubuntu Touch [Bluetooth headset does not work]" [Critical,Fix committed]14:16
rhuddiecyphermox, Hi, yes, I think that one can be closed14:17
cyphermoxrhuddie: thanks :)14:17
brendandseb128, mterry - do we know when/how systemd-shim is going to land in RTM?14:17
rhuddiecyphermox, I also checked on the Vivaldi speaker and updated that bug report14:18
cyphermoxrhuddie: for the Altavoz Vivaldi speaker, would you be able to gather some extra information for me, assuming you have it14:18
seb128brendand, I don't14:18
davmor2brendand: looking at it now14:18
cyphermoxahah, great minds think alike!14:18
mterrybrendand, ogra_ and asac were looking at it above.  I think very soon14:18
rhuddiecyphermox, sure thing14:18
cyphermoxlet me refresh, I didn't see your update I think14:18
=== om26er is now known as om26er|doc
rhuddiecyphermox, no prob. Let me know if you need any more info on it. I have a big box of devices sat here :)14:19
cyphermoxrhuddie: indeed I missed the update, that's all; but the hcitool output doesn't contain what I expect14:19
cyphermoxrhuddie: I'll get you a package to test14:20
rhuddiecyphermox, thanks14:20
asacbrendand: davmor2 is testing that together with the systemd-shim14:22
asacer system-settings silo 015 ans 01614:22
asacmterry: seb128: are landing the wizard crash in utopic already? i think we will soon need to pull that into rtm14:24
asacguess the 015 silo will actually have the same crash14:24
seb128asac, not sure if kenvandine plans a landing today, we can probably do one14:24
asackenvandine: can you do that?14:24
asacat best now :)... we need that to land a crash free system-settings in rtm14:25
asacfor HERE and all the good fixes that are in ss14:25
kenvandineasac, been trying... it failed qa verification again...14:26
kenvandinethe biggest issue is the wizard crashing, along with the location service14:26
kenvandinewhich i suspect was introduced with the HERE stuff14:26
kenvandinethe wizard crashing didn't seem obvious to me, it looks like the wizard finishes... but it leaves crash files14:27
asackenvandine: wait :)14:27
kenvandinefor the location service and ubuntu-system-settings-wizard14:27
asackenvandine: talking about utopic14:27
asackenvandine: the rtm landing we have now understood... it was missing shim14:27
kenvandineoh... the HERE stuff is in utopic-proposed14:27
asacand also we need this crash there14:27
seb128kenvandine, https://code.launchpad.net/~mterry/ubuntu-system-settings/wizard-crash/+merge/23358914:27
seb128kenvandine, that should fix the crash in the wizard14:27
kenvandinegreat14:27
asacright14:27
kenvandineso we need to land that :)14:27
asacso once we have that in we can also add that to system-settings14:27
asacand HERE silo14:27
kenvandineseb128, brendand also said he had trouble with the cellular panel14:28
asackenvandine: exactly :)14:28
kenvandinewhich didn't change... and it works fine for me :)14:28
seb128kenvandine, I've 2 trivial changes waiting review if you want to include that as well14:28
asackenvandine: isnt that the SIM PIN problem?14:28
asachats the systemd-shim that is in 01614:28
kenvandineasac, yes... but it worked for me :)14:28
seb128kenvandine, there is a SIM unlock issues, but mterry thinks it's the systemd issue as asac just said14:28
asackenvandine: it worked on utopic because systemd-shim is in there14:28
kenvandineok... i thought that too14:28
asacbut not in rtm14:28
kenvandinebut i tried it on rtm 30 minutes after brendand failed it and it all worked14:28
asacmterry confirmed that the systemd-shim fixes taht in rtm (which bounced you rlanding)14:29
kenvandinewoot14:29
seb128;-)14:29
asackenvandine: do you have a locked SIM?14:29
asacyou need that to reproduce14:29
brendandkenvandine, did you try on mako or krillin?14:29
seb128that bug is random one14:29
kenvandineasac, no... but i know the pin for my ATT sim14:29
seb128it's not consistent14:29
kenvandineand can unlock/lock/changepin14:29
kenvandinebrendand, both...14:29
asacif its not locked it isnt showing the problem according to bug14:29
asaclocked aka you need to enter sim pin to make it work14:29
kenvandineasac, but what if i lock it?14:30
kenvandinethat worked14:30
asackenvandine: not sure what that means14:30
asacyou need to have it in locked state14:30
asacthen wipe user data14:30
kenvandineasac, in settings, you can lock the pin14:30
asacand boot14:30
kenvandineon the sim14:30
mterrykenvandine, and you have to be on krillin I believe14:30
asacmaybe that too14:30
* asac doesnt know14:30
asacanyway, we think we have that under control. just need the crash fix in utopic14:30
asacso we can clear it all into rtm14:30
kenvandinecool14:31
brendandkenvandine, i saw other problems in the cellular panel, but the silo is in davmor2's hands now so i trust that if what i saw was a real bug he'll find it14:31
kenvandinei desparately want to land rtm :)14:31
brendandkenvandine, so if davmor2 passes it you're ok14:31
asackenvandine: thanks. let us know when its in utopic later today so w can finish the rest14:31
kenvandinebrendand, weird... all the cellular panel features worked for me... and the landing to rtm doesn't include any changes to cellular14:31
kenvandineasac, will do14:31
balloonsfginther, any thoughts on what might be wrong with this job? s-jenkins.ubuntu-ci:8080/job/ubuntu-calculator-app-autolanding/35/ I thought it was something within jenkins, but s-jenkins.ubuntu-ci:8080/job/ubuntu-calculator-app-autolanding/34 seemed to run fine . . .14:33
fgintherballoons, I'll be able to take a peek in about an hour14:34
balloonsty14:37
kenvandinewhoops14:38
kenvandineasac, seb128: no available silos :)14:38
kenvandinethostr_, pmcgowan: can we free silo 15 (apneditor)?  It's not ready to land and I need a silo to land the settings fix that we hope will clear the way for an rtm landing14:42
pmcgowankenvandine, i vote yes, Wellark is working with mpt on agreeing design14:42
kenvandineit's outdated anyway :)14:43
asacMirv: ^^ can you clear silo if wellark is fine?14:55
=== plars changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: plars | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
pete-woodstrainguards: hi guys. could someone re-trigger the builds in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-017/+packages15:01
pete-woodsthe broken dependency seems to have made it into distro now :)15:01
cjwatsonpete-woods: done15:07
cyphermoxasac: I thought Mirv had left, I can clear silos if confirm the silo?15:13
cjwatsonjibel: could ubuntu-rtm/landing-003 (spreadsheet line 46) make its way onto the QA trello board, please?  the important change is re-enabling signature checking - so making sure that ordinary app installation from the store still works, and also that sideloading apps onto a device from the SDK still works (which broke the last time we did this, and we believe we've fixed).  note that the latter requires the qtcreator-plugin-ubuntu ...15:17
cjwatson... from ubuntu/landing-003, which is landing in utopic at the moment15:17
cjwatsonjibel: this is moderately urgent as (a) it's one of the current blockers in landing team mails, (b) ubuntu/landing-003 was published a little prematurely and these two were meant to be in sync15:18
Wellarkpmcgowan, kenvandine, asac ?15:18
kenvandineWellark, i freed silo 15 with the apneditor15:22
pete-woodscjwatson: thanks!15:23
Wellarkkenvandine: ack.15:24
Wellarkkenvandine: I will ping thostr_ when I've done the fixes from the design review.15:24
jibelcjwatson, done15:24
kenvandineWellark, thx15:24
Wellarkkenvandine: need to revert the OptionSelectors :(15:24
Wellarkthey look way better than the ListItem.ItemSelector15:24
cjwatsonjibel: thanks15:25
Wellarkbut it's better to suck consistently ;)15:25
john-mcaleelydavmor2, how was my luck at a QA pass? will we be discussing results when the landing team meet in half an hour?15:25
kenvandineWellark, consistency is best :)15:25
davmor2john-mcaleely: having issue fighting sim pin locks on rtm currently15:26
kenvandineWellark, i wish the OptionSelector had a better style15:26
john-mcaleelydavmor2, ok, thanks :-)15:26
kenvandinedavmor2, oh?  in system-settings?15:26
kenvandineoh right.. we think that was because of the systemd-shim problem15:27
davmor2kenvandine: Yeah I have the systemd-shim installed I think let me double check that and try again15:27
davmor2kenvandine: the silo with the fix in I should say15:27
kenvandinedavmor2, oh... rtm silo 1 is interesting15:29
kenvandinedavmor2, looks like a fix for a regression in ofono that prevented entering pin15:30
davmor2kenvandine: the other issue is that sim unlock constantly tells you there are 3 attapts left15:31
kenvandinedavmor2, is that in system-settings?15:31
kenvandineor the shell?15:31
davmor2kenvandine: everywhere15:31
kenvandineok, that could be related to the fix in silo 115:31
davmor2kenvandine: leading me to lock my phone15:31
kenvandinewhich i never even saw that regression15:32
davmor2sim even15:32
kenvandineugh15:32
bzoltanasac: are you around?15:34
bzoltanasac: I wonder if it would be possible to set up group highlights for this channel. For example we define and "sdk tools dependency" group with the "click, android tools, emulator, phablet-tools, QtCreator" and the CI train would ping the sdk-tools-deps when any of the dependencies put in a silo for landing.15:37
bzoltanpmcgowan:  ^15:37
fgintherballoons, I'm a little confused by that one too15:41
balloonsfginther, so the merge redoes the tests, but afaict the autolanding never gets past setup right?15:42
cjwatsonbzoltan: hm, does your IRC client not have suitable highlighting facilities?15:42
fgintherballoons, right, the setup failed during phablet-config writable-image15:43
cjwatson/hilight -channels #ubuntu-ci-eng -regexp Silos:.*click15:43
cjwatsonor whatever15:43
fgintherballoons, which it had successfully executed a few commands earlier15:43
fgintherand is working in the next 2 test runs15:43
bzoltancjwatson: I have :) But I would love to see something formal in place. So to make sure that certain information reaches the defined parties.15:43
cjwatsonI dunno, I'm a big fan of decentralisation for this kind of thing :)15:43
bzoltancjwatson:  as the dude who's butt is kicked when something goes wrong with the SDK tools I do love centralization  :D15:44
balloonsfginther, so is it possible something in the merge is causing it? Seemingly the answer is no, but since they work on other mp's...15:44
bzoltancjwatson:  My dream would be actually to have an SDK signature flag in the CI sheet for all projects what can cause regression in the SDK. The same way I could imagine that all projects with dependencies would benefit from such policy.15:46
fgintherballoons, no no no, this is during the generic setup of the device. Completely unrelated to the MP. It's possible there are some lingering setup and timing issues that need to be resolved after the adb user change15:46
balloonsfginther, it's just odd that it worked for the others. That's actually the third try for that mp15:47
balloonsautolanding 32 and 33 are also autoland attempts15:47
cjwatsonbzoltan: I think what I'm saying is that you're in a better place to know what you need to pay attention to from your experience, and it seems like an odd choice to want to put that information somewhere where it's harder for you to update15:47
cjwatsonregressions> this is what autopkgtests are meant to be for :)15:48
bzoltancjwatson: what I am thinking about is an information pushing instead of pulling.15:48
cjwatsonthey're exactly meant as a way to assert things about the behaviour of your dependencies15:48
bzoltancjwatson: can autopkgtests test emulator creation, deployment, chroot creating and usage, app launcher features from the QtC?15:49
cjwatsonall this business with highlighting people to do manual testing isn't very scalable15:49
cjwatsonit's all software, I don't see why not15:49
cjwatson(though nested VMs may become an issue)15:50
bzoltancjwatson: yeps... exactly15:50
cjwatsonall I'm saying is that figuring out how to ask more people to do manual testing on things isn't a very forward-looking approach15:50
bzoltancjwatson: With that one I agree. I am not suggesting more manual tests.15:51
bzoltancjwatson: I am thinking about how to make sure that projects get informed about the upcoming changes of their dependencies.15:52
cjwatsonbzoltan: might be something to ask the CI Airline people about, rather than bodging more stuff into the spreadsheet15:53
cjwatsonsome kind of subscription approach15:53
bzoltancjwatson:  might sound childish, but in my past it proved to be working. Like making mandatory to walk to the owner of a project what depends on your project and have a handshake. Not more..15:53
balloonsfginther, so I guess I can just leave it in your hands then and you can get it passing?15:54
bzoltancjwatson: I know the CI sheet is heavy already.15:54
fgintherballoons, yes, there is one thing that I can tweak and then see how it goes after that. Am I ok to re-approve that MP?15:55
balloonsfginther, yes15:55
cjwatsonbzoltan: I suspect those were smaller projects than Ubuntu though :)15:55
bzoltancjwatson: That is how Maemo/Meego used to work. That was not very small :)15:56
cjwatsonbzoltan: considerably smaller than Ubuntu15:56
cjwatsoncertainly in terms of the platform's dependency graph15:57
bzoltancjwatson: from that point, no doubt15:57
ogra_meego cloud, meego server and meego desktop were surely rare occurences ;)15:57
asacbzoltan: i would suggest to wait till sil is back and see if there are aliases to also include in the pings15:57
bzoltancjwatson:  the point is that making dependency lines to meet and shake hands at agreed milestones is something what i have seen working and it was improving stability15:58
bzoltanogra_: by then Qt was an internal project :)15:59
cjwatsonbzoltan: yeah, I'm just familiar with the dependency graphs above some of the things I maintain, and I fear having to talk to 100 people any time I change anything :P15:59
cjwatsonso anything like that probably needs to be non-blocking most of the time16:00
bzoltancjwatson: that is why I am suggesting an automatic step, if that is possible. If not, then just ignore me :) I am daydreaming too often16:01
cjwatsonbzoltan: right, that's why I'm suggesting talking to the airline folks as they're better-placed to do things that aren't horrible ongoing  :)bodges16:02
cjwatsonerr rearrange the end of that to make sense16:02
bzoltancjwatson: Yes, I will do so. Thanks for your input.16:03
kenvandineasac, i tested utopic silo 15 on both utopic-proposed and on my krillin with rtm + silo 1 and silo 16 (ofono and shim)16:06
kenvandineasac, no more crash in the wizard... but there is still a crash file left by _usr_bin_ubuntu-location-serviced16:07
kenvandinesim lock/unlock also worked in settings, and i verified i could unlock a locked sim  from the shell after reboot16:07
=== Ursinha is now known as Ursinha-afk
asackenvandine: locationserviced is not a regression afaik16:14
kenvandineok16:14
kenvandinegood16:14
asacso its fine and we can tackle it after imo16:14
popeywho maintains the 7digital scope?16:14
kenvandineasac, so syncing the landing will also pull in the location settings which is line 2016:16
kenvandineasac, which requires a manual step for trust-store for testing16:16
kenvandineasac, should i change rtm silo 15 from a utopic sync to sync from the current utopic landing?16:16
kenvandinethe end result will be the same16:17
asacdavmor2: ^^ fine with thsi?16:17
kenvandinei'll copy dbarth's comment over to the other line with instructions to manually start that16:17
kenvandineor rather a link to the bug it works around :)16:18
asacdavmor2: he is talking about getting system-settings that has the ziward crash into the silo 15 for one sign off16:18
asacdavmor2: alternatively we could first clear that 015 silo with the crash whitelisted given that we have it in the pipe and then just land that fix after16:18
kenvandinedavmor2, since the location access stuff landed already in utopic, it'll pull that in regardless16:18
asackenvandine: wait for davmor2 ... he is testing those silos right now16:18
davmor2asac: let me have a quick think about it while I test shouldn't take too long.16:19
asacdavmor2: thanks16:19
asackenvandine: just continue on your utopic silo for now :)16:19
asace.g. get that fixed, landed etc.16:19
kenvandinei like option 2 :)16:19
asacdavmor will ome back16:19
kenvandineasac, landed already16:19
kenvandinejust not merged back16:19
sergiusenspopey: someone in thostr_'s team, pete-woods would be a wild guess16:19
popeysergiusens: ta16:20
kenvandinedavmor2, note i tested the utopic silo on krillin rtm and it was all good for me16:20
Mirvback to check, is there anything urgent? robert should be here as soon as his morning meeting ends.16:21
pete-woodspopey: you need to speak to facundobatista I think16:21
popeypete-woods: ok16:21
Mirvrobru: note the cyphermox's missing mtp package, it needs to be hunted. possibly a case of "publish returns success but does not actually publish anything"? I've gotten into habit of double checking rtm publishings on what they I actually did16:21
robruMirv: yep, there absolutely was (and may still be) a bug where rtm publishings report success without actually doing anything.16:24
robrucyphermox: ^16:24
Mirvrobru: and that ^ a watch_only build seems to fail after sync build, the configuration seems empty. I've resolved such cases by adding the package names manually instead of using sync:N, after the build, reconfiguring, and building with watch_only after that.16:24
robruMirv: yep, the sync:N logic isn't implemented very well. unfortunately I'm drowning in fixing up basic code quality of citrain, it's hard for me to even look at large bugs like that.16:25
Mirvso basically nothing trainguards can't workaround, but the workarounds need to be applied every time16:25
Mirvrobru: yes, I don't think it should be tackled now, but sync works for syncing the sources, then manually reconfiguring + building with watch_only should work for now.16:26
Mirvfor users of the train it should all be transparent, we just have some more clicking to do than optimal :)16:26
robruMirv: "requiring more clicking than is optimal" is the core ethos of citrain.16:30
balloonsogra_, if you don't mind: https://code.launchpad.net/~nskaggs/phablet-tools/remove-python2-support/+merge/233754. I fixed the bug nik90_ mentioned on g+ the other day by just removing python216:32
tedgrobru, In silo 11 I think I fixed the approval, but the dashboard is still showing an issue.16:38
tedgrobru, Is that a manual thing?16:38
cjwatsontedg: the dashboard is showing the result of the last publish attempt16:38
tedgAh, okay.16:39
robrutedg: yeah, the MP looks good, just need to run the publish job again. I'm on it16:39
tedgrobru, Can you please publish silo 11?16:39
tedgThanks!16:39
ogra_balloons, i assume we dont have anyone running these tests on older images at home ?16:39
davmor2asac, kenvandine: so I don't think that the wizard crash is the last of the blockers.  So let me try and get settings, sim unlock and location landed, if it is just the wizard crash we can whitelist, if it isn't there will still be 3 free silos in about 20minutes that you can add the new fix too, hope that makes sense16:40
robrucjwatson: ah, that silo has a NEW source package, can you review it? or should I just publish it to the real NEW queue? ;-)16:40
cjwatsonrobru: NEW source?  easier for us to review that in the real queue16:40
cjwatsonit's only new binaries that need pre-review16:40
kenvandinedavmor2, ok, do you know what the other blockers are?16:40
balloonsogra_, I think that is a very fair assessment. Some of the testsuites even require python3 now16:40
ogra_balloons, ACK then ... not sure when i can land it though, i'm a bit swamped in developer mode fixes16:41
asacdavmor2: cool. yeah, lets get the big pile pushed and then get the crash fix in right after16:41
asacdavmor2: the crash fix we can put into the HERE silo then16:41
asacso we can land those together16:41
robrucjwatson: ok i'll publish it for real then, thanks16:41
asacwe could already built it there16:41
ogra_sergiusens, second pair of eyes for: https://code.launchpad.net/~nskaggs/phablet-tools/remove-python2-support/+merge/233754 ?16:41
sergiusensogra_: why not16:43
robrucjwatson: do you remember if there's some kind of whitelist before citrain is able to sync a NEW source into utopic? I remember it used to be that way on the old daily_release system (pre-citrain), but I can't remember if it's still like that. anyway let me know if you don't see indicator-datetime show up in NEW shortly.16:43
davmor2asac, kenvandine: oh sure if you can build it in the here silo go for it I thought it needed targeting against 15 which seems to be fixing stuff already so didn't want that having to be re-tested16:44
ogra_sergiusens, dunno, you tell me :)16:44
cjwatsonrobru: not afaik, I think the only reason this whole preNEW idea exists is because otherwise it used to block a whole stack16:44
sergiusensogra_: already added needs fixing ;-)16:44
kenvandinedavmor2, i think asac meant if we can, land silo 1516:44
ogra_oh16:44
kenvandinethen we'll push the crash fix in the HERE silo16:44
asackenvandine: right. think you can already push the fix into the HERE silo16:45
robruMirv: any reason you didn't get packaging ack for silo 2? I see you published it but it's just sitting there requiring ACK16:45
robruseems a simple diff16:45
asacso its ready for davmor to get on right after signing off the current silo thatjust has teh wizard16:45
asacif he doesnt trust us he could also take a sneak preview then :)16:45
cjwatsonrobru: IMO preNEWing of source packages is an obsolete concept; just having code review of the packaging should be good enough16:45
robrucjwatson: ahh makes sense, yeah I'm glad we don't have stacks anymore ;-)16:45
cjwatsonrobru: indicator-display in https://launchpad.net/ubuntu/utopic/+queue now16:46
robrucjwatson: anyway I looked over the packaging, seems sane to me16:46
kenvandineasac, how do i add it to the HERE silo?  that's a sync:1016:46
robrucjwatson: thanks!16:46
kenvandineasac, can i add an additional sync?16:46
asacerr16:46
asacrobru: ^^ can you help kenvandine ?16:46
robrukenvandine: no. no you can't do that.16:46
asacrobru: he wants to sync from archive now i think16:46
asacinto the HERE silo16:46
asacI THINK16:46
asac:)16:46
kenvandinewell... i was thinking from utopic silo 1516:46
kenvandineit's in utopic-proposed16:47
kenvandinenot release16:47
asackenvandine: isnt that in the archive now?16:47
asacright16:47
asacbut will soon be16:47
asacrobru: let us know what options we have :)16:47
kenvandinesettings takes longer than most to publish16:47
asacor rather let kenvandine know16:47
robrukenvandine: you can't have multiple sync:s, but you can list additional source packages and copy-package them directly. and then reconfigure the silo and WATCH_ONLY build...16:47
kenvandinei think the autopkgtests16:47
robruqueuebot: yay! ;-)16:48
kenvandinerobru, oh... i could do a copy package then :)16:48
robrukenvandine: copy-package ALL THE THINGS16:48
bzoltan1robru: I am still testing the UITK in silo10 for Ubuntu. The QtCreator MRs have no Silo. Do you think it would be OK to use the silo10 for QtCreator plugins too?16:49
bzoltan1robru:  because I see that it is hard to get silo today :)16:49
robrubzoltan1: yes there are currently none available. feel free to merge your requests and then I can reconfig the silo for you.16:50
kenvandinerobru, i don't have upload rights to the ppa16:53
kenvandinecopy-package --from=~ci-train-ppa-service/ubuntu/landing-015 --suite=utopic --to=~ci-train-ppa-service/ubuntu-rtm/landing-004 --to-suite=14.09 -b ubuntu-system-settings16:53
kenvandinerobru, ^^16:53
asackenvandine: are u core-dev?16:54
kenvandineyes16:54
kenvandinebut i guess that isn't good enough for the ppa16:54
asaci can add you to the uploaders for that ppa then16:54
kenvandineasac, cool16:54
asacwithout any alignement16:54
asacone sec16:54
asacdone16:54
asackenvandine: just dont misuse :)16:55
asacyou can now16:55
kenvandineok, copied :)16:55
=== Ursinha-afk is now known as Ursinha
cjwatsonI think it would be possible to give ubuntu-core-dev an upload ACL on the ci-train-ppa-service PPAs without making them a member of the team and causing everyone to get loads of build failure mails16:57
cjwatsonthough it would have to be done individually for each PPA16:57
robrucjwatson: why is everybody afraid of the build failure mailvalanche? don't people have mail filters? ;-)16:59
cjwatsonit's rude to impose that on a big team16:59
=== boiko_ is now known as boiko
=== plars changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
tedgrobru, So desrt said that he should have the systemd-shim patch we need for cgroups by tomorrow morning, which makes me want to try the UAL cgroups landing tomorrow afternoon.17:05
tedgrobru, How does that work from the "expected amount of chaos" perspective?17:05
tedgrobru, Are there are big landings you're expecting?17:06
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
asac19:16 < davmor2> asac, ogra_, robru: also I'm happy with 001, 015 and 016 combination, but they will all need to land in the same image or they will break stuff between them.17:20
asacrobru: ^^17:20
asacthanks!17:20
asacall push, then image, then we go for HERE silo :)17:20
ogra_asac, we're talking about rtm silos, right ?17:24
asacyeah17:25
asacrobru: ^^17:25
asacsee above17:25
asac:)17:25
asacogra_: dont you know how to publish?17:25
ogra_asac, i sure do17:25
asacok ... well i will not suggest anything that would not be normal as i am sure then something bad will happedn :)17:26
ogra_asac, 001 cant land17:26
asacwhy?17:26
ogra_according to the dashboard it hasnt been signed off or even tested17:26
ogra_http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=17:27
asacdavmor2: davmor posted above that he signed it off17:27
asacerr17:27
asacogra_: ^^17:27
ogra_asac, i think awe_ just said it misses top approbval in one MP17:27
bzoltan1robru: the silo10 is ready for reconf17:27
ogra_asac, which means it will block17:27
awe_ogra_, asac, it's *not* ready17:27
asacrsalveti: can you check out the MP for 00117:27
awe_which is why it's not top-approved17:27
ogra_awe_, thanks ... thought so17:27
awe_regressions found and bugs filed on Fri, I will update the MP shortly17:28
rsalvetiasac: check #phablet :-)17:28
asack17:28
asacshorly meaning?17:28
asac:)17:28
asachehe17:28
* asac will go for dinner and check back later17:28
asacthis is a key part to get system settings in and also HERE17:28
asacetc.17:28
asacmany thing are depending on this17:29
asacso no pressure17:29
asachehe17:29
asacrsalveti: ^17:29
asaccu17:29
awe_asac, sure...but we can't land things that are obviously broken17:29
* asac checks out for 2h17:29
asacjust make it so that its not more broken than the current situation :)17:29
asacso no regressions17:29
asachehe17:29
asacanyway 2h gone17:30
asacwill check then17:30
asacwe could go and just do the fix enter pin part17:30
ogra_we could just fix everything and land all silos a day before release, sure17:31
asacright, but i am suggestint the opposite ... just cherry pick the sim enter one if the other part is the problem17:31
asacsplit up landings17:31
asachehe17:31
asacanyway, think its under control for the next couple hours17:32
ogra_asac, sure17:32
Mirvrobru: no, just ran out of time17:32
ogra_plars, looks like we're missing a device for the 233 utopic-proposed tests ?17:32
ogra_wow, filemanager is as bad in utopic as it is in rtm17:33
ogra_and we seem to have the same 9 failures in unity817:33
ogra_in both images17:33
Mirvwhile here, I'll try fixing boiko's landing before going towards sleep, now that the media landing happened.17:35
boikoMirv: please let me know if you need anything from my side17:37
Mirvboiko: looking good, it should be ready for testing once the build job reports so (it's running watch_only build on the triggered rebuilds)17:39
Mirvand amd64 already succeeded17:39
boikonice!17:40
* boiko flashes the phone with the rtm image again for testing17:40
plarsogra_: good catch! I restarted one earlier but there's a 3rd one that needed it. It's running now17:42
plarsogra_: and the security fix seems to work locally, merging it now17:42
plarsjdstrand: ^17:42
ogra_plars, yay17:43
ogra_overall that looks really good !17:43
jdstrandnice, thanks!17:43
ogra_these security issues once again show how moot the percentages are :P17:45
robrutedg: i dunno, it's all chaos, as long as we build images in between the big ones I'm happy17:45
balloonssergiusens, replied back. I would rather keep the changes separate as phablet-click-test-setup has some other issues as well and may take more time to land17:45
robrubzoltan: sorry for the delay, was having breakfast. done: https://ci-train.ubuntu.com/job/prepare-silo/1866/console17:46
sergiusensballoons: as this change requires a ci run of every test I don't think it will be fast enough anyways; I'd rather do the full run once only.17:47
tedgrobru, K, do you know when other big ones are?17:47
sergiusensballoons: unless you take care of the actual landing; then it's fine17:47
balloonssergiusens, fair enough, fair enough.. I'll drop the second MP and roll the changes into the one that is open17:47
robrutedg: sorry no, just published rtm1 and rtm15, will build an image once they land17:49
ogra_robru, 001 was definitely not ready17:49
ogra_and according to davmor2 there wwere three silos that need to go together17:50
ogra_(001 being one of them=17:50
ogra_)17:50
cyphermoxrobru: Mirv: so what's your suggested course of action for mtp; should I copy it in rtm, should something else be done?17:50
robruogra_: yeah, on davmor2's approval I published them...17:50
ogra_robru, if you scroll 50 lines up you see the conversation about this17:50
robruogra_: ah sorry I just read the ping itself not the whole scrollback.17:51
ogra_robru, that was blocked by the owner of silo 00117:51
ogra_and the MP sholdnt be landeable at all17:51
ogra_it was not top approved17:51
ogra_how could you publish that ?17:51
robruogra_: yeah, how could I publish that?? maybe because rtm syncs don't deal with MPs, they do source package copies from other silos and/or archives.17:52
ralsina_robru: can I get a silo for row 67? I see you're running low, so I have no problem with "not today" :-)17:52
robruogra_: seriously rtm1 doesn't have an MP.17:52
ogra_ouch, right17:52
ogra_robru, well, it has a corresponding utopic silo thats blocked17:52
robruogra_: ok, well, fix it in utopic and we'll re-sync it to RTM I guess.17:53
robruawesome.17:53
bzoltanrobru:  thank you17:53
robrubzoltan: you're welcome!17:53
robruralsina_: eh, can you be fast?17:53
ralsina_robru: well, it has to go to rtm but I can get the utopic stuff done in 45' or so17:53
ogra_robru, except that everyghing will be broken now in rtm til that is fixed (by tomorrow i was just toold)17:53
robruralsina_: ok cool17:53
robruogra_: well, here we are.17:53
ogra_yeah, bad ...17:54
robruogra_: perhaps we'll be saved by that bug that makes rtm silos report publication without actually having been published properly.17:55
tedgrobru, Oh, I think I just merged and cleaned 11 before the rtm silo was made.17:56
tedgrobru, Did I screw that up?17:56
robrutedg: yes but no worries, we can just sync from utopic rather than the silo, no worries.17:56
=== Ursinha is now known as Ursinha-afk
charlesgrumble17:57
tedgrobru, Okay, so I just need to put the package name there?17:57
robrutedg: on the rtm row, additional sources column should read 'sync:ubuntu,utopic your package names here'17:57
charlestedg, commit message added17:57
robruralsina_: you got 12 ^17:57
ralsina_robru: thx!17:57
robruralsina_: you're welcome!17:57
tedgrobru, K, updated line 5117:58
tedgrobru, Can I get silo 11 for line 53 ?17:58
tedgIt should make everyone else build faster :-)17:58
robrutedg: sure, once it finishes freeing (sloooow)17:59
robruit's a race, let's see if silo 6 or 11 frees faster ;-)17:59
tedgHeh, go!18:00
awe_robru, can you help me clear up some confusion re: the ofono silos?  Apparently I've been told that silo-001 has landed, although the "Testing pass? Image #" hadn't been recorded?18:01
tedgcharles, Thanks, think we're good.18:01
robruawe_: right, so what happened was that davmor2 said it was tested, so I published it18:01
awe_robru, right... we need to figure out some way for there to be coordination between QA and the lander18:02
awe_I will keep this in mind for the next landing18:02
robruawe_: well somehow davmor2 got it in his head that it was his job to be testing silo 1. he probably got that idea by reading from the dashboard that silo 1 was tested and ready for QA signoff (or maybe somebody told him that, I dunno). anyway there are systems in place for communicating this stuff, we just need to use them.18:03
kenvandinerobru, well he got into a situation where he had sim locking problems, because of the shim landing...18:04
kenvandineand added silo 1 to try to get out of it, because of the description on the silo18:04
kenvandinerobru, he wasn't intending to test it when he did... but he hit a problem that seemed related18:05
robrugreyback: Saviq: please approve your MPs https://ci-train.ubuntu.com/job/ubuntu-landing-019-2-publish/11/console18:05
Saviqrobru, oop18:05
Saviqkgunn, can you https://code.launchpad.net/~mir-team/qtmir/gles-sync/+merge/23365018:06
greybackSaviq: done18:06
Saviqgreyback, and I can't reproduce your issue with the sudo pwd :/18:06
greybackSaviq: ok I'll approve it as it unblocks stuff18:06
Saviqgreyback, yeah, it's definitely better than before...18:07
greybackslow internet is slow18:07
Saviqrobru, done, sorries18:07
Saviqkgunn, unping18:07
greybackSaviq: robru: ok all should be approved18:07
awe_robru, can we just publish silo-018, and then merge?  We'll handle the reported regressions in a subsequent landing.18:10
robruawe_: sounds good to me!18:11
ogra_awe_, robru, it would probably also be nice to have a new blocker bug for this and have it mentioned in the landing mail18:11
ogra_since that image we're trying to build is planned to go to the customer for QA18:12
robrutedg: ok you got silo 618:13
awe_ogra_, have we promoted an rtm image yet?18:13
tedgrobru, Great, thanks!18:13
robrutedg: you're welcome!18:14
ogra_awe_, no, but the landing robru just did closes one of the blocker bugs18:14
awe_ogra_, rtm14 tag added to the new bug18:14
robruogra_: oh, I fixed something? yyaaaaaaayyyyy!18:14
ogra_awe_, so it would be promoted without having a new one18:14
awe_ogra_, you mean a block-promotion bug?  Note sure how this is indicated18:15
awe_ogra_, I added rtm14 to the new bug and it's Critical18:15
ogra_awe_, we just need a bug for the issue and robru needs to add it to the blocker list18:16
awe_https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/136623118:16
ubot5Ubuntu bug 1366231 in ofono (Ubuntu) "[krillin] When FlightMode disabled ConnectionManager interface isn't restored" [Critical,In progress]18:16
ogra_awe_, so give the bug number to robru and he should put it in the blocker list of the landing mail18:16
ogra_(not sure where else)18:16
awe_ogra_, how does the merge happen now?  Do I just top-approve the MP?18:17
ogra_awe_, yeah, and someone needs to publish the silo after tthat18:17
ogra_that should then auto-merge18:17
davmor2awe_: I was testing the shim that helped fix the sim card lock issue but the rtm branch meant you could type in any number and it would say it was wrong including the right number,  So without your fix from silo 001 it was impossible to test and land the other fixes that were needed so we could unblock the location fixes18:18
ogra_robru, you landed 016 too, right ?18:19
davmor2awe_: In general a pig of a day that needed 3 silos landing in order to test 118:19
ogra_davmor2, right, but ofiono wasnt even remotely ready ...18:20
robruogra_: no, somebody else did before I even saw it. it was already merged & cleaned before I even got the ping to publish it.18:20
ogra_robru, ok18:20
davmor2ogra_: Why are we landing stuff in silos that isn't ready? Surely that is what trunk is for, Then you request the silo when it is ready to land?18:22
ogra_davmor2, both silos get assigned at the same time ... not sure why 001 had content before ofono landed in utopic though ... it shouldnt18:23
davmor2ogra_: I think it might of been filled directly18:23
awe_davmor2, I care about and do most of my testing on rtm18:23
ogra_davmor2, right, still, the rtm silo should only be filled once the utopic one landed18:23
awe_davmor2, and I don't like landing things in either place with regressions18:23
ogra_davmor2, by the rule nothing should be in the rtm silo before that18:24
awe_anyways, let's try and keep more in sync with landings...  this kinda slipped thru our own processes18:24
ogra_not sure why it did here18:24
awe_ogra_, no not true18:24
tedgrobru, Can I get an rtm silo for line 52 please?18:24
awe_silos can be done in parallele18:24
davmor2awe_: Indeed and that is why I thought it was safe18:24
awe_davmor2, well... the utopic MP hadn't been approved, and neither utopic nor rtm silos had a testing pass set to "yes" w/image #18:25
davmor2awe_: I figured it just needed to wait for you to come on and test it against rtm but had already landed in utopic and so was safe.  But to be fair is did fix the sim unlock issue I had landed in18:25
awe_anyways, what's done is done18:25
ogra_awe_, they shouldnt18:26
robrutedg: ok you got rtm1618:26
tedgrobru, Great, thank you!18:26
ogra_awe_, the plan is that you get an rtm silo reserved when you get your utopic silo18:26
ogra_awe_, but only fill it once utopic landed18:26
awe_ogra, marked the MP as top-approved; looks like someone already clicked publish for utopic18:29
awe_does the merge happen automagically?18:29
ogra_hmm, dunno18:29
ogra_i know that sil added a check that blocks promotion if an MP isnt top approved18:30
ogra_i dont get how that could get published at all18:30
* davmor2 blames the shell script, in the python script, in the perl script, in the javascript, in the ether18:32
brendandrobru, hey - is there any code around in citrain that can update the spreadsheet? preferring python18:39
ralsina_robru: silo 12 ready to publish, if you can start a copy to rtm, I'm done with it18:45
robrubrendand: no, it doesn't work that way. you have to write JS code in the spreadsheet that polls your other thing and updates itself. you can't push data into the spreadsheet without triggering horrible revert explosions (it doesn't scale and then google solves this by throwing away hours worth of work at a time)18:57
robrubrendand: but don't write any code in the spreadsheet because that particular code base has no version control, no unit tests, and no review process. we just live-edit production. it's a total clusterfuck that i'd like to see shrink, not grow.18:58
brendandrobru, ah i was worried about swearing but well, you've set the precedent now18:58
brendandso i say, poo18:58
=== Ursinha-afk is now known as Ursinha
robruralsina_: ok you're building in silo 17: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-017-1-build/4/console19:01
ralsina_robru: ack19:01
brendandrobru, so where should i put my code then?19:01
robrubrendand: you just... don't. I dunno. you're trying to make the trello board update the spreadsheet status right?19:02
brendandrobru, yup19:05
robrubrendand: yeah I'm not sure what to tell you. citrain wasn't designed for this level of web-service integration hooks. we're not github. this isn't web2.0. This is a pile of shitty python scripts and a spreadsheet. it's a miracle that any of it works, and it's a delicate balance.19:08
robrubrendand: the dashboard and queuebot only work because they are read-only things that poll the spreadsheet, they don't put anything into the spreadsheet19:08
brendandrobru, no worries - i can tell anyone who asks it's just not feasible right now19:10
brendandrobru, i'll focus on the things i can do with read-only19:10
davmor2robru: hahahaha nice I'm glad to see you rank your fellow team-mate coding skills so highly ;)19:15
ralsina_robru: silo rtm-17 job says SUCCESS but the packages are not in the silo19:16
davmor2robru: I'm with you though sometime I'm amazed the bandaids are still stuck on :)19:16
robruralsina_: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-017 looks fine to me?19:17
ralsina_robru: ha, it's there now. I'm impatient I guess :-)19:23
robruralsina_: no worries19:26
robrutedg: your'e building in rtm1: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-001-1-build/45/console19:36
tedgrobru, How does that work with rtm 1 and 2 ?19:41
tedgrobru, 1 should pick up 2's changes since we built them in utopic in order.19:41
tedgrobru, Should we just kill rtm2? Or let QA test them in order?19:42
robrutedg: oh I didn't notice the duplication there. yeah I guess just skip right to the newest one, if they were released to utopic in order then rtm1 should contain everything in rtm2. no point wasting QA's time with two very similar landings.19:55
robrutedg: make sure you test rtm1 in in rtm ;-)19:55
robrubefore sending to QA19:55
tedgrobru, Cool, on it.19:58
ralsina_robru: can you publish silo 12 please?20:04
robruralsina_: it was already, but merging it for you now20:05
ralsina_robru: oh, thx20:05
robruralsina_: you're welcome!20:09
* robru -> lunch20:09
alecuhi trainguards! Dobey and I are working on some bugfixes for pay-ui, because gatox is on vacation. Now we got a new click for pay-ui that we'd like to submit to the store. I know that gatox usually asks fginther to upload those packages... but is there any other thing that we should keep in mind?20:22
fgintheralecu, there is a review utility that that app store reviewers use, make sure that passes20:24
fgintheralecu, at the moment I can't find what this called20:25
fgintheralecu, I think this is it: https://code.launchpad.net/~click-reviewers/click-reviewers-tools/trunk20:26
alecugreat, I'll check with that too20:26
alecuseems to be already packaged as click-reviewers-tools20:29
alecubut doesn't seem to be up-to-date.20:31
robrualecu: yeah just get the trunk of that20:33
alecurobru: fginther: trunk gives two errors, but I think that should be expected from pay-ui, since it runs unconfined and it has a special hook: http://pastebin.ubuntu.com/8293383/20:35
alecupopey: do you know about that? ^20:35
robrualecu: seems reasonable, i'd say go for the upload and let popey sort it out ;-)20:36
alecugreat. fginther, robru, where should I upload the click package?20:36
robrualecu: not sure. only a tight cabal has the password to upload core apps. ping popey20:39
alecuok, I've sent mail about that to popey and francis.20:48
tedgrobru, Can I please get a silo for line 60?20:54
robrutedg: silo 9!20:55
tedgrobru, Great, thank you!20:55
robrutedg: you're welcome!20:55
popeyalecu: if fginther uploads it, I'll approve pay-ui20:59
asacrobru: all going fwell?21:18
robruasac: yep, fixing up citrain piece by piece21:20
robruasac: publishings coming alnog as well21:20
asacrobru: citrain busted? what did you do :)?21:37
balloonsrobru, once you are done playing with the citrain :-), can you give a quick peek at the autopilot packaging changes I have in my MP and approve/deny? It's just adding a couple depends https://code.launchpad.net/~nskaggs/autopilot/fix-1328600/+merge/22739921:40
asacrobru: anyway. i will be out today. wonder how close we got in elimiating our big blockers today on rtm21:42
asacbut will check the mail tomorrow21:42
asacso we can continue on that mission21:42
robruballoons: lgtm, but I'd prefer if you could sort the dependency list. Please run 'wrap-and-sort -a -t' in the source tree root and then re-add the comment in debian/control that that'll discard21:42
asacpromotable == rtm branch21:42
robruasac: yeah, from what I gathered, I published a regression but I fixed another, we'll have to wait for QA to get the next image to know for sure21:43
asacgood luck. if you need any support or so, slangasek is probably around for a while longer; otherwise text me :)21:43
asacrobru: published a regression?21:43
asachmm. with QA sign off?21:43
asacno wayt o back out?21:43
asacwell, i will let you figure and hope we can resurrect that tomorrow to promotable state at least21:43
robruasac: yeah, no worries, upstream is on it21:43
asacfor backouts etc. steve can probably help if you want to get that out21:43
robruthanks21:44
asacrobru: right, but remember that that will take days usually21:44
asac:)21:44
asacupstream fixing someting quick is rare21:44
asachehe21:44
asacbackout is usually better21:44
asaccu21:44
balloonsrobru, command run. what do you mean by 're-add the comment in debian/control that that'll discard'?21:45
robruballoons: running wrap-and-sort discards comments in debian/control, which you should have one if you follow the citrain packaging guidelines. check your diff. if you see a comment block deleted from debian/control, copy&paste it back in there21:46
balloonsrobru, ahh.. k, no comments in the debian/control :-)21:47
balloonsrobru, if you can add your 'OK' to the MP I'd appreciate it22:14
robruballoons: oh sorry, sure22:19
robruballoons: ah that wrap-and-sort was noisier than I'd expected ;-)22:21
balloonsrobru, yes, veebers said the same thing ;-) But it's done22:21
balloonsI thought it would just inline my changes22:22
veebersI'm blaming you for that robru ;-)22:22
dobeyrobru: hi. any idea why something would be on the "Archive" page of the spreadsheet, but not actually in ubuntu-rtm?22:32
robrudobey: probably something exploded. it's happening. if you notice it, just make a new request and I can take care of it22:33
dobeyrobru: ok22:34
dobeyalecu: ^^22:34
robruveebers: blame away! I love sorted debian/controls ;-)22:34
alecudobey: ouch :P We better take a close look at the latest landings.22:35
alecurobru: is that fixed if we do a new landing + srccopy?22:35
dobeyi guess it would be22:36
dobeyif just asking for a srccopy again would fix it, anyway22:36
robrualecu: yep, any new landings that go through utopic will contain previous releases from trunk by definition, so everything that gets released to rtm will by definition contain all previous releases, even if the previous release never made it to rtm22:36
dobeyand we need to do a new landing for ubuntuone-credentials at least (once my branch is approved), so maybe we should just do that22:37
dobeyalecu: do we need to do a unity-scope-click landing?22:38
robrubfiller: please approve your MPs. https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-020-2-publish/2/console also I have no idea why you have MPs in an rtm landing, that makes no sense to me22:38
robrubrb folks, gotta get dinner started22:41
fgintheralecu, are you still around?22:52
slangasekrobru: do you need help with a revert for whatever this regression is you mentioned above?23:29
robruslangasek: I don't think so. upstream said they'd have a fix by morning. if not, europeans can look at reverting it. I'm not in a great position to know what the image quality is currently like, currently I'm knee-deep in citrain internals23:32
robruslangasek: the thing is, the regression I published fixes a different blocker. so if we revert it, from what I understand, we don't actually get ahead there. so I think we should just wait for upstream to fix that regression and enjoy the other blocker that got fixed.23:33
slangasekrobru: ok; so the regression and the fix weren't in unrelated uploads, and a clean revert doesn't get us anywhere - thanks for confirming23:36
robruslangasek: you're welcome!23:37

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