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