[08:37] <ogra_> Laney, http://reports.qa.ubuntu.com/smokeng/trusty/touch/ has the feedback ;)
[08:38] <ogra_> (your #9 build was the best one we had in a long time)
[08:38] <ogra_> psivaa, looks like gallery didnt run again on maguro
[08:39] <ogra_> (and unity8 fails still the same way on mako)
[09:07] <psivaa> ogra_: i'll take a look at them
[09:08] <ogra_> thanks
[09:17] <popey> ogra_: #10 seems good here
[09:18] <ogra_> popey, havent done calls/sms yet,. but from what i see atm here too ...
[09:18] <ogra_> to sad the fix didnt work though
[09:18] <ogra_> (which apprently was the only change vs #9)
[09:19] <popey> calls/sms work fine here
[09:19] <popey> ☹
[09:21] <ogra_> yup, looks fine here too
[09:21] <ogra_> if we could get the dashboard a bit greener i would actually propose to promote this
[09:43] <psivaa> ogra_: re: unity8 failures on mako, there was a new upload to unity (7.83+14.04.20131031-0ubuntu1) but it dint fix the issue apparently
[09:43] <psivaa> Mirv: ^
[09:48] <ogra_> psivaa, yeah, see whay i wrote above :)
[09:48] <ogra_> *what
[09:50] <psivaa> ok, known then :)
[09:51] <ogra_> well, probably not by Mirv yet :)
[13:12] <fginther> morning
[13:42] <plars> balloons: a couple of things you might be interested in: 1. I got clock to finally pass today on maguro after a rerun, it's been failing for a while, includeding the first time it ran on image 10
[13:42] <plars> 2. weather is failing some extra tests on mako - even after rerunning, I'll try again but that's kinda strange
[14:17] <ogra_> plars, psivaa, did anyone try to re-run munity8 on mako yet ?
[14:17] <ogra_> the image looks so good, would be a shame to not promote it ...
[14:17] <ogra_> but i dont want to with these unity test results
[14:17] <plars> ogra_: I can, did we expect it to be fixed now?
[14:18] <ogra_> plars, yes, apparently it didnt suffice though
[14:18] <plars> ogra_: I'm restarting it now
[14:18] <ogra_> Mirv was pinged about it above
[14:18] <plars> ogra_: but it looked the same on the custom image with mako also
[14:18] <plars> ogra_: so I suspect it's still broken
[14:18] <ogra_> (probably we should also poke Saviq )
[14:18] <ogra_> yeah
[14:18] <ogra_> me too
[14:31] <plars> ogra_: failures are still the same
[14:31] <plars> ogra_: after the rerun
[14:31] <ogra_> *sniff*
[14:32] <ogra_> plars, how is the house btw ?
[14:32] <ogra_> all dry again ?
[14:32] <plars> ogra_: mostly, we came out ok. Some people not far from us were stuck in trees, on rooftops, etc
[14:32] <plars> we are up high enough that it wasn't so bad
[14:33] <ogra_> ugh
[14:33] <plars> ogra_: also we are a bit farther away that they are from the creek that got to 19 feet above flood level
[14:34] <ogra_> wow
[14:35] <plars> (about 5.7 meters for the metric folks)
[14:36] <ogra_> yep, my brain turned into ~5m :)
[14:36] <ogra_> we have that in the east of germany regulary every year since a few years ...
[14:37] <ogra_> and it seems to be higher with the years
[14:37] <ogra_> (and didnt occur at all 20years ago)
[14:38] <plars> ogra_: yeah, it comes in cycles. Nearest similar flooding in my immediate area was in 1925 or somthing like that
[14:38] <ogra_> yep
[14:39] <ogra_> well, i guess the water from the melting ice caps has to go somewhere ... and if it isnt the sea it is the atmosphere
[14:57] <sergiusens> heh, we get a bit of rain here from time to time and some areas with very little go up to 3m (it never rains here)
[14:57] <fginther> josepht, want to help review? https://code.launchpad.net/~fginther/cupstream2distro-config/core-apps-trusty/+merge/193612
[14:57] <josepht> fginther: sure
[15:27] <doanac> plars: i just noticed our unity8 touch  test still installs the unity8-autopilot package. is that really needed?
[15:27] <plars> doanac: iirc we needed that to bring in some dependencies right?
[15:28] <doanac> sergiusens: you remember? ^^^
[15:28] <plars> doanac: but in reality, it's going to run the tests out of the click-test-setup installed bits since they are in the python path
[15:28] <doanac> plars: that's true, so it might just be to pull in some other dep
[15:29] <doanac> someone should thank thomi_ for making autopilot add ./ to the python path. its probably saved a lot of tech support questions over the years :)
[15:29] <thomi_> doanac: :)
[15:30] <doanac> thomi_: its quite hard to work around my ignorance - it knows no bounds!
[15:30] <thomi_> heh
[15:54] <Saviq> plars, ogra_ the known issue is fixed indeed - not sure yet what's the new thing (it only started happening yesterday or so that all the test started failing)
[15:54] <Saviq> obviously non-reproducible locally :/
[15:54] <plars> Saviq: it seems to only happen on mako and not maguro though
[15:54] <ogra_> Saviq, and restricted to mako
[15:54] <Saviq> ogra_, yeah
[15:56] <Saviq> it's aborting somewhere in Mir, nothing obvious, though :/
[15:57] <ogra_> maguro is probably just to slow to notice any breakage :P
[16:47] <plars> ogra_, Saviq: I think I have the tests working locally on mako... no idea why it was a problem on mako and not maguro, but it appears related to the screen not being on properly
[16:48] <ogra_> yeah, i said that yesterday
[16:48] <plars> we used to turn it on earlier, but were asked to quit doing that because there was some suspicion that it was causing some sort of powerd problem iirc
[16:48] <plars> ogra_: ok, I missed that conversation I guess, sorry
[16:48] <thomi_> fginther: Anny ideas what happened here? http://10.97.0.26:8080/job/autopilot-testrunner-otto-trusty/279/console
[16:49] <ogra_> plars, yeah, that was easy to miss ... and totally out of your TZ anyway (in my morning)
[16:50] <fginther> thomi_, sorry, I can't take a look now. please see if cihelp can
[16:50] <thomi_> fginther: no worries.
[16:51] <plars> ogra_: do you have any ideas on how to really make sure the screen gets turned on? doanac had previously made a change to do this sooner after the boot, and I think that was pretty effective but iirc asac wanted us to turn that off.  It seems like somtimes using powerd-cli to turn the display on after it's timed out already doesn't work
[16:51] <ogra_> no, i dont really know anything else but powerd-cli
[16:52] <ogra_> and i dont know why that was ripped out instead of fixing the apparent race
[16:52] <thomi_> cihelp: can someone help me figure out how CI runs the Ap tests for the ubuntu-clock app?
[16:52] <ogra_> since it clearly breaks us now
[16:52] <thomi_> cihelp: The specific problem is that ubuntu-clock-app isn't in the archive it seems
[16:53] <plars> ogra_: I think even if the timeout is configurable somehow, that would do the trick
[16:53] <plars> thomi_: hmm, isn't that one that we run as click now?
[16:53] <ogra_> yes, but thats a feature thats still missing
[16:53] <thomi_> plars: could be. If so, how do I configure that in http://10.97.0.26:8080/job/autopilot-trusty-master ?
[16:53] <thomi_> or maybe I can't?
[16:55] <plars> thomi_: ah, I thought you meant the image tests, sorry
[16:56] <thomi_> no worries
[16:57] <plars> ogra_: so running everything locally on my mako all passes, even if I run it the same way we run it in smoke testing, provided I make sure the screen is on
[16:57] <ogra_> right
[16:58] <plars> ogra_: do you know if anyone is working on a configurable screen timeout?
[16:58] <ogra_> so we should probably add the code that does this back ... even if we have to rip it out next week again
[16:58] <ogra_> it is a supposed feature of the shell
[16:58] <doanac> thomi_: probably should ask fginther, but it almost looks like in that test it shouldn't matter if its click or not
[16:58] <ogra_> so i would expect someone to work on this, yes
[16:59] <thomi_> doanac: but it fails because it can't install ubuntu-clock-app package
[16:59] <thomi_> doanac: http://10.97.0.26:8080/job/autopilot-testrunner-otto-trusty/279/console
[17:00] <doanac> thomi_: isn't it in the archive that gets copied over: http://10.97.0.26:8080//view/mediumtests/job/generic-mediumtests-builder-trusty-amd64/296/artifact/*zip*/archive.zip
[17:01] <thomi_> doanac: so I don't have to specify it?
[17:01] <thomi_> I was just copying the deps from debian/control
[17:06] <doanac> thomi_: not sure. i'm surprised it failed. if you look at the ubuntuuitoolkit job that ran before that (job 278) it did something similar and worked
[17:07] <thomi_> doanac: yeah, but the sdk *is* in the archive :)
[17:07] <thomi_> doanac: it's OK, I'll mess around with it some more
[17:26] <elopio> hey ci team, all tests failed in mako here:
[17:26] <elopio> https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/2947/consoleFull
[17:26] <elopio> any idea why?
[17:28] <elopio> oh, nevermind. Tests are running again. I'll let you know if it fails again.
[17:28] <cjohnston> elopio: looks like a test failed to me
[17:29] <elopio> cjohnston: all tests failed. when that happens, just in one of the environments, it's more likely an environment issue.
[17:46] <om26er> this machines is running low on disk space, can anyone look into that ?
[17:46] <om26er> http://10.97.0.26:8080/computer/ps-generic-precise-amd64/?
[17:46] <om26er> ci ^ (incase anyone have that for a highlight)
[17:46] <cjohnston> om26er: ping the vanguard
[17:47] <om26er> cjohnston, he is not online it seems
[17:47] <om26er> actually
[17:47] <cjohnston> retoaded: you should probably use your nick as 'vanguard'
[17:47] <om26er> retoaded, ^
[17:51] <om26er> Saviq, ^
[17:57] <retoaded> cjohnston, thought I had. apparently something else was in mouse memory
[17:58] <retoaded> om23er ps-generic-precise-amd64 is a vm but I will take a look
[17:59] <Saviq> retoaded, whatever's happening, jobs for that machine are blocked http://10.97.0.26:8080/job/generic-land/
[17:59] <Saviq> retoaded, there's a job running for 2 days now, too
[17:59] <retoaded> Saviq, ack
[17:59] <Saviq> http://10.97.0.26:8080/job/generic-covlpsync/1394/console
[17:59] <Saviq> retoaded, thanks
[18:05] <retoaded> Saviq, 70% of the disk space on that VM is sitting in /tmp; do the jobs not clean behind themselves?
[18:05] <retoaded> Saviq, used disk space that is
[18:06] <Saviq> retoaded, no idea
[18:20] <retoaded> Saviq, space is freed up and the node is processing jobs again
[18:26] <elopio> ci team, what does this failure mean? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-maguro/2902/console
[18:26] <elopio> remote object '/.setup_complete' does not exist
[18:26] <elopio> SETUP FAILED - CAN'T CONTINUE
[18:28] <cjohnston> elopio: there was a an issue installing packages so it needs to be rerun
[18:29] <retoaded> elopio, looks like it failed to resolve ports.ubuntu.com
[18:29] <elopio> so, just rerun, ack.
[18:29] <elopio> thanks cjohnston, retoaded.
[18:31] <cjohnston> elopio: /11
[18:31] <cjohnston> elopio: sorry. nvm
[18:32] <elopio> np/
[18:55] <plars> ogra_, Saviq: ok, I'm pushing a change to move the display-on stuff again right now, and I'll rerun those unity8 tests
[18:55] <ogra_> awesome
[19:28] <plars> ogra_: the world just got a little greener: http://reports.qa.ubuntu.com/smokeng/trusty/touch/
[19:29] <plars> ogra_: we see this hud-service crash there now though
[19:30] <plars> but that's known I think
[20:32] <Saviq> plars, awesome, thanks
[20:51] <thomi_> cihelp - I seem to be seeing some otto errors, and I don't understand the errors: http://10.97.0.26:8080/job/autopilot-testrunner-otto-trusty/295/console
[20:56] <cjohnston> thomi_: E: Unable to locate package ubuntu-clock-app
[20:57] <thomi_> cjohnston: doh! I just saw the otto message
[20:57] <thomi_> ugh, thanks