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

robrursalveti, jenkins is down for maintenance, should be back soon though00:42
imgbot=== trainguard: IMAGE 76 building (started: 20140610 02:05) ===02:04
robrursalveti, sorry about that, had an absurdly long phone call. you're in silo 18 now03:17
imgbot=== trainguard: IMAGE 76 DONE (finished: 20140610 03:30) ===03:29
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/76.changes ===03:30
sil2100ricmm: hi! I see your silo has some problems building certain archs08:00
sil2100ricmm: is that on your radar?08:01
ricmmsil2100: sure, but that was last night08:34
ricmmsil2100: if you see again, you'll see they rebuilt 9 hours ago08:34
ricmmthe remaining failing arches are not published in the archive for any of the pkgs08:35
ogra_sil2100, looks like to dropped08:43
sil2100Ugh08:44
sil2100Wifi died for a moment :o08:44
sil2100Ok guys, this wifi madness is making me unable to hear any of you08:47
sil2100So I drop off from hangouts08:47
ogra_sil2100, well, you know where to look for the changelog :)08:48
davmor2ogra_: http://paste.ubuntu.com/7622470/08:48
popeycongratulations sil210008:55
popeyhttps://twitter.com/ubuntudev/status/47628637648559308908:55
sil2100Thank you!08:56
sil2100Damn, sucks that I don't have tweeter ;p08:56
* sil2100 is like a caveman from the stone age08:57
ogra_OOOOHH !09:00
ogra_congrats !!!09:00
Mirvsil2100: congrats!09:07
sil2100Thanks guys ;)09:07
mandelogra_, what partitions are mounted in recovery mode?09:10
sil2100Holy crap, just went to my balcony for a moment and it's hot like hell outside09:15
dbarthMirv: ping?09:16
ogra_mandel, just / and /cache by default iirc09:16
mandelogra_, so I can do a adb push of resize2fs (static one) to /cache or / correct?09:17
dbarthMirv: the new qtwebkit seems fine for old webapps overall09:17
mandelogra_, I want to resize the system partition :)09:17
dbarthMirv: do you have a timeline for landing it?09:17
ogra_mandel, that should be preinstalled09:17
Mirvdbarth: I'm at QtCS this week, but I can do the publish from here if needed. I maybe just don't have the complete picture of what would still be tested, like did you test HTML5 apps? I did start some cordova tutorial created app and it seemed to work.09:22
popeysil2100 went to the balcony to announce to his followers that he's now a #motu, right?09:23
cjwatson<followers class="adoring">09:23
sil2100popey: right! Although there was only one guy with a dog listetning...09:23
popeyheh09:24
popey"He's not a MOTU, he's a very naughty boy!"09:25
brendanddo we reboot devices between autopilot suites?09:25
Mirvdbarth: I also tried Cordova Mobile Spec app that was installable, but I'm not sure which all of those should work to which extent etc, but surely it was navigable09:26
dbarthMirv: ok, i'll get back to you re: more html5 apps testing09:39
=== vrruiz_ is now known as rvr
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #71 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
davmor2sil2100: network disconnecting over night issue https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/132847810:19
ubot5Ubuntu bug 1328478 in network-manager (Ubuntu) "Network-manager seems to lose connection" [High,New]10:19
Mirvsil2100: building is broken https://ci-train.ubuntu.com/job/landing-005-1-build/82/console10:33
Mirv(second try already)10:33
Mirv...as seb128 also just found out10:36
seb128yeah10:37
seb128same on https://ci-train.ubuntu.com/job/landing-012-1-build/40/10:37
sil2100hmmm10:44
sil2100It might be related to that jenkins switch that happened last night10:44
* sil2100 looks into that10:44
sil2100Ah shiiit10:45
seb128rsalveti, ricmm: when is platform api v2 going to land?10:46
sil2100So the worst-case scenario happened10:46
seb128rsalveti, ricmm: it's blocking unity8-desktop-session bugfixes to land10:46
seb128the desktop-next iso is useless until that happens...10:46
Laneywhy does it need to block that?10:46
seb128if the api stuff is not ready to land, could we get the bugfixes in and then go back to yours?10:47
seb128Laney, because you can't have the same projects in multiple silos10:47
sil2100seb128: I was asking that yesterday, it was supposed to be landed ASAP10:47
seb128sil2100, ok, thanks10:47
* popey notes that desktop-current iso is currently useless ☻10:47
seb128popey, how so?10:47
sil2100We didn't want to override again as geh, papi is already waiting for weeks10:47
popeyubiquity is broken, it doesn't start at all.10:47
seb128urg10:47
LaneyI don't even know for sure that this will fix it10:48
seb128popey, bug number?10:48
popeyhttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/132670710:48
ubot5Ubuntu bug 1326707 in ubiquity (Ubuntu) "Ubiquity does't start, hangs in "/usr/lib/ubiquity/bin/ubiquity", line 426, in acquire_lock, test_debconf.stdout.readline()" [Critical,Fix released]10:48
seb128Laney, well, I want to see that landing before I spend time debugging10:48
popey\o/ fixed 9 hours ago!10:48
seb128popey, ;-)10:48
Laneyseb128: indeed10:48
popeyI love sleeping. Things get fixed when I sleep.10:48
LaneyI just mean that it's hard to test until things get in10:48
Laneythe slow pipeline makes this difficult10:49
seb128right10:49
xnoxpopey: it's fixed, but there ain't yet an iso with a fixed ubiquity =)10:51
popeygood enough ☻10:52
popeythank you!10:52
xnoxpopey: thus can't actually verify it's "fixed fixed"10:52
dbarthsil2100: o/ hi, i have a quick branch to pass, for an extra HTML5 binding10:52
dbarthsil2100: would be handy for a UOS session later this week10:52
sil2100Hey!10:53
sil2100dbarth: sure, we're having problems with jenkins right now though10:53
dbarthok, nw; just to know if i can be that last silo that remains ;)10:53
davmor2Mirv: how's the conference?10:55
Mirvdavmor2: interesting, a lot of Qt interested folks from different companies + Digia. I'm showing my Qt 5.3 running U-Phone to interested people.11:00
Mirvruntime OpenGL vs ES switching still being planned, which is good11:01
davmor2Mirv: sounds fun then :)11:01
Mirvindeed. now -> lunch11:01
davmor2popey: did you ever write a bug for video stalling on playback?11:08
sil2100NOTICE! There will be a jenkins outage in a moment!11:09
popeydavmor2: no, i thought there already was one.11:10
sil2100(by jenkins outage I mean citrain jenkins)11:10
popeyxnox: tested your fixed ubiquity on a live cd, it is fixed ☻11:26
davmor2popey: be pretty daft calling it a fixed ubiquity if it wasn't ;)11:28
popeyPenfold, shush.11:28
xnoxdavmor2: well, i claim it's a python3 regression.11:28
xnoxpopey: did you read the comment next to the one-liner fix?! =)11:29
popeynope11:29
xnoxpopey: http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/618811:29
xnoxin retrospect, it's not that funny.11:30
popeywow11:30
cjwatsonxnox: I'm not convinced printing was ever guaranteed to flush.11:36
cjwatsonxnox: I don't agree that's a regression.11:36
=== zsombi_ is now known as zsombi
cjwatsonxnox: Leaving aside the flush=True keyword arg, test_debconf.stdin.flush() was available.11:36
cjwatsonxnox: Maybe the default buffering changed or something; some equivalent of setvbuf might be worth looking into, rather than manually flushing all over the place, though.11:37
cjwatsonI think we were wrong to make any particular assumptions about the default buffering on pipes.11:38
xnoxcjwatson: experimentally, changing try: except:, feeding stdin & closing stdin/stdout. is all looks clunky.11:38
xnoxwhen:11:38
xnoxstdou, stderr = test_debconf.communicate ("VERSION 2.0")11:39
xnoxis all that's needed.11:39
xnox(with try/except IOError)11:39
xnoxso i was going to propose that as a longer term fix.11:39
cjwatsonThat seems wrong.  .communicate is defined to "read data from stdout and stderr, until end-of-file is reached".11:40
cjwatsonNow as it happens you probably get EOF because it's run out of stuff in the pipe, but it doesn't seem conceptually right to me.11:40
cjwatson.communicate is really meant for "and I don't want to do anything else with this process later".11:40
cjwatsonI think you should figure out how to make test_debconf.stdin line-buffered instead.11:41
* cjwatson goes out for a bit before UOS starts11:41
=== pete-woods is now known as pete-woods-lunch
xnoxbuffering=111:45
sil2100ogra_: I guess we'll have to cancel the evening meetings for the next 3 days I guess11:46
seb128sil2100, what's the status on the infrastructure issues? can I retry the build that failed earlier?11:47
sil2100seb128: not yet - it's almost fixed, we're still having some permission issues and webops are looking into that11:47
* sil2100 is using seb128's job for that11:47
sil2100I'm using your job for testing ;)11:48
ogra_sil2100, yeah, makes sense11:48
seb128sil2100, great, thanks11:48
=== gatox is now known as gatox_brb
=== alan_g is now known as alan_g|lunch
* sil2100 goes preparing lunch in the meantime12:29
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #71 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #71 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
=== alan_g|lunch is now known as alan_g
=== pete-woods-lunch is now known as pete-woods
tedgsil2100, silo 14 has some deps that need to be sorted, can you deallocate it?13:00
sil2100tedg: you want the silo freed?13:03
sil2100Ok :)13:04
sil2100I like the idea as we're low on silos13:04
seb128sil2100, did you fix the build environments?13:04
tedgsil2100, Yeah, it's going to take a while to fix the deps. No reason to hold it.13:04
sil2100seb128: not yet... webops are working on it as I have no access ;/13:05
sil2100seb128: I'm trying to help out as much as I can, but it's lunch time for the vanguard as well13:05
seb128k13:06
brendandsil2100, i'm looking for some info on how the smoke tests are run. is there a jenkins job i could look at?13:24
ogra_brendand, bzr branch lp:ubuntu-test-cases13:26
ogra_IIRC13:26
ogra_it is run as part of UTAH13:26
brendandogra_, not much in that branch13:27
davmor2popey: for the bulk of the default app (Note not core apps) if you long press them do you get a description you would expect?13:29
davmor2popey: ie compare calendar/clock with amazon/dialer etc13:30
popeydavmor2: probably not for the ones installed via debs13:31
=== gatox_brb is now known as gatox
popeydavmor2: the ones that have descriptions are coming from the store, until all of the apps are clicks, the debs will have missing descriptions I guess13:33
davmor2popey: ah okay that explains it ta13:34
sil2100brendand: yeah, one moment:)13:34
sil2100brendand: https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/274/console13:35
sil2100brendand: here for instance you have the run that had filemanager in it (and some others)13:35
dobeydavmor2: eh?13:35
popeyuh, did we break ubuntu-bug?13:36
popeyphablet@ubuntu-phablet:~$ ubuntu-bug unity813:36
popeyusage: whoopsie-upload-all [-h] [-t TIMEOUT]13:36
popeywhoopsie-upload-all: error: unrecognized arguments: unity813:36
dobeypopey: the apps installed from debs will only have missing descriptions if the .desktop doesn't have a "Comment=" field. however, the ones that do have it seem to have pretty awful descriptions :-/13:36
popeyok13:36
dobeymany of the click packaged apps also have pretty horrible descriptions13:37
davmor2dobey: why the eh?13:37
dobeydavmor2: i'm trying to understand what you're asking about13:37
dobeydavmor2: you are seeing apps with blank descriptions?13:38
=== barry changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #71 promoted | CI Train Support: US: barry, robru, stgraber - EU: sil2100, Mirv | Known issues: -
davmor2dobey: not blank just not descriptive compare clock app to dialer13:38
davmor2dobey: or clock app and friends13:39
dobeydavmor2: yeah, many apps have very poor "descriptions"13:39
popeyyes, clock = click, dialer isnt a click13:39
dobeyand the store has this "tag line" thing when you upload an app, which it munges into the description, and actually gives us as the first line of the description text13:39
dobeypopey: whether it's a click or not is irrelevant i think13:40
dobeypopey: the description for twitter and most of the default web apps are pretty awful too :)13:40
popeyfile a bug13:40
davmor2I only just noticed as I flicked through them testing the platform api for any breakages :)13:41
dobeyi did file one against friends already13:41
brendandsil2100, so we are rebooting the devices between test suites13:44
dobeyoh, well i filed a bug about friends-app.desktop not being translated, but i guess i didn't mention the bad description in it13:45
popeybug 132853513:45
ubot5bug 1328535 in unity8 (Ubuntu) "Performance overlay no longer works" [Undecided,New] https://launchpad.net/bugs/132853513:45
sil2100brendand: yes, as I remember correctly we do13:48
popeydavmor2: can you confirm bug 1328536 pls?13:49
ubot5bug 1328536 in apport (Ubuntu) "ubuntu-bug <package> broken in #76 mako" [Undecided,New] https://launchpad.net/bugs/132853613:49
brendandsil2100, ok. i'm trying to figure out why it's so difficult to reproduce these failures locally13:49
brendandsil2100, is there a single script that runs the smoke test from start to finish?13:49
davmor2popey: I use apport- bug I didn't even know ubuntu-bug was installed :)13:50
popeywell thats broken too13:50
sil2100brendand: uh, I remember doing something like this once, but I can't remember the exact steps and if that didn't change... so I guess the safest way is poking plars-away or reading up the logs13:51
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #71 promoted | CI Train Support: US: barry, robru, stgraber - EU: sil2100, Mirv | Known issues: -
sil2100ogra_: any news on the failing security tests?14:18
ogra_sil2100, yes, i pinged jdstrand in -touch earlier, he is looking into it14:19
sil2100Awesome :)14:19
sil2100Thanks!14:19
jdstrandit should be fixed now. bad test. sorry14:22
sil2100jdstrand: thanks o/14:23
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
bfillersil2100: getting failures trying to build silo-003: https://ci-train.ubuntu.com/job/landing-003-1-build/72/console14:40
bfillersil2100: is it a jenkins problem?14:40
sil2100bfiller: ah... yes, let me update the header on the spreadsheet14:40
sil2100bfiller: we're currently fixing jenkins ;/14:40
balloonsping fginther14:45
fgintherballoons, yo14:45
balloonsfginther, hey :-) So, I wanted to let you know about the discussion we had on running tests on trusty during merge proposals. Basically, given all the issues surrounding it and lack of support, we decided to just remove the trusty builds.14:47
balloonscan you tweak all the core apps at some point to go ahead and stop running trusty?14:47
fgintherballoons, that's easy enough to do14:47
balloonsawesome.. and hopefully we won't have another friday like the last one :-)14:48
rsalvetiseb128: you might be able to help us on that :-)15:03
rsalvetiwe wanted to land it today, but there's a bunch of packaging renaming happening in the platform-api mr15:03
rsalvetiand that will require someone to approve them from NEW15:03
seb128rsalveti, I can do the NEW side, sure15:03
rsalvetiwe're just finishing the testing side of it as we speak15:04
rsalvetiseb128: in case you already want to take a look at the renaming: https://code.launchpad.net/~ricmm/platform-api/v2-dynamic-refactor/+merge/22072115:04
ricmmseb128: we iterated a few times over it, but there might still be something amiss that you will catch15:06
seb128ricmm, rsalveti: k, looking in a bit, thanks15:09
sil2100seb128, bfiller: issues resolved (most probably)15:31
sil2100seb128: your silo is running build right now15:31
seb128sil2100, great!15:31
seb128thanks15:31
sil2100seb128, bfiller: it seems that *somehow* the debootstrap chroot got broken during the migration, which is strange15:31
* Mirv builds too, Qt 5.3 PPA shoud be again functional pretty soon after that (currently webbrowser is lagging behind archive version)15:36
=== gatox is now known as gatox_lunch
Mirvbfiller: could you look through the open Qt 5.3 issues and do some bugs assigning when you know who to assign to? http://is.gd/gZFEqm is the best link (filters out fixed-in-PPA ones)15:37
sil2100bfiller: I'll run the build job for you15:39
bfillerMirv: will do15:40
bfillersil2100: ty15:40
sil2100robru, davmor2, ogra_, slangasek, plars-away, popey: ok, so as discussed, let's skip the US TZ meetings during UOS15:44
sil2100There's a session I want to listen into even15:44
ogra_++15:44
robrumost excellent15:45
sil2100davmor2, popey: as you guys have the power of the calendar for the US TZ event, can you maybe cancel the 3 meetings?15:45
robrusil2100, which session interests you presently?15:45
Mirvbfiller: thank you15:45
davmor2I'd forgot this was even on15:46
sil2100robru: Unity8 Desktop Preview Image15:46
sil2100Anyway, as a track lead I need to be available for all the platform tracks15:48
popeysil2100: yes, i can15:49
sil2100popey: thank you!15:49
popeysil2100: done15:49
popeynp15:49
* sil2100 is a master of the universe but not a master of the google calendar it seems15:49
davmor2popey: damn you I'd just figured out how to do that too :)15:51
davmor2popey: I don't mind really though as long as it is done :)15:51
Mirvelopio: hey! could you run the gatekeeper job with ci-train-ppa-service/landing-005 again? since Friday we've gotten working media player and camera, so it'd be interesting to have results for those plug in general have another autopilot run. music app still crashes, though.15:54
Mirvelopio: oh, with the caveat that about 30 minutes from now, when https://launchpad.net/~ci-train-ppa-service/+archive/landing-005/+build/6087001 is safely published (finished building >20mins ago)15:54
elopioMirv: yes, I can. I'll see if autopilot is using the job.15:59
elopioping Ursinha: can we get this one triaged please? https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/127501216:00
ubot5Ubuntu bug 1275012 in Ubuntu CI Services "Add a job to run all the image tests with new qt versions" [Undecided,New]16:00
elopioI would like to know if we will have it in the near future.16:00
Mirvelopio: thanks. the Friday's run was fine (although I'm not sure if all AP:s from the image dashboard were again included or not)16:01
elopioMirv: do you have a link to that run?16:01
Ursinhaelopio: I'll have a look/hand over to the next vanguard person16:01
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #71 promoted | CI Train Support: US: barry, robru, stgraber - EU: sil2100, Mirv | Known issues: -
elopiothanks16:01
robruhmmm i'm not getting the video feed on the uos page...16:02
Mirvelopio: http://q-jenkins:8080/job/autopilot-release-gatekeeper/151/? - robotfuel mentioned something about that the "ALL" description for tests might be outdated and in theory it should be really ~all. I'm just wondering why there weren't camera AP failures reported since camera was still broken on Friday16:02
robrusil2100, can you get me a link for the unity8 video stream? it's not showing up on the summit page for me16:05
elopioMirv: camera app was not run there.16:06
sil2100robru: still waiting for it to be setup16:06
robruhm16:06
elopiooh, wait, actually it was16:06
elopioMirv: http://q-jenkins:8080/job/autopilot-release-gatekeeper/151/label=daily-mako/testReport/camera_app.tests.test_capture/TestCapture/16:07
elopioI don't know the camera tests, so I'm not sure what they are doing.16:07
Mirvelopio: it should take a picture, but the taking a picture button was disabled still on Friday. but there's only three tests there, while http://ci.ubuntu.com/smokeng/utopic/touch/mako/76:20140610:20140530/8503/camera_app/ has 1116:08
Mirvwell, we can also just simply see how it's this time that it's not disabled/broken16:08
ricmmanyone here familiar with u8 autopilot ?16:09
elopioMirv: there are 11 tests, http://q-jenkins:8080/job/autopilot-release-gatekeeper/151/label=daily-mako/testReport/16:09
elopioall passed.16:09
davmor2ricmm: so I had 3 fails on unity8 addressbook running now16:10
elopioricmm: I am familiar, but I tried to run them yesterday after a couple of weeks and I'm still trying to recover my machine.16:10
fgintherelopio, can I discuss the qt smoke test runner job with you later today?16:10
elopioit crashed badly.16:10
ricmmdavmor2: address book ran OK in all tests for me16:10
ricmmbut I'm having issues with unity8, after a while it reboots16:11
ricmm?16:11
elopioricmm: are you on desktop or phone?16:12
davmor2ricmm: so it ran fine for me bar the 3 failures16:12
ricmmphone16:12
ricmmdavmor2: mako? I ran them on flo16:12
davmor2ricmm: yeah mako16:12
ricmmoh you had 3 fails on unity816:13
ricmmI misunderstood that16:13
elopioricmm: on desktop, unity7 was restarted here. I can try on the phone as soon as I recover my desktop.16:13
ricmmelopio: what tests are you talking about?16:13
ricmmI'm talking about silo 7, what davmor is trying out16:13
elopioricmm: unity8 autopilot tests.16:14
ricmmdavmor2: how did you run it exactly? it's literally dying after a few runs for me, with an actual reboot16:14
ricmmdavmor2: also, do you have the error output?16:14
elopiore: <ricmm> anyone here familiar with u8 autopilot ?16:14
davmor2ricmm: I'm going to go back and dig into stuff I just want to get things running and compare it to the current run tests16:15
ricmmdavmor2: ok awesome, thank you for that16:15
ricmmI just want to understand what the failure on my device is16:15
ricmmif I run it without -v then a bunch of them pass until it reboots randomly, if I run it with -v none of them pass16:15
davmor2ricmm: it hates you, hate it back it worked for me :)16:16
ricmmI will16:16
davmor2ricmm: cordova 1 failure16:30
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #71 promoted | CI Train Support: US: barry, robru, stgraber - EU: sil2100, Mirv | Known issues: -
sil2100ogra_: do we have a bug for the indicator-network crash?16:43
ogra_sil2100, nope, since Wellark said the whole week in malta he would fix it i dont think anyone filed one16:46
* sil2100 sighs16:46
sil2100Right16:46
sil2100;)16:46
sil2100Ok, I'll fill it in then once I have a time window for that16:46
sil2100For now I'll simply add it to our list bugless16:46
balloonsogra_, would you happen to know where I can get old manifest files from? older than what's on cdimage atm.. seems to keep about a week's worth, I need a bit more than that16:47
sil2100Wellark: we're putting pressure on you!16:47
ogra_balloons, i think they are gone ... unless cjwatson has a secret place where he stores backups or some such16:48
ogra_balloons, my manifest diff files have the added/removed packages though16:48
ogra_http://people.canonical.com/~ogra/touch-image-stats/16:48
cjwatsonI don't16:48
cjwatsonI already referred balloons to the build logs though16:48
balloonsyea, he pointed out some nice build logs..16:48
cjwatsonWhich we do keep indefinitely16:49
sil2100ogra_: regarding that, let's have a chat tomorrow about moving our bots and scripts to canonistack16:49
balloonsmeans some tool tweaking.. ok, I may rebase to use your diffs instead of the manifests16:49
balloonsty ogra_16:49
ogra_sil2100, ++16:50
=== gatox_lunch is now known as gatox
sil2100davmor2: did you get any update from tedg or design on some of the greeter-related issues?17:01
davmor2sil2100: yes thanks but I'm not telling you :P17:02
=== alan_g is now known as alan_g|EOD
sil2100Heeey17:03
sil2100That's mean!17:03
sil2100;)17:03
davmor2sil2100: So the biggest one being redesigned is messaging, the others have tweaks no news on when those will land.  The stuff the needs fixing is in the master bug and will be worked on at some point I still need to add links to those17:03
davmor2sil2100: does that help any?17:05
sil2100davmor2: yeah, at least something, thanks :)17:06
elopioMirv: I'm starting the jenkins job again.17:11
sil2100ogra_: https://plus.google.com/109159869108744115904/posts/9YuCXibF2CS17:21
* ogra_ hugs sil2100 17:22
ogra_yay \o/17:22
ogra_now google has you !!17:22
sil2100Is that ok? ;p17:22
ogra_totally17:22
sil2100Since I'm a bit noob with this...17:22
ogra_it is perfect17:23
sil2100\o/17:24
elopiofginther: sure17:31
elopiosorry, I found your message too late :)17:31
asacricmm: how is the platform-api landing going?18:22
asaci see we need Prerequisite: lp:~thomas-voss/platform-api/hw-alarms-api18:23
asacto fix my avenger bug :)18:23
ricmmthat landed a long while ago18:23
ricmmhw-alarms-api that is18:23
ogra_asac, we're missing the indicator changes that use it properly now18:23
asacricmm: ok thats in the image?18:24
asacthat prereq?18:24
ogra_i was told it landed a week before malta or so18:24
asacso charles tells me he also needs the /dev/alarms being read-only fixed for his branch to land18:29
asacricmm: ogra_: who is doing that? you know?18:30
ogra_asac, charles i think18:30
asaccharles: ?18:30
charlesno18:30
asacsee :P18:30
charlesI just spoke to tvoss about it a few minutes ago, iiuc he's doing it18:30
asacok, but we dont know how?18:30
ogra_magic !18:31
ogra_he will swing his wand18:31
charleslooks like he's not idling here, I'll ping him to join18:31
asaclol18:31
asaci pinged him already18:31
charlesno reply yet, we'll see18:32
ricmmit is 8:30pm18:32
asaccharles: are your reviews etc. done already?18:32
* cjwatson gets frustrated waiting for the PPA publisher and considers spending half a day optimising it18:32
asace.g. could you start landing if this would be avail?18:32
charlesasac, if we want to wait for review signoff, ted is looking at it18:33
charlesasac, if push came to shove IMO we could start landing it18:33
asaccharles: in general we want MPs to get eyeball review first to avoid wasting silo/landing overhead18:34
asactedg: ^^18:34
asactedg: are you happy with charles branches :)?18:34
ricmmasac: in general we want more than eyeball18:34
asacyeah18:34
asaceyeball and pre-testing etc.18:34
asacevery compnent should have a check list that should be followed18:34
asacricmm: any idea how tvoss might plan to fix /dev/alarm read-only?18:35
asacand which component he will touch18:35
charlesprobably ought to add wakeup tests to the indicator-datetime walkthrough plan18:35
asacyep18:35
asacplease update testplan :)18:35
charleshyep18:35
ricmmasac: ogra_ this is probably an android item18:35
asaconce this is fixed i will put my life in the hands of our devel images18:35
ricmmwe should be able to fix those nodes permissions without much issue18:36
asacso better not regress :)18:36
ricmmogra_: am I right?18:36
asacudev :)18:36
asactvoss_: \o/18:36
tvoss_here we go18:36
tvoss_asac, what's up?18:36
asac20:34 < asac> ricmm: any idea how tvoss might plan to fix /dev/alarm read-only?18:36
charles:)18:36
sil2100ricmm: how's the papi landing proceeding?18:36
ricmmsil2100: very well, there is a special unity8 AP test that misbehaves with it18:36
ricmmbecause the test is launching unity8 directly and not using upstart18:36
sil2100Ouch18:36
ricmmso its not inheriting environment18:37
ricmmmterry is reviewing my patch for it18:37
tvoss_asac, we have to fix /dev/alarm permissions to whatever the indicator requires18:37
tvoss_rsalveti, around?18:37
asactvoss_: yeah, but charles said you said you will do it :)18:37
asacso wonder what you wanted to do:18:37
asac1. find someone else to do :)18:37
asac2. have a plan :)18:37
sil2100ricmm: thanks :)18:37
charlestvoss_: tell him ogra_'s working on it18:37
tvoss_asac, ogra_'s working on it :)18:37
asacogra_: i assume thats news to you, so ignoring that how do we fix it :)?18:38
asacudev rule?18:38
tvoss_asac, I would think so, much like we set the permission for the haptic feedback devices18:38
ogra_i am ?18:38
tvoss_ogra_, we need to adjust permissions on /dev/alarm18:39
* sil2100 EODs18:39
sil2100Or maybe not...18:39
tvoss_charles, eds would be setting the alarm?18:39
ogra_tvoss_, ah, trivial18:39
charlesogra_, just completing the blame circle from you -> me -> tvoss18:39
asacogra_: what needs landing for that? can you do the patch so we can get that into the silo for charles fix?18:39
ogra_can someone file a bug and assign to me so i dont forget over UOS18:39
charlestvoss_, not sure I understand the question? indicator-datetime-service will be the process that calls platform-api's hardware API & sets the wakeup alarm18:39
asacogra_: hmm. i can ping you every 30 minutes :)18:39
charlestvoss_, EDS doesn't do wakeups per se18:40
ogra_asac, ok do that then :P18:40
* ogra_ wants to see how long you persist :P 18:40
tvoss_charles, okay, that runs under which user? phablet?18:40
asacogra_: ok, whats the status on /dev/alarm permissions?18:40
tvoss_lol18:40
ogra_asac, nearly done ... 29min to go18:40
* asac points out it would be better to remember if the alarms would work on ubuntu phone :)18:40
asaclol18:40
ogra_haha18:40
asacogra_: ok, please ping me in 28 minutes so i can remember you18:40
* asac thinks thats a smart solution18:41
asachehe18:41
charlestvoss_, will check owner as soon as I can shell in18:41
tvoss_charles, ack18:41
asacogra_: anyway, would really be cool if we could have that patch when charles and tedg are doner eviewing their patches18:41
tvoss_ogra_, I would think a group permission for writing would do it18:41
asacthink that should happen in 1-2 hours earliest18:42
charlesphablet runs the primary, lightdm runs its own18:42
ogra_tvoss_, ACTION=="add", KERNEL=="alarm", OWNER="system", GROUP="system", MODE="0664"18:42
ogra_seems to be 0664 already18:42
asacbut where do we ship that line in?18:42
asacwhats the package?18:42
ogra_asac, lxc-android-config18:42
asacin indicator-datetime directly?18:42
ogra_lib/udev/rules.d/65-android.rules18:42
asachmm. i hate that package. caused so many regressionms :)18:42
ogra_pfft18:42
tvoss_charles, is the indicator in group system?18:43
tvoss_charles, or better: the indicator user?18:43
tedgWe don't have any special permissions for the indicators today.18:43
* tedg is back18:43
asachey tedg :)18:43
charlestvoss_, ^ what tedg said wrt permissions18:44
asacwe need your pedantic review and testing role for charls alarm MPs :)18:44
asactedg: ^^18:44
asac:)18:44
charleshe knows, I've been pestering him in PM18:44
asacyou never know :)18:45
tedgHeh, yeah. I figured it was a DoS attack on my IM client at first ;-)18:45
rsalvetitvoss_: what's up?18:45
rsalvetiMirv: are you also testing qt 5.3 on the x86 emulator?18:46
asachope rsalveti is also here for the alarm topic :)18:46
tvoss_charles, tedg so yeah, the user under which the indicator runs should be in group system18:46
ogra_yeah, alarms on 5.3 in the emulator18:46
asaccan the emulator deep sleep?18:46
ogra_the more important qurestion is "does it dream ?"18:47
asacdunno, i know that i am dreaming far too much because of the broken alarm :P18:48
tedgtvoss_, I've got no one in that group...18:48
ricmmso many words18:48
ricmmall we need is to either put phablet in system, which wont happen18:48
ricmmor make /dev/alarm 66618:48
ricmmand go to hell18:48
ogra_lol18:48
ogra_and have jdstrand show up at your home at 3am in the morning18:48
tedgWhy isn't logind doing the permission here like with audio?18:48
asacis /dev/alarm confined so apps cannot access? if so 666 sounds okayish :)18:48
ogra_tedg, its handled by udev at creation time ...18:49
ogra_you could surely stack something else on top18:49
tedgHmm, wait. If multiple users are logged in, do we want both their alarms to go off?18:49
tvoss_tedg, let's fix that post rtm18:49
tvoss_tedg, it would require global knowledge18:50
asacdoesnt feel thats something that should be solved through permissions :)18:50
rsalvetiogra_: we should ideally have group to access alarm18:50
ogra_rsalveti, no prob with that18:50
rsalvetinot sure we want everyone to have access to it18:50
rsalvetibut yeah, let's just open it up for now18:50
asacawesome ... so 666 it is?18:50
ogra_yeah, we'll give jamie your address18:51
charlesto be replaced with group later, yes?18:51
rsalvetithe group won't fix the multiple user issue18:52
tedgWe could make indicator-datetime sguid18:52
ogra_right18:52
rsalvetiwe need to think further to get that fix properly18:52
ogra_you will need a service on top18:52
asaci am not sure... if 666 is good enough for RTM and it wont fix multiuser, we probably dont need to do the group18:52
tvoss_rsalveti, right, but it will get us moving if we open up now18:52
asacack, what rsalveti says basicall18:52
ogra_managed by logind18:52
rsalvetiogra_: something along that line18:53
rsalvetiyeah, change to 666 for now18:53
ogra_ugh18:53
asacfeels like something we can do when we land multiuser18:53
rsalvetiso we can unblock this already18:53
asacgood18:53
asacwho is owning multiuser topic?18:53
rsalveticonfined apps won't be able to access it anyway18:53
asacwhoever that is, we should enusre he knows that we should include alarm support in this plan18:54
ogra_probably mterry18:54
ogra_as he owns the greeter18:54
asacmterry: you have a multiuser plan already? can you inject the alarm for multiuser topic if it isnt in there?18:54
asacso we wont forget?18:54
mterryasac, I have some ideas for multiuser, sure.  Didn't realize I owned it, but I suppose that makes sense.  :)18:55
mterryasac, will make a note18:55
cjwatsonI'm a bit worried about the approach of "open up permissions for now, we can fix it when we do multiuser"18:57
cjwatsonNot that I have a better suggestion, but it'd be pretty easy for this to bite us down the line18:57
tvoss_cjwatson, we could take the somewhat cleaner approach and add phablet to group "system"18:58
cjwatsonThat's an android-compat group, isn't it?18:58
ogra_cjwatson, we could just add an alarm group and add the user to it18:58
ogra_(and change the udev rule accordingly)18:58
charlesthat's sane...18:58
ogra_a bit more work but i agree its worth it18:59
cjwatsonPossibly, yeah, though extra groups are annoying to manage if we need to remove them later18:59
cjwatsonIs there no other reasonably-fine-grained existing group that would work?18:59
cjwatsonHow about "audio?19:00
ogra_phablet adm tty dialout cdrom sudo dip video plugdev autopilot nopasswdlogin radio bluetooth android_graphics android_input audio sdcard_rw gps android_net3 android_net android_net219:00
ogra_thats what phablet is in atm19:00
cjwatsonSo tell me why audio isn't appropriate19:00
ogra_audio might work19:00
asacjdstrand: what do you suggest?19:01
ogra_not sure there are android bits on the ubuntu side of the fence that need it as systme gropup though19:01
mterrycjwatson, ogra_: does the greeter need access to this dev19:01
mterry?19:01
asacjdstrand: making /dev/alarm 666 is too evil to do?19:01
asac:)19:01
charleshardware wakeups don't necessarily need audio19:01
charlesand audio doesn't necessarily need hardware wakeups19:01
charlesit's just that indicator-datetime needs both19:01
ogra_mterry, well, can the greeter contolr volume (read is it in the audio group)19:01
asaccjwatson: is it hard(er) to add a new group? or why try to reuse an existing one?19:02
ogra_asac, it is hard to remove it on installed systems19:02
asacoh session started19:02
cjwatsonasac: It's annoying to manage more of them, requires changes in more places, we don't have good ways to sunset them19:03
asack19:03
cjwatsonIt's certainly not impossible if that really is the right answer, but my experience is that it's worth thinking about it first19:03
mterryogra_, it sets volume via AccountsService right now and user session that happens to be open sets it via hw19:04
mterryogra_, but sound in the greeter is a wider problem right now19:04
jdstrandso, the phablet user is in too many groups as it is19:04
asac:P19:04
mterryogra_, like in future, there may not be an open session19:04
jdstrandthe phonedations team has todo items to clean that up19:04
jdstrandseems like we would want to avoid using a group they plan to clean19:05
jdstrandI'm not keen on 66619:05
cjwatsonthe set of groups that we currently add desktop users to should be fine though19:05
cjwatsonthe first desktop user at least19:05
jdstrandI'd like mdeslaur to comment actually, because he and mterry have talked about pk, the greeter and seat management quite a bit19:07
jdstrandis is in a session atm19:07
mterryogra_, actually yeah, greeter can control volume because logind gives it access as the active session19:08
jdstrandmdeslaur: when you get a chance, please comment on /dev/alarm ownership. apparently indicator-datetime needs access to /dev/alarm. some have suggested 666 for /dev/alarm (yuck), others to add a group and other to use 660 with an existing group (eg, 'audio')19:08
mterryI guess this would be similar issue19:08
ogra_yeah19:09
jdstrandmdeslaur: also note that the phablet user is in too many groups atm and that phonedations is hoping to clean that up for rtm (ie, adding a group or reusing an android group may not be the best choice if we are just going to remove it later)19:12
ogra_jdstrand, there are groups we need because the android bits need to be able to use them with the right UID ... android is all about groups, no other proper device control mechanism there19:15
ogra_so if we change them things start to break19:16
rsalvetiaudio group doesn't seems right though19:17
rsalvetithe main feature here is being able to wake up the system by triggering alarms19:17
rsalvetihas nothing to do with audio itself19:17
ogra_well, i dont see another group that would fit better in the list19:19
ogra_android_input ?19:19
rsalvetiwell, we could just use any group then :-)19:19
ogra_right19:19
ogra_audio is as good as any other19:19
rsalvetiright19:20
rsalveticdrom19:20
rsalvetihahah19:20
rsalvetijust noticed phablet is part of that19:20
ogra_lol, right, thats a spare one19:20
rsalvetimaybe phablet group?19:20
rsalvetias this will be single user only anyway19:21
ogra_yeah19:21
ogra_works too19:21
ogra_can we make it 0660 ?19:21
rsalvetiat least not 66619:21
rsalvetiyup19:21
ogra_or do you think the 4 is needed in the end19:22
rsalveti0660 system:phablet19:22
rsalvetiright19:22
rsalvetidon't think reading is bad19:22
rsalvetibut won't help in anyway19:22
rsalvetiso just put 066019:22
rsalvetieasier to open up than close it down later19:22
ogra_yeah19:23
mterryAgain, consider greeter19:24
mterryOr multi-user in general19:24
ogra_http://paste.ubuntu.com/7625093/19:26
rsalvetiogra_: looks fine19:28
rsalvetimterry: in which terms?19:28
rsalvetiwho will be reading the alarm device file?19:29
rsalveticharles: ^19:29
rsalvetias which user?19:29
mterryrsalveti, I guess i'm not 100% clear on the use case we're talking about.  But if greeter needs the same permissions, phablet group won't cut it.  Nor I imagine will that work great for multi-user devices?19:29
rsalvetiin the greeter use case19:29
mterryrsalveti, the user for greeter is lightdm:lightdm19:29
rsalvetimterry: we're not trying to solve the multi-user case atm19:29
charlesrsalveti, the phablet user runs the main indicator-datetime service19:29
charlesrsalveti, lightdm also runs one19:30
rsalvetiright19:30
rsalveticharles: what is the service started by lightdm?19:30
mterryrsalveti, charles: in not-too-distant future, consider the possibility of an encrypted home dir where the greeter is running but user session isn't19:30
rsalvetimterry: sure, in that case the alarm shouldn't even be enabled19:30
mterryProbably not RTM19:30
rsalvetiI'd imagine19:30
charlesrsalveti, for both users it's indicator-datetime-service19:31
rsalvetihow to trigger a user alarm if the user session is not even up19:31
ogra_it is up19:31
ogra_(currently at least)19:31
mterryrsalveti, well we have an external location for some information (AccountsService) -- conceivably, the alarms could be stored there.  Depends if design wants alarms to work in that case19:31
ogra_we have constantly two sessions running now19:31
rsalvetiin case the user session is not up, on a multi-user use case19:31
mterryogra_, rsalveti: right.  I was just listing future scenarios where this current plan is insufficient19:32
rsalvetiright19:32
rsalvetifor sure, we're not trying to solve that right now19:32
rsalvetiall we want is a working solution for a single user and not cause any more damage later on, once we implement the multi-user use case19:32
charles+119:32
ogra_mterry, for that we will need a service sitting on the alarm device anyway ... and then drop all the gruop hackery19:33
rsalvetiright, ideally we want to have someone controlling the hw access19:34
mterrySure, I'm not trying to be stop energy.  Just better to know future plans when doing something shorter term19:34
mterryWell that's probably logind, which controls access to all sorts of devices already19:34
mterryFor example, the fact that phablet is in audio group is a hack around that, back when logind wasn't configured correctly19:35
mterryBut this current group plan is fine for now19:35
mterryLogind needs more smarts anyway to do the right thing19:35
rsalvetiright19:35
ricmmrobru: hey, are you alive?19:36
robruricmm, barely19:36
robruwhat's up?19:36
ricmmrobru: ;)19:36
ricmmrobru: is it possible to remove an MR from a silo, and thus drop the already-built pkg from it?19:36
ricmmis the only way a full reconf/rebuil? or is there a shortcut19:37
robruricmm, yep I can take care of that.19:37
robruoh hmm19:37
robruricmm, reconf is definitely necessary, it *should* be possible to avoid a full rebuilt by doing a WATCH_ONLY build but that's been buggy lately19:37
robruricmm, did you take the MP out of the spreadsheet yet?19:38
ricmmno, not yet19:38
ricmmits a possibility with a fix im working on19:38
robruricmm, ok just let me know, I'll have to delete the package from the PPA manually19:38
ricmmalright19:38
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #71 promoted | CI Train Support: US: barry, robru, stgraber - EU: sil2100, Mirv | Known issues: -
* mdeslaur reads backscroll19:59
robruricmm, just a heads up, we're about to publish telephony-service, so that'll at least need a rebuild in your silo soon20:00
sil2100o/20:00
ricmmrobru: how long until it hits trunk?20:01
mdeslaurogra_, jdstrand, mterry: so that does /dev/alarm do exactly?20:02
asacdid we reach agreement on what to do with the 666?20:02
asac:)20:02
asaccharles: ?20:03
asacsorry was focussed on session20:03
mdeslaurogra_, jdstrand, mterry: ah, so it wakes up the device...in a multiuser scenario, in theory some sort of system power daemon would manage that, and the user would use a dbus call to set it which would use policykit and would make sure the user owns the current session20:05
bfillerrobru: can I have a silo from line 39 please?20:05
robrubfiller, sure20:12
robrubarry, ^ wanna do it? ;-)20:12
barrymonkey wakes up20:12
robruricmm, oh sorry, missed you message. probably a couple horus20:12
barrybfiller: silo 1220:13
bfillerbarry: thanks20:14
robrubarry, so, eg if you look at https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&rm=full&pli=1#gid=30, the spreadsheet for the silo page, the button there is called "merge & clean", that's why the bot says "click merge & clean". my dashboard page is newer than both of those things though20:16
barryrobru: ah20:16
robrubarry, alright, I'm going to pop off for lunch, back soon!20:17
barrysounds good20:17
asacrsalveti: did we agree on 666?20:21
rsalvetiasac: we decided to use 0660 and system:phablet for now20:21
asaccool20:21
asacrsalveti: who is landing what?20:21
rsalvetiogra_ did the debdiff, not sure if he already uploaded it20:21
asacwe probably want that to go into the same silo that charles will use?20:22
ricmmrobru: well, lets see, maybe im there first ;D20:22
ricmmrobru: I'll make sure to rebuild otherwise20:23
rsalveticould land separately, but won't hurt to make it as part of that sile20:23
rsalveti*silo20:23
asacyeah, lets put it in there20:23
asacso we test the real thing together20:23
rsalvetisure20:23
rsalvetiogra_: ^20:23
asacdo we need to do something so that indicator runs as the right user/group too?20:23
asaccharles: do you already need/have a silo?20:23
asactedg: how do the reviews look like? :)20:23
tedgasac, I think that jenkins tripped over itself :-/20:24
asactedg: how about the code review by your eyeballs? does that look good?20:24
tedgasac, yes, that looks good.20:24
asactedg: did you test it locally too?20:25
tedgasac, Not for a code review, will for the silo landing.20:25
asack20:25
asactedg: what is missing from here: https://wiki.ubuntu.com/Process/Merges/Checklists/indicator-datetime ?20:26
asacjust jenkins? :)20:27
tedgYup, though that gets updated a bit in the MR.20:27
asacguess the unit tests would be run in the ppa too?20:27
* asac thinks that jenkins build and unit tests would be happening in the silo ppa anyway, so is kind of fine to fastpath if we are confident that both will work20:28
tedgYes20:28
asacbut your guys call (its your checklist etc.)20:28
tedgUhm, yeah, in general though I try to avoid using silos until we're sure it builds somewhere in infrastructure.20:29
tedgThey're usually in demand.20:29
asacack20:29
asactedg: can you try build locally?20:29
asac:)20:29
asacnot sure what is going on wiht the CI bot jenkins, maybe its just a retry20:29
tedgI did and it works. But my machine is way easier to build things on than Jenkins :-)20:29
asaccheck with vanguard i guess20:29
asactedg: your x86 machine? or your phone/arm?20:30
tedgI didn't build it on the phone, but that is easier to build on than Jenkins as well.20:31
tedgIt has a bunch of dev stuff on it.20:31
asack20:31
asacwell, you guys know how to do things right20:31
asacrobru: how manu silos are free?20:31
tedgSpreadsheet says 220:32
tedgG120:32
asacheh20:32
asachmm. had bip problems20:35
* asac reboots bip machine after sec update - maybe ttyl :)20:38
ricmmthomi: hey, are you awake? :)20:43
asactedg: so did you convince yourself that building and testing on your phone might help us to move forward :)?20:45
balloonsfginther, just checking to confirm / deny trusty has been removed from core apps builds.. specifically I need it gone from reminders atm :-)20:45
asactedg: would be cool to really follow rule book20:45
asactedg: you need that phone wiped for testing the silo anyway, so the earlier to say good bye to thwat is on it the less likely you will try to dodge that step :)20:46
tedgasac, Not sure why building on the phone is "following the rule book" ?20:47
tedgAFAICT the rules state that Jenkins needs to be happy, which is exactly what I'm doing.20:47
tedgYou're suggesting skirting around the rule book.20:47
tedgAnd, none the less, testing on the phone isn't all that's required for an indicator. I would hope that people don't think that's adequate.20:48
fgintherballoons, sorry about that, updating the jobs right now (the currently running jobs will need to finish before it's done-done)20:48
balloonsfginther, lol.. you can cancel them all then20:49
ricmmtedg: did you test on the phone or not?20:49
asactedg: point taken, what i sensed though by you saying that you dont want to kill your phone setup is that you wont test the silo :)20:49
asacpoint about rul book20:49
asacnot the rest :L)20:49
balloonsfginther, I top approved several pending merges under the assumption, then thought I should ask20:49
ricmmjust wondering about phone testing before we go into proper silo testing and deployment20:49
ricmmso pre-siloing20:49
tedgI'll test the silo, but testing isn't a code review20:49
balloonsfginther, I can can them20:49
ricmmconsiering this is a phone HW alarms related task, its worth checking on the phone20:49
thomiricmm: yup20:50
ricmmand by the phone I mean the phone an a tablet, as their sleep behaviours are different20:50
fgintherballoons, thanx20:50
ricmmthomi: \o/ good morning20:50
ricmmthomi: can I tell autopilot to run tests in the order I want?20:50
ricmmI want to run three tests from the unity8 suite20:50
ricmmbut autopilot seems to be deciding what order to run them on, or phablet-test-run, whatever does it20:50
ricmmI dont have greater knowlege of these tools, so wondering if you can shed some light20:51
thomiricmm: yup, you can list the test ids explicitly, one after the other on the command line20:51
fgintherballoons, reminders is now updated, it's ok to approve again20:51
ricmmI did, but its rearranging the order20:51
ricmm:(20:51
thomi'autopilot run test.id.one test.id.two ...'20:51
balloonsfginther, awesome thanks20:51
ricmmto whatever it pleases20:51
thomiricmm: hmmmm. so veebers is now looking after autopilot - you should talk to him :)20:51
ricmmbut do you know?20:51
ricmmconsiering its your brainchild20:52
ricmmveebers: or you :)20:52
thomiricmm: I suspect it's a bug, no onen has reported it yet20:52
veebersricmm: hey, just checking something one mo :-)20:52
ricmmthank you!20:52
veebersricmm: hey, no way currently to set the order specifically (you can randomise so it's different each run though ;-) )20:53
veebersricmm: a workaround right now, which is a pain I know, is go: autopilot run test.id1; autopilot run test.id2  . . .20:53
veebersI haven't came across anyone needed to run suites in a specific order as of yet20:54
robruricmm, sorry about that, was on lunch. yeah, silo 19 is merged now, you'll have to rebuild telephony-service20:56
ricmmrobru: alright, im on it20:56
ricmmwill wait for my other branches to rebuild tho20:56
robruricmm, no rush, just needs to be done before you can publish20:57
rsalveticrap, disconnected20:57
ricmmveebers: how can I randomise?20:57
ricmmI only have two tests, I'm sure ill hit the right order eventually ;)20:57
veebersricmm: heh :-) argument to run: "-ro, --random-order " (i.e. from autopilot run --help)20:57
veebersricmm: why is the order important?20:58
ricmmcan I pass that to phablet-test-run somehow?21:03
ricmmveebers: well I have an odd feeling that one test isnt reverting some stuff in the teardown as it should21:03
ricmmand the order might be impacting21:03
=== dpm is now known as dpm-afk
veebersricmm: ah I see, um I'm not sure about phablet-test-run. I think either 1 of fginther, doanac or something might be able to answer that question (or point you at who can)21:04
ricmmveebers: ok21:05
ricmmveebers: to confirm, each test kills the previous running instance of autopilot and brings up a new one?21:05
ricmmor does it all run in the same "env"21:05
veebersricmm: the autopilot process is the same across a whole run21:05
fgintherricmm, you can try using the '-x' option to phablet-test-run to run whatever cmd line you need to give it21:06
veebersricmm: if any environment variables are altered within the test using the correct mechanism (i.e fixtures.EnvironmentVariable or deprecated patch_environment) they are reset after the test ends21:06
fgintherricmm, but you can't otherwise change the options passed to autopilot by default21:07
ricmmI want to run all three tests, in one autopilot run, in the order I want21:08
ricmmcan I achieve that with any of the cmd line runners?21:09
thomiricmm: how about 'phablet-test-run -x "autopilot run test_one; autopilot run test_two; autopilot run test_three"' ?21:09
ricmmveebers: its using patch_environment() but I'm still weary of it21:10
veebersricmm: do you know what it may or may not be modifying (i.e. is it an env var)? Perhaps you could modify the test to log out the contents of envat the start and end of the tests21:13
ricmmI guess I can try that21:14
ricmmbut then I need to run the full suite again, heh21:14
ricmmoh wait nevermind, im being dumb21:14
ricmmmaybe because its late21:14
veebersheh :-)21:14
ricmmI think I can get rid of that env patching21:14
ricmmrobru: ok, I've pushed a build req for telephony-service plus my two packages21:17
ricmmin the end we wont need to remove one of them21:18
ricmmjust rebuil21:18
robruricmm, cool21:18
tedgrobru, So for the android change, I've not had an "extra package" before. Is that something that I need to upload?21:22
tedgrobru, Or does it happen automagically?21:22
rsalvetitedg: I already did21:22
tedgrsalveti, ? to the PPA?21:23
rsalvetitedg: yup21:23
* tedg refreshes21:23
tedgAh, okay.21:23
rsalvetineeds someone with enough permission to upload it directly to the ppa21:23
tedgrsalveti, Thanks! Is that something I should have done had I known? :-)21:23
tedgOh, okay.21:23
robruyeah, nothing magical about CI Train21:27
bfillerrobru: we need a silo for line 33 (telephony-service) - not sure if this was waiting on anything to be cleared in other silos first21:37
bfilleris that the ricmm stuff?21:37
robrubfiller, ricmm has a silo with telephony-service yeah21:37
rsalvetithere's plat v2 from ricmm21:37
robruricmm, are you close to landing?21:37
bfillerok21:37
robrubfiller, the funny thing is, ricmm *just* started a rebuild on telephony-service because we just published a conflicting one a couple hours ago.21:38
robrubfiller, so if ricmm isn't ready to land today I'd say we can do yours, but I don't want to step on his toes if he's just moments away from publishing...21:38
bfillerrobru: no rush, we'll just wait for his to land21:38
robrubfiller, ok great21:38
rsalvetiricmm: what else is needed besides the packaging review by seb?21:39
=== barry changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #71 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
charlesrsalveti, I'm getting an error installing lxc-android-config from silo 1422:02
charlesrsalveti, http://paste.ubuntu.com/7625734/22:03
rsalvetioh, indeed, that needs special instructions, to be done from recovery22:08
rsalvetilet me find it22:08
rsalveticharles: http://paste.ubuntu.com/7625773/22:16
charlesrsalveti, ty22:16
ricmmrobru: im working on it22:27
ricmmrobru: some things just finished building22:27
ricmmI need to run some clean tests with the current silo state and DONE22:28
robruricmm, sweet, i can publish, just say the word22:28
ricmmit will need seb to look at it in the morning, he said he would today but it didnt happen in the end22:29
ricmmas he needs to ack some NEWs22:29
ricmmrsalveti: still alive?22:30
rsalvetiricmm: yes22:44
rsalvetilooking for dinner, but around22:44
tedgrsalveti, Got an error when upgrading lxc-android-config, should I be concerned about it?23:04
tedgrsalveti, unping, charles set me straight23:15
tedgLooking for a tablet, neither myself nor charles has one to test silo 14.23:16
tedgIf someone has a tablet and can test it that'd be great, else we can ask folks in the morning.23:16

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