[02:05] === trainguards: IMAGE 232 building (started: 20140908 02:05) === [03:05] === trainguards: RTM IMAGE 23 building (started: 20140908 03:05) === [03:45] === trainguards: IMAGE 232 DONE (finished: 20140908 03:45) === [03:45] === changelog: http://people.canonical.com/~ogra/touch-image-stats/232.changes === [04:15] === trainguards: RTM IMAGE 23 DONE (finished: 20140908 04:15) === [04:15] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/23.changes === === 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. [07:01] trainguards, can I please have a reconf on silo 19 [07:02] added qtmir-gles there [07:02] Saviq: I'm not here, but ok ;-) [07:02] robru, yeah, you should *not* be here [07:02] hmm :) [07:02] Mirv: ah, you're here. ok I got this one but I'm really not here ;-) [07:03] robru: when you're not really here, you should really really not be here :) [07:03] Mirv: who are you talking to? I don't see anybody here. [07:03] exactly [07:26] Mirv: have you heard anything about how to (a) disable the edges intro and (b) how to unlock the screen remotely? [07:30] bzoltan: 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.sh [07:31] Mirv: the `phablet-config edges-intro --disable` does not do the job, so yes a working solution would be cool [07:32] ok, I'll keep my ears open [07:33] Mirv: for the unlucking ... WOW, if that works then I am saved :) [07:33] bzoltan: 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] ;) [07:33] (from http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/287) [07:36] bzoltan, hello - do you have results from you tests for silo 12 landing? [07:38] brendand: that is the 28.08 lanidng for RTM, right? [07:40] bzoltan, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-012 [07:45] brendand: 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:46] bzoltan, no i just want to have the logs for comparison === tvoss is now known as tvoss|test === tvoss|test is now known as tvoss [08:11] robru: "AttributeError: 'bool' object has no attribute 'isdigit'" https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-007-1-build/25/console [08:12] Mirv: 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] Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY [08:14] bzoltan, that it can't connect to the session bus I guess [08:14] bzoltan, try to adb shell; su - phablet; [08:15] bzoltan, running as root? [08:15] seb128: tvoss: with new adbd all my commands are run as phablet. but I can try to force [08:15] bzoltan, thats a bug with cgroups that mterry works on since a few days [08:15] bzoltan: I wonder if that one hasn't been updated to the new world similar to the provisioning [08:16] bzoltan, could be that the env is wrong/doesn't include the dbus session [08:16] the env is definitely wrong, you need the sudo wrapper, but even then it wont work [08:17] logind doesnbt hand out proper sessions due to the cgroups issue [08:17] ogra_, hasn't the cgroup bug fixed by desrt/slangasek in systemd-s on friday? [08:17] "debian/patches/0001-cgmanager-stop-doing-async-calls.patch: [08:17] cgmanager: stop doing async calls; fixes a race condition on login. [08:17] Thanks to Ryan Lortie . Closes LP: #1365095." [08:17] Launchpad 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/1365095 [08:17] dunno, i have seen mterry and hallyn discuss into the (european) nige [08:17] k [08:17] I though that was ^ [08:18] *nite [08:18] but maybe there is another issue still [08:18] well, you definitely still need the sudo wrapper [08:18] dbarth: the syncing seems broken in yet new other way, I'll help your silo manually in a bit [08:18] adb shell doesnt have the full env [08:18] Mirv: seb128: ogra_: when I manually adb shell in and execute the command then the screen get unlocked [08:18] bzoltan, what ogra_ said [08:19] seb128: I just have read... so ogra_, what is the trick? [08:19] (i have been looking into that over the weekend, might be i can fix it in adbd) [08:19] bzoltan, wrap the gdbus command in "sudo -u phablet -i" as usual [08:19] ogra_: OK, I try that [08:21] (apologies for the spam, I edited the description) [08:21] ogra_: works now, thank you [08:27] Morning all [08:29] dbarth, ^ no no no for that rtm settings silo [08:29] dbarth, we have settings in sile 015 and are trying to land that to rtm for a week, don't hijack it with your version [08:30] Mirv, ^ [08:30] seb128: noted [08:30] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-015/+packages [08:30] get that to land first please [08:30] that should be good, just need qa verification [08:31] will do that [08:31] thanks [08:31] should we clear 007 out meanwhile to avoid errorS? [08:31] it's going to need to be rebased on top of what is 015 anyway [08:31] yeah, I'll clear it too, the current build has no use [08:32] or well, is that a sync of current utopic u-s-s? [08:32] because then that would be fine, but it would required a new round of testing, so we should still land 015 which has been tested already [08:32] ogra_: meeting? [08:34] Mirv, i wish i could, firefox doesnt let me :P [08:36] seb128, hey - silo 15 seems to have issues [08:36] brendand, shrug [08:36] brendand, which ones? [08:36] seb128, wizard crashes, and sim cards can no longer be unlocked [08:36] at least. still more testing to do [08:36] brendand, settings have nothing to do with sim unlock [08:37] are you supposed you tested settings only? [08:37] (running with watch_only since it had wrong status) [08:37] seb128, i have only upgraded the system-settings packages [08:37] brendand, 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 issue [08:38] block those fixes on* [08:38] brendand, that "can't unlock sim" looks like it could be the systemd issue fixed in friday [08:39] brendand, anyway, as said, settings don't do sim unlock, so if you found a bug it's not with settings [08:39] brendand, it's more likely a random one which is already there in the image [08:39] seb128, it works before installing the packages [08:39] brendand, that shouldn't count as a settings blocker [08:39] you got lucky [08:39] seb128, several times [08:39] it might work on another try who knows [08:40] you got lucky several times [08:40] what I can tell you [08:40] seb128, alternatively - you're wrong [08:40] brendand, settings don't have sim unlock code, they are not involved in that [08:40] shrug [08:40] k, I give up, do whatever you want with settings [09:03] actually 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:04] dbarth: ^ so your location settings landing might take some time to reach rtm until the previous u-s-s rtm landing is agreed by QA [09:05] Mirv, brendand has issues with settings anyway, so it looks like it's not ready to land [09:05] brendand, btw having a bug report of those specifics issue would help [09:05] seb128, i'm just going to confirm (again) what's going on [09:10] Mirv: ok, noted [09:17] thanks for the allocation :) [09:19] pete-woods: you're welcome :) we just had 0 silos free so I didn't do that earlier. [09:24] Mirv: 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.gz [09:25] my diff for this change is totally insignificant (just adds the X-Ubuntu-Use-Langpack: yes line) [09:27] pete-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] Mirv, ouch ... [09:29] pete-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 did [09:30] nothing wrong with the new upstream version otherwise, but Qt is just very strict about numbers... [09:30] no problem :) [09:30] I pinged him on #ubuntu-devel now, there's either a revert option or faking the module version option [09:31] well I'll just be happy to build my package :) will follow along to see when it's resolved [09:33] seb128, so the bug is reproducible by installing the silo and then resetting the device [09:34] seb128, on utopic it's not reproducible - at least not on mako [09:35] brendand, can you describe "the bug" [09:35] seb128, i'll file it [09:35] thanks [09:37] Morning - can someone help me get upstart 1.13.2-0ubuntu1 into the rtm branch? [09:37] seb128, until then, when you click on the unlock button, indicator-network just seems to reload itself [09:39] brendand, k, your are speaking about the SIM unlock on boot? [09:40] brendand, 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 only [09:40] brendand, I hope somebody figure it out though [09:40] seb128, it doesn't seem to happen if the wizard doesn't run, so maybe that leaves something in a bad state [09:43] brendand, that would be and is more likely than having settings involved [09:53] Mirv: 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) [10:01] jodh: sure, but add where exactly? line 4 is the utopic landing [10:02] jodh: or do you mean add a new upstart rtm landing for syncing from utopic? [10:02] yes, I think you mean that [10:02] Mirv: yes, a sync of the latest upstart in utopic which is a pre-requisite for line 4 actually working :) [10:04] bzoltan, with my latest android-tools upload the sudo wrapping shouldnt be necessary anymore (once it landed in all images) [10:04] (it wont do any harm either to keep it though) [10:05] jodh: 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] Mirv: thanks very much! [10:11] Saviq, are you landing https://code.launchpad.net/~unity-team/unity8/new-adbd/+merge/233684 somewhere ? [10:11] ogra_, yeah, silo 19 [10:11] ogra_, but need to fix a sh$tload of ap tests that assumed there's no password [10:11] Saviq, see above ... adbd should be fixed now ... while it wont do harm it also shouldnt be absolutely necessary anymore [10:11] Mirv: erk, looking [10:12] ogra_, yeah, k [10:12] Saviq, (might make sense to verify it though ... but i think it shoudl "just work") [10:12] ogra_, kk [10:19] Mirv: 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 sil [10:19] landed on friday. [10:24] 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] () [10:24] Greeter unlocked [10:24] ogra@styx:~/Devel/branches/phablet-tools$ [10:24] yay !!! [10:26] GGRRR did anyone elses krillin touchscreen get super sensitive in the recent images [10:26] i cant even scroll in news weballs without having it open unwanted links all the time [10:26] *webapps [10:28] this is unusable ! [10:28] ogra_: ooh, i noticed that at teh weekend. have you got a bug for it? [10:28] funnily there is no issue in the G+ app ... but in all news apps i tried [10:28] yeah, same [10:29] popey, nope, only noticed it on sat and thought my display was to dirty or something [10:29] heh, ok, I'll confirm if you bug it. [10:29] guessing oxide? [10:29] but it persists (and feels like it got worse, though probably i'm just easier to annoy now) [10:29] popey, we didnt have oxide updates in rtm [10:29] i think ... [10:29] * ogra_ checks [10:30] i assume its the device tarball [10:30] http://people.canonical.com/~ogra/touch-image-stats/rtm/21.changes thats all that landed on the weekend [10:36] seb128, here's a twist [10:36] seb128, i can reproduce it in utopic without the silo installed... but only on krillin :/ [10:37] brendand, utopic already has the changes though, no need of a silo [10:40] robru: 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:43] seb128, well yes - i suppose that statement is a bit redundant [10:43] seb128, but i've tested the same thing on both krillin and mako with utopic and it only fails on krillin [10:43] brendand, k, fun [10:45] yay [10:45] 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] () [10:45] Greeter unlocked [10:45] ogra@styx:~/Devel/branches/phablet-tools$ [10:45] works on rtm fine as well :) === MacSlow is now known as MacSlow|lunch [11:00] cihelp, this jobs looks stuck, 'innit http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako/4375/console ? [11:00] so do the next two ones... /me worried that's what plars reported about devices getting stuck :| [11:01] what devices are these ? makos ? [11:03] (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:07] Saviq: ogra_: these devices are not offline. could be some other issue [11:07] yeah, not that then [11:08] its only krillin utopic anyway, mako and rtm should be fine [11:12] Mirv: 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 building [11:14] ogra_: 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] Ubuntu bug 1363190 in gallery-app "Gallery APP autopilot tests pollutes the file system" [Undecided,New] [11:21] Saviq: 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 now [11:21] yay [11:21] good to know [11:22] psivaa, oh ok thanks [11:22] oof [11:27] davmor2: bfiller has written there ": these are isolated bug fixes don't need QA signoff". and I've written that telephony-service failed to build [11:27] probably because of some media related landing missing from rtm [11:32] Mirv: 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 through [11:33] davmor2: 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:34] Mirv: okay I'll chase it up with jfunk latter [11:34] davmor2: see line 58/59 for another example. I think I haven't seen others lately. [11:39] trainguards, I can get silo for line 29 please [11:47] Saviq: with pleasure. how's the utopic silo testing looking? [11:48] Mirv, had to fix a lot of autopilot because of the adb change (we didn't support pinlocked tests until now) [11:48] Mirv, so that's building now [11:48] or built actualy [11:48] +l [11:48] so am testing now [11:51] Saviq: ok, cool === MacSlow|lunch is now known as MacSlow === iahmad_ is now known as iahmad === om26er is now known as om26er|afk [12:22] 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) === om26er|afk is now known as om26er [12:26] ogra_: feel free to fire, I'm not holding my breathe on anything specifically [12:26] heh, ok [12:26] triggered [12:29] Mirv: see -touch for your help [12:30] mterry: so i think we might wnt to move the systemd-shimd source packag efrom utopic in the system-setting silo? [12:30] mterry: do we also need li8ghtdm? [12:30] asac, no [12:31] mterry: no for putting it into the same silo? [12:31] think would help if it really fixes the problem that the system-settings silo bounced === iahmad is now known as iahmad|afk [12:31] woudl be good if someone who has the issue could confirm that first though [12:32] (that systemd-shim actually fixes the SIM unlocking) [12:32] right [12:32] davmor2 is at lunch [12:32] but given that mterry fixed the same issue [12:32] i am sure it does [12:32] before you pile up more stuff in that poor silo [12:32] https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1365095 [12:32] Ubuntu bug 1365095 in systemd-shim (Ubuntu-rtm 14.09) "Greeter not asking for pin code in image 11 (krillin)" [Undecided,New] [12:32] ogra_: that silo currently onlyhas system-settings [12:32] asac, with a bunch of MPs though [12:32] asac, well... I am not sure that they are the same root problem yet [12:33] right, but if those depend on this one then they should go in together to avoid duping QA [12:33] mterry: ok. let us know [12:33] Mirv is chcecking whty the shim silo didnt ubild [12:33] Mirv: 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:34] hmm. it cant find the orig it seem [12:34] yeah, that cant work [12:34] s [12:34] guess it should come from ubuntu archive [12:34] mabye that thing was stuck in proposed?: [12:34] no [12:34] i saw it enter the utopic image [12:34] ogra_: when? before the silo failed? [12:34] must be in the utopic archive proper [12:34] asac: if you say -touch, then I discuss at -touch :) I copied it now manually. [12:34] asac, yes [12:34] Mirv: thanks [12:34] === trainguards: IMAGE 233 building (started: 20140908 12:35) === [12:35] Mirv: yeah, i just thought as we continued we might wanna go back here. sorry [12:35] for me its one tab away though :P [12:35] hehe [12:35] right next door [12:35] asac, 7-3 was an upload, didnt go though silos in utopic [12:35] (systemd-shim 7-3 that is ) [12:35] ogra_: sure, but could have been stuck in proposed when wee tried the silo for rtm [12:35] https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/6/console [12:35] ogra_: it was siloed for rtm after [12:36] but anyway, we got it in now :) [12:36] asac, silo buildds behave slightly different to distro builders ... [12:36] * ogra_ got bitten by that on the weekend with android-tools too [12:37] ogra_: its not in the buildds [12:37] its before... check the log [12:37] but 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 proposed [12:39] is the theory here that the silo might have built against a package from -proposed? [12:40] asac's theory is, yeah [12:40] that would be anomalous as silos are not normally configured to build against -proposed [12:40] i think the copy-package would have copied the orig.tar.gz in any case [12:41] copy-package does not concern itself with such details :) but the publisher would republish that when it runs [12:41] if bzr-builddeb is relying on the .orig.tar.gz being in the archive already, then it may have to wait a publisher cycle [12:42] no ... i said that the silo upload through the jenkins job might have been tried when the package wasnt in proper archive yet [12:42] hence we get the weird "cannot download orig tarball" failyure [12:42] https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/6/console [12:42] but *shrug* [12:42] IMO the problem there is that the version is wrong [12:43] asac, the "silo upload" is a manual script call ... [12:43] This 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-3 [12:43] which essentially does something similar to a dput ... which in turn i would expect to have uploaded the orig tarball [12:43] * asac desnt know and leaves it to the smart folks [12:43] I seem to remember somebody mentioning that bug/misfeature/whatever here recently [12:44] yeah, i think lukasz was looking into that on friday [12:44] we could just do a source copy instead though, right? [12:44] yeah i see the version now [12:44] defiitely bogus [12:44] unless this is a cherry-pick [12:44] cjwatson: Mirv alreadu uploaded manually to the silo now [12:44] ok [12:45] i think the ci train source copy feature is what failed here initially [12:45] but guess the version mangling is really bogus still there [12:45] if it's doing version mangling it's not a copy ... :) [12:45] yeah [12:45] so i am not sure :) [12:45] have 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 could [12:45] I did copy-package now [12:45] hard to remember who did what there ... thought they used the sync: feature [12:46] Mirv: will the silo status figure that it got fixed? [12:47] i mean here: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q= [12:47] if it was a dput it will ... with the next watch_only build [12:48] (which you can only do after the packages have built ... be patient :) ) [12:48] heh [12:48] you can do it a bit before and it'll wait [12:50] asac: yes, it just requires watch_only build that can't be done right away. it's now running. [12:50] cool. thx [12:51] * ogra_ thinks the last android-tools fix is the grossest hack he has ever done ... bt it makes things work [12:51] Sep 8 14:50:32 ubuntu-phablet sudo: phablet : TTY=pts/38 ; PWD=/home/phablet ; USER=phablet ; COMMAND=/bin/bash -c /bin/bash -cl env [12:51] (thats the log output of "adb shell env" [12:51] ) [12:52] (see the COMMAND) ... [13:17] rsalveti: 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 silo [13:17] rsalveti: https://launchpadlibrarian.net/184207757/buildlog_ubuntu-rtm-14.09-amd64.telephony-service_0.1%2B14.10.20140905~rtm-0ubuntu1_FAILEDTOBUILD.txt.gz [13:21] boiko, it's in silo 11. I'm testing it. [13:21] jibel: ah, nice! [13:22] hi. I have a new device tarball I'd be interested in publishing today, if possible [13:23] is someone able to give it a QA pass? [13:23] Mirv: 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 yet [13:23] ogra_, ^ (as person running the landing meetings...) [13:23] john-mcaleely, perhaps davmor2 [13:24] depends how swamped he is ... looks like he is alone [13:24] davmor2, something you could do today? (brendand did the honours on friday) [13:24] ogra_, understood [13:25] boiko: yeah, would work after a rebuild [13:25] boiko: didn't yet land because silo 11 is still to be tested [13:25] john-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 it [13:25] from my experience it takes a few days for the rtm stuff to be signed [13:26] davmor2, it is worth doing, if I can land it before cob (~6pm) UK today [13:26] davmor2, otherwise, it can wait [13:26] rsalveti: ok, I'll just leave my silo sitting there waiting, would you mind giving me a heads up once silo 11 lands? [13:27] boiko: sure [13:27] rsalveti: thanks [13:29] davmor2, http://people.canonical.com/~jhm/barajas/device_krillin-20140908-d8c11f3.tar.xz [13:29] davmor2, simply download, and use --device-tarball with your favourite ubuntu-device-flash command to test [13:29] john-mcaleely: no worries I'll give it a go asap [13:29] davmor2, I'll ping you in a bit and see if I get lucky on your capacity :-) [13:32] Mirv: hey [13:33] Mirv: I'm seeing mtp as landed in the spreadsheet, and no longer in any silo, but apparently not in ubuntu-rtm [13:38] ogra_: Mirv: how are the landings for the rtm proposed blockers going? [13:38] i think all but one had an MP according to sils mail on friday [13:39] let me check his list [13:40] ogra_: its the four bugs i cut and forwarded to ue-leads with you CCed [13:40] as you were appopinted the driver [13:40] nobody told me :P [13:41] ** Sometimes input breaks and only edges are responsive [13:41] https://bugs.launchpad.net/bugs/1295623 => Merge requests present -> It should land soon, it's next in the unity8 queue. [13:41] Ubuntu bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress] [13:41] ** Seekbar tests are skiped only on nexus 4 and 5 [13:41] ogra_: it was in the mail by sil [13:41] https://bugs.launchpad.net/bugs/1359040 => Merge requests present -> Is this really a blocker? Comment needed. [13:41] Ubuntu bug 1359040 in mediaplayer-app "Seekbar tests are skiped only on nexus 4 and 5" [High,In progress] [13:41] asac, yes, i see it [13:41] ogra_: so please ensure we dont pick up too risky landings while we try to get that [13:41] e.g. push back on crazy folks :) [13:41] the seekbar stuff is really ignorable [13:42] Saviq: when is landing of bug 1295623 scheduled? [13:42] bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress] https://launchpad.net/bugs/1295623 [13:42] but yeah, fix wouldnt hurt (four tests that should be skipped arent ... we tend to simply ignore their results ... purely cosmetic) [13:42] asac, am testing now [13:42] this one is definitely important [13:42] asac, unless you mean the bug itself, then it landed around the time we started doing the phone ;) [13:43] 15:40 < ogra_> the seekbar stuff is really ignorable [13:43] 15:41 < asac> Saviq: when is landing of bug 1295623 scheduled? [13:43] bug 1295623 in unity8 (Ubuntu) "Sometimes input breaks and only edges are responsive" [Critical,In progress] https://launchpad.net/bugs/1295623 [13:43] 15:41 < asac> ogra_: wll, we have an MP for that i read [13:43] 15:41 < asac> so why not get it in and get it off our worry list [13:43] asac, no idea why it is on that at all [13:44] rsalveti, 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:45] ogra_: wll, we have an MP for that i read [13:45] so why not get it in and get it off our worry list [13:45] jibel: nops, that's it [13:45] 15:44 < asac> ogra_: well, sure that QA didnt like it and wants to get this resurrected [13:45] ogra_: well, sure that QA didnt like it and wants to get this resurrected [13:45] damn flaky connection [13:45] oops :) [13:46] * asac doesnt understand when irssi reposts stuff after disconnect and when not [13:46] asac, answered your mail [13:46] i didnt get tthat i was explicitly CCed ... evo just showed it in the thread [13:46] ogra_: anyway, i think that one is wihtelistable if we have the unity part [13:48] asac, phew had some laptop troubles -- in case you are still wondering, looks like the systemd-shim fix solves the SIM PIN problem [13:48] robru, 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:49] mterry, right, it simply didnt land in rtm yet [13:50] ogra_, sure... Though note that the bug can still be reproduced on the latest utopic images until the next spin [13:50] mterry, already spinning ;) [13:50] ogra_, and there was some question on whether the bugs were the same root cause [13:50] mterry, with an adbd fois for your un lock issue too btw ;) [13:50] *fix [13:50] ogra_, why don't we just land the unity8 branch? [13:51] mterry: nice one [13:51] ogra_, that's been approved for like a week [13:51] davmor2: can you do a joint tesating of 015 and 016? [13:51] davmor2: seems they going in together will fix the SIM PIN problem [13:51] davmor2: and that will then clear the path for location landing [13:51] thanks! [13:51] boiko: yes, but please ask someone with ppa rights to trigger the rebuilds in there directly [13:51] jibel: ^ [13:51] [13:52] asac: right okay so I'll actually need 016 to finish building then I can [13:52] davmor2: wait ... finish? [13:52] mterry, it hasnt been approved [13:52] davmor2: its just dashboard brokenness [13:52]