[07:20] <jibel> Good morning
[07:20] <elfy> hi jibel
[07:21] <jibel> Hey elfy
[08:30] <jibel> pitti, FYI I fixed jenkins publisher for new jobs. Jenkins has been upgraded from 1.424 to 1.480 during the move to 1SS and configuration of matrix jobs are incompatible
[08:30] <pitti> jibel: ah, thanks; i. e. new tests didn't appear in jenkins.q.u.c.?
[08:32] <jibel> pitti, yes
[09:30] <DanChapman> good morning :-)
[11:04] <davmor2> Morning all
[11:35] <DanChapman> jibel, good morning :-) it seems the failing tests where ubiquity closes before the test finishes are failing for the same reason http://paste.ubuntu.com/6473351/.
[11:41] <pitti> jibel: oops @ http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-autopkgtest/9/ARCH=i386,label=adt/console
[11:41] <pitti> jibel: I indeed dropped --paths-{host,testbed}, I'll adjust our scripts
[11:43] <pitti> jibel: whoops, I didn't actually mean to commit yet before your review, but I can always uncommit/overwrite: http://bazaar.launchpad.net/~auto-package-testing-dev/auto-package-testing/trunk/revision/260
[11:44] <pitti> jibel: I also renamed --tmp-dir to --output-dir and cleaned up garbage in there; but I kept --tmp-dir as a backwards compat alias
[11:44] <pitti> jibel: I guess we still want these scripts to run on saucy and older, so let's keep --tmp-dir for a while
[11:44] <pitti> jibel: if you are happy with this, would you mind rolling this out?
[11:53] <pitti> jibel: there are other changes in trunk which haven't been rolled out yet, are you happy with them?
[12:34] <jibel> DanChapman, so ubiquity crashed, this error usually means something went wrong earlier
[12:34] <jibel> DanChapman, did you try manually?
[12:34] <jibel> to confirm the crash
[12:37] <jibel> pitti, looks good. I think we can keep tmp-dir until trusty is out. we'll move all LTS tests to this release then.
[12:39] <DanChapman> jibel, I'm just running manually now, i had already tried it then realised I was using an older image :-D
[12:41] <jibel> DanChapman, something crash right before the stack trace /var/local/autopilot//logs//autopilot.log: Segmentation fault (core dumped)
[12:42] <jibel> argh, the crash file has no useful inforamtion to allow retracing, I'll fix that
[12:42] <DanChapman> jibel, I can confirm it happens for noneng_encrypt_lvm on ubuntugnome ubiquity just completly dies out.
[12:43] <jibel> DanChapman, yes python segfaulted
[12:43] <DanChapman> jibel i presumed the seg fault was autopilot looking for a object memory address which was no longer there :-S
[12:43] <DanChapman> jibel ahh ok
[12:44] <jibel> DanChapman, the command that crashes is /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --autopilot
[12:45] <jibel> DanChapman, if you can reproduce in a VM, run ubutnu-bug /var/crash/<crash_file>.crash and report it to launchpad where is will be retraced
[12:45] <jibel> ubuntu-bug
[12:46] <DanChapman> jibel ok cool will do that
[12:47] <jibel> DanChapman, might be a bug in autopilot though: Nov 25 08:03:08 ubuntu kernel: [  175.333778] ubiquity[5889]: segfault at 0 ip b713e158 sp bf979240 error 4 in libautopilot.so[b7136000+10000]
[12:55] <pitti> jibel: thanks; so ok to roll this out?
[12:56] <jibel> pitti, it's done, forgot to mention it.
[12:57] <pitti> jibel: ah, merci
[12:57]  * pitti retries the failed tests then
[12:57] <pitti> err, if d-jenkins would play along, that is
[12:58] <pitti> ok, done
[14:13] <elopio> good morning!
[14:14] <DanChapman> good morning elopio
[14:16] <balloons> good morning :-)
[14:17] <DanChapman> morning balloons o/
[14:20] <DanChapman> jibel, what logfiles would ubuntu-bug usually send? i'm having issues with ubuntu-bug either the UI is freezing up after the ubiquity error so it won't load, and trying ubuntu-bug from TTY doesn't want to send anything, so looks like manual route
[14:26] <xnox> DanChapman: if there is a /var/crash/ubiquity*.crash file just copy that & attach to a bug report.
[14:27] <xnox> DanChapman: plus /var/log/installer/*; /var/log/syslog; /var/log/partman
[14:28] <DanChapman> xnox, ok thanks :-)
[14:44] <jibel> xnox, all the artifacts are there https://jenkins.qa.ubuntu.com/job/ubiquity_ap-ubuntu_devel_daily-test_english_default/ARCH=i386,label=rabisu/16/ but crash file is useless if apport has not reprocessed it first
[14:46] <xnox> jibel: it's python, so it should have a traceback in plain Python.
[14:46] <xnox> =))))
[14:46] <xnox> jibel: one can unpack/view the crash file binary with apport-cli.
[14:47] <jibel> xnox, actually python segfaulted
[14:47] <jibel> and the crash file only have a core file attached
[14:47] <xnox> =(((((
[14:59] <slickymaster> hi all
[15:04] <balloons> hi slickymaster
[15:05] <slickymaster> hi, balloons
[15:05] <slickymaster> hop everything is fine with you
[15:05] <slickymaster> hope ^^
[15:14] <balloons> slickymaster, yes, everything is going quite well. Lots of post-uds work to get started on, but it was a good week last week
[15:14] <balloons> and some turkey and thanksgiving to be had yet this week .. Not bad :-0
[15:15] <slickymaster> yeah, it's true. Holiday's season is at your front door, that side of the atlantic :)
[15:18] <elfy> slickymaster: I found you :p
[15:18] <slickymaster> hi, elfy
[15:19] <slickymaster> I'm not that hard to find, either here or on #xub-dev
[15:19] <elfy> you about for a while - want to talk to you about something, but I've just got in from work
[15:19] <elfy> yea I know :)
[15:19] <slickymaster> elfy: at your disposal
[15:20] <elfy> ok :)
[15:25] <slickymaster> elfy, I'll be around until 17:30 UTC, after that I'll have to take my son to his tennis lesson
[15:28] <elfy> slickymaster: PM window somewhere
[15:28] <slickymaster> elfy: I saw it, but I'm unable to write anything in there
[15:46] <knome> hey slickymaster :)
[15:46] <slickymaster> hi, knome
[15:46] <knome> slickymaster, congrats ;)
[15:46] <slickymaster> knome: thanks
[15:46] <elfy> hi knome
[15:47] <slickymaster> it's a pleasure to be of help
[15:47] <elfy> it's a pleasure to have someone wanting to help ;)
[16:20] <Ursinha> so, I'm trying to find a way to avoid regression bugs that affect ubuntu touch packages to be missed when evaluating an image
[16:21] <Ursinha> my idea was to create a team in launchpad and subscribe it to all packages that are seeded for ubuntu touch
[16:21] <Ursinha> didrocks (that's not here) said it could be useful for you guys as well
[16:23] <balloons> Ursinha, interesting
[16:25] <Ursinha> balloons, that would give us a list like this one: https://bugs.launchpad.net/~dx-packages/+packagebugs
[16:26] <balloons> Ursinha, right. And that would be helpful to see what's happening at a glance. I wonder if there is an existing team you can use/reuse
[16:27] <Ursinha> balloons, for the other teams I created a team called <team>-packages, because some of them use the subscription to packages to something else
[16:29] <jibel> Ursinha, that'd be useful for our reporting too. For example during exploratory testing sessions we'd want to create report on the bugs found by the QA team agaisnt Touch packages
[16:30] <jibel> we tried to figure out that list from the umbrella project ubuntu-touch-preview
[16:30] <jibel> but with little success
[16:30] <Ursinha> jibel, good. would it be accurate to include all packages that are seeded in touch image?
[16:32] <jibel> Ursinha, I think it would be a good start. maybe too much accurate, but we could always exclude some packages if they generate too much noise
[16:32] <Ursinha> jibel, all right
[16:35] <balloons> DanChapman, btw, did you see this? http://www.piware.de/2013/11/whats-the-autopilot-widget-that-i-want/
[16:35] <elfy> hi balloons
[16:36] <balloons> hi elfy!
[16:36] <DanChapman> balloons, I did indeed :-) will definately be helpful in places
[16:36] <elfy> what was the 'bug' mailing list it would be useful to join?
[16:36] <elfy> hi DanChapman - thanks for the time the other day
[16:37] <DanChapman> elfy your welcome :-)
[16:41] <elfy> balloons: was it the bugsquad m/l that wasn't high volume and perhaps useful to watch ?
[16:41] <balloons> elfy, might have been.
[16:41] <balloons> ubuntu-bugs
[16:42] <elfy> that's high volume
[16:42] <elfy> must have been the other one - really should listen to them properly ...
[19:43] <dkessel> good evening
[19:44] <Noskcaj> hey dk
[19:44] <Noskcaj> dkessel,
[19:45] <dkessel> hey Noskcaj, thanks for putting me in the lubuntu group
[19:45] <Noskcaj> no problem
[19:45] <dkessel> oops I forgot to send the email though... :)
[19:53] <dkessel> done...
[19:53] <dkessel> guys... pyside or pyqt for a typical ubuntu application?
[19:55] <Noskcaj> dkessel, it probably depends on what you want. many still use pygobject and pygi
[19:56] <dkessel> Noskcaj, but that's only for gnome stuff, right? I am asking for the "standard" framework for qt with python
[19:57] <Noskcaj> dkessel, yeah. since you want Qt, i'm no help sorry
[19:58] <Noskcaj> maybe ask ubuntu-devel or ubuntu-app-devel
[19:58] <dkessel> yeah... waiting for life there
[20:03] <dkessel> Noskcaj, do you have any idea why testdrive freezes so many times (on trusty) yet?
[20:04] <dkessel> testdrive-gtk, that is
[20:04] <Noskcaj> dkessel, no, although there has always been a startup freeze
[20:04] <Noskcaj> I'd like to do the pygi port first, since that might "magically" fix it
[20:04] <dkessel> yeah, possible
[20:30] <balloons> dkessel, ahh python + qt.. honestly I suppose I haven't kept up enough. At one time it was pyqt
[21:28] <balloons> Letozaf_, how are you?
[21:29] <Letozaf_> balloons, Hi, I'm fine and you ?
[21:30] <balloons> good ;-) turkey day is coming soon here
[21:31] <Letozaf_> balloons, ah! Thanksgiving (hope I wrote it right)
[21:31] <Letozaf_> balloons, you're gonna eat a lot :)
[21:32] <balloons> you wrote it correctly. And yes, traditionally it is time to pig out. I'll try not to eat too much
[21:33] <Letozaf_> balloons, well once every now and them does no harm!
[21:33] <Letozaf_> sorry then
[21:33] <balloons> Letozaf_, so what's the status of rssreader atm?
[21:33] <Letozaf_> balloons, you can pig out without worrying  :D
[21:34] <balloons> haha, you still feel queasy afterwards!
[21:34] <Letozaf_> balloons, same as before, I was writing a test for music app now
[21:34] <balloons> Letozaf_, yes I'm sure it's the same. I just don't remember :-) I'm re-running on the device to jog my memory
[21:34] <Letozaf_> balloons, I think it still has that tabs problem
[21:35] <Letozaf_> balloons, we wern't able to switch tabs
[21:35] <balloons> ahh, right!
[21:35] <Letozaf_> balloons, I don't think I saw the problem solved yet, or am I wrong ?
[21:36] <Letozaf_> balloons, and then there was the activity indicator problem too
[21:37] <balloons> Letozaf_, well I'll see what it looks like in another minute. But yes, thank you for the reminder
[21:37] <Letozaf_> balloons, by the way what image do you run the tests on on your device ?
[21:37] <balloons> I figured you would know..
[21:37] <balloons> Letozaf_, always the latest proposed
[21:38] <balloons> Letozaf_, 2 failures, both on the toolbar animating, nice memory :-)
[21:38] <Letozaf_> balloons, ah! went away for a couple of days and forgot everythig :P
[21:39] <balloons> pretty much. UDS does that to you
[21:39] <balloons> well that and the weekend
[21:39] <balloons> I've been really out of my mind recently.. but that's a sidenote
[21:39] <Letozaf_> balloons, yes suppose so
[21:40] <Letozaf_> balloons, not the out of the mind, I mean that UDS and week end
[21:40] <Letozaf_> balloons, does that to you :P
[21:53] <dkessel> night
[21:53] <Letozaf_> night I'm going to bed too :D