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

plarsLaney: I talked to thomi about the USS tests, he said they are planning a new AP release and we should have a fix for it soon: https://bugs.launchpad.net/autopilot/+bug/127827204:21
ubot5Launchpad bug 1278272 in Autopilot "Autopilot cannot attach process stdout or stderr that contain non-ascii characters" [Critical,In progress]04:21
* plars -> zzz04:21
fgintherveebers, are you still there?04:32
veebersfginther: Hi, yep still here04:32
fgintherveebers, what's up with autopilot/cupstream2distro-config04:32
fginther?04:32
veebersfginther: I'm not too sure. I noticed earlier today this failure here: https://jenkins.qa.ubuntu.com/job/autopilot-1.4-trusty-amd64-ci/13/console04:33
veebersand see that it's trying to use lp:autopilot/1.4 instead of lp:autopilot04:33
fgintherveebers, ok, autopilot/1.4 was removed I see04:34
thomisorry about that fginther.04:34
fgintherI'm confused as to why the autopilot-1.4 job was used, there still a set of jobs dedicated to lp:autopilot04:37
fgintherbrb04:37
veebersfginther: just heading back home, will be online again shortly (or file  me an email :-))04:43
fgintherveebers, ack04:43
fgintherveebers, I think I have it figured out, will send a message04:43
veebersfginther: awesome thanks04:45
seb128s!09:00
seb128(ups, xchat changing channels on start while typing)09:01
sil2100Mirv: meeting!09:31
Mirvmöte09:34
psivaasil2100: https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-daily/28/artifact/clientlogs/ubuntu_system_settings/_usr_sbin_system-image-dbus.32011.crash/*view*/09:42
psivaaprobably for Laney to look at?09:42
psivaamay be not..09:43
ogra_PermissionError: [Errno 13] Permission denied: '/var/log/system-image/client.log'09:48
vilasil2100: also, this morning, a kernel crash on an otto node you may want to track: http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1419/console09:48
popeysil2100: so was there a discussion last week while I was away about who should dogfood?09:49
popeyI am happy not to do any more dogfooding if someone from QA is taking it on09:49
ogra_Mirv, have you seen my mail about rootstock-ng ? you should be able to procude testable images for Qt 5.2 now09:49
popey(I have other things I can of course be doing) but if it's still needed, happy to do it.09:50
ogra_*produce09:50
Laneypsivaa: not me, system-image is barry09:53
LaneyI actually got this a lot on my desktop already and filed https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/126023709:53
ubot5Launchpad bug 1260237 in system-image (Ubuntu) "system-image-dbus crashed with PermissionError in initialize(): [Errno 13] Permission denied: '/var/log/system-image/client.log'" [Medium,New]09:53
psivaaLaney: ack, got that late, my bad09:53
Laneyand there's https://bugs.launchpad.net/ubuntu-system-image/+bug/1222984 which is Won't Fix...09:54
ubot5Launchpad bug 1222984 in Ubuntu system image "traceback when run as non-root" [Low,Won't fix]09:54
ogra_well09:54
ogra_i would think that system-image-dbus talks to a root owned process on the other side09:55
ogra_weird if it doesnt09:55
ogra_(and that process should own the logging preferably)09:55
psivaapopey: i brought it up in the meeting since i saw someone from QA team started doing it last week. I could have wrongly assumed about it.09:57
LaneyI haven't looked into the details, but crashing is certainly wrong09:57
Mirvogra_: yes, very interesting! the QA team should be able to use that too for fully flashed testing.09:57
Laneya) it should print an error09:57
Laneyb) why is it a d-bus activated service if only root can make use of it?09:57
Laneyanyway, I'm not really here :-)09:58
thostr_sil2100: can you publish silo 1 and 3. also reconfigure silo 5?10:04
sil2100popey: so, I know there were discussions, I know Didier and Jason were chatting with Julien a lot, but nothing definite got set10:07
sil2100popey: at least I don't know about it10:08
sil2100thostr_: hello! I'll reconfigure silo 5, with publishing we try to wait a little bit until we get one failure tracked down10:08
sil2100thostr_: but I promise to publish them before evening today10:09
popeypsivaa: I asked omer to test while I was away at the sprint.10:12
psivaapopey: ohh, then my assumption was wrong. sorry :)10:12
popeynp10:13
thostr_sil2100: reconfigured?10:20
sil2100thostr_: ...done!10:22
thostr_sil2100: thanks10:23
ogra_Mirv, right ...10:41
sil2100psivaa: any luck with downgrading telepathy?11:09
sil2100I mean, telephony11:09
psivaasil2100: the dialer app test failure is not as deterministic as we thought before.11:10
psivaathe tests sometimes pass11:10
psivaasil2100: so i am having to run the test a few times before confirming anything11:10
sil2100psivaa: oh, right, the smoketesting gave the impression it's reproducible all the time11:11
sil2100psivaa: if you manage to find something out, just ping me here please11:11
psivaasil2100: right it failed on the first attempt, but a couple of reruns passed, then it failed again, so there is flakiness.11:11
psivaasil2100: reverted the package and running now to see if the flakiness is going and i'll update you11:12
sil2100Thanks :)11:13
=== mhr3__ is now known as mhr3
rsalvetimorning12:12
sil2100Morning12:15
=== MacSlow is now known as MacSlow|lunch
psivaasil2100: ogra_: still no luck on the dialer-app hangup test failure.12:17
psivaaone thing i see is that in all the attempts where the test fails, i see http://pastebin.ubuntu.com/6908750/12:17
psivaasil2100: ogra_ but i couldn't see which package that could cause it,12:18
psivaai tried reverting the dbus related packages in http://people.canonical.com/~ogra/touch-image-stats/20140206.2.changes too but to no avail12:18
ogra_psivaa, did you try telephony-service too ?12:20
ogra_(http://people.canonical.com/~ogra/touch-image-stats/20140207.changes)12:20
psivaaogra_: that was the first one and it dint make any difference12:20
sil2100hmmm12:20
psivaasil2100: ogra_ https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1226298 appear to have some similarities. but this was fixecd12:27
ubot5Launchpad bug 1226298 in telepathy-ofono (Ubuntu) "[mako] After 5-10 incoming calls ( ended remotely ), no more ring/snap decision" [Critical,Fix released]12:28
ogra_and quite a while ago it seems12:28
psivaayes, the kernel log is kind of similar though12:29
ogra_it actually points to pulse/alsa though12:29
psivaaogra_: are there any recent uploads on these?12:30
ogra_http://people.canonical.com/~ogra/touch-image-stats/20140207.1.changes12:30
ogra_libasound212:30
ogra_(and *-data)12:30
psivaaok, let me try them next12:31
=== alan_g is now known as alan_g|lunch
psivaareverting that doesn't help12:45
sil2100;/12:45
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: josepht | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
xnoxcihelp: josepht: autopilot project configuration was broken, so https://code.launchpad.net/~xnox/autopilot/use-fb-sizes/+merge/199295 jenkins bot at the end disapproved things.13:10
xnoxcihelp: josepht: can that be re-triggered please?13:11
josephtxnox: looking13:11
=== MacSlow|lunch is now known as MacSlow
xnoxjosepht: also I need to land https://code.launchpad.net/~xnox/autopilot/use-fb-sizes/+merge/199295 into the archive ASAP. Can we trigger the CI-train upload for that branch?13:12
tvosssil2100, ping13:14
rsalvetisil2100: who will review unity-mir's landing now that Saviq is in vacation?13:29
rsalvetikgunn: ^13:29
rsalvetithat's a blocker for latest mir landing request13:30
josephtxnox: I've kicked off the autopilot-ci job once that's finished successfully I'll kick off the autolanding job.13:39
xnoxjosepht: not sure about the autolanding job, since it's under ci-train management actually.13:40
xnoxjosepht: and i'm not the person who requested this.13:40
asacjosepht: err... please dont do autolandings for stuff in CI train.13:40
asacjosepht: these thigns are in CI train silo staged, most likely waiting for veebers and thomi to get up finish their testing13:41
josephtxnox, asac: ack no autolanding13:41
asacthx13:41
=== tvoss is now known as tvoss|test
=== alan_g|lunch is now known as alan_g
Mirvupdated libunity in archive now14:01
kgunnrsalveti: thanks....we can get gerry to do it (he's wanting this mir anyway)14:02
rsalvetikgunn: thanks, otherwise this will block us for days14:03
rsalvetiand we don't have days14:03
greybackrsalveti: what do I need to do?14:03
rsalvetigreyback: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=2214:03
rsalvetigreyback: there was a landing request for unity-mir that Saviq created a few days ago14:04
rsalvetistill needs testing, so it can be approved and landed14:04
kgunnrsalveti: oh...you were talking about Saviq's14:04
kgunnrsalveti: he might have left that with mzanetti let me check14:04
kgunngreyback: i thot rsalveti meant a review of this one... https://code.launchpad.net/~kgunn72/unity-mir/um-mir0.1.5-bump14:05
greybackkgunn: ah ok14:05
rsalvetiI want the big landing first :-)14:05
* kgunn loves that rsalveti doesn't consider mir a big landing anymore :)14:06
kgunnrsalveti: ok, tsdgeos is looking at the 004 silo build14:09
tsdgeoswell i'm not14:09
kgunntsdgeos: huh ?14:09
tsdgeos*yet*14:09
tsdgeosi'm getting cimi and/or mzanetti to give me access to their maguros14:09
kgunnah14:09
tsdgeosand then i'll get it fixed14:09
psivaasil2100: no luck at all with the dialer app failure.. there is a lxc-android-config change in http://people.canonical.com/~ogra/touch-image-stats/20140206.2.changes14:09
kgunn...oh yeah...how could i forget14:09
tsdgeoshopefully14:10
tsdgeosnot so easy to get a thing fixed over the interwebs :D14:10
tsdgeosbut we'll see14:10
kgunntsdgeos: hey...wait, i thot that ended up being due to AP update ?14:10
rsalvetimaybe davmor2 can give you a hand as well?14:10
kgunnand davmor2 and elopio were looking into that?14:10
kgunn...but maybe i'm missing some new info14:10
kgunn?14:10
ogra_psivaa,14:11
ogra_lxc-android-config (0.136) trusty; urgency=medium14:11
ogra_  * 30-no-surface-flinger: adding logic to start/stop surface flinger via14:11
ogra_    properties (needed by the SDK team to compare performance against MIR)14:11
ogra_unrelated14:11
tsdgeoskgunn: i don't know, i told elopio to send me an email on friday night after his shift ended, but i never got anything14:11
tsdgeoskgunn: it may be14:11
psivaaogra_: ack, it was a last ditch attempt14:12
rsalvetitsdgeos: what do you need to do with maguro?14:15
rsalvetitsdgeos: I can open a port for you14:15
tsdgeosrsalveti: cimi just gave me one14:15
rsalvetitsdgeos: awesome then14:15
tsdgeosrsalveti: well, figure out those autopilot tests that fail and are blocking us14:15
tsdgeoswhich honestly if we don't support it14:16
tsdgeosmakes no sense to me14:16
tsdgeosbut i'm not the one that decides if that makes sense or not, so i'll just fix them14:16
rsalvetihaha, alright14:16
kgunntsdgeos: i feel you brother...14:18
kgunnrsalveti: so when do we officially move to 4.4 ? :)14:18
elopiogood morning.14:18
rsalvetikgunn: well, I'm also waiting on you for that :-)14:18
kgunnelopio: hey there!14:18
elopioI'm just waking up, so trying to parse what you are saying.14:18
kgunnrsalveti: oh no...chicken egg?14:18
kgunnelopio: no worries14:18
rsalvetikgunn: first I need mir 1.5, then the backend packaging split that alf_ is working on14:18
elopiotsdgeos: davmor2 leaves pretty much at the same time you leave, so we couldn't collect more maguro information.14:19
kgunnyep....chicken egg14:19
rsalvetikgunn: yeah14:19
tsdgeoselopio: ok14:19
elopiotsdgeos: the other bug you found is already reviewed and approved by mterry.14:19
tsdgeosi saw :)14:19
tsdgeoselopio: so basically we still don't know why and how to fix the other 2 AP fails, right?14:19
elopiotsdgeos: right. But I understand from your recent messages that you now have access to a maguro, right?14:20
tsdgeoskind of yes14:20
tsdgeosi'll take care of it14:20
tsdgeoswill ping you if need help14:20
tsdgeoselopio: or maybe, let's both try to get something out of it if you can get davmor2 or rsalveti to give you another maguro14:20
davmor2tsdgeos, kgunn, elopio: what's needed on what now save me digging into a lot of backscroll14:21
tsdgeosso if one fails the other gets it to work14:21
tsdgeoswe need to be able to land14:21
kgunndavmor2: sorry...14:21
tsdgeosdavmor2: is there any chance you can give ssh to elopio in a maguro so he can debug the AP failures we're having in unity8?14:21
kgunndavmor2: we're trying to determine what remains an unknown on the AP failures14:21
xnoxjosepht: thanks for that. There are a few other autopilot jobs that need a re-kick now that it's correctly configured:14:21
xnoxhttps://code.launchpad.net/~thomir/autopilot/trunk-add-output_stream_tests/+merge/20479314:22
xnoxhttps://code.launchpad.net/~veebers/autopilot/fix_deprecate_pick_app_launcher/+merge/20278414:22
xnoxhttps://code.launchpad.net/~thomir/autopilot/trunk-fix-functional-tests/+merge/20551214:22
elopioI didn't know rsalveti could give access to maguros. rsalveti, how does that work? I could use one.14:22
xnoxhttps://code.launchpad.net/~veebers/autopilot/fix_1275913_launch/+merge/20481514:22
xnoxhttps://code.launchpad.net/~thomir/autopilot/trunk-add-unit-test-coverage/+merge/20551714:22
rsalvetielopio: sure, with system-image as rw I'd guess?14:22
kgunndavmor2: basically those 2 AP failures are the current landing process log jam....unity8, and then mir is also help up due to that...etc14:22
rsalvetielopio: which image as well?14:22
davmor2kgunn, tsdgeos, elopio: ah right is this what we started digging into on Friday night?14:23
elopiodavmor2: yes, before you left on friday, I thought you could reproduce it. What I would love is to see a video from it failing.14:23
josephtxnox: sure, is just the autopilot-ci job enough or do you need autopilot-1.4-ci as well?  the second seems to fail a lot.14:23
elopiotsdgeos: are we seeing the error in the latest image too? Or which image should I get?14:23
xnoxjosepht: the autopilot-1.4-ci is obsolete, and shouldn't be used any more.14:24
xnoxjosepht: just autopilot-ci please.14:24
tsdgeoselopio: no idea :D14:24
josephtxnox: okay14:24
tsdgeoselopio: i'm just trying to get it to fail now14:24
davmor2elopio: is there a way to run just the one test?  Other wise there is no way I can grab it.  elopio I don't think the video capture will work on maguro for the same reason that the screenshot doesn't14:25
elopiorsalveti: the most recent image please.14:25
rsalvetialright, flashing14:25
elopiodavmor2: yes, you can run only one with phablet-test-run test unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_open_applications_scope14:27
davmor2elopio: right give me a couple of minutes I'll see what I can rig up14:28
elopiodavmor2: and if it happens every time, maybe you can record it with a camera? Maybe I'm asking too much :)14:28
davmor2elopio: no that is what I was going to do14:28
elopiodavmor2: thanks!14:29
davmor2elopio: hmmm hang on phone doesn't seem to be accepting charge give me about 10 minutes to remove the battery and get a small amount of charge in it.14:29
elopiodavmor2: sure. We'll try to gather more information from our side.14:31
psivaasil2100: so, i'm going out for lunch... one thing that we could do is to flash image 169 to see if this issue is there. and then upgrade the packages one by one to see if the issue pops up.14:32
psivaasil2100: but that will take quite a lot of time..14:32
josephtxnox: I've re-kicked the autopilot-ci job for all of those MPs14:36
xnoxjosepht: thanks!14:37
davmor2elopio: I'm guessing this isn't the right response http://paste.ubuntu.com/6909483/ :D14:46
elopiodavmor2: that means it didn't find the test.14:47
elopiodavmor2: do you have unity8-autopilot installed on the phone?14:48
elopiowell, that's not a phone.14:48
davmor2elopio: hmmm I bet had to the reinstall it to test 170.  I'll grab the stuff again D'oh14:48
elopiodavmor2: https://bugs.launchpad.net/autopilot/+bug/127846214:51
ubot5Launchpad bug 1278462 in Autopilot "Test runner should report an error when no tests where found" [Undecided,New]14:51
=== tvoss|test is now known as tvoss
sil2100psivaa: ouch...15:00
sil2100psivaa: how often can you reproduce the problem locally on the device?15:01
sil2100psivaa: and, is it also possible to encounter the problem during normal usage?15:02
sil2100bfiller: hello!15:02
sil2100bfiller: even though it doesn't seem to be caused by any of the changes you and your team made, we seem to have a problem with one of dialer-app's AP tests since some images15:03
sil2100bfiller: psivaa tried bisecting which package could have caused this failure to appear, but we seem to not have much luck with that15:04
bfillersil2100: crashes still? probably the same mir bug15:05
sil2100bfiller: could you have someone investigate this failure here? http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/756161/15:05
bfillersil2100: ok15:05
sil2100bfiller: not the crash thing sadly, something new - seems like a problem with hangup15:05
sil2100bfiller: from what I know the test failure is reproducible (but not always)15:06
sil2100psivaa mentioned that he usually required some re-runs of the test to get the failure15:06
sil2100bfiller: thanks!15:13
davmor2elopio: okay this is getting frustrating now I can run phablet-test-run -n -p unity8-autopilot unity8 and that runs fine if I run phablet-test-run test unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_open_applications_scope I get the 0 tests run15:30
davmor2elopio: and I have unity8 listed in the the /home/phablet/autopilot dir15:31
elopiodavmor2: let me double check the module path.15:31
davmor2elopio: will do15:31
elopiounity8.shell.tests.test_emulators.DashEmulatorTestCase.test_open_applications_scope15:32
elopioseems correct, that's what I've been running.15:32
elopiodavmor2: but, I have run the single test 20 times without failures, on this magic rsalveti's maguro.15:32
elopioI'm trying to run the whole suite now to see if it's because there's a test war.15:32
elopiodavmor2: oh, you have an extra "test" on your command15:33
=== alan_g is now known as alan_g|tea
elopiophablet-test-run -n unity8.shell.tests.test_emulators.DashEmulatorTestCase.test_open_applications_scope15:34
davmor2elopio: thanks15:35
=== alan_g|tea is now known as alan_g
davmor2elopio: http://paste.ubuntu.com/6909764/ note the last one15:45
davmor2elopio: not sure why they are so vastly different in times15:46
elopiodavmor2: yes, I'm looking that here too.15:46
elopioaccording to tsdgeos, the device can get busy and it takes a lot of time to settle.15:47
davmor2elopio: yeah only on a full test run there is no settle time15:47
tsdgeosi may be lying :D15:47
davmor2tsdgeos: ^15:47
tsdgeosyes i've seen that too15:48
tsdgeoshonestly it's not what bothers me15:48
tsdgeosif you add some prints15:48
tsdgeosyou'll see it's at the end15:48
tsdgeosit's not what's causing this problem15:48
asacsil2100: http://people.canonical.com/~ogra/touch-image-stats/20140208.changes thats the changes that made the dialer_app problem firs tappear, right?15:58
asacand we cant reproduce at all?15:58
ogra_asac, thats not clear15:58
asacogra_: i dont see it before int he results15:59
ogra_asac, psivaa rolled back piece by pice of any phone related packages since 2014020615:59
asacoh wait15:59
asachttp://people.canonical.com/~ogra/touch-image-stats/20140207.1.changes that one seems to have ti15:59
ogra_there were a few images where everything was broken15:59
davmor2elopio: off hand do you know what the test is looking for to confirm that the screen is now on the applications page?15:59
* ogra_ needs to re-locate for meeting, one sec16:00
asacogra_: on 7 (with .1) it was green16:01
asachttp://ci.ubuntu.com/smokeng/trusty/touch/mako/169:20140207:20140115.1/6492/16:01
asacthere were crashes though16:01
asacpsivaa: there?16:02
psivaaasac: yep, just came back from lunch16:02
asackk16:03
psivaaand reading the backlog16:03
asacpsivaa: the bisecting for dialer-app regression failed or you still have options to try out?16:03
psivaaasac: not in terms of reverting packages.16:03
asacpsivaa: so you reverted everything and the issue was still there?16:03
ogra_asac, on 7 ?16:03
psivaaasac: yea, reverted everything that we thought might cause the issue, but the issue is still there16:04
ogra_asac,  the last green image was 6.116:04
asacogra_: 6.2 also had a green dialer-app16:04
asachttp://ci.ubuntu.com/smokeng/trusty/touch/mako/168:20140206.2:20140115.1/6487/16:04
asacwith crashes, but still16:04
sil2100The problem is that even when it was green, the issue could still have been there16:04
psivaaasac: not really knowing when this was introduced is making decision difficult16:05
sil2100As the problem is not reproducible in 100%16:05
ogra_asac, after 6.1 (167) there were several images that were so broken that you cant take any results serious)16:05
asacso i guess16:05
asachttp://people.canonical.com/~ogra/touch-image-stats/20140207.changes16:05
elopiodavmor2: it waits until the current index is the previous index + 116:05
asacogra_: 168 above has green dialer-app16:05
sil2100I flashed my phone and will try investigating a bit further16:05
ogra_asac, ignore 168 and 169 please16:05
asacogra_: why? they are green :)16:05
asacon dialer-app16:05
asacso 170 is the first to show this problem16:05
ogra_asac, there were low level issues, i wouldnt take any of the tests serious on these images16:06
asacogra_: well, i think a green can be taken into account16:06
asaclow level issues might invalidate a red16:06
asacbut not a green :)16:06
asachttp://people.canonical.com/~ogra/touch-image-stats/20140207.changes16:06
asacpsivaa: did you work against 170 and backed out the ones fromt he changes in the line above?16:07
ogra_asac,  we went through the phone related packages, he tested while backing them out one by one16:08
psivaaasac: i worked with 173 and reverted packages16:08
ogra_(back to 07)16:08
asacpsivaa: try start from 170 ... and revert the few from above16:08
asacmost likely telephony-service :)16:08
asac169 as green on dialer app16:08
ogra_tried already16:08
asac170 had the same issue we see16:08
sil2100Looking at the failure right now16:09
ogra_was my first shot too :)16:09
asacmaybe there was confusion or a mistake16:09
psivaaasac: ack, will do that. in the meeting and once this is over i'll install 170 and try16:09
davmor2elopio: so why would the test suddenly take nearly 4 times as long to run  :/16:10
tsdgeosno didrocks?16:11
asactsdgeos: what do you need?16:11
sil2100tsdgeos: no, he's on holidays16:11
asacsil is here for you16:11
sil2100bfiller: any luck regarding the issue?16:11
tsdgeossil2100: so about the failing AP tests for the unity8 silo16:12
bfillersil2100: boiko is looking at it, no update yet16:12
tsdgeossil2100: i can make them fail without any of the MPs from that silo16:12
sil2100tsdgeos: oh oh! Did you manage to reproduce it?16:12
tsdgeossil2100: so they were already broken16:12
sil2100tsdgeos: yes, we know16:12
tsdgeosdo you?16:12
tsdgeosok16:12
sil2100tsdgeos: that's why we don't want to land anything until it's fixed16:12
tsdgeosi thought we were blocking because it was a regression16:13
asacsil2100: when did that rregress?16:13
tsdgeosbut it's not a regression16:13
sil2100tsdgeos: Didier's point is: no new landings of unity8 as long as it's not fixed, as it seems to have regressed in one of the earlier landings16:13
tsdgeosit's just an unstable test16:13
asactsdgeos: it probably regressed last week sometimes16:13
tsdgeossil2100: that's bad point16:13
tsdgeosit's new tests16:13
tsdgeosnothing regressed16:13
tsdgeosit's just that CI doesn't run galaxy nexus16:14
tsdgeosso nothing runs those tests16:14
asactsdgeos: maybe you are talking about something different?16:14
asacsil2100: ?16:14
tsdgeosexcept the ultra blocker silo thing16:14
tsdgeosi'm talking about16:14
tsdgeos"2 test failures on maguro that we need to understand:16:14
tsdgeoshttp://ci.ubuntu.com/smokeng/trusty/touch/maguro/167:20140206.1:20140115.1/6480/unity8-autopilot/741839/16:14
tsdgeoshttp://ci.ubuntu.com/smokeng/trusty/touch/maguro/168:20140206.2:20140115.1/6490/unity8-autopilot/744272/"16:14
tsdgeosthat the ci train document mentions16:14
tsdgeosif you say we can't merge new stuff until those tests don't fail anymore16:15
asacsil2100: can you check that those never succeeded and are new? if so, it might be indeed not right to block on them16:15
tsdgeosasac: they do succeed16:15
tsdgeoseventually16:15
tsdgeosi mean i run it 10 times in a loop16:16
asacsure16:16
tsdgeosit succeeds aroud 50%16:16
asacthats not the point :)16:16
tsdgeosthe point is16:16
asactsdgeos: when were they introduced?16:16
tsdgeosthat it may have succeed in an earlier run16:16
tsdgeosand you'll claim "look they worked"16:16
tsdgeosand i'll claim "they worked the same they work now :D"16:16
asachttp://ci.ubuntu.com/smokeng/trusty/touch/maguro/169:20140207:20140115.1/6491/unity8-autopilot/16:16
tsdgeoswe were just lucky16:16
asactsdgeos: are they in there at all?16:16
tsdgeosone is old16:17
tsdgeosso yes it is there16:17
tsdgeosthe other let me check16:17
asactsdgeos: which one is old?16:17
tsdgeosyes it is there too16:17
tsdgeosthe hud_click_one16:17
sil2100tsdgeos: do you know why this test is so flacky then? You think it can be fixed?16:17
asaccant find the string :/16:17
asaccant find "click_one"16:18
tsdgeosasac: sorry unity8.shell.tests.test_hud.TestHud.test_hide_hud_click16:18
tsdgeossil2100: i think it can be fixed, yes16:18
tsdgeossil2100: i am not sure it is worth doing the effort of fixing them *now*16:18
asactsdgeos: check if you can find this happening regularly in the past https://jenkins.qa.ubuntu.com/job/trusty-touch-maguro-smoke-unity8-autopilot/16:18
asactsdgeos: if its flaky it should have been there a few time in that list16:19
sil2100tsdgeos: I just looked at maguro results from the past weeks and I didn't see these tests failing, so we had to be *really* lucky before ;)16:19
asactsdgeos: did you figure why they fail?16:19
ogra_asac, just an observation, but between the dialer-app working and it failing there was the utah change ...16:19
asacdoanac: what changed in utah?16:20
sil2100ogra_: but it fails also on local devices16:20
tsdgeosasac: no, if i had figured why they fail i'd be fixing them and not arguing here :)16:20
tsdgeossil2100: true16:20
asactsdgeos: so the way of htinking is that on maguro you see nasty stuff that will strike us later. hence its very valuble to check them out if they are reproducible right now16:21
asace.g. if its non-hw related races16:21
asacyou certainly want to get rid of them16:21
asacogra_: do you know what changed?16:21
ogra_asac, note that the test links have different names between 169 and 17016:21
tsdgeosasac: i can reproduce them now, i also have 13 branches landing that are starting to conflict amonst themselves16:21
tsdgeosso it'd be helpful if we could land them16:21
sil2100ogra_: you talking about the dialer-app failure now?16:21
tsdgeosbut if you guys are blocking until we get that test fixed16:21
ogra_asac, nope, i see that it seems to have gotten a lot more reliable ... zero change images come out with the same results now16:21
asactsdgeos: if you land your branches how do the APs look?16:22
tsdgeoswe'll get it fixed16:22
asactsdgeos: did you run every AP16:22
asac?16:22
ogra_sil2100, yes16:22
asacand you get exactly this 1 failyre only?16:22
tsdgeosasac: you get the same errors16:22
sil2100ogra_: you think it might be caused by utah?16:22
asactsdgeos: did you test all APs on mako?16:22
tsdgeosasac: i mean, isn't that what the silo does?16:22
doanacasac: utah hasn't changed. we stopped using utah over the weekend and use phablet-test-run directly now for autopilot tests16:22
asactsdgeos: the silo does not test anything16:22
asactsdgeos: you are supposed to test stuff that is in there16:22
tsdgeosasac: ah ok16:22
asac:)16:22
sil2100ogra_: since as I mentioned before, it's reproducible on local devices - but I might misunderstand your point ;)16:22
ogra_sil2100, not sure, i'm just seeing that between dialer-app passing and dialer-app failing there was the change16:22
tsdgeosasac: anyway yes, i've run all the stuff on my nexus4 and nothing fails16:22
sil2100ogra_: since the test fails on my mako every time I run it16:22
ogra_sil2100, in 169 the test is called dialer-app-autopilot, in 170 it is just named dialer-app16:23
asactsdgeos: not even the dialer_app?16:23
asactsdgeos: seems you didnt test enough then :)16:23
asactsdgeos: unity8 needs all APs run16:23
asacfrom apps etc.16:23
tsdgeosasac: ok16:23
tsdgeosi'm bailing out from here16:23
tsdgeosi'm not even the lander of my team16:23
tsdgeosand i'm not going to run the dialer_app tests for fun16:23
asackgunn: we need  alnder16:23
ogra_sil2100, right, i didnt mean to say there must be a connection between the failure and the utah change, i just pbserved that it happened exactly when the failing started16:23
sil2100hmmm16:24
asactsdgeos: unity is a big beast that has impacted lots of apps etc.16:24
tsdgeosbecause you know it's the dialer team that should be running the dialer tests16:24
tsdgeosnot me16:24
asactsdgeos: hence unity landings need to run all or most of app tests ... so we protect the folks that have green app tests16:24
tsdgeosasac: i'd like to see an example of when unity8 broke any app16:24
asactsdgeos: ask bfiller :)16:24
tsdgeosno, i'm asking you since it's you that are arguing it did16:24
tsdgeosand i really have a hard time seeing how we can break apps16:25
tsdgeoswe can break apps not starting, i can take that16:25
asacits accumulated intrinsic know how/best practices we got from doing these landings for many month16:25
asaccan be revisited16:25
tsdgeosok16:25
ogra_tsdgeos, you could put the panel to the bottom, suddnely all taps the AP test generates would be off by a margin16:25
tsdgeosi'm back to fixing the tests16:25
tsdgeosogra_: that only would happen if the ap tests were crap16:26
ogra_unity8 will not break apps, but it can break AP tests16:26
tsdgeoswith hardcoded numbers16:26
tsdgeosit's not *my* issue at all if someone elses tests are crap16:26
ogra_well, you will be the first go-to person since your change exposed it16:26
bfillertsdgeos: this bug breaks the dialer - if the shell (or mir) crashes: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/124040016:26
ubot5Launchpad bug 1240400 in mir (Ubuntu) "dialer-app crashed with SIGSEGV in __GI___pthread_mutex_lock()" [Critical,Triaged]16:26
ogra_doesdnt mean it is your fault indeed :)16:26
kgunnjosepht: ping16:27
tsdgeosbfiller: that's mir crashing yes16:27
josephtkgunn: hi, what's up?16:27
rsalvetitsdgeos: asac: so what is the real blocker here, just the dialer-app?16:27
kgunnjosepht: how are you?16:27
rsalvetiwhile I understand we want to fix the maguro issues, they are not regressions16:27
ogra_rsalveti, just ...16:27
tsdgeosrsalveti: honestly, i don't have a clue what the blocker is16:27
kgunnjosepht: hey, we're seeing a sudden trend in ci runs16:27
kgunnfor mir, they are starting to time out16:28
rsalvetiand blocking a new landing causes way more issues than first trying to fix the "regressions" we had for maguro16:28
kgunnwondering if something changed on the ci infra end of things16:28
kgunnjosepht: e.g. like https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-trusty-armhf/415/consoleText16:28
josephtkgunn: let me do some digging16:28
kgunnjosepht: thanks...16:28
asacrsalveti: no, we have maguro regressions that someone should confirm are a) really no regression or b) are understood to be hardware related (e.g. nothing general in our software stack)16:28
ogra_rsalveti, what are these regressions ?16:28
kgunnjosepht: one other piece of info from history...16:28
asacrsalveti: i couldnt confirm a) from looking at the past runs16:29
kgunnfrancis gave us a dedicated host previously when this was happening a bunch16:29
ogra_we have five test failures ... pretty much the same ones we have all the time16:29
=== gatox is now known as gatox_lunch
rsalvetiasac: if I understood correctly tsdgeos said that those failures were already happening before, and not related with the silo16:29
rsalvetioh, ok then16:29
ogra_yeah16:29
kgunnjosepht: after he did that those problems went away...i wonder if maybe we're back to "gen-pop"16:29
sil2100It's for didrocks and/or asac to decide whether we unblock or not16:29
rsalvetiogra_: asac: and who is looking at the dialer-app regression?16:30
ogra_rsalveti, everyone it seems16:30
ogra_(see backlog of the last hours)16:30
rsalvetialright :-)16:30
bfillerrsalveti: if you guys are talking about the one failed autopilot test in the nightly smoke test, my team is looking at it16:30
ogra_rsalveti, the issue is that we cant really pin it to one specific landing16:30
rsalvetibfiller: cool16:31
ogra_rsalveti, i thinnk psivaa is currently trying with a different image and different roll-backs ... but that will take time16:31
josephtfginther: is what kgunn is referring to above with the timeouts related to what you worked on on Friday?16:31
bfillerrsalveti: don't think it's critical or should be a blocker, but whatever. a failed test is a failed test. works fine manually16:31
rsalvetiogra_: right, might be just better to have someone from bfiller's team to look for a fix instead16:31
rsalvetiinstead of reverting tons of stuff to try to find the culprit one16:32
rsalvetias that's really painful16:32
bfillerare we talking about this? http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/756161/16:32
kgunnasac: ogra_ rsalveti : i (tried to :) read most of the backlog....so basically AP failures on maguro were there before, but now dialer app has a new failure ?16:32
sil2100rsalveti: that's what I did16:32
ogra_rsalveti, ++16:32
bfiller???16:32
ogra_kgunn, dialer-app has developed a failure over the weekend16:32
sil2100rsalveti: once I noticed bfiller online, I poked him about the problem - we couldn't do it earlier because he wasn't around, so psivaa was doing bisection of packages16:32
rsalvetiright, awesome then16:32
rsalvetibfiller will fix it ;-)16:33
ogra_kgunn, the maguro failures are always around 5 (+/-2)16:33
kgunnogra_: ack... i see now16:33
sil2100I'm sure he will, there's no task their team can't handle ;)16:33
* psivaa is just installing 170 on a mako16:33
kgunnogra_: right...so tsdgeos is focused on trying to fix those16:33
sil2100davmor2: hi!16:34
davmor2sil2100: hello16:34
ogra_kgunn, i would say as long as your tests dont expose a signficantly different result to the last image test on http://ci.ubuntu.com/smokeng/trusty/touch/ your landing should be fine16:34
rsalvetiright16:34
ogra_we should define that in some policy :)16:34
ogra_so people can be pointed to it16:34
asackgunn: noone showed me that the maguro AP failres were there before16:34
asackgunn: i ddont see any data in our test log indicating that thats the case16:34
asacbut you guys can show me :)16:34
ogra_asac, see http://ci.ubuntu.com/smokeng/trusty/touch/16:35
* kgunn just remains silent16:35
asacogra_: i looked through them16:35
ogra_maguro always varies around 5-7 test failures16:35
ogra_since like forever16:35
asacogra_: wello, we talk about specific tests here16:35
asacogra_: the new unity8 ones16:35
asacogra_: those have never shown up before in the whole history that i can see16:35
ogra_if the failures kgunn see are identical with the ones on the dashboard i'd say all is fine16:35
asachttps://jenkins.qa.ubuntu.com/job/trusty-touch-maguro-smoke-unity8-autopilot/16:36
ogra_if they vary thats indeed different16:36
asacin general i agree with what you say16:36
asachowever, there is risk that we accumulate new issues in the same part16:36
asacwithout seeing16:36
ogra_http://ci.ubuntu.com/smokeng/trusty/touch/maguro/173:20140210:20140115.1/6529/unity8/16:36
asacand people still claim its old issues16:36
ogra_that has one failure16:36
asacso i would like to undersand that claim16:36
fgintherjosepht, kunn, I don't think this is related to any recent changes, the armhf builds have always been in 'gen-pop'. There has been more armhf builds lately which may be dragging down the build speeds.16:37
asacogra_: yes, thats a pretty new image16:37
ogra_asac, it wasnt clear to me that we talk about one single test run and not the whole suite16:37
asacright16:37
asacogra_: they say this particular test (which happens daily now) is not new16:37
ogra_against the whole suite there are always 5-7 failures on maguro ... in random places16:37
asacwhich can be right, but i just dont see them failing looking back :)16:37
fgintherjosepht, kgunn, I'm in the process of getting a few more armhf machines update to saucy, until then, I'll increase the timeout to at least avoid the failures16:37
ogra_unity8 only is a different thing16:37
kgunnalan_g: ^ bummer16:38
ogra_http://ci.ubuntu.com/smokeng/trusty/touch/maguro/172:20140209:20140115.1/6520/unity8/16:38
ogra_that one has two16:38
josephtfginther: ack, thanks16:38
ogra_http://ci.ubuntu.com/smokeng/trusty/touch/maguro/171:20140208:20140115.1/6511/ has two as well16:38
alan_gkgunn: yes, waiting for more than 2 hrs for a CI build is a PITA16:38
ogra_and the last image dropped to one unity8 failure on maguro16:39
=== josepht changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
asackgunn: so lets talk again about your silo :)16:39
asackgunn: what we need at minimum to go forward (ignoreing the maguro) is to be sure that you see exactly the same errors as on the dashboard16:40
davmor2ogra_, kgunn, sil2100, asac: is it worth doing a comparison between maguro and mako.  If maguro fails and mako passes we look into the issue but don't hold up promotion and then if maguro and mako both fail a test we look at that being a blocker and really dig into that.  Maguro seems to have so many faults with hardware that it could just be that some of the time16:40
rsalvetiiirc the new errors are all maguro specific16:40
ogra_yeah16:40
sil2100rsalveti: one is mako specific ;) The dialer-app test failure16:40
rsalvetiright, not this one :-)16:41
ogra_davmor2, right, but this is about landing and doing tests before actually getting a package in the archive16:41
ogra_davmor2, i.e. running the unity8 tests on a new unity8 package before it gets in16:41
sil2100davmor2: btw. are you free now for some dogfooding?16:42
asackgunn: can you show up on the landing team call in 20?16:42
ogra_he usually does anyway :)16:42
asacso we can sort this out?16:42
kgunnasac: if course16:43
asacah good16:43
asaci will be there16:43
asacand sell blank landing approvals :)16:43
asaclol16:43
ogra_uuuh, manager participation16:43
asaci take bitcoins through private channels :)16:43
rsalvetiasac: can you invite me as well?16:43
kgunnasac: are you money laundering :)16:43
asacrsalveti: done16:43
davmor2sil2100: I can be on what 173 or is there a new image landing?16:43
rsalvetiasac: thanks16:43
ogra_kgunn, nah, he is monbey dry cleaning :)16:44
ogra_*money16:44
asackgunn: lol16:44
asacnot yet16:44
sil2100davmor2: 173 is fine16:44
ogra_davmor2, with all that back and forth i think we'll not have a new image before 3am UTC16:45
sil2100davmor2: since I'd like to maybe promote it if bfiller finds a fix for the test failure16:45
davmor2sil2100: ah what a wishful thinking man ;)16:46
davmor2sil2100: It's nice to optimism :)16:46
ogra_davmor2, hey, bfiller's team is cool, they'll find a fix fast ;)16:46
davmor2ogra_: Every team is awesome here :P  It's just if it is the maguro tests they are trying to fix we are not having much joy reproducing them :)16:47
ogra_davmor2, nah it is the dialer-app issue16:48
sil2100tsdgeos: hey, so hm, after some discussion with asac, I'm willing to unblock unity8 if you guys promise to try and fix the flacky unity8 tests on maguro in the nearest landings16:48
bfillerogra_: so far I can't even reproduce the issue on mako, have run the tests like 5 times16:48
davmor2ogra_: oh the real issue, oh well that is fixable I'm sure :)16:48
sil2100bfiller: uh16:49
ogra_bfiller, hmm, well ... as i stated before (even though this might be a complete coincidence) between http://ci.ubuntu.com/smokeng/trusty/touch/mako/169:20140207:20140115.1/6492/ and http://ci.ubuntu.com/smokeng/trusty/touch/mako/170:20140207.1:20140115.1/6500/ the test infra was upgraded (note the different test names)16:50
ogra_bfiller, and that seems when the failure started ... but as i said, could be just coincidence16:50
ogra_bfiller, i think psivaa could reproduce it somehow16:50
sil2100bfiller: I can reproduce it everytime on my mako16:50
sil2100MismatchError: '0612302' != u''16:51
bfillersil2100: with build 173?16:51
sil2100bfiller: yes, I just flashed my device16:51
ogra_http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/756161/16:52
ogra_thats the dialer-app test from 17316:52
bfillersil2100: just did the same and ran successfully, now rebooting and trying again. must be a race16:52
bfillerwill figure it out16:52
sil2100hmm16:52
ogra_plars, doanac, could we probably have only one single entry per logfile on the test results scrolling down on http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/756161/ looks pretty weird16:53
bfillerboiko: just flashed 173 on nexus4 and autopilot running fine for me, wondering if the notification for an end call is getting in the way of the test and it's a race condition16:53
boikobfiller: that might be, om26er also reported that16:54
boikobfiller: I will remove those anyways, as the design has changed16:54
doanacogra_: hmm. i thought i'd fixed that.16:54
ogra_:)16:54
ogra_fix harder :)16:54
ogra_no biggie indeed ... not having logs at all would be worse16:55
doanacogra_: yeah. i guess its just fixed for the "testsuite": http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/ not the test-case16:55
bfillerboiko: weird I can't reproduce. which package would need to be updated to get rid of the notifications?16:55
doanacogra_: you are referring to all the artifacts showing up, correct?16:55
boikobfiller: telephony-service16:55
ogra_doanac, exactly16:55
doanacogra_: ack. i'll work up a fix. thanks for noticing!16:56
ogra_doanac, btw, nice work, it seems to be way more reliable (zero chnage images suddenly have the same results on first run etc)16:56
boikobfiller: I'm flashing the device right now to test16:56
asaccyphermox_: will you be in the call in 5?16:56
doanacogra_: thanks. it took a lot of work in spare time to convert thing over :)16:56
om26erboiko, its a race you may need to run the suite multiple times16:56
ogra_you should do that in paid time really :)16:56
boikobfiller: ^16:56
cyphermox_asac: I am supposed to be off today, just happen to be looking at IRC :)16:57
asacsil2100: ^^16:57
sil2100heh, my device has to be really racy, as it fails every time here ;p16:57
ogra_cyphermox_, look away then !!!16:57
asaccyphermox_: that eliminates our hopes to do an aggressive landing move tonight16:57
sil2100Oh crap16:57
bfillersil2100: it's weird, still no failures for me16:58
cyphermox_sil2100: we discussed this on thu or fri16:58
sil2100asac: well, I think tonight it might not be needed16:58
asack16:58
cyphermox_asac: what do you want to land? maybe there's a way to do it anyway16:58
sil2100asac: let's wait for tomorrow with the aggression - I mean, let's kick the image with new AP in the morning16:58
asackk16:58
sil2100cyphermox_: will you be on tomorrow?16:58
asacsil2100: sounds good16:58
cyphermox_sil2100: no, wednesday16:58
bfillersil2100, asac : bottom line - the failure seems to be occuring because of a notification that was added when a call ends, and that interferes with autopilot depending on timing16:58
bfillerso it's a test bug, not a functional bug16:59
ogra_yay16:59
cyphermox_sil2100: I will likely be online though, so don't hesistate to ask me for packaging reviews if needed16:59
sil2100bfiller: \o/16:59
bfillerasac, sil2100 : we plan to remove the notification anyway because design wants it removed now16:59
psivaabfiller: how was that introduced ?16:59
asacbfiller: what would have to land for removing those?16:59
psivaai mean the failure is quite recent16:59
bfillerasac: a new telephony-service16:59
rsalvetiawesome16:59
bfillerpsivaa: telephony-service last week17:00
asacsee :)17:00
asaci knew it :)17:00
rsalvetithen we can speed up landings today still17:00
asacbfiller: did you back that out and it went away? :)17:00
bfillerasac: I can't repro it in the first case honestly17:00
bfillerit's a race17:00
bfillerbut that is the problem17:00
bfillerit never failed during our landing testing either17:00
asacpsivaa: can you confirm? you seem to be able to reproduce this dialer issue17:00
asacjust backout the telephony-service... then it shoudl be gone17:01
asacbfiller: its odd.,..17:01
ogra_it isnt17:01
ogra_that was the first thing we backed out17:01
asacbfiller: ^^17:01
psivaaasac: just running the test for the first time after 170 install and was able to see the failure. now i'll revert telephony and see if that goes17:01
asacogra_: maybe you did a mistake?17:01
asacor just an oversight?17:01
asacpsivaa: thanks!17:01
ogra_asac, psivaa did the test17:01
om26ersil2100, psivaa where to find the failing dialer-app test log ?17:02
ogra_om26er, http://ci.ubuntu.com/smokeng/trusty/touch/mako/173:20140210:20140115.1/6527/dialer_app/756161/17:02
bfillerasac, ogra_ : telephony-service was released on Feb 6th: 0.1+14.04.20140206-0ubuntu117:02
asacbfiller: ack. thats the one that landed first in 17017:03
ogra_bfiller, right and it entered the image friday morning http://people.canonical.com/~ogra/touch-image-stats/20140207.changes17:03
ogra_(which was image 170)17:03
om26erthis one is different17:03
om26erboiko, I have seen this as well, it happens when the page title is not updated, thats probably due to a hang phonesim thing we use for fake calling17:05
ogra_om26er, well, it is the one that is reliably showing since friday17:05
tsdgeossil2100: asac: great, that's good. i'll ask mzanetti to do the landing since he's a trained-lander17:05
ogra_(and currently blocking landing)17:05
boikoom26er: hmm, ok, as soon as the device finishes flashing I will debug this further17:05
rsalvetitsdgeos: so can we say that the landing-4 was fully tested then?17:08
tsdgeosrsalveti: honestly, i can't say, it was Saviq doing landing-417:09
rsalvetior should we wait mzanetti to publish his test results17:09
tsdgeosif the only two problems were the tests listen in there, yes we can17:09
rsalvetiright, as he's gone we need someone to sign for it, just not sure who yet17:09
tsdgeosotherwise, not sure17:09
tsdgeosrsalveti: i'd say mzanetti17:09
tsdgeoshe's having dinner, but said he'd be back17:09
rsalvetigreat17:09
bfillersil2100: can you run this test and tell me what happens on the screen? does it never get to the live call page?17:10
bfillerdialer_app.tests.test_calls.TestCalls.test_outgoing_answer_local_hangup17:10
bfilleras I can't make it fail17:10
bfillerom26er: ^^^^17:10
om26erbfiller, the title stays blank, the live call page does open17:11
om26erbfiller, reboot the phone, I mostly get it to fail on clean boots17:12
bfillerom26er: does the call duration update or stay on 00:0017:12
om26erbfiller, I believe it stays at 00:00 sil2100 is that right ?17:13
om26erI am updating the phone as well to check17:13
sil2100bfiller: one moment, on a meeting17:14
bfillerogra_: has ofono-phonesim* been upgraded recently?17:15
ogra_bfiller, i dont think so17:15
ogra_bfiller, last upload way jan 817:15
ogra_*was17:15
bfillerogra_: ok17:15
psivaafirst run after reverting telephony-service on 170 was successful, running a couple of more times to confirm17:18
asacpsivaa: cool17:24
asacpsivaa: can you try the same on the latest image? just to confirm that there is no other issue hidden underneath17:24
psivaaasac: ack, once confirming that revert on 170 works, i'll go back to 173 although i did that before as the first attempt.17:25
asacpsivaa: right. sounds good17:25
om26erbfiller, hey, there are two issues, the more apparent one can be fixed in a single line:17:25
om26erself.assertThat(lcp.title, Equals(number))17:25
om26erself.assertThat(lcp.title, Eventually(Equals(number)))17:26
asacpsivaa: yeah, might be just a mistake or something or we really grew another regression in the same spot17:26
sil2100bfiller: ok, trying to run it and see what's on the screen17:26
om26erthe other is a race and happens very less often17:26
psivaaasac: ack17:26
sil2100om26er: ok, the dialer-app test fails when the state is still in 'calling'17:26
boikoom26er: nice catch on this one, I will fix it17:26
om26ersil2100, yeah, that will be fixed with the above change17:27
sil2100\o/17:28
bfillerom26er: is the other race due to the notification?17:28
om26erbfiller, yes, probably17:29
davmor2sil2100: maguro finally finished flashing dialer app works fine from what I can see17:30
bfillersil2100: can you confirm that changing line 178 of test_calls.py to self.assertThat(lcp.title, Eventually(Equals(number))) fixes your failure?17:30
sil2100bfiller: doing that, just need to finish restarting my phone17:31
bfillersil2100: cool thanks17:31
sil2100bfiller: fixes ;)17:36
=== gatox_lunch is now known as gatox
bfillersil2100: great, om26er nice catch there. boiko please submit and MR and we can get this released17:37
boikobfiller: yep17:37
om26ergreat ;)17:38
boikobfiller: sil2100: om26er: is there a bug reported on this problem? just to reference it17:38
bfillerboiko: let me file one17:38
boikobfiller: thanks17:38
bfillerboiko: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/127851917:39
ubot5Launchpad bug 1278519 in dialer-app (Ubuntu) "autopilot test failure on live call view" [Undecided,New]17:39
boikobfiller: thanks17:40
davmor2sil2100: tea has been called back in 3017:48
sil2100davmor2: ok, thanks! The test results look good so far17:50
psivaabfiller: ogra_: asac: so now we are running the tests using phablet-test-run and dont use utah to run autopilot tests individually so the timing related issues are more visible.17:51
bfillerpsivaa: that's good for sure, but it still didn't fail for me using phablet-test-run or autopilot directly but I guess it's not an environment issue, rather a poorly writtent test17:52
psivaaso even after reverting telephony-service on 170 i see the failures when running using the latest method of running the test17:52
bfillerpsivaa: turns out the failure is not because of telephony-service17:53
psivaabfiller: ohh. did i fail to read the backlog17:53
bfillerpsivaa: it's this: https://code.launchpad.net/~boiko/dialer-app/fix_test_calls/+merge/20563617:53
boikosil2100: I have submitted an MR, just waiting for jenkins to run it to fill the ckecklist17:53
bfillersil2100: MR is here: https://code.launchpad.net/~boiko/dialer-app/fix_test_calls/+merge/20563617:54
psivaabfiller: boiko ack, thanks17:54
sil2100bfiller, boiko: thanks guys! Could you set up a landing for that? I'll assign a silo then straight away :)17:54
bfillersil2100: yup17:55
bfillersil2100: done17:58
sil2100bfiller: thanks, let me assign a slot17:58
om26ersil2100, I have a new source that I want to add to CI and at the same time get it uploaded to ubuntu universe, I can do the former part, who to contact about the latter ?18:00
bfillersil2100: I started the build, going to lunch now. can test when I get back (like 1 hr)18:02
sil2100om26er: you mean the ubuntu-integration-tests?18:02
om26ersil2100, yes18:02
sil2100bfiller: excellent, I'll inform Robert to keep a look at this silo18:02
=== bfiller is now known as bfiller_afk
sil2100om26er: ok, so we can try doing that normally, we can add it to the CITrain and push it to the archive18:03
sil2100(I'll try doing that tomorrow)18:03
om26ersil2100, that sounds great, thanks18:03
sil2100ogra_: can you ACK 2 packaging changes for me ;) ?18:06
sil2100Seem trivial18:06
ogra_show me18:06
sil2100http://162.213.34.102/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-keyboard_0.0.0+14.04.20140207-0ubuntu1.diff <- bamf dependency removed (in CMake it seems to be removed as well, and builds!)18:06
sil2100http://162.213.34.102/job/landing-001-2-publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-sound_12.10.2+14.04.20140207-0ubuntu1.diff <- a new Recommends, changelog sounds legit18:06
ogra_sil2100, hmm, was that second one discussed with the desktop team ... i.e. seb128 ?18:08
ogra_sil2100,  adding that recommends means pavucontrol by default on all desktop installs18:08
ogra_sil2100,  the first one is fine18:08
ogra_sil2100, for the second one i'd like to defer to a desktop team member, that seems very intrusive18:09
sil2100ogra_: not sure, let me dig deeper - it's a |, so it shouldn't be as long as others are visible18:09
sil2100ogra_: ah, seb acked it18:09
sil2100ogra_: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-sound/trunk.14.04/revision/411 <- approved by Sebastien18:09
ogra_ok,. then ack from me too18:10
ogra_yeah18:10
sil2100phew, dodged a bullet here18:10
sil2100Since this way we're not responsible for anything being broken now ;D18:10
ogra_haha18:11
=== alan_g is now known as alan_g|EOD
sil2100ogra_: ok, so, it seems that the image is fine so far, so let's promote #173!18:14
sil2100robru: morning :)18:14
sil2100robru: I have some missions for you today o/18:14
robrusil2100, sure18:15
sil2100robru: let me just finish writing the e-mail18:15
robrusil2100, no worries18:15
davmor2sil2100: they look good so far :)]18:19
sil2100ogra_: whenever you're ready press the promote button!18:20
ogra_yeah yeah ... already running ...18:20
ogra_takes a while :)18:20
om26ercihelp if there is no launchpad project for a source package and only a lp branch, can it be added to cupstream2distro-config for CI ?18:21
ogra_=== Image 173 Promoted ===18:23
sil2100\o/18:23
ogra_:)18:23
sil2100robru: ok, done18:26
robrusil2100, thanks18:27
sil2100robru: soooo:18:27
sil2100robru: could you make sure once the dialer-app landing from silo 007 is tested you release that?18:27
robrusil2100, sure thing.18:28
sil2100robru: same for the unity8 landing from silo 00418:28
robrusil2100, alright, I'll keep an eye18:28
sil2100robru: try also finding a silo maybe for the platform-api landing from l63, I think this might be good to have an it's small (and I don't think we'll need to release platform-api anywhere else)18:29
sil2100robru: you can also add one or two more landings silos if you want, just be sure that the component is no-risk and that we won't block anythin important ;)18:30
sil2100robru: just don't assign mir for now!18:30
robrusil2100, ok, no mir, sure.18:30
sil2100robru: as it's an ABI break, so this locks up many silos at once18:30
robrusil2100, ahhhh ok thanks18:30
sil2100robru: unity-scope-scopes is +1'ed by seb and ready for release, but I don't know how to proceed with new pacakges in CITrain yet - not sure if the whitelist is updated and such18:31
sil2100robru: so let's wait with that till tomorrow I guess18:31
sil2100robru: anyway, thanks :)18:31
robrusil2100, yeah, I saw that one. I guess we have to wait for didier to preNEW it18:31
sil2100robru: I think seb just did it today, we asked about it and he said it's ok... but not sure if he did all the other manual stuff for preNEWing, like the whitelist and such18:32
sil2100Not even sure if that's still used18:32
robrusil2100, well what's the worst that can happen if I publish it? the archive robot won't copy it...18:32
sil2100robru: right, but I won't sure if it won't leave the package in some strange transient state18:33
sil2100But I guess not18:33
robrusil2100, well the only "inconsistent state" it'll get is that citrain will say it's published, but it won't actually make it into the archive18:34
sil2100robru: well, you can try publishing with 'ACK PACKAGING' later on I think, if it doesn't go through we'll check the code and try to proceed18:34
sil2100Ok, time for me to EOD18:37
sil2100See you tomorrow!18:38
om26erfginther, I created a simple test job but its failing with https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-trusty-armhf/2788/console18:44
om26erhelp ?18:44
boikopsivaa: tests passed on dialer MR: https://code.launchpad.net/~boiko/dialer-app/fix_test_calls/+merge/20563618:51
fgintherom26er, yes, branches can be added, as long as the branch is owned by a team which ps-jenkins is a member18:58
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
fgintherom26er, supply lp:ubuntu-autopilot-tests/ubuntu-integration-tests as the landing_candidate instead of the target_branch and it should build19:00
thomiMirv: hey - are you able to give me write access to the CI train self service SS please?19:01
om26erfginther, trying that, triggered a rebuild19:01
psivaaboiko: ack, does not look like that the tests are run in the MP is similar to what we run smoke now. but hope the test passes with the image19:02
psivaain smoke19:02
psivaaboiko: i meant the way the tests are run ^19:04
boikopsivaa: yeah, I have seen in the past tests that would pass in one and fail in another19:05
om26erfginther, ps-jenkins is now added in the team that supervises that branch, can you add CI for that ?19:20
om26erlp:ubuntu-autopilot-tests/ubuntu-integration-tests19:20
fgintherom26er, will add it to the list for today19:35
om26erfginther, lastly, do you know why these tests are failing on otto ? https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-trusty/2684/?19:37
ogra_hmm sil2100 is gone19:37
ogra_173 doesnt actually look good on my mako19:37
* ogra_ has a completely hanging UI 19:38
fgintherom26er, is this error meaningful to you? ERROR content:49 - Could not add content object 'None' due to IO Error: [Errno 13] Permission denied: '/var/log/syslog'19:39
ogra_hmm, after a unity crash it seems to behave now19:39
om26erfginther, not really, doesn't sound related to the tests, could be an environmental fault19:40
fgintherom26er, I'll add it to the pile, but probably won't be help to provide any further insight today. I've noticed that https://jenkins.qa.ubuntu.com/job/dialer-app-ci/179/ passed just recently, possibly there is a fix that needs to be merged in19:48
=== bfiller_afk is now known as bfiller
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
robrubfiller, I published dialer-app. please merge & clean silo 7 once it hits the archive23:01
robrubfiller, also history-service in silo 8.23:02
robrusergiusens, assigned platform-api to silo 9, please build23:23
sergiusensrobru, thanks23:23
bregmafginther, what's going on with the head/unity tests?23:38
cjohnstonbregma: link?23:39
fginthercjohnston, we've been discussin in emal23:39
cjohnstonack. nevermind :-)23:39
fgintherbregma, I've been running some single test suite experiments, the nvidia machine is passing a lot more tests then the intel one23:41
bregmafginther, I was just wondering if you had some kind of idea about causes, since I see you've been doing what appear to be dark and ritualistic experiments23:42
fgintherbregma, should these machines have dual monitors?23:42
fgintherbregma, unfortunately the dark arts have not spoken to me today23:42
bregmafginther, some times they do and sometimes they don't have dual monitors, which revealed latent bugs in our test code recently, so either *should* be OK23:43
fgintherbregma, I've also got a test in the queue to run the suites in a different order23:43

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