/srv/irclogs.ubuntu.com/2015/02/05/#ubuntu-ci-eng.txt

=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
imgbot=== IMAGE 90 building (started: 20150205-02:05) ===02:05
imgbot=== IMAGE RTM 227 building (started: 20150205-03:05) ===03:05
imgbot=== IMAGE 90 DONE (finished: 20150205-03:30) ===03:30
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/90.changes ===03:30
imgbot=== IMAGE RTM 227 DONE (finished: 20150205-04:25) ===04:25
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/227.changes ===04:25
bzoltanwhere my MRs went from the "Landing documentation" cell of the CI sheet05:42
bzoltanMirv: robru ^05:42
bzoltanI reentered05:43
robrubzoltan: hm?05:54
robrubzoltan: do you have a silo you want assigned? i don't see it05:56
bzoltanrobru:  I am ready to release the silo2306:03
bzoltanrobru:  hmm... ci sheet is playing with me06:05
bzoltannow it is OK06:05
Mirvbzoltan: someone pressed delete accidentally?06:06
bzoltanMirv:  I have seen few times that when my local sheet gets out of sync it pushes changes I do not intend once the net comes back.06:07
Mirvbzoltan: google does that too.. sometimes waiting more helps, sometimes not06:09
bzoltanMirv: yes... Strange that there is no notification abuut that line here. WOuld you publish the silo23 please?06:12
Mirvbzoltan: done.06:13
bzoltanMirv: thanks06:19
Mirvhmm, where did the queuebot go..06:26
=== marcust__ is now known as marcustomlinson
Mirvand it's back07:02
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
fgintherrobru, the problem with doing POST requests is that the entity doing the POST must also supply credentials as part of the request.07:35
robrufginther: right, thanks07:36
fgintherrobru, oh, you're still awake :-)07:37
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
robrufginther: only barely. goodnight!08:02
kgunntrainguards can i get reconfig on vivid silo 008:24
kgunnplease08:24
bzoltanMirv:  I would need a vivid silo for a super important QtC hot fix08:37
Mirvbzoltan: ok08:38
Mirvkgunn: ok08:38
Mirvkgunn: something funky again with reconfiguring08:39
Mirvkgunn: what's the idea of having "sync:ubuntu/vivid qtsystems-opensource-src" for a vivid silo?08:40
Mirvkgunn: seems to work by removing the sync part of it08:42
Mirvkgunn: now done08:43
satorisping cihelp, what seems to be going wrong here (this is my first SRU, so the package setup might be wrong): https://ci-train.ubuntu.com/job/ubuntu-landing-020-1-build/82/console10:03
vilasatoris: trainguards should work better for that10:04
sil2100satoris: let me take a look in a moment10:04
satorisThanks.10:05
popeyjibel: so was that a "yes" or "no" to adding music to the trello? :)10:38
jibelpopey, it's added to the trello10:39
popeythank you!10:39
SaviqMirv, we had the sync: for libevdev (new dependency, just want to make the silo citrain-tool-friendly), sorted that out already and dropped the sync: again10:46
Saviqjust FYI10:46
SaviqMirv, oh, and welcome back!10:46
MirvSaviq: thanks!10:47
=== alan_g is now known as alan_g|reboot
sil2100satoris: interesting failure, need to take a look if there's anything wrong with the 14.04 chroot, but so far it seems you're doing everything alright10:50
sil2100satoris: oh, no, wait10:52
sil2100satoris: ok, found the problem10:58
sil2100satoris: so, it seems the lp:thumbnailer/trusty branch is not train ready10:58
sil2100satoris: you are missing the .bzr-builddeb/default.conf with the split option there10:59
sil2100satoris: this basically means that when the train tries to build your package, it does not generate a new tarball off from your source code (which it has to do) because of this missing config file11:00
sil2100satoris: best if you add it to your merge11:00
sil2100And then rebuild11:00
pstolowskitrainguards hello, could you please reconfigure rtm-landing-002 (new project added)?11:03
sil2100pstolowski: sure11:08
sil2100pstolowski: done11:10
pstolowskithanks11:13
satorissil2100: check, the file is in trunk but for some reason not in that branch. Fixing.11:39
=== MacSlow is now known as MacSlow|lunch
mzanettisil2100: mind reconfiguring silo vivid/000 for us please?12:25
sil2100mzanetti: no problem12:26
mzanettita12:26
sil2100mzanetti: wow, getting bigger and bigger ;)12:27
sil2100mzanetti: done12:30
mzanettisil2100: thanks. yes, it's getting bigger and bigger, but its *awesome* :D12:32
sil2100lool: hey! Did you upgrade or remove the terminal-app from the ubuntu-rtm custom tarball for mako by any chance?12:44
=== alan_g is now known as alan_g|lunch
bzoltansil2100:  would you be so kind to publish the silo3, please?12:52
sil2100Oh! Missed it, on it now12:52
sil2100lool: from what I see that didn't happene yet - if you could do any of the two in the nearest time it would be most awesome ;)12:56
=== chihchun_afk is now known as chihchun
* sil2100 off to lunch13:06
Mirvkenvandine: seb128: I heard you had been asking for newer qtsystems-opensource-src? it also removes StorageInfo class, would you want to land ubuntu-system-settings together with it, or alternatively if I'd land the new qtsystems as part of Qt 5.4 maybe do a build time check for 5.4 instead?13:17
seb128Mirv, no strong preference, whatever works best for you13:18
davmor2seb128: I'll sort you out a log after lunch13:18
seb128davmor2, thanks13:18
davmor2seb128: I'm just running through qt5.4 to see waht is broken by it currently so there might be a few more but that looks like the only view broken in uss13:19
seb128davmor2, k13:19
Mirvseb128: kenvandine: well then I could include the ubuntu-system-settings MP in the Qt 5.4 silo.13:20
seb128Mirv, is there one or does somebody needs to work on that?13:21
Mirvseb128: the silo is ready for all practical developer purposes https://wiki.ubuntu.com/Touch/QtTesting13:21
seb128Mirv, included u-s-s changes or is that todo?13:21
Mirvseb128: oh, that, I only know u-s-s is broken by new qtsystems so yes it's a todo. I thought since you had requested new qtsystems you might know already what needs to be changed in the About page.13:22
seb128Mirv, no, but I can have a look, we requested it because the battery changes stopped to be reported with the new upower13:23
Mirvseb128: oh, ok. thanks if you could have a look at that bug then!13:24
=== alan_g|lunch is now known as alan_g
davmor2seb128: hahaha, of course I would love to to get you logs unfortunately the developer mode switch is in the about the phone page ;)  I'll see if it is still enabled :)13:43
Mirvdavmor2: it is after simply updating the PPA :) I got the log now to the u-s-s bug because I updated the qtsystems build in the PPA and wanted to make sure it looked same still (yes it did)13:44
Mirvso yes, the u-s-s fix needs to go with Qt 5.4 since the replacement for what was removed from qtsystems is only available in qtbase 5.413:45
davmor2Mirv: nice, I added a before log for seb128 so he can see the difference then :)13:46
Mirvactually, that might need something a bit extra... if the new class is in qtbase, that means there's nothing for QML13:47
Mirvanyhow, that's how it is, the feature is gone13:47
=== marcusto_ is now known as marcustomlinson
LaneyMirv: do you know anything about this change in particular?14:13
Laneylooks like StorageInfo::DeviceType has no equivalent now ...14:14
Laneyor DriveType or whatever it's called14:14
=== MacSlow|lunch is now known as MacSlow
MirvLaney: no, I don't know anything particular, other than qtsystems is not supported by upstream so they are free to also remove features14:32
Laneybleh14:34
dbarthtrainguards, hey, can i get a new rtm silo on line 65 ?14:35
Mirvdavmor2: done14:36
dbarththanks14:38
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
pstolowskitrainguards hey, could you please purge unity-scopes-api from rtm-002 (we've reconfigured the silo and rebuilt without it, but it still in the ppa)15:08
sil2100pstolowski: on it!15:08
sil2100pstolowski: yeah, we have a bug for that15:08
pstolowskisil2100, thanks!15:08
kenvandinervr, don't forget to mark silo 3 as verified on the spreadsheet :)15:20
rvrkenvandine: I'm on it :)15:20
kenvandinervr, thx :)15:20
rvrkenvandine: Your silo is approved. Make sure the strings get to in Launchpad for translation in RTM.15:21
kenvandinervr, i don't think i need to do anything for that15:23
kenvandineor maybe i do... i can't remember :)15:23
=== slangase` is now known as slangasek
=== marcusto_ is now known as marcustomlinson_
Chipacatrainguards, at your earliest convenience please to publish silo #7 / row 5816:59
robruChipaca: done17:10
Chipacarobru: thanks muchly17:11
robruChipaca: you're welcome17:11
=== chihchun is now known as chihchun_afk
brendandrobru, hey about that silo diff code17:52
brendandrobru, we've been finding out recently that part of the diff is inaccurate for some reason, might be something to check out if you're going to make it a part of the citrain itself17:53
brendandrobru, it's the debian/changelong that is wrong, for some reason it ends up with extra content17:54
brendandi'm not sure why17:54
pstolowskitrainguards hey, the branches from silo 8 are now all be approved and it should be ok to publish17:55
sil2100brendand: hey! Still around?17:55
brendandsil2100, yes :)17:56
brendandsil2100, i've not disappeared17:56
sil2100brendand: excellent - so I have prepared some changes to the old spreadsheet to enable tracking of click/tarballs17:57
brendandsil2100, yeeees17:58
sil2100brendand: every entry will get an UID after a landing team member approves it - and I decided that the magic string of [non-citrain] will be present in the comments field (can be inside of the string)17:58
brendandsil2100, ok. i think we might need to co-ordinate a bit on pushing these changes17:58
brendandsil2100, can we try and do that tomorrow, or some other time not today?17:59
sil2100Tomorrow seems fine17:59
robrubrendand: wrong in what way? like stuff appears in the diff that doesn't appear in the uploaded package? or the changelog is just wrong all around.18:19
robrubrendand: changelog generation code is known to be pretty horrible...18:20
robrumterry: kenvandine: anybody around for a packaging ack? https://ci-train.ubuntu.com/job/ubuntu-landing-008-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity-scopes-api_0.6.13+15.04.20150205.1-0ubuntu1.diff/*view*/18:21
jdstranddbarth: ok, I added apparmor-easyprof-ubuntu to line 65 of the spreadsheet (rtm silo 000). I'll prepare a package and get it in there a bit later18:21
dbarthjdstrand: thank you!18:24
boikorobru: silo 13 is showing some packaging changes in dbus-test-runner?!?!18:29
robruboiko: https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dbus-test-runner_15.04.0+15.04.20150116-0ubuntu1.diff/*view*/ looked pretty trivial to me18:32
boikorobru: the thing is, there was no dbus-test-runner on the silo :)18:34
robruboiko: was there previously?18:44
boikorobru: you mean since I got the silo? nope18:44
robruboiko: yeah, like did you add it and then remove it or something. guess not18:44
robruboiko: k, i have no idea where that diff came from, but at least the packagelist looks sane: https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/lastSuccessfulBuild/artifact/packagelist_rsync_landing-013-vivid/*view*/ this means that dbus-test-runner wasn't actually published with the silo, so nothing to worry about.18:45
robruboiko: did you have this silo since before last friday? could be a glitch from the new production rollout.18:45
boikorobru: yes, I have it since before the update18:46
boikorobru: but ok, if it was not published I guess it is fine18:47
robruboiko: yep, not even in the PPA either. just some inconsistent state in the jenkins server somehow. my only guess would be a glitch when syncing silo contents from the old server to the new one but I'm not sure how it would happen.18:47
brendandrobru, well stuff appears in the changelog that is *already* in the uploaded package18:48
robrubrendand: but like, the changelog as it appears in the upload matches the changelog as it appears in the diff right? the diff is accurate, it's just the changelog that's wrong?18:50
brendandrobru, seems to be just the changelog - the changes that are mentioned in the changelog don't appear in the diff18:51
mterryrobru, looking at that packaging diff...18:51
mterryrobru, python-tornado got added?  for tests?18:51
robrumterry: no idea ;-)18:52
mterryrobru, who do I ask about that?  (I'd also like to advocate to them to use python3-tornado if possible)18:52
robrumterry: that would be pstolowski18:53
mterryrobru, I don't like this method of packaging-ack -- it's so far after the MPs land, if there is a suggestion like this, it's a pain to correct, so I feel like I should just say OK and fix it in post18:53
robrumterry: but the MP didn't land? this ack is pre-publication18:53
mterryrobru, well but it's post silo-bundling.  Which is a bunch of work that someone has already done -- and blocking one change like this blocks the rest of the silo.  Vs at MP-review time18:54
robrubrendand: sounds like you're describing http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/view/head:/citrain/build.py#L547 this... thing. I will be touching that code today but I'm not really sure how to improve upon that in particular.18:54
robrumterry: I agree, it's definitely suboptimal. I'm going to be making some changes today that makes the diffs appear at build time rather than publish time, so maybe that can alleviate your worries. other than that I'm not sure how we'd get core dev acks pre-build.18:55
mterryrobru, if we were pulled in at MP time.  Just have the project not pre-approve anything that touches debian/ until a dev reviews18:57
mterry*top-approve18:57
kenvandineso maybe a packaging ack before the MP is approved18:57
kenvandinebefore the silo18:57
robrumterry: that's something you'd have to work out at a per-project level though. the train doesn't enforce top approving MPs until publish time.18:57
robrumterry: like, the train has no way to enforce any sort of policy *before* you get a silo ;-)18:58
mterryrobru, but I could imagine at the same time it enforced top-approving, it could check that there was an approved review labelled "packaging" -- if projects new they'd be rejected unless they had that...  they'd make it happen at MP time18:58
mterry*knew18:59
kenvandineit would be to their best interest anyway18:59
robrukenvandine: agreed, but the issue is how can we communicate that to them.18:59
kenvandineknowing if the packaging got nack'd would mean more work later18:59
kenvandineunderstand18:59
kenvandinei just think mterry has a good point19:00
kenvandinea nack after all the time has been spent getting through silo testing19:00
kenvandinejust to have to redo all that19:00
kenvandinekind of sucks19:00
robrumterry: kenvandine: i agree with your points, I think you should raise this with slangasek and we can schedule a more in depth meeting on the topic. right now I'm sort of just putting out fires and can't really change this behavior today.19:00
mterryIt's a lot of (silent) social pressure on the reviewer to approve19:00
kenvandinerobru, understood19:00
mterryrobru, sure didn't mean to add to your load  :)19:01
kenvandinei know i feel the same way, i feel bad giving a nack19:01
kenvandinealthough, i haven't found many i wanted to nack though19:02
robrukenvandine: yeah I hear you, I've also felt that pressure even just asking for acks, especially in rtm, it's like "qa just spent 3 hours verifying this, don't you dare nack it"19:02
mterryrobru, as for that review itself, I mean, sure.  It doesn't seem to be doing anything insane, so ACK.  But I would like to converse with pstolowski when he's around19:02
robrumterry: thanks.19:02
mterrykenvandine, but just a conversation point -- things that aren't so bad as to NACK but should be fixed ideally19:02
kenvandineindeed19:03
robrumterry: kenvandine: https://bugs.launchpad.net/cupstream2distro/+bug/1418699 filed a bug for you guys19:09
ubot5Launchpad bug 1418699 in CI Train [cu2d] "Packaging ACK workflow is sub-optimal." [Undecided,New]19:09
* mterry hugs robru19:10
robru;-)19:10
jdstranddbarth: fyi, I uploaded apparmor-easyprof-ubuntu to rtm silo 000 and it successfully built, but the silo needs to be configured19:14
jdstranddbarth: I tried to do it myself but it failed19:14
jdstrandERROR apparmor-easyprof-ubuntu was not in the initial list of components for that silo. Please ask the trainguards to reconfigure this silo for you.19:14
jdstrandseems I used to be able to do that...19:14
jdstrands/configured/reconfigred/19:15
robrujdstrand: you're a core dev right? you should be able to reconfigure. the error you quoted is from the build job though19:15
robruor, wait...19:15
jdstrandI am19:15
jdstrandI'm not the lander though... perhaps that is the issue?19:15
jdstrandrobru: yes, that is from the console output19:16
jdstrandrobru: I clicked the Reconfigure link from the spreadsheet and it took me to a page that had 'Build' at the bottom19:16
robrujdstrand: oh right. you have permission to do this you're just calling the wrong job.19:16
jdstrandeverything looked ok in that jenkins page, so I tried19:16
dbarthso you can reconfig the silo?19:16
dbarth(i don't have the rights for adding new branches myself)19:17
robrujhodapp: the 'reconfigure' link is the unpriviledged one that non-core-devs use, it doesn't let you add packages. you should go to the 'landing team tools -> assign silo' menu and it'll do a super-reconfigure for you19:17
robrujdstrand: ^19:17
robrujhodapp: unping, sorry19:17
jdstrandrobru: ok, looking19:17
jdstrandrobru: where are landing team tools?19:18
jdstrandI feel like I have done this before...19:19
robrujdstrand: in the menubar right next to 'help'19:19
jdstrandah19:19
robrujdstrand: just make sure you select a cell on the row you want to reconfigure before clicking that, and it should do the right thing19:20
jhodapprobru, np :)19:20
robrustupid j<tab> completing the wrong name ;-)19:21
robrujdstrand: got it working? it should pop up a little dialogue confirming which spreadsheet row you're acting on, then a link that says 'click here then click build' or something like that.19:23
jdstrandrobru: yes, seems to have worked19:23
robrucool19:23
jdstrandFinished: SUCCESS19:23
jdstrandrobru: thanks!19:23
robrujdstrand: you're welcome19:24
jdstrandthat's what I was looking for ^19:24
jdstranddbarth: ok, I think we are in business19:24
jdstranddbarth: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-00019:24
* jdstrand is performing the build step now19:25
* jdstrand is working to fix that ^19:27
robruthat's curious, I'm not sure why it would report that error *after* reporting it was ready to build. seems out of order19:28
jdstrandI went to tht ebuild step and put apparmor-easyporf-ubuntu in the list to rebuild with watch only19:28
robrurather, it *is* out of order, I'm just not sure how it got that way19:28
jdstrandthat was a mistake19:28
jdstrandso now I'm building with only watch only19:29
robrujdstrand: oh I see, yes "rebuild" and "watch" are mutually exclusive. that makes more sense.19:29
robrujdstrand: I was thinking that status was a stale leftover from when you were having trouble reconfiguring.19:29
dbarthjdstrand: sweet !19:31
dbarthi'll take the silo for testing tomorrow morning, thanks for adding the package19:32
jdstrandok, everything look ok now. the job was successful, the bot picked it up, just the spreadsheet and the dashboard need to catch up19:36
davmor2pmcgowan: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1418707 this may not be unity8 but I thought it a reasonable place to start :)19:45
ubot5Launchpad bug 1418707 in unity8 (Ubuntu) "Vivid Random lockups" [Undecided,New]19:45
pmcgowandavmor2, we always blame unity8, kgunn  lovers that19:46
pmcgowanloves even19:46
davmor2pmcgowan: I blame Saviq for most things anyway and when it's not his fault it is normally ogra_ 's it's winds up getting sorted in the end, this time though I think it is lower in the stack to be honest it's too random and on too many things for it to just be unity8 but it is a good start point, I think you might be onto something with a hal/dbus issue possibly19:49
pmcgowandavmor2, need to chat with rsalveti on that19:50
* rsalveti reading19:50
rsalvetiit's probably unity8 :P19:50
davmor2rsalveti: yeah blame Saviq ;)19:51
rsalvetidavmor2: is it locking up completely?19:51
rsalvetiI mean, can you see unity8 after pressing power coming from a suspended phone?19:51
rsalvetiis the clock stuck19:51
rsalvetibecause I got some serious lock ups with rtm as well19:52
rsalvetidavmor2: also, could you use adb normally?19:53
davmor2rsalveti: clock has been stuck, and clock missing from the welcome screen,  apps randomly stop functioning and eventually close, scopes will stop taking input and the scope will restart or unity8 will and so on19:53
rsalvetioh, sounds like it's quite broken indeed19:53
davmor2rsalveti: it's completely random as to what dies and when19:53
rsalvetidavmor2: is that only happening with qt 5.4?19:53
rsalvetidavmor2: got your syslog?19:54
davmor2rsalveti: no mako had no QT5.4 and was doing the same19:54
davmor2rsalveti: that's the weird thing there isn't much showing up anywhere19:54
davmor2let me grab logs for you19:54
rsalvetiright, guess I'd need to use and see what happens19:55
rsalvetiphablet@ubuntu-phablet:~$ ifconfig19:55
rsalvetih�ؾ(��: error fetching interface information: Device not found19:55
rsalvetithat's interesting19:55
rsalvetivivid/mako19:55
rsalveticyphermox: ^19:55
davmor2yeah crazy crap like that :)19:55
davmor2rsalveti: that might be because the sim stuff is totalled maybe19:56
davmor2rsalveti: adding syslog from mako (none Qt5.4) now19:58
cyphermoxyikes19:58
cyphermoxrsalveti: so something gets borked on the system at a very low level19:59
rsalvetiyeah19:59
pmcgowanrsalveti, could there be some mismtach between rootfs and android hal stuff19:59
rsalvetiioctl(4, SIOCGIFCONF, {96, {{"lo", {AF_INET, inet_addr("127.0.0.1")}}, {"wlan0", {AF_INET, inet_addr("192.168.1.61")}}, {"h���", {AF_INET, inet_addr("191.18.192.182")}}}}) = 019:59
cyphermoxis that always the case on mako, latest image or just on your system?19:59
rsalvetiioctl(4, SIOCGIFADDR, {ifr_name="dummy0", ???}) = -1 EADDRNOTAVAIL (Cannot assign requested address)19:59
rsalvetiioctl(5, SIOCGIFFLAGS, {ifr_name="h���", ???}) = -1 ENODEV (No such device)19:59
rsalvetiwrite(2, "h\244\367\276: error fetching interface i"..., 61h���: error fetching interface information: Device not found19:59
rsalvetiyeah, just installed latest on mako + apt-get update/upgrade20:00
cyphermoxany changes to android?20:00
rsalveticyphermox: nops20:00
rsalvetifor months20:00
cyphermoxkernel then?20:00
rsalvetipmcgowan: nothing really changed20:00
cyphermoxI don't see why else you'd have an interface with a corrupt name20:00
rsalvetilatest kernel change happened on jan 2020:00
davmor2rsalveti: krillin syslog attached too20:01
cyphermoxifconfig doesn't work, but does ip link ?20:01
rsalveticyphermox: yes: http://paste.ubuntu.com/10078645/20:01
rsalvetidavmor2: thanks20:01
rsalvetilet me reflash latest20:01
cyphermoxwow20:02
cyphermoxso something got broken in ifconfig20:02
rsalvetiusual whoopsie respawn20:03
rsalvetithis needs to be fixed asap20:03
cyphermoxhrm, no recent change to net-tools20:04
rsalvetiyeah, reflashing to make sure20:04
cyphermoxit must have been a bad flash, I see no other reason\20:04
davmor2rsalveti, cyphermox: it could always be part of the issues that I have been fighting all day :)20:08
rsalveticyphermox: nah, latest mako, flashed with --bootstrap, same issue20:10
rsalvetimako v90 vivid20:11
rsalvetilet me first revert this annoying whoopsie change20:11
davmor2rsalveti: my ifconfig looks quite normal :(20:12
rsalvetidavmor2: weeerrid20:13
davmor2rsalveti, cyphermox: http://paste.ubuntu.com/10078785/20:13
rsalvetiyeah, wonder if that might be might device somehow20:14
rsalvetibut nothing really changed here20:14
rsalvetiwill flash another image and see20:14
rsalvetirtm should be working20:14
davmor2rsalveti: did you see anything interesting in the syslogs by the way?20:15
rsalvetidavmor2: nothing major, no20:16
davmor2rsalveti: I'm off tomorrow but jibel has had a similar experience with his mako on vivid today20:16
rsalvetidavmor2: sure, will give it a try and see20:17
rsalvetiwe need to get vivid to work20:17
rsalvetiboiko: any news for silo 9?20:17
rsalvetijust before you go EOD, wanted to land this today still20:18
boikorsalveti: back from coffee, silo 13 landed, let me rebuild telephony-service20:21
rsalvetigreat, thanks20:21
dobeycihelp: can we get autopilot tests enabled for MPs to lp:pay-ui in the same way we have for lp:unity-scope-click? lp:pay-ui has a "make autopilot" target to run them. thanks.20:41
rsalvetitedg: what are we missing still in order to be able to land silo 3?20:45
cyphermoxrsalveti: in that case I'll flash my mako now see if I get that too20:49
tedgrsalveti, I haven't gotten to testing it yet20:50
rsalvetitedg: alright, will give it a try20:50
rsalvetireally wanted to land that as well20:50
tedgI am too. :-)20:50
tedgrsalveti, Just FYI, I can still break it in a couple cases, but this makes the phone much more usable. I think we need a bigger fix to get to 100%.20:51
rsalvetitedg: what are the use cases that are still broken?20:52
rsalvetiright, we can still land this if it improve things at least20:52
tedgrsalveti, I can get it to show a notification when changing levels in machine-vs-machines, but not on every bullet like before.20:52
rsalveticyphermox: yeah, got that with rtm as well, something is really broken with my device20:54
rsalvetiwill reflash android again20:54
tedgHmm, the music app is crashing for me... anyone else?20:57
tedgOh, is this the delete the cache thing?20:57
ahayzentedg, if it says unsupported schemas then yes20:58
ahayzentedg, instructions here https://lists.launchpad.net/ubuntu-phone/msg10939.html20:59
josephtdobey: I'll add a task to our sprint backlog for that20:59
tedgYup, that was it.21:01
boikorsalveti: silo approved ^21:02
dobeyjosepht: no way to bribe for expedited enablement there? something i can make a branch for myself and propose?21:02
josephtdobey: lemme check, I think it's a pretty simple thing to do.21:03
rsalvetiboiko: awesome, wiell land21:04
rsalveti*will21:04
tedgrsalveti, It works for me, are you seeing the same?21:04
rsalvetitedg: waiting my device to flash and will check21:05
cyphermoxrsalveti: I don't get an issue with ifconfig but I booted and got no wifi device21:07
rsalvetihm21:08
josephtdobey: pay-ui is an app not a unity-scope, right?21:12
dobeyjosepht: it is a click package not a deb, yes. it's sort of an app. it is technically neither an app nor a scope21:12
jgdxcihelp: I'm seeing a ap test failure in u-s-s on mako [1] which I cannot reproduce on my own mako. Seems to fail consistently too; not sure what I should do. [1] https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/1038/21:15
cyphermoxrsalveti: nevermind, it's good after a reboot21:16
jgdxand here's the same again https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/992/21:16
josephtdobey: I've got an MP out to add autopilot testing to pay-ui.  It might not get deployed until fginther wakes up though.21:34
dobeyok21:34
dobeythanks josepht21:35
josephtdobey: my pleasure21:39
tedgrsalveti, good?22:01
rsalvetitedg: music-app seems fine here, testing your package now22:03
robruTime is an illusion. Lunchtime, doubly so.22:03
rsalvetitedg: yeah, still got a few issues with it22:13
rsalvetisometimes showing when pause/playing22:13
rsalvetiwhen jumping to the next song22:13
rsalvetibut something else is seriously broken here22:13
tedgI think the issue is that we're getting a "hickup" of things connecting and disconnecting.22:14
tedgSo each song Pulse sees as a new connection.22:14
tedgWhat I think we need is a little more perspective, and not only using Pulse to decide when we change roles.22:15
tedgrsalveti, Anyway, don't consider this the full fix, but wanted to get something landed that made things better.22:25
rsalvetiit didn't improve much for me though22:26
rsalvetistill investigating22:26
rsalvetibut I got other serious issues with my system22:26
rsalvetione time after rebooting I had 3 pulseaudio running as phablet22:26
rsalvetiand indicator-sound failed to start22:26
rsalvetipulse will just tell what is the current role22:27
tedgWell, not really. It tells us who the last person connected was and their role.22:30
rsalvetiright, sorry, by current I wanted to say the last one active/connected22:31
tedgI think the problem is that we're getting multiple active/connected per app.22:31
tedgi.e. machines-vs-machines there's a different for background and effects.22:31
tedgSo I think looking at the last connected is what the source of the problem is.22:32
tedgWe need to be a bit more clever22:32
rsalvetioh, ok, got it22:33
rsalvetiyeah22:33

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