/srv/irclogs.ubuntu.com/2013/09/17/#ubuntu-ci-eng.txt

fgintherplars, essentially, it was the desire to test a touch + mir enabled image in parallel with the regular images14:30
fginthermir requiring a small bit of extra work to turn on14:30
plarsfginther: sure, we can turn on mir by just touching a file right?14:31
fgintherRight.14:31
fgintherI was assuming this is dependent upon the work to restructure the touch slaves14:31
plarsfginther: it's a complete extra test run though, it's something we could look at, but we should talk about how to differentiate the results in the dashboard and all that14:32
plarsfginther: yes, it's partly dependent on that, but could be done before14:32
fgintherplars, that sounds very cool.14:33
cjohnstonbug #1234514:33
ubot5bug 12345 in isdnutils (Ubuntu) "isdn does not work, fritz avm (pnp?)" [Medium,Fix released] https://launchpad.net/bugs/1234514:33
cjohnstonsweet14:33
plarsfginther: another possibility is that if we have some specific tests we'd like to target at running under mir, we could set it up as part of the regular test run14:33
fgintherplars, didrocks also mentioned a ppa for testing with mir, but I didn't fully understand how that fit in14:33
plarsfginther: that's a whole different issue14:34
didrocksfginther: plars: I'm writing an email14:34
plarsfginther: one thing at a time :)14:34
fgintherdidrocks, thx14:34
plarsfginther: if we have a specific test to run with mir, we could add setup/teardown for that test to enable mir, reboot, run the test14:34
didrocksdone14:35
fgintherplars, that would be interesting, perhaps running the unity8 suite under mir would be just as helpful as a full image test14:35
plarsfginther, didrocks: doing it like that would be much better I think, because we wouldn't have to repeat a lot of the things that are not relevant to mir (install, default smoke, etc)14:35
didrocksplars: so, you handle that, adding the ppa and so on?14:36
plarsdidrocks: let me go read the mail, typically no14:36
didrocksas mir doesn't have specific tests, I think you will add unity8 and all apps tests14:36
didrocksplars: so, does the email makes sense? any way we can run that automatically?14:40
plarsdidrocks: sorta, I responded. For the image testing though, the input is exactly what you would expect: an image14:41
plarsdidrocks: I've set up a temporary one-off for some qt stuff recently, I could do the same but it's not a long term fix14:42
plarsdidrocks: ideally this shouldn't be running long-term though right?14:42
didrocksplars: ok, answered ;)14:42
didrockslet's do that14:42
plarsdidrocks: so you will get us an image with this?14:42
didrocksplars: hum? no, we need latest image + a ppa14:43
didrocksis this possible?14:43
plars<plars> didrocks: sorta, I responded. For the image testing though, the input is exactly what you would expect: an image14:43
plars<plars> didrocks: I've set up a temporary one-off for some qt stuff recently, I could do the same but it's not a long term fix14:43
kgunnfginther: ping14:43
didrocksand we can't add ppas to anything in UTAH?14:43
didrocksplars: ^14:43
plarsdidrocks: we could, but we've actually been actively moving away from depending on any kind of ppa as that's where the images are going14:44
didrocksplars: right, but this kind is tested in isolation14:44
didrockscode*14:44
didrocksthe goal for it is to not land for the coming week in distro14:44
didrocksbut we need test14:44
plarsdidrocks: sorry, just trying to figure out where this fits best. It seems like it's sort of like autolanding testing, except you don't want to autoland it, right?14:45
plarsbut it's not really image testing either14:46
didrocksplars: right, it's while Mir is in its own silo14:46
plarsfginther, didrocks: I think we need to discuss further where we can fit stuff like this into the ci - I don't think it's a perfect fit anywhere at the moment, and typically things like this have been hand tested in the past by the dev teams I think (by doing what you suggest, pulling the ppa into a latest image and running tests on it)14:47
plarsit could probably be shoved in to a number of places, but it sounds like something we might need again14:47
didrocksplars: we need the support for dailies on the phone14:47
didrockswhat jibel did at 95%14:48
plarsdidrocks: not sure what you mean14:48
didrocksbut asac is telling me there is nobody at the moment to finish this support14:48
asacdidrocks: fginther can look at it i assume14:48
didrocksplars: if the dailies support testing phone, we would be done (it's basically the same contect)14:48
didrockscontext*14:48
asacafter we got the MP straight14:48
didrocksasac: Mir needs 5 components to be built to test14:48
asacalso we said that jibel would still support us14:48
didrocksasac: as they change ABI14:48
asacand we said we might be able to dodge it14:48
asacif we cant14:49
asacwe have to go back14:49
didrocksasac: so you can't do that at the MP level without having the notion of "you need this, this and this"14:49
didrocksand for this week, what sergio needs, is testing14:49
asacdidrocks: right. thought we asked them to change ABI/API decently14:49
didrocksasac: they still plan to do it everyday14:49
didrocks(and now, the devs tries to push back if you follow #ubuntu-mir btw)14:49
didrocksso short term solution, I would say, let's do manual testing if we can't get anything else14:50
didrockspulling the iso14:50
didrocksinstalling the ppa (once Mir builds…)14:50
didrocksand running unity8 + apps tests14:51
didrocksfginther: plars: makes sense? ^14:51
asacprobably14:52
asacdidrocks: check with fginther what it takes to bring his way of doing things into daily-release testing14:52
fgintherdidrocks, plars, if it's just a matter of we need an image first, we can build an image on jenkins and feed that into smoke14:52
asacdidrocks: feels like its just changing the ppa to use for testing14:52
asacinstead of merge ppa, test with the release ppa14:53
asacfginther: right. so what we want is to be able to produce an image from daily-release ppa14:53
didrocksasac: but the Mir MP will fail14:53
didrocksbecause it's changing the lib14:53
asacfginther: that either includes all or just a subset14:53
didrocksso, you don't have the unity-mir, u-s-c and platform-api you need to test with14:53
didrocks(yet)14:53
asacdidrocks: sorry. i phrased correctly. was saying that if we need testing at daily-release level so badly14:54
asacwe can see if our MP solution for phone provisioning could work there14:54
asacdidrocks: i understand that part14:54
asacbut guess we have to reside on manual testing14:54
asacthough if we have a way to send a job to the lab saying: take image x), add ppa A and install packages C,D,E14:55
asacwe could use that rather than manual14:55
fgintherasac, if that's what we need, than we should just build the image that contains all of that14:56
plarsasac: this is sort of what I suggested earlier when I thought it was just a matter of enabling mir. What is actually wanted is to run pretty much all the tests though, so it's a complete extra test run14:56
plarsright14:56
plarsso that's when it became apparent that it should probably just be a whole image set up the way it's needed (mir enabled, packages installed, deps in place)14:56
plarsit's still a new test run, but unless what's wanted is a continuous run of this (unlikely?) It's a one-off sort of like what we did for qt5114:57
fgintherplars, asac, I can queue up a job to create this image. just want to make sure this works for everybody and what the schedule should be14:58
plarsthat would be in the case of "this is a quick test to make sure nothing breaks before we merge and land this"14:58
asacfginther: we need to select parts14:58
didrocksasac: yeah, otto provides that on the desktop for a long time14:58
didrocksasac: and the phone prototype that jibel has does as well14:58
didrocksit's juts a question of finishing up14:58
plarsif this is way out still, then manual testing probably makes more sense until it's almost ready14:58
asacdidrocks: jibel says its not htere14:58
asacjibel: ^^14:58
asacjibel: so seems we wont be able to dodge getting your stuff in14:58
asaci hoped i could14:58
fgintherkgunn, pong14:59
didrocksasac: weird, it was almost there before my holidays AFAIK14:59
didrocksbut I'm unsure about the ro image though, maybe his work was pre-ro image14:59
asacdidrocks: otto is lxc based etc.15:00
asacthat seems to be not cleared on kernel side etc.15:00
fgintherI'm not saying we abondond jibel's work, but I would prefer a solution that fits in with the existing infrastructure15:00
asacso its a dead end potentially...15:00
didrocksasac: no for the phone one15:00
fgintherfor the next 4 weeks15:00
didrocksAFAIK15:00
asacjibel: can you tell us what your stuff is?15:00
didrocksit's using the same code, but the lxc part15:01
asacjibel: and how far we are?15:01
asacok15:01
asacso lets have a call on that one i guess15:01
asacdidrocks: lets talk about todays landing first :)15:01
asacwhere do we stand with those?15:01
asaconce we have those pushed we can talk about phone testing15:02
didrocksasac: remember I told I needed to go at 5PM?15:02
didrocksI can go back afterward15:02
didrocksbut I have an appointment for the wedding15:02
didrocksI'm already late15:02
didrocksand stuck in discussion with the Mir guys15:02
asacdidrocks: we can do that call tomorrow15:02
asacdidrocks: just wanted to check where we stand with what sil2100 wanted to land etc.15:02
didrocksapparently, the devs don't want to do library proper development15:02
asaci can deal with him alone :)15:02
asacdidrocks: yeah. however, thats for the special mir PPA15:02
asacso we can dodge that discussion for 2 more days15:03
asac:)15:03
asacdidrocks: so go to a wedding15:03
didrocksasac: well, 2 more days :p15:03
didrocksI don't go to a wedding, I go to prepare my wedding :p15:03
asacright. hence, lets first sort the other landings15:03
asacah15:03
asacand then talk about that lib thing15:03
asacsil2100: so ... where do we stand :)15:03
asacsil2100: can you try what we planned to get in?15:04
asaci assume stuff has built by now?15:04
didrocksasac: most of the thing built, see the link I pasted to you an hour ago15:04
* didrocks goes now15:05
asacsil2100: so content hub stuff is inproposed?15:06
asacnice15:06
asacsil2100: i think we wanted to try scopes and application #2 as well for today15:07
asacsil2100: i think plars and psivaa are happy to help testing if you explain how to do that15:07
asacMirv: ^15:07
sil2100asac: ACK15:12
sil2100asac: I'm testing those on the phone now15:12
cwayne1asac: hi, just wondering if there was any update on lightdm?15:27
jibelasac, my stuff uses the same runner than we use on desktop, with the major difference that we cannot use overlays fs on phone and the device is reprovisioned between each run (takes between 6min on N4 and N10 to 9min on NG) instead of just dropping the overlay15:30
asacsil2100: are the content-hub things out of proposed now?15:30
asacjibel: where does it stand? how can we hook what you have up to the system?15:31
jibelasac, it requires full RW access to the FS which I think can be done by remounting / RW upon provisioning15:31
asacright15:31
asacthats a workaround for now15:31
asacChickenCutlass: so let me know what you want to land15:32
asacbefore multimedia15:32
ChickenCutlassasac, ok, yes we will15:32
sil2100asac: yes, it's all in archive15:33
jibelasac, the nodes are labeled by the name of the devices so we should be able to plug then to the daily-release machinery by /just/ adding the labels to the list of executors on the saucy_daily-release job15:33
jibelasac, that part is untested15:34
cwayne1asac: any update on lightdm15:34
asaccwayne1: so that one is discussed in management15:34
kgunnfginther: sorry...i walked away15:34
asaccwayne1: do we need it or not ... given the locales are connected we want it i think15:34
kgunnfginther: we were wondering...15:34
cwayne1asac: from a customization point of view we need it15:35
kgunnwe basically want to bump the mir server so on every mp15:35
asaccwayne1: just need to be tested15:35
asaccwayne1: that involves running all autopilots15:35
asacand also ensuring it doesnt break utah15:35
kgunnwe were wondering if we could modify the jenkins bot to do this15:35
kgunnas part of the merges done for mir ?15:35
ricmmkgunn: bump ABI in *each* commit ?15:35
kgunnricmm: yep15:36
cwayne1asac: ok, that sounds reasonable15:36
asaccwayne1: ok... thats ubuntu-touch-session?15:36
asacthat feels like work we cant do short term15:36
asaccwayne1: so you can help us by supporting us in that effort15:36
fgintherkgunn, probably, we just need to modify the value in the packaging before building?15:36
asaccwayne1: otherwise it will wait until we have cleared the stuff we need to land before beta freeze15:36
cwayne1asac: how can i help support it?15:37
asaccwayne1: ubuntu-touch-session is not in CI?15:37
cwayne1asac: ?15:37
fgintherkgunn, but you also want this change to make it into trunk, correct?15:37
kgunnfginther: yes...it would be bumping on our mir trunk15:38
asaccwayne1: so ... the landing ask ask for an update to ubuntu-touch-session15:38
asacwhich probably will bring it into the image15:38
asaccwayne1: what we want is to have that change, and have someone test it on phones and run all autopilots15:38
asacif you have a good log of those succeeding you can just upload them after checking here15:38
kgunnfginther: could we do it as early as today?15:38
fgintherkgunn, that's a little more work, but also doable.15:38
fgintherkgunn, I think so15:39
asackgunn: sounds not like short term15:39
kgunnfginther: you would be a life saver15:39
asaccertainly doable though15:39
fgintherkgunn, do you happen to have a script for automating the bump?15:39
cwayne1asac: im happy to test it on the phone15:39
kgunnfginther: we can make one15:39
asaccwayne1: when are you awake?15:39
kgunnso says robert_ancell15:39
asacsil2100: are the app tests going well?15:39
fgintherkgunn, thanks, I'll start getting the other bits lined up15:39
cwayne1asac: EST15:39
kgunnfginther: awesome!15:39
robert_ancellfginther, I'll write one now15:39
* kgunn 's "i owe you a beer" ledger grows longer15:40
sil2100asac: problematic, I might have found an issue15:46
asacsil2100: oki...15:47
asaclets not rush15:47
asacsil2100: if its hard to figure, lets try scopes instead i guess15:47
asacsil2100: mayube explain plars and sivaa how to test these15:48
fginthersil2100, is this the same problem you've been seeing on daily release (Unauthorized when talking to launchpad)? http://10.97.2.10:8080/job/autopilot-gtk-saucy-armhf-ci/25/console15:54
fginthersil2100, it's intetmittent15:54
sil2100fginther: no, we had could not resolve host etc. issues on daily-release mostly15:55
asacanyone knows if we still see DNS issues?16:10
asacor are those gone?16:10
sil2100asac: yesterday I saw some on intel sadly - today I didn't, but maybe didrocks saw?16:13
robert_ancellfginther, http://paste.ubuntu.com/6120034/16:13
sil2100asac: the apps issues are resolved, I'm preparing for release \o/16:14
asacsil2100: nice... you think you can try the scopes as well?16:14
asacbut guess that requires lots of testing :)16:14
asacsil2100: mayve you can explain to plars and psivaa how they can find which packages to try?16:14
asacthey can certainly tests in parallel then16:14
asacsil2100: but dont hold back pushing the apps :)16:15
fgintherrobert_ancell, thanks16:16
asacsil2100: did you try to take all aopps16:17
asacor just the two we marked?16:17
asacdont care either16:17
asacjust wondering if we might even get more than i hoped for :)16:17
sil2100asac: I was testing history-service, dialer-app and messaging-app basically, and also re-testing ubuntu-keyboard in the meantime16:18
mandelasac, ping16:19
asacmandel: hi16:19
asacsil2100: kk16:20
mandelasac, hello! I was told that I should ping you (or didrock) if I needed to land bug fixes for the phone image (ubuntu-download-manager package), is that correct?16:20
asacmandel: who is your techlead/manager?16:20
mandelasac, _ralsina16:21
mandelasac, and _alecu16:21
asacmandel: ok... you can ask him to add your landing to the spreadsheet and we will process it asap16:21
asacmandel: just ensure its cleawr that its a bugfix only release16:21
mandelasac, ok, will do16:21
mandelasac, yes, no new features, just bugs16:22
asacmandel: how big is the diff?16:22
mandelasac, hm.. there are several mp but not less than 200016:22
mandelasac, I can have a small diff per bug16:22
mandelrather than a crazy diff16:22
asacmandel: think is not needed16:24
asacmandel: just add it to the landing list16:24
mandelok16:24
asacmandel: once we get closer you might want to offer support to test autopilots locally to give up front confirm that stuff is good16:25
mandelasac, hmmm autopilot tests with the downloader are going to be interesting.. since is a daemon16:26
asacmandel: its not about your tests16:26
asacmandel: its about confirming that your cdhanges dont break tests of other apps16:26
asacetc.16:26
mandelah, ok16:27
asace.g. install your stuff, run a few autopilots for apps and unity16:27
asacif thats confirmed, we can fastpath it more easily16:27
asacsil2100: hey ... so folks say we should at least file a bug with the log and add it as a comment in case something odesnt make it16:43
asacguess makes sense16:43
asacnot sure how to do that16:43
asacfginther: so what came out of the discussion on how we could easily test custom images with ppas and package list added?16:43
asacon demand?16:44
asacfginther: was the outcome that we should just finish jibel's stuff?16:44
fgintherasac, the solution to me is to just build the image somewhere else first16:44
fgintherno one replied to my suggestion yet16:45
asacfginther: hmm. what does that mean "build the image somewhere else first"?16:45
asacfginther: not as part of jenkins?16:46
fgintherbuild the image as part of a separate jenkins job, not while trying to do the actual smoke test setup16:46
fginthera job that does nothing more than produce an image16:46
asacfeels reasonable16:47
asacfginther: so we use that for both: MPs and daily-release? or are you talking daily-release stage only for now?16:47
fgintherasac, I'm talking about smoke test16:47
asacfginther: but smoke test we have phone testing right now16:48
fgintherthe topic was triggered by wanting to test smoke with mir enabled16:48
asacsmoek test == daily image testing on reports.qa.ubuntu.com16:48
asacfginther: hmm. ok then i think the topic was mixed up\16:48
fgintherindeed16:48
asacwhat i am talking about is to have something to test our daily-release ppa content16:48
asacbefore we publish it16:48
asaca) all that is in there16:48
asacb) just a subset of changes added against the last image16:48
asacright now sil, mirv and didrocks arrange that manual16:49
fgintherright16:49
asacso i wondered if an dhow we can reuse either what utah does in image testing or what you did in MP16:49
asacsil2100: am i right that if i take last green image and dist-upgrade to the daily-release ppa16:50
asaci get everything currently staged?16:50
fgintherasac, I think we can engineer a solution close to what we're doing in upstream merger. But honostly I haven't had time to look at jibel's stuff yet to see if that would be easier.16:52
asacyeah16:52
asacguess cant be created in a day anyway16:52
asacreally think we want a microservice16:52
asacthat takes and image +ppa + a set of packages to install from that16:53
asacand flashes, boots, etc.16:53
asac:)16:53
asacand reuse that everywhgere16:53
fgintherthat's pretty close to what we're already doing, we're just missing the ppa bit and that really isn't hard to add.16:53
fgintherit's a bit of a hack16:54
fgintherI'll talk to sil2100 and didrocks to make sure I'm not overlooking something16:54
* fginther back in a bit16:54
loolasac: here17:02
asaclool: hi :)17:02
asacyeah17:02
asacsil2100: so... lool and me had the idea if we could try "EVERYTHING" that is currently built in https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages17:02
loolasac: so perhaps we could start with listing all the changelogs + diffs of things in daily-build against saucy17:03
asacand see how autopilot acts up17:03
asaclool: yeah. if we had that we would clearly see more :)17:03
loolasac: so you're saying it's too costly for the time we have to spin up a side image that would have the PPA bits included17:03
asaclool: it would only help us if we could do one off image spins that only include parts of it17:04
loolI think we could17:04
asaclool: and at best be able to send that to our phones in the lab...17:04
asacbut that part we can do with fginther i feel17:04
loolwe could also build the image by hand until we find it's good enough, then let things through and build it17:04
asaclool: fginther basically said that his problem is getting the image to test17:04
sil2100asac: please wait with that17:04
asacrather than running the test17:04
loolbut that requires costly build image + upload image cycles17:04
asacsil2100: wait :)17:05
sil2100asac: we have an unwanted package in daily-build...17:05
asacsil2100: we discuss the plan17:05
asacso you are welcome to contribute :)17:05
asacsil2100: so if we had something to produce images nicely with a subset of stuff in there17:05
asacwe could send that to our phones17:06
asacright?17:06
asacand we could at least stop manually running the tests17:06
asacbut rather using our infrastructure to test17:06
asacsil2100: oh wait ... just ONE unwanted package?17:06
asaclool: so i think we can also make a job that does something like fginther does in MPs17:07
loolwhat is that?17:07
asaclool: he takes an image that is there, and then dist-upgrades it17:07
asacand after ppa-purges17:07
asacnot nice17:07
asacbut seems to work17:07
asac99% of cases17:07
asaclool: only problem when we get to RO17:07
loolwell that's fine, we could even publish the modified image17:07
asacright17:07
asaclool: anyway. i think thats all not good to do if we dont have everyone here :)17:08
asaccertainly nothing to start today17:08
loolok17:08
asacfor today what would help is getting a view17:08
asacof what is in thtere17:08
loolI can start the script thing17:08
asacthat isnt in sauch17:08
asacsaucy17:08
loolit's something I can continue tomorrow and can stop anytime17:08
asacthen we can look and see what subset we can try to pipeclean17:08
asaclool: i will get you into the standup for tomorrow morning17:09
loolbah, someone removed http://people.linaro.org/~lool/ and I just googled and found a link to a script I had published there, erf17:09
loolnow I need to find the original  :-)17:09
asachehe17:10
kgunnfginther: one thing about our mp builds....can someone tell us, which is which ?17:13
kgunnalan_g & I noticed there seems to be an android & armhf build17:13
kgunnwhat's the diff ?17:13
kgunnalso alan_g thinks there's a setup prob with the armhf one17:13
alan_gfginther: kgunn this looks like a config issue? https://jenkins.qa.ubuntu.com/job/mir-saucy-armhf-ci/7/console17:14
asacsil2100: what was the bad package you talked about?17:25
asacogra_: did the 53 image come out yet?17:25
ogra_yep17:25
asacogra_: not yet in qa it seems... guess not long ago17:26
ogra_https://system-image.ubuntu.com/saucy-proposed/ ...17:26
ogra_16:48 UTC17:26
asacogra_: hmm. adb shell makes me shell@...17:26
asacthink i am in the android container17:26
ogra_sounds like17:26
asacogra_: just try rebooting?17:27
asacunity is running17:27
ogra_whats after the @ ?17:27
asacand stuff17:27
asacshell@android:/17:27
ogra_yeah, thats the container17:27
asacis it sometimes that might go away on reboot?17:27
ogra_should be disabled by default17:27
ogra_try it17:27
asacour whole UI is surely working17:27
asacok just reboot?17:27
ogra_might be that some test you ran left the property enabled or so17:27
ogra_yeah, just reboot and see17:28
asacogra_: oh... yeah i had some complains17:28
asacsomething about adb props ... ro17:28
ogra_yeah17:28
asacok i am root@ again17:28
asacguess was a one time thingy17:28
sil2100asac: xpathselect - the new version of that package landed in daily-build, breaking unity stacks17:30
asacsil2100: where did that come in through?17:33
asacsil2100: do we have CI for that?17:33
asacsil2100: also ... arent unity stacks diverted to the experimental ppa right now?17:33
asacsil2100: anyway, did you kill it? i am dist-upgrading righ tnow17:34
asacand i dont see it coming :)17:34
* asac is brave and upgrades the whole lot :)17:34
sil2100asac: it got in by accident, we had a bug in the config - the config wasn't redeployed because of a typo etc.17:35
sil2100asac: I removed it from the PPA and fixed daily-build17:35
sil2100asac: I'm re-spinning unity now17:35
kgunnsil2100: ^ is that related to my query on experimental ?>17:37
asacsil2100: ok so i distupgraded everything. .. we have right now, i assume thats broken then?17:37
sil2100kgunn: I don't think so... but I would have to double-check17:38
asacunity at least still boots with all :)17:39
sil2100asac: not sure if it's broken, since it only causes a FTBFS for unity7 - but it still has xpathselect with features that are not supposed to be in saucy17:39
asackk17:39
asacsil2100: let me do a start on some tests17:40
asacto see17:40
plarsasac: all the latest touch_ro images just failed to install properly in the lab, I'm investigating locally but I can't see those devices any more17:53
plarsasac: I pinged rfowler, but I don't want to kick it off on another device since it's likely to kill those also17:53
plarss/another device/another device in the lab/17:53
asacplars: right17:53
asacthats awful17:53
plarslocal is fine to break, I'll fix that17:54
asacplars: do we have any log?17:54
plarsjenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-install-and-boot/148/consoleFull17:54
plarserr17:54
plarshttp://jenkins.qa.ubuntu.com/job/saucy-touch_ro-maguro-smoke-install-and-boot/148/consoleFull17:54
plarsasac: not much of use though, it seems to have just timed out17:55
asacplars: so did we manage to get a new phablet-flash?17:55
asacor do we still run a hacked version? i am sure its related?17:55
plarsasac: no, it's an official version that we have running on there now17:56
plarsasac: it ran fine for a couple of runs after installing it17:56
plarsasac: this is new with the current build17:56
plarsasac: anyone who tries to run a phablet-flash on touch_ro *needs* the new version, or else it will not work17:57
asacogra_: ^^17:58
asacmaybe the build is busted?17:58
ogra_no, i just flashed it fine here17:59
ogra_ogra@chromebook:~$ adb shell system-image-cli -i|grep version17:59
ogra_version version: 5317:59
ogra_version ubuntu: 2013091717:59
ogra_version device: 2013091717:59
ubot5Error: Ubuntu bug 20130917 could not be found17:59
ogra_using: sudo phablet-flash ubuntu-system --channel=saucy-proposed --no-backup -d maguro17:59
ogra_but yeah i always update phablet-flash before using it17:59
ogra_that should be a general rune of common sense for everyone anyway though18:00
ogra_*rule18:00
sil2100asac: running tests for the new scopes18:01
* asac hopes that bogus devices in the lab doesnt become a daily phenomenon :)18:02
plarsrfowler: strange, this is working for me locally18:05
ogra_do we dump the package version of phablet-tools into the log somewhere ?18:06
ogra_if not, we should :)18:06
plars  Installed: 1.0+13.10.20130916-0ubuntu118:08
sil2100asac: unity8 tests with the new scope version and libunity looks ok, passes tests18:08
plars  Candidate: 1.0+13.10.20130916.2-0ubuntu118:08
sil2100asac: with new unity-scope-home18:08
plarsso there was a newer one even since the one sergio did yesterday?18:08
* plars wonders what changed18:08
asacogra_: plars: so maybe mtp busted our automation18:10
asaci just saw a nice mount thing coming up18:11
asacand then the device was not adb'able18:11
asacogra_: plars: can you log into the machine and see if you can umount whatever it mounted?18:11
asacmaybe that helps18:11
plarsasac: log into what machine?18:12
ogra_asac, my devices are all adbable all the time18:12
plarsasac: oh, the host?18:12
ogra_no matter if the mtp mount is up or not18:12
asacplars: the host18:12
asacplars: see if something got mtp mounted etc.18:12
ogra_its a server, very unlikely it even has libmtp18:13
plarsasac: I don't see anything18:13
plarsasac: where did you see the mount message?18:13
asacplars: on the desktop :)18:14
asacscreen18:14
asacogra_: so maybe false alert :)18:14
ogra_yeah, would surprise me if that influenced adb much18:15
ogra_it might delay adb in coming up perhaps ...18:15
asacso sigh :)18:16
ogra_if timing is critically narrow for these jobs that *could* have some impact ... though i dont think thats very likely18:16
asacphones dead ... noone knows18:16
ogra_do we have feedback whats on the screen ?18:16
asacplars: do we not even see the commands we ran for flashing?18:16
asacin some log?18:16
ogra_do they sit in recovery ... fastboot ?18:16
ogra_google logo ... etc18:17
sil2100asac: ok, so after testing the libunity and unity-scope-home versions that are requested for release by "scopes #1" it seems to look ok from the touch point of view - but we still need to make sure it doesn't cause a regression in unity7 (which is still building now)18:17
asacogra_: you can try to use the in-lab camera :)18:17
plarsasac: not directly, but it's not hard to get at, and not anything too strange. It's doing just flashing the daily-proposed image for touch_ro18:17
asacpretty nice18:17
plarsasac: I ran the same command locally that gets run from jenkins and it worked here18:17
asacplars: but both mako and maguro failed at same time?18:18
asacthat sounds odd18:18
rfowlerplars: looks like you are talking in here...18:18
ogra_heh, we'r etalking split across both channels18:19
plarsyeah18:19
plarslet's just talk in #ubuntu-touch18:19
plarsmore people are in that channel that would care18:19
ogra_yeah18:19
plarsrfowler, asac: ^18:19
asacok18:20
asacfine18:20
asacrfowler: guess you are far away from those phones :)?18:21
asaci think we would like to extract some logs etc before trying to flash again18:21
ogra_asac, i have a theory, but need rsalveti to come back from lunch to confirm18:27
* rsalveti back18:34
rsalvetiogra_: what's up?18:34
ogra_rsalveti, we need to drop the "adbd spawns inside the container" stuff18:35
ogra_rsalveti, seems all tests fail18:35
ogra_my theory is: mtp sets the mtp property ... adbd respawns ... utah conncts exactly now and ends up inside the container18:36
ogra_so adbd on ubuntu never comes back since the one in the container is used18:36
rsalvetioh, right, let me think18:36
rsalvetiso it's a consequence of mtp18:36
ogra_it is fine using it manually since you never connect that fast18:36
rsalvetiright18:37
ogra_so thats why we never spotted it18:37
ogra_for disabling adb the container bit needs to go anyway i think18:37
rsalvetibut it's interesting that's getting inside the container18:37
rsalvetias at that time it'd have 2 adbd running18:37
ogra_why ?18:37
ogra_setprop changes the property, the current adbd dies and respawns18:38
ogra_upstart sets the property again on startup of the job18:38
ogra_that kills the in container adbd and spawns the ubuntu one again18:39
ogra_effectively plars connects exactly in that moment where upstart respawns the job but isnt done18:39
ogra_and hits the race18:39
rsalvetiright, but why is the first adbd dying18:39
ogra_because setprop brings down the gadget18:40
ogra_uh, we need to make the mtp upstart job safer and make it read existing props ... (not related to this issue though)18:41
ogra_it assues there is always adb and mtp ... if you want rndis it would break18:41
rsalvetiyup, as I said during the sprint18:42
ogra_it needs to read the existing property18:42
rsalvetiseems it only supports 2 modes18:42
rsalvetiat the same time18:42
ogra_yeah, but that might not be adb18:42
ogra_anyway, unrelated ... just saw we hardcode it18:42
* ogra_ will submit a fix later 18:43
ogra_lets first get the images testable again :)18:43
rsalvetiso trying to think a way to not get the android adbd completely disabled18:43
rsalvetias that's useful18:43
ogra_just make it a manual thing18:43
rsalvetibut guess chmod -x might do the work18:43
ogra_that would be a quick fix indeed18:43
rsalvetiinteresting, looking at the android init, there's not mtp + rndis in there18:44
rsalvetijust rndis + adb18:44
ogra_its in the device specific init.rc18:44
rsalvetiyup18:44
ogra_oh, you mean that18:44
rsalvetiso you either use mtp or rndis18:45
rsalvetias done in android18:45
ogra_yeah, i see18:45
rsalvetithat's why you have that option in android18:45
ogra_thats indeed intresting18:45
ogra_yep18:45
rsalvetithat you need to select which mode you want18:45
ogra_so no mtp in debugging mode in android ... never noticed that18:46
rsalvetiogra_: yeah, which is fine, as long we have an ui for that18:46
rsalvetibut topic for 14.0418:46
ogra_anyway, should we go with the -x fix ?18:46
rsalvetiogra_: so let's get back to your previous change, that removes adbd in lxc-android-config18:46
ogra_i know sergiusens might work on a finer grained change for the disabled adb18:46
rsalvetibut that would only be for the ubuntu side, right?18:47
ogra_which means we perhaps get a better fix before release18:47
ogra_well, it would have to handle the android side too as it is now18:47
rsalvetiright18:47
ogra_we cant leave it as is in either case18:47
rsalvetiindeed, let's just remove it for now18:47
sergiusensrsalveti, ogra_ I'll get that fixed since it sort of blocks me18:47
ogra_so lets do the quick fix with the option to get something better18:48
rsalvetisergiusens: what is your fix?18:48
sergiusensrsalveti, I'm looking at that now18:50
sergiusensdon't have the answer yet18:51
rsalvetisergiusens: should we push a workaround now then?18:51
asaci am not sure18:52
asacdoes plars have a workaround for automation?18:52
plarsasac: it seems to be working fine now, are we just getting lucky?18:52
ogra_asac, not easily, has to be in the image18:53
asacplars: what did you change?18:53
sergiusensasac, plars yes, just getting lucky18:53
ogra_asac, its a timing issue ... plars hit a race18:53
plarsasac: nothing, once I restarted adb and got the devices visible again, it just worked18:53
sergiusensogra_, asac plars there is a quick workaround18:53
asacdid we change anything? or is likelyhood still the same as before?18:53
asachmm18:53
sergiusensjust add the pre.d script that deletes adbd18:53
asacso what is interesting is that it happened on both sides18:53
asacerr both phones at same run18:53
plarsasac: well, something had adbd running on the host as another user, which didn't have the proper permissions18:53
sergiusenslucky as I was in android user shell, ran adb root and got to the ubuntu shell18:54
asaci personally would prefer a workaround18:54
asaci dont want this kind of luck :)18:54
ogra_asac, yes, we have a fix18:54
plarsgenerally I'd say this happens because either adbd dies, or someone kills it, then the next one to run adb <anything> gets the adbd ownership18:54
plarsthat's why we couldn't see the devices18:54
ogra_yeah18:54
plarsbut as for why that happened, don't know yet18:54
asacplars: yeah. we should investigate how that host behavioru can happen too ... and eliminate18:54
sergiusensyou should still see the devices though18:54
asachowever, since it happened right on mtp landing day18:54
ogra_right18:54
asaclets land a fix on image18:54
ogra_yes18:55
asacplars: so tests are running happily?18:55
ogra_lets see after the first reboot :)18:56
asachehe18:56
plarsasac: yes, so far18:56
asacyeah18:56
ogra_for this boot they will surely just run18:56
asacplars: what is "far" ? 1,2,3,4 reboots?18:56
plarsasac: maguro is 3 or 4 tests in, and mako is installed and running the second set of tests18:56
asacok18:56
asacnice18:56
ogra_plars, did we have reboots inbetween ?18:56
plarssorry, that's backwards, mako is on the 4th, maguro now on 3rd test18:57
asachmm. thought he meant autopilots. we reboot in between autopilots18:57
plarsogra_: yes, reboots between each18:57
ogra_great18:57
asacgoodie18:57
ogra_so its actually only the first boot thats affected18:57
plarsand working ok for me locally too18:57
ogra_yeah, here as well18:57
asacsergiusens: https://bugs.launchpad.net/autopilot/+bug/1226505 is fixed in trunk?18:57
ubot5Ubuntu bug 1226505 in Autopilot "New autopilot version breaks three ubuntu-ui-toolkit tests" [Critical,Fix committed]18:57
asace.g. can we try landing again?18:57
* ogra_ tries to find the revert for lxc-android-config with the fix in it 18:58
* plars -> doctor - back in a bit18:58
kgunnfginther: ping18:58
thomiasac: yes18:58
fgintherkgunn, pong18:59
thomiasac: I reverted the changes18:59
asacthomi: did you run all autopilots succeessfully afterwards?18:59
asac:-P18:59
kgunnfginther: hey..sorry, been xmir-ing so on and off irc18:59
kenvandineasac, those content-hub features has a status of in image 5318:59
thomiasac: The changes would have made test authors lives *much* easier, but if you don't want incompatible changes in S then you'll have to wait until T18:59
asackenvandine: right18:59
kenvandinebut the code for those haven't been merged yet18:59
fgintherkgunn, I don't remember pinging you, did i?18:59
sergiusensrsalveti, ogra_ wouldn't rm $LXC_ROOTFS_PATH/init.usb.rc solve it better?18:59
kgunnfginther: was there an issue with the mir armhf build config we were pinging about earlier18:59
ogra_sergiusens, not sure what else we remove with that ... seems a bit broad19:00
fgintherkgunn, let me refresh my memory, one moment19:00
asackenvandine: well, it was added to the landing asks19:00
kenvandineasac, well one of them hit trunk a little bit ago19:00
sergiusensogra_, all the usb settings which we probably want to control from ubuntu anyways19:00
kgunnfginther: it was this...? We're seeing what look like setup problems: https://jenkins.qa.ubuntu.com/job/mir-saucy-armhf-ci/7/console19:00
asackenvandine: i wonder why you would add it to landing asks if its not there19:00
asac:/19:00
asackenvandine: we landed content-hub today19:01
asacthat was suppose to be it19:01
kenvandineasac, there are others that are waiting for code19:01
kenvandinewell, i was told to make sure the pending features are on your radar :)19:01
ogra_sergiusens, hmm, wont init parf if it cant find the include file ?19:01
ogra_*barf19:01
kenvandineasac, the stuff that was published today was just minor changes to the API from 2 weeks ago19:01
asackenvandine: they didnt have waiting for code as status this morning or any hint that we  should wait19:01
fgintherkgunn, that's a transient launchpad communication problem that I just started seeing today. I don't know what we did to upset the gods19:01
ogra_we might have to sed the init.rc as well if it cant hanlde that19:01
asacor was that an oversight?19:01
asackenvandine: anyway19:02
asaca bit painful, but what not19:02
kenvandineasac, sorry.. that's what i told jason when he asked me for the details19:02
ogra_sergiusens, i think i prefer the proven fix we had before so we can get another image out with that fixed19:02
kenvandinethe peer registry branch is ready, wayting for a review from tvoss19:02
ogra_sergiusens, we can do the complete removal of the file after some more testing imho19:03
kenvandinethe store stuff for confined apps should be proposed for merging by tomorrow morning19:03
sergiusensogra_, ack19:03
kenvandineand gusch has some SDK components he is trying to get merged too19:03
ogra_sergiusens, i.e. land it with the other changes to adb19:03
kgunnfginther: ok, cool that you're aware19:03
asackenvandine: can you come back if all is in?19:03
asackenvandine: or whenever you want an update in?19:03
kenvandineasac, will do... i changed the status to waiting for code19:04
asacsure. an you make another entry that asks for a general code landing right before that19:04
fgintherkgunn, also, the android build was added before I started paying attention. perhaps thomi knows what it's for (https://jenkins.qa.ubuntu.com/job/mir-android-saucy-i386-build/)19:04
asackenvandine: and set that to INIMAGE19:04
asacand list 53?19:04
kenvandinei would like to plan to get it landed in the image this week, really want to get this out in the wild to get more testing19:04
asacwell, we can land it if its there, but not before :)19:05
kenvandineof course ;)19:05
asackenvandine: please add a new entry that requested the landing we just did :)19:05
asacok19:05
kenvandinewill do19:05
asacand set it to DONE ... assign it to lukasz etc.19:05
asackenvandine: just put it before the current content hub things19:05
asacthanks19:05
asaccyphermox: :)19:06
asaccyphermox: do you know what we usually would do for the scopes on desktop?19:06
asaccyphermox: sil left saying that touch was validated and good and only waiting on unity7 and its tests19:06
asac20:17 < sil2100> asac: ok, so after testing the libunity and unity-scope-home versions that are requested for release by "scopes  #1" it seems to look ok from the touch point of view - but we still need to make sure it doesn't cause a  regression in unity7 (which is still building now)19:06
cyphermoxso we're just wiating for the results of the check job for the unity stack19:07
cyphermoxasac: I'm theoretically off today, not currently in a position to connect to the VPN to get to see the jenkinds output19:08
asack19:08
asacguess has to wait then19:08
rsalvetisergiusens: I wouldn't recommend you to remove the device specific usb file yet19:08
rsalvetias I'm sure that is still used to setup the usb properties19:08
asaccyphermox: where do i find that jenkns thing?19:08
kenvandineasac, ok, so i added it to the asks sheet and updated the status of the others, so now the one of the plan sheet basically references that asks entry19:09
rsalvetisergiusens: ogra_: to be safe, just remove the adbd binary when mounting the container19:09
cyphermoxasac: : http://10.97.0.1:8080/19:09
sergiusensrsalveti, that's done in the upstart script19:09
cyphermoxkenvandine: do you know if the unity stack is done with its tests?19:09
ogra_rsalveti, yes, i have a package ready19:09
ogra_rsalveti, just testing19:09
kenvandinecyphermox, i don't19:09
asackenvandine: good. so the one DONE reflects what was done and the outstanding ones reflect the outstanding ones19:09
ogra_to make sure it still works all fine19:09
asackenvandine: can you just update each if the code is tehere and ready?19:09
asacso we see it in the morning?19:09
rsalvetisergiusens: not that sure for mtp19:10
rsalvetiogra_: cool19:10
ogra_rsalveti, ugh ... we also need to unset mtp on shutdown ...19:10
ogra_in the property19:10
ogra_else nautilus acts up19:10
rsalvetiwhy unset?19:10
rsalvetiyeah, might be better19:10
ogra_because the gadget stiull exposes it and gvfs tries to connect to a non existing daemon19:10
kenvandineasac, i will19:10
asaccyphermox: where do i look there?19:10
asacin cu2d?19:10
ogra_so nautilus spits out an mtp mount error on device reboot19:11
rsalveticyphermox: something for you to fix in the mtp service19:11
ogra_yeah19:11
asaccyphermox: seems cu2d-unity-saucy #3 is still running :)19:11
cyphermoxasac: ack19:11
cyphermoxrsalveti: yeah? bug?19:11
asaccyphermox: so if that is finished someone can promote that in theory?19:11
rsalveticyphermox: just disable mtp when the device is shutting down19:12
ogra_asac, plars, lxc-android-config 0.98  has the fix for adb19:12
rsalvetiso we can still tell the host side that mtp is now gone19:12
ogra_right19:12
asacogra_: ok... debdiff? uploaded?19:12
asacguess is already up19:12
asacso next image will have it19:12
ogra_asac, yeah19:12
ogra_right19:12
asacdid we validate the fix? :)19:12
ogra_asac, debdiff is this one reverted: http://launchpadlibrarian.net/144051867/lxc-android-config_0.42_0.43.diff.gz19:12
asacin tehe sense that i can relax now? or do we expect another bustage with >2% ? P)19:12
ogra_asac, i tested locally adbd still behaves, mtp still works19:13
asacogra_: where you able to reproduce the broken behavioru before?19:13
ogra_no19:13
asacsee :)19:13
asacbut well.. story sounds a bit sane19:13
ogra_only plars can do final verification here i fear19:13
asacso i am happy19:13
asacin theory we should try to validate that our fixes fix something though :)19:14
ogra_yeah, but that kind of requires that you can reproduce it19:14
asacexactly :-P19:14
ogra_which you cant manually19:14
ogra_its one of these fixes ...19:15
ogra_:)19:15
asacdo we have a story why that cant be done manually as well? :)19:15
ogra_timing19:15
asacyeah. thats where the story usually ends :)19:15
ogra_i suppose you could kind of do it semi scripted19:15
asacrandomness struck two devices duringt he same image test run :)19:16
ogra_but since it also only seems ot happen on first boot thats time consuming19:16
asacyeah. lets hope19:16
ogra_and it is a change in lxc-android-config we need anyway for disabling adb by default19:17
ogra_so even if it wouldnt work the change would be needed ofr something else19:17
asacright19:17
asacall fine19:17
ogra_yeah, lets just all sit in awe and wait for the next image test :)19:18
asaclets stay awake for the next 10 image runs :)19:18
ogra_haha19:18
ogra_my jetlag waves19:18
asaccyphermox: which check do i care about?19:21
asac0%19:21
asaccu2d-unity-head-2.2check ?19:21
cyphermoxyep19:23
asacwow i am confused19:23
asacthat one was listed as failed, but now i found another path to that job and there its still running :)19:23
asachttp://10.97.0.1:8080/job/cu2d-unity-saucy-2.2check/19:24
asacvs.19:24
asachttp://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-2.2check/19:24
asaccyphermox: the latter didnt run since sep 1219:24
asacguess we dont use head anymore?19:24
asaccyphermox: i think it failed like this: http://paste.ubuntu.com/6120814/19:26
asaccyphermox: is that usually a thing to retry?19:26
thomifginther: just watching this: http://s-jenkins:8080/job/autopilot-1.3-ci/19/console it seems like it runs the various CI configurations serially, rather than in parallel - is that just because not all the configuration machines are available  at the same time?19:47
thomior rather, not available at once19:47
fgintherthomi, all of the "$series-$arch" jobs are run in parallel as long as that resource is available19:49
thomiI see19:49
fgintherthe console log is only updated as the builds complete19:49
kgunnfginther: so wrt transient launchpad communication problem that you just started seeing today is making it hard to land code changes....and suggestions ?19:50
fgintherkgunn, I was working on a retry fix, want to review :-)19:51
kgunnfginther: if needed i can select a victim19:51
asacrsalveti: can you update in asks exactly what is coming and where from?19:51
fgintherkgunn, I don't know what's the root of the problem, if we are beating on it too hard or something else, I need to ping launchpad ops19:51
asacrsalveti: so for qtmultimedia bzr branches and so on19:51
kgunnfginther: we notice it started yesterday and is always armhf...so19:52
asacbuild issues?19:52
rsalvetiasac: yup, cleaning that up still so we can have them all done in good shape to just be pushed to the archive19:52
kgunnwonder we should turn it back off19:52
asacfginther: is that ppa build issues?19:52
rsalvetibut still work to be done from jim's side19:52
fgintherasac, no, it's an issue with our build scripts getting data from launchpad19:53
asacic19:53
asacfginther: soyuz/archive or code/merge api?19:54
fginthercode/merge api19:54
* fginther wonders if this is actually a race condition that we just didn't hit until now19:55
asacfginther: i asked wgrant and stevenk to come in here when they get up19:58
asacthey are aus timezone19:58
asacthey are our launchpad experts19:58
asacand should be able to get you a better idea19:58
fgintherasac, thanks19:59
thomifginther: how often does the upstream-merger job scan for new MPs to land?20:17
fgintherthomi, 15 minutes20:19
fgintherthomi, however, it's now taking 25+ minutes to run20:20
thomi:(20:20
thomimakes me sad20:20
thomifginther: out of interest, how come it takes 25 minutes to run?20:22
* fginther suddenly realizes why it's taking so long20:22
fgintherthomi, the recent switch to the 'saucy' stacks caused the change20:23
fgintherit wasn't in the magic list of 'run these in parallel20:24
thomiso.... we can fix that, right?20:24
fginthernow it is, the next one should run faster20:24
* thomi crosses fingers20:24
thomi\o/20:24
rsalvetiasac: what do you mean by waiting for code?20:24
rsalvetiasac: for example, for the "Adding gstreamer1.0-pulseaudio to the seeds" we already have a MR for it20:25
rsalvetifurther steps would be getting that merged and pushing a new meta20:25
cjohnstondoanac: should we merge in the two branches and release utah?20:26
doanaccjohnston: your branch and pauls?20:27
cjohnstondoanac: yes20:27
doanacsure20:27
cjohnstonunless there is other stuff outstanding that we need?20:27
doanaci don't think so. i'll pull the trigger20:27
cjohnstonack20:27
=== ogra_ is now known as ogra
asacrsalveti: FFe? thats not approved i think yet20:34
asacrsalveti: isnt that just going on the touch image?20:35
asacah its a patch20:35
rsalvetiasac: that line is just about adding gstreamer1.0-pulseaudio to the seeds :-)20:35
kgunnalan_g: fginther has a plan b :)20:35
rsalvetiwe have gstreamer0.10-pulseaudio already, but we need the 1.0 now20:35
asacrsalveti: you could call that out. i thought you want to land a new package20:36
fgintherkgunn, I should have it ready in a few minutes20:36
rsalvetiasac: no, just including it to the seeds (we need a new package, but later on)20:36
rsalvetiasac: can we push that forward then?20:36
asacrsalveti: is that ok frmo legal? :) ... otherwise go for it20:37
rsalvetiasac: yup, that's just the pulseaudio plugin for gstreamer20:38
rsalvetiall good20:38
rsalvetiok20:38
asacrsalveti: its about -bad20:38
asaci thought20:39
rsalvetithat on I'm breaking into a separated package20:39
asacrsalveti: i am talking about " gst-plugins-bad1.0 with libstagefright support (android hardware decode/rendering)"20:39
rsalvetiso we don't need to include the entire bad set20:39
asacrsalveti: ok you talk labout the seeds thing20:39
rsalvetithat's indeed still waiting on code, and FFe20:39
rsalvetiyeah, my request was a different one20:40
asacrsalveti: that impacts music app and videoplayback?20:40
asacthe seed?20:40
rsalvetinops, as that is still using the gstreamer0.10 packages20:40
rsalvetiwe're still migrating stuff to gst1.020:40
rsalvetiall I want to do now is making sure we also have the same set of gst1.0 packages20:40
rsalvetito avoid dependency issues later on20:40
doanacplars, cjohnston: building a new utah for you guys20:40
cjohnstondoanac: plars at some point I'd like to chat about parallelizing the smoke tests... figure out exactly what we want to do20:40
cjohnstonsweet. ty20:40
doanaccjohnston: yep. we should talk soon20:41
asacrsalveti: so i assume its ok. i set status to "self upload" so the team can look at what happened tomorrow20:41
rsalvetiok20:41
asacrsalveti: the rest all is waiting for code, right?20:41
rsalvetiyup20:41
fgintherkgunn, does mir need to build with ppa:ubuntu-unity/daily-build. I'm assuming the answer is no20:43
asacsergiusens: looking at your phablet-flash request. how can we be sure that phablet-flash doesnt break utah? you think you could learn how to run utah and try that locally to give me confidence?20:44
kgunnfginther: mmm...eventually20:44
kgunnfginther: we'd hope that when we do land our stuff in our trunk, we then build in experiemental...test it, then tell didrocks we want to go to archive20:45
kgunnfginther: so at that point of going to archive..i assume the path resumes normally (via daily-build)20:45
fgintherkgunn, right, but to actually build mir for upstream merger, do you need anything from that ppa that wouldn't already be in the archive?20:45
fgintherkgunn, the other components in the mir stacks all build into a shared local archive (so unity-system-compositor builds with the most recent commit of mir)20:47
cjohnstondoanac: https://code.launchpad.net/~cjohnston/qa-dashboard/ci-dashboard/+merge/18605720:51
cjohnstonfginther: ^^ didn't get run through CI20:51
doanaccjohnston: was the rename a request? ie - i  wonder if renaming is going to cause confusion?20:53
cjohnstondoanac: it wasn't... but as we push more to make the dashboard do more things, it really becomes more of a CI tool20:54
fginthercjohnston, thanks for the reminder, I think I found the problem20:54
doanaccjohnston: probably should send this to the QA and CI mailing lists to see what people think20:55
mmccHi folks, I have a package that needs to be added to CI - lp:ubuntuone-credentials. We're going to be adding it to the landing pipeline spreadsheet soon and want to be sure it's integrated correctly.20:56
cjohnstonseems a little overboard to me. but not my decision I guess20:56
mmccmy question is - what's my next step? I have a branch of cupstream2distro-config that adds it to the webcred stack, but it at least needs a thorough review if not just having someone do it correctly for us. :)20:57
cjohnstonfginther: ^20:57
cjohnstonheh..20:57
fginthermmcc, I can help20:58
fginthermmcc, just send me the branch20:59
mmccfginther: great, thanks. my changes are here: https://code.launchpad.net/~mikemc/cupstream2distro-config/add-ubuntuone-credentials20:59
fginthermmcc, I can add the changes right now to start the upstream merger builds, but the integration team will need to do additional reviews to make sure these two projects are ready to go into the archive21:00
asacrsalveti: you see anything else low hanging with code in the landing asks?21:01
rsalvetilet me check21:01
asacjust thinking that you usually test your uploads so maybe we hsoudl test something at the same time on your device :)21:01
asaclol21:01
mmccfginther: that sounds like progress to me. do you know of anything I can do to help make that review process smoother?21:01
fginthermmcc, but if you want to wait, you can just convert that into a MP21:01
asacplars: back :)?21:02
asacj.k.21:02
cwayne1asac: there's code for landing lightdm :P21:02
asaccwayne1: i know... its in a MP21:02
mmccfginther: sorry, didn't follow - if I want to wait for what?21:02
asaccwayne1: i am saying we can try. we will look at it tomorrow. most likely it requires you to merge to trunk21:03
asacso we can pick it in the staging ppa21:03
asacand test it with something else together21:03
fginthermmcc, if you want to wait for the integration team to also review the projects you're adding. I suggest adding the upstream merger bits now, and letting didrocks team review when they have time21:03
plarsasac: yes21:03
asacrsalveti: so something in daily-build ppa broke 3 unity8 tests :)21:04
asacrsalveti: i uphgraded the whole lot21:04
asacif you find what to kick out so we can let everything else in, you get something nice :)21:04
asachehe21:04
fginthermmcc, there's a couple changes needed to your branch to make that happen. I'll do it on my end first21:04
asaci wouldnt start looking though21:04
rsalvetihahah, right21:04
sergiusensasac, give me instructions to setup utah and I'll run it, but given the code I saw in utah it shouldn't break21:05
mmccfginther: OK, thanks. I'll go with your recommendation, since I'm not aware of any special circumstances for our projects.21:06
asacnothing should break21:06
asacbut then there are those bugs :)21:06
asaclol21:06
mmccfginther: ie, I don't know if I want to wait for them to review it or not, so it's all the same to me :)21:06
asacsergiusens: i think plars knows how to use utah commands to flasha nd run tests on your local devices21:07
asacand doanac21:07
sergiusensplars, give me the goods :-)21:07
fginthermmcc, http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro-config/trunk/revision/78621:07
plarssergiusens: you want to do it exactly the same way we do in the lab right?21:08
sergiusensplars, I don't really want to, but it seems necessary ;-)21:08
plarssergiusens: https://wiki.canonical.com/UbuntuEngineering/QA/ImageTestingRun is almost accurate - if you want touch_ro builds, there's one more thing you need21:09
plarssergiusens: one sec and I'll update21:09
plarssergiusens: of course if you don't want to run an autopilot test, just provision, you just need to run provision.sh, not jenkins21:09
mmccfginther: should those be project names? it looks like it's missing the 's' at the end of 'ubuntuone-credentials'21:10
sergiusensplars, yeah, I'm stopping after provision :-)21:10
fginthermmcc, ughhhhhhhhh21:10
sergiusensplars, can this run fine in a schroot?21:10
plarssergiusens: ok, reload21:11
plarssergiusens: don't see why not, as long as you have an adb  connection21:11
plarssergiusens: the thing you need for touch_ro is to set TOUCH_IMAGE=--ubuntu-bootstrap (obviously based on a historical flag... we'll probably change that to something nicer soon)21:12
plarssergiusens: also note that I changed the branch mentioned in that wiki21:12
plarssergiusens: otherwise, should be good to go21:12
sergiusensplars, ok, I'm setting up a schroot for precise to test this21:13
fgintherrobru, can you assist mmcc in what is needed to get signon-plugin-password and ubuntuone-credentials in daily release?21:13
mmccfginther: and I made a noob mistake on the signon plugin - that's a package dep, but it's from lp:signon which is already included in the stack :\21:14
mmccI got fooled by signon-plugin-oauth2 being a separate LP project21:15
sergiusensasac, fginther can we add utah env setup tests for phablet-tools ci?21:16
fginthermmcc, turns out I messed up too :-)21:16
asacsergiusens: i think for that you need to have real phones and flash and test them?21:18
sergiusensasac, yes21:18
mmccfginther: :) hopefully I'm not too contagious in here21:18
asaci guess might be possible21:18
sergiusensasac, provision, network setup and test setup (they do all that)21:18
sergiusensasac, and a simple test run21:18
sergiusensasac, just one test21:19
fginthersergiusens, is that already part of phablet-tools?21:19
asacsergiusens: do you plan to still test locally? :)21:19
asacotherwise i can see how you shoot down our nice phones :)21:19
asacfginther: it is21:19
sergiusensasac, yes I am, but having it as part of ci would be better21:19
asacphablet-flash, phablet-network, phablet-test-run ...21:19
asacsergiusens: absolutelu21:19
asacalso utah21:20
asacso at best both :)21:20
asactest utah and phablet on phablet-tools ci21:20
sergiusensasac, that's the beauty, if you run a utah cycle, you have great confidence on almost all the tools21:20
fginthersergiusens, I know nothing about these tests, can we execute them from "autopilot run" or do we just need to build a special job?21:21
sergiusensfginther, very custom job21:21
fginthersergiusens, that's what I though21:21
sergiusensfginther, a precise instance that sets up utah, then installs the built phablet-tools and instances utah to do stuff21:21
asacsergiusens: do you know how to publish stuff from daily-release?21:21
asacsergiusens: i assume not?21:21
sergiusensfginther, that 'precise' env would need to have a device hooked up21:22
sergiusensasac, I'm not allowed to, don't have the permissions21:22
fginthersergiusens, our devices are all hosted on the same system.21:23
asaccyphermox: can you help phablet-flash after sergiusens confirms that utah still works?21:23
fginthernot necessarly a problem, but need to be careful21:23
asaccyphermox: from what i understand its already staged in the ppa21:23
asacsergiusens: can you confirm its in daily-build?21:23
sergiusensasac, it's not in daily-build, daily release wasn't triggered for it today21:25
sergiusensasac, so it would need a full daily-release cycle21:25
fginthersergiusens, can you create a work item or bug for this somewhere? I need to take off for a while21:25
sergiusensfginther, sure21:26
doanacplars, cjohnston: the utah update is available for deployment if you want it21:26
kgunnfginther: any news on armhf ?21:27
asacplars: webbrowser failed i think21:27
asacon maguro21:27
asacotherwise looks good21:27
plarsasac: I know, I've already retriggered it21:27
plarsdoanac: you got https://code.launchpad.net/~cjohnston/utah/1225700 also right?21:27
kgunnfginther: did i fail to answer your ques above...which is yes, we should only need to build mir21:27
doanacplars: yes21:28
plarsdoanac: great!21:28
plarsasac: you mean on mako?21:29
plarsasac: on maguro, it had the testcase failure that I mentioned on #ubuntu-touch21:29
asacplars: maguro i wondered if thats a retry21:29
plarsasac: I can retrigger it if you like there, but it's one that we've seen before as being flaky21:29
asacthing21:29
plarsasac: it is - known flaky test21:29
asacplars: yeah better retry21:29
asacnot sure if maguro is busy otherwise :)21:30
asacmako is more improtant to get in shape though :)21:30
kgunnfginther: just checked it seems to be failing in a different way21:36
alan_gkgunn: FWIW "old" way - https://jenkins.qa.ubuntu.com/job/mir-saucy-armhf-ci/7/console and "new" way https://jenkins.qa.ubuntu.com/job/mir-saucy-armhf-ci/8/console21:39
robrufginther, mmcc, sorry I was on lunch. glad to help -- still need me?21:44
mmccrobru: yes, thanks - I need to add lp:ubuntuone-credentials to CI, as fully integrated as possible, and basically I need to know first what that means, and second what to do to make it happen :)21:45
robrummcc, ok, are talking CI or daily release? For CI you want fginther, but for daily release I can help ;-)21:46
robrummcc, assuming you meant daily release, first I need to do a packaging review, then I need to twiddle some bits in the daily_release machine21:46
mmccI believe fginther handled the CI upstream merger stuff - and he pinged you for daily release, yes21:47
robruok, great. I'll look over the packaging then. what's the lp branch for the signon one?21:47
mmccsignon-password-plugin is in lp:signon, which may already be included.21:47
robruok, i'll check21:47
robrummcc, ok, ubuntuone has no packaging at all ;-) has it ever been released in distro?21:48
sergiusensplars, asac ok, setup took some time... utah is running in my schroot now21:49
robruhmmm, i see it in distro. i'll have to track down where the packaging lives21:49
mmccrobru: my apologies, you're talking to a packaging noob - are you looking for the debian/ directory? our projects have been keeping that in a separate branch21:49
mmccI'm not sure why, but i can point you to it, one sec21:49
robrummcc, yes, we need to merge debian/ into trunk and make some changes there in order to have daily release work.21:50
robrummcc, https://wiki.ubuntu.com/DailyRelease/InlinePackaging this is the checklist we go by, but don't worry, I'll do the work.21:50
mmccrobru: FYI, it's over here - https://launchpad.net/ubuntuone-credentials/packaging-dailies21:50
robrummcc, thanks21:51
mmccrobru: great, thanks. I'll be following along in case you need anything.21:52
robrummcc, k, shouldn't be long21:52
robrummcc, hmmm, odd version number. 99.12? is that right?21:53
mmccrobru: I'm pretty sure that's intentional but unfortunately the people who can give a definitive answer are past EOD right now... dobey (Rodney Dawes) has been doing most of the packaging work for our group21:54
mmccand he just left 30 minutes ago ...21:55
robrummcc, ok, no worries21:55
robrummcc, it looks like a date -- this hasn't been in development since december 1999 has it? ;-)21:56
mmcc:) no, definitely not21:56
robrummcc, hehe, ok. mostly looks good over here, just doing a couple test builds to confirm some stuff.22:04
mmccrobru: great.22:05
mmccrobru: I just remembered the method there - trunk has that 99.blah version number, and separate stable branches get set up where he updates the version number to make releases. e.g.: http://bazaar.launchpad.net/~ubuntuone-control-tower/ubuntuone-credentials/stable-13-10/revision/32?start_revid=3222:06
robrummcc, hmmm, that's gonna have to go away. daily release will be making releases direct to distro daily ;-)22:07
robrummcc, so I changed the version number to what's in distro, should be ok I think.22:07
robrummcc, http://paste.ubuntu.com/6121449/ some discrepancy in the symbols file. can you comment here? is this symbol necessary or is it a mistake?22:07
mmcchmmm22:07
mmccre the release branches going away, I assume that'll be fine. has to be, anyway22:08
mmccas for that symbol, I think I do recognize that change, but I don't understand the context (like I said, I'm a linux packaging noob)22:09
robrummcc, well, this is less of a packaging issue and more of a "did you or didn't you introduce new API recently?" issue22:09
mmccwe did add a new constructor for that class, yes. I'm double-checking now to be sure that signature matches22:10
robrummcc, ok, I need help demangling the name for the symbols file because I'm not a C++ guy ;-)22:11
mmccit's UbuntuOne::AccountRequest::AccountRequest(QString, QString, QString, QString)22:12
robrugreat, thanks.22:12
mmccso, yes that was introduced in r 60 http://bazaar.launchpad.net/~ubuntuone-control-tower/ubuntuone-credentials/trunk/revision/6022:12
robrubrb22:13
robruok22:17
mmccso, I'm not clear on why both those lines in the diff get translated by c++filt into the same signature, though.22:17
robrudunno22:18
mmccWell, a duplicate symbol shows up in the symbols file for the other constructors too22:22
robrummcc, it's ok, I think I've got it fixed, now I'm just cleaning up a few minor lintian warnings.22:23
mmccI guess duplicates in that file is not a problem22:23
mmcccool22:23
sergiusensasac, plars doanac just found a small issue with deploying with utah, we need to use the --no-backup or --bootstrap option (the latter is pending landing)22:27
sergiusenswithout that, $HOME is saved22:27
sergiusenswhich could lead to inconsistent system tests22:28
sergiusensboth options achieve the same btw22:28
plarssergiusens: ok, so if I add --no-backup, will we need to change it later?22:29
plarssergiusens: we already use --bootstrap for non-ro, but it wasn't available for ro22:30
sergiusensplars, no, but for a future reader, adding it as --bootstrap would be better22:30
sergiusensplars, there was no concept up until 3 weeks ago22:30
sergiusensthat's why, the whole thing was a bootstrap always22:30
doanacplars: you need me to make the fix or are you working on it?22:32
plarsdoanac: I'm looking at something else right at this moment, I can get to it shortly though22:32
doanacplars: i'll try it out.22:33
doanaci'm having other issues at home so not sure how well the test will go. but ogra said the next image should help my issue22:33
plarsdoanac: it should be pretty easy. And I can roll that out tonight along with the utah fix and from_host22:33
plarsdoanac: I'm just finishing up retries on 53 at the moment, for some reason mako ended up in recovery mode, trying to figure out which job left it there22:34
plarsdoanac: it might be safer to do adb reboot at the beginning, rather than (as I think I recall we do) adb shell reboot22:34
robrummcc, ok, so, with CI what you need to do is watch this: https://code.launchpad.net/~robru/ubuntuone-credentials/packaging/+merge/186173 wait for jenkins to approve it, and then set it to 'approved'. it will merge itself within an hour usually.22:34
robruwell, also, you can review it yourself if you like ;-)22:35
doanacplars: i  *think* we are doing "adb reboot" now22:35
plarsdoanac: odd22:35
plarsok22:36
plarsdoanac: oh, it might have tried to get info from it first or something... not sure, I'll look into it22:36
sergiusensasac, plars my phablet-tools is safe http://paste.ubuntu.com/6121516/22:36
doanacsergiusens: --bootstrap isn't available in for the system-image option?22:36
plarsdoanac: not yet22:36
sergiusensdoanac, it is in the unrelease package I'm testing22:37
doanacah - okay.22:37
doanaci'll test with that. thanks22:37
sergiusensdoanac, which from the looks of it it's ok (pastebin ^^)22:37
mmccrobru: thanks for your help! So, I may review it but I'm sure dobey will want to look. There's no harm in waiting until tomorrow to land that, I assume?22:37
sergiusensasac, are we good to daily release?22:37
sergiusensdoanac, plars that said, what utah does after fails...22:38
sergiusensERROR: running adb -s 0149C2230F018007 shell apt-get update -qq \; echo ADB_RC=\$? stdout was:22:38
plarssergiusens: hmm, check utah.log?22:39
robrummcc, no harm at all, I just assumed you were in a rush22:39
plarssergiusens: clientlogs/utah.log that is22:39
sergiusensplars, hmm, it's empty22:39
doanacthere might not be much if "apt-get update -qq" failed.22:39
doanacsyslog might have something about it22:39
sergiusensdoanac, running adb -s 0149C2230F018007 shell apt-get update (without -qq) works if I run manually22:40
mmccrobru: great. We are in a bit of a rush, but it doesn't have to go through today. Thanks again!22:40
sergiusensdoanac, plars plenty of Sep 17 22:40:17 ubuntu-phablet kernel: [  507.997802] adb_open22:40
robrummcc, ok, so lp:signon is definitely already doing daily release. you're sure that's all you needed? once that packaging lands all I have to do is throw a switch and it'll start daily releasing.22:41
sergiusensplars, doanac I'm betting it's just mtp22:41
asacsergiusens: can you release just that?22:41
mmccrobru: that should be it, yes. so then I'll ping you tomorrow once your MP lands (or dobey may ping you first if he has questions) - that OK?22:41
asacotherwise, let me put your paste into the spread22:41
asacfor tomorrow22:41
robrummcc, no worries, I'll be around22:42
mmccrobru: cool, thanks again22:42
robrummcc, you're welcome22:42
sergiusensasac, well phablet-tools from the utah run is solid, what comes after isn't but not related to phablet-tools22:42
asacsergiusens: thats not what i am asking :)22:42
asaci wondered if you can do the daily release to distro ... otherwise we have to find someone :)22:42
sergiusensasac, I can't, but for your peace of mind, it's the only MR that landed http://bazaar.launchpad.net/~phablet-team/phablet-tools/trunk/changes/187?start_revid=18722:43
sergiusenskenvandine, robru cyphermox can you trigger a daily release for phablet-tools and phablet-tools only?22:44
sergiusensasac, there ^^22:44
robrusergiusens, yes I can do that22:44
sergiusensthanks22:44
asaccool22:45
asacrobru: can you put that into the landing plan?22:45
robrusergiusens, no, wait, you mean not the whole misc stack? hmmmm I'm not sure if I can do that22:45
robruasac i don't have edit rights on that doc22:45
asachmm. please not all :)22:45
sergiusensrobru, I thought it was possible22:45
asacrobru: you should..22:45
sergiusenswell I know it is22:45
robrusergiusens, let me double check. I know how to do the whole stack for sure, never done just one branch before22:45
robrusergiusens, oh yeah yeah, nm, it's easy22:46
asacrobru: you work with didrocks, right?22:46
robruasac, yep22:46
robruasac, i'm a direct report to didrocks22:46
asacok22:46
asacrobru: added you22:46
asacrobru: so this one is fine. just document the landing progress in the landing plan22:46
asacput it where it fits by time :)22:47
asacguess 18 am22:47
asacput his paste in a comment22:47
asacand refer to his landing ask on the other sheet22:47
robruasac, ok. hey, i'm having trouble with the webapps stack. i fixed the latest build failure but when I rerun the stack, it just gives the same error again -- as if it's ignoring the latest commit in trunk. any ideas?22:47
asace.g. update that that is "In Landing Plan"22:47
asacnow22:47
asacthx22:47
asaczero idea :)22:48
robrubah22:48
asaci hope i never have to dive soo deep :)22:48
asacsergiusens: i think its save to wait till cyphermox comes back or we will pick it up tomorrow22:48
asacif robru is not familier with publishing a single thing then lets not risk :)22:49
robruasac, hmmm, I ran the command, doesnt' seem to have worked...22:49
sergiusensasac, ok, I think robru triggered and was asking about something else though22:49
robrusergiusens, yeah, I was asking about a different issue22:49
robruasac, ^22:49
asacstill... didnt sound like you know how to publish a single package from misc :)22:50
plarsasac: I'm still getting lots of this adb_open message in the syslog when rerunning that webbrowser test22:50
plarshttp://10.97.0.1:8080/job/saucy-touch_ro-mako-smoke-webbrowser-app-autopilot/112/console - in progress22:50
robruasac, well, i've never done it before. but i just read the docs. sounds easy enough22:50
sergiusensplars, that will be fixed with ogra's package22:50
plarssergiusens: ah, ok22:50
plarsasac: ^ so this build may be difficult to get much more out of until we get that22:50
asacrobru: ok.22:50
sergiusensplars, adb from the container gets enabled and mtp resets the bus so we have plenty of errors then22:51
asacplars: can we switch device?22:51
asacsergiusens: oh so thats mtp?22:51
sergiusensasac, it's a mix22:51
asacis ogras fix in ?22:51
robruasac, sergiusens: ok, looks like it's running. just takes a sec to show up in web view.22:51
asacmaybe we need a new image then :)22:51
asacrobru: go ahead i guess22:51
sergiusensasac, no, that's u-t-s which I'm testing now22:51
asackk22:51
asacrobru: can you try to update the landing spread? the ask is in row 32 -> update that when you add it to the landing plan22:52
robruasac, in here? https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0 row32 is blank22:53
plarsasac: we can definitely switch devices, but from what sergiusens said it wouldn't help22:53
asacsergiusens: the adb thing is u-t-s?22:54
asacsergiusens: sure?22:54
doanacplars: building utah 0.15+20130917.1 right now.22:54
asacsergiusens: thought we add lightdm there22:55
asacsergiusens: :/22:55
sergiusensasac, no, sorry22:55
asacsergiusens: i think the adb fix was uploaded a while ago22:55
doanacits got --bootstrap. so you can deploy once we have a new phablet-tools22:55
sergiusenstoo many packages22:55
sergiusensasac, it's lxc-android-config and it seems to be in22:55
sergiusensasac, at least the udd branch22:55
lool'night all22:55
asacnight lool22:55
asacsergiusens: right. lets get a new package for that i guess22:55
asacerr build22:56
asacunless we plan to get something else in right now22:56
asacbut i dont see that :)22:56
sergiusenshttps://launchpad.net/ubuntu/saucy/+source/lxc-android-config/0.9822:57
asacsergiusens: right. can you do a new image?22:57
asacthe last image busts our automation :)22:57
asacor did we do a new run afer?22:58
sergiusensasac, no, according to http://people.canonical.com/~ogra/touch-image-stats/20130917.changes last build has 97, we want 9822:58
asacsergiusens: right. so give it a kick if you can22:59
sergiusensasac, sure, let me just confirm it reached the archives/ports22:59
asacwe couldnt finish running llast image in utah because of adb22:59
asacthanks22:59
plarssergiusens: it's not enough that it says it's in the release pocket?22:59
plarsI guess there's a sync delay due to that also23:00
sergiusensplars, no, not really... already been bit by that23:00
sergiusensplars, needs to make it all the way to Packages.gz23:00
plarsyeah23:00
sergiusensit's in, I'm triggering23:00
plarsall these "it's there, but it's not *really* there yet" things make automating simple stuff a pain23:01
sergiusensplars, yup, that and no API for many things; scrapping stuff is just too old school23:01
sergiusensplars, that's why I love our move to the image server, the json stuff really helps a lot23:02
plarssergiusens: we even have to wait for that one23:02
plarssergiusens: just because the json is there, the files may not be yet23:02
sergiusensplars, hmmm, I would of thought you'd get the files in and then push the json :-/23:03
sergiusensbuild triggered btw23:04
plarssergiusens: I believe that's so, but then it gets rsynced or something23:04
plarssergiusens: if we have a new phablet-tools, I can apply that, utah, and the supporting bits we all discussed earlier before the new image arrives23:15
robrusergiusens, asac: anyways, it's building, but it's going really sloooowww... http://10.97.0.1:8080/job/cu2d-misc-saucy-2.1build/8/console23:17
asacrobru: what stuff is in the misc branch?23:18
asacok i think i see it23:18
asacwell.. if its finished we can pick it up tomorrow easily23:19
asacdont know why we hurry :)23:19
plars"<asac> dont know why we hurry :)" - that's one for the quotes page :)23:20
asaclol23:20
asacsure23:20
plarsheh seriously though23:20
plarsasac: sergiusens noted earlier that we should use the --bootstrap flag as it would be safer23:21
asacabout phablet-tools landing that got fastpathed and folks want it even faster :)23:21
plarsthe new phablet-tools has that - basically wiping home so that we get a cleaner system between boots23:21
asacplars: protects us from what kind of things?23:21
plarsasac: gremlins23:21
asacplars: ok. but i dont think its all hands on deck pririoty :)23:21
asacits not fixing a critical bug like the adb23:22
plarsasac: it's not, but if we're already respinning the build, and have an automation branch that depends on it, it's easier to land it tonight while I'm here and it's fresh on my mind and I'm waiting on the next build to watch the results anyway23:22
asacplars: so you can test it with an existing image?23:23
asacotherwise it doesnt really help i guess23:23
asacand risks our test run23:23
plarsasac: I could test it locally, and the risk is lower if all of it is fresh on our minds23:24
plarsasac: I could even test it on the server if we have a gap still before the next image comes, just we might still get the adb_open stuff23:24
asaclanding all at once with a tired mind sounds risky. first time i heard about landing uitah update to use new phablet-flash23:24
asacplars: anyway. your call :)23:24
asacyou are the one who suffers, because i am off soonish :)23:25
asachappy to see this go in etc.23:25
asacjust scared to wake up with psivaa not able to poke the image23:25
plarsasac: it depends on timing - if it looks like it's going to land too close for me to ensure it doesn't break something, I'm waiting23:25
asacyeah23:25
plarsasac: but we have to take windows when we can to roll these things into production23:25
plarsasac: there is always a next build coming23:25
asaci trust you make a good decision. as long as we have spare phones still on standby we can at least risk something23:25
asacplars: yeah, but if we miss a build, we dont know if our landings so far broke it23:26
asacand we cant risk more in next landing batch23:26
asacwanted to have a big landing batch tomorrow :)23:26
asacplars: we have busted our infrastructure more than once. cant we have a fresh day to look at that and then do it :)?23:27
asacbut anyway23:27
asacjust my preference23:27
asaci will survive whatever i guess23:28
asacif you feel its well tested etc. and ready :)23:28
asacsergiusens: otherwise i have listed phablet-tools for tomorrow to be picked up when it built by us23:29
asacplars: sergiusens: give me a heads up when you know more23:29
asaccu23:29
sergiusensasac, not sure I got that entirely, the part of 'know more'... which I guess is adb related23:31
asacsergiusens: lost backoog23:33
asacbacklog23:33
asacsergiusens: nevermind. we will pick it up tomorrow from the misc stack and land it. then land the utah changes with a fresh eyes23:35
plarsyeah, the image came out before phablet-tools23:56
plarsdoanac: we'll land all that stuff in the morning after we have a good build23:56

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