[05:24] <pitti> Good morning
[09:26] <jibel> pitti, can we assume bash is always installed in the testbed? it is the case for ubuntu because it's in minimal but I am not sure about debian
[09:29] <pitti> jibel: yes, you can; it's Essential: yes, also in Debian
[09:29] <jibel> pitti, great quoting is trivial then and we can drop the perl code
[14:43] <jibel> pitti, http://paste.ubuntu.com/7580287/ also fixes the problem of the return code when the exec embedded in perl failed
[14:44] <jibel> pitti, but I now have found another issue http://paste.ubuntu.com/7580538/
[14:44] <jibel> digging ...
[14:46] <pitti> jibel: ah, opts.user_wrap might need adjustment for that?
[14:46] <pitti> jibel: in def finalise_options()
[15:46] <balloons> elfy, ping
[15:57] <elfy> balloons: pong
[15:57] <balloons> elfy, offtopic for this channel a bit so I guess I'll pm you
[15:57] <elfy> okey doke
[16:06] <jibel> pitti, FYI the "su" error is due to wrong quoting when the script is executed through ssh
[16:07] <pitti> jibel: ah, so it wasn't (just) opts.user_wrap?
[16:08]  * pitti waves good bye
[16:09] <jibel> pitti, it wasn't , it can be reproduced with http://paste.ubuntu.com/7581274/
[16:27] <balloons> jibel, still about?
[16:27] <jibel> balloons, I leave in 2 min, so be quick :)
[16:28] <jibel> balloons, just ask, I'll be back later anyway
[16:30] <balloons> jibel, ahh yes. .just curious about how the ole AP tests for ubiquity where. Feeling the need to restart the push to get those made part of gating
[16:30] <balloons> that's all.. just placing it back in your mind as well
[16:31] <balloons> enjoy your evening :-)
[16:32] <jibel> balloons, everythings green excepted xubuntu but them seem to have not run since may 21rst. adding to my list for tomorrow to check why
[16:54] <knome> jibel, thanks
[17:27] <jibel> balloons, actually the slave which runs ubiquity tests was down. It's now up and executing the tests. results should be visible on public jenkins soon
[18:28] <balloons> jibel, great ty
[19:24] <balloons> Letozaf_, evening to you :-)
[19:25] <Letozaf_> balloons, hello :) how are you ?
[19:25] <balloons> Letozaf_, a bit roughed up.. I haven't felt normal in weeks, heh
[19:26] <balloons> but the latest round is my fault
[19:26] <Letozaf_> balloons, lol
[19:26] <Letozaf_> balloons, well the important thing is you did not get seriously hurt :P
[19:35] <elfy> balloons: so jenkins ... I can see the 'result' of what's being run - but where can I find the cause of a failure?
[19:36] <balloons> Letozaf_, yes, nothing broken. So how about you?
[19:36] <balloons> elfy, link to what you are looking at?
[19:36] <elfy> https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Xubuntu/
[19:37] <elfy> trying to get some sense from why our builds are failing - perhaps it'll help me see why we can't actually install them :)
[19:37] <elfy> oh ...
[19:37] <balloons> elfy, ahh.. Yes, hence why we use the dashboard and not jenkins. It collects the logs and info, but doesn't display them easily
[19:37] <Letozaf_> balloons, I'm ok, just got a bit burnt sun tanning on sunday :P
[19:37] <elfy> now I look at the others - everything is failing
[19:38] <balloons> elfy, https://jenkins.qa.ubuntu.com/job/ubiquity_ap-xubuntu_devel_daily-test_custom_install/153/ARCH=amd64,label=rabisu/
[19:38] <balloons> you can look at the logs.. check the console output and build artifacts for jenkins jobs
[19:38] <balloons> sometimes the goodies are nested
[19:41] <elfy> mmm
[19:41] <elfy> that's just a link to one - where do I even start trying to find other xubuntu stuff
[19:43] <elfy> like how to start from  https://jenkins.qa.ubuntu.com/job/
[19:44] <elfy> which just gets me status code 404
[19:44] <balloons> elfy, you should look at the dashboard
[19:44] <balloons> http://ci.ubuntu.com/
[19:44] <balloons> but yes, it doesn't have much of interest for you. The point is jenkins isn't really intended to convey that sort of info
[19:45] <balloons> https://jenkins.qa.ubuntu.com/ is the toplevel
[19:45] <balloons> but it won't be useful
[19:45] <elfy> ok
[19:46] <elfy> so basically all *we* can usefully find is if something is red or amber or green
[19:46] <elfy> and by that time we'd already know anyway
[19:48] <elfy> aaah - got there now :p
[19:54] <balloons> elfy, well at the moment if you see something red you can ask about it
[19:54] <elfy> yea
[19:54] <balloons> that's all anyone can do, since there isn't a dashboard view for it.. and honestly the tests are intended to be an automated part of the process. Reviewed only on failures by someone who has acess and knowledge to do so
[19:55] <elfy> balloons: there's a big red round thing on the xubuntu jenkins tests - do you know why :)
[19:55] <balloons> Letozaf_, how's reminders for you.. Im behind thanks to messing myself up :-)
[19:55] <elfy> balloons: ok that makes perfect sense - so who does someone like a flavours QA lead talk to in order to find out
[19:56] <elfy> or is that someone my fave community team bod :)
[19:56] <balloons> elfy, at the moment jibel is the best bet if you see something broken
[19:57] <elfy> ok - cheers
[19:57] <elfy> shall be looking at that a bit more this cycle
[19:58] <balloons> at the moment, jibel said it was red earlier because a runner was down. Now it fails likely due to the bug you mentioned :-) It tries to install it the same way as you
[19:59] <Letozaf_> balloons, I'm still stuck :(  now when I run one of my tests I get this: http://paste.ubuntu.com/7582617/
[19:59] <Letozaf_> balloons, elopio wrote he would take a look this week
[20:00] <balloons> Letozaf_, yes progress is slowed by the sprint, travel, sickness, and now the world cup :-)
[20:00] <balloons> hehe.. life eh?
[20:00] <Letozaf_> balloons, no worries