[03:46] <pitti> Good morning
[08:21] <dkessel> morning pitti. i read your post about the new autopkgtest version. effortless support for perl and ruby packages sounds pretty great. good work ;)
[08:22] <pitti> hey dkessel ; thanks :)
[12:58] <numand> Hi, I want to help QA team as an tester. I upgraded to 14.10 from 14.04 and want to run a laptop/hardware test but it seems that there is not a laptop/hardware test for 14.10 in http://laptop.qa.ubuntu.com/qatracker/milestones/307/builds
[12:58] <numand> Is there something I missed?
[14:21] <balloons> hello numand
[14:48] <gQuigs> how would I mark this bug also affect "14.04", (and then I would mark the main task as fixed released) and triaged on 14.04
[14:48] <gQuigs> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1359304
[14:57]  * balloons looks
[15:06] <balloons> gQuigs, try pinging on #ubuntu-bugs
[15:06] <gQuigs> balloons: thanks
[15:06] <balloons> I'm with you, I'm not seeing it
[15:26] <balloons> elfy, tracker fixes have landed
[15:26] <balloons> go break it if you can
[16:15] <elfy> balloons: I thought the mouseover fail was one of the fixes? http://en.zimagez.com/zimage/screenshot-170914-171445.php
[16:17] <balloons> knome, did make some changes; not sure
[16:18] <balloons> elfy, you can drag and drop bugs onto the form now
[16:20] <elfy> that'll be useful when the bugs if the bugs are in some sort of order - with them just being bug icons you have to mouseover - which is ok if there are 3 or 4 - http://iso.qa.ubuntu.com/qatracker/milestones/315/builds/79345/testcases/1303/results
[16:20] <elfy> would you want to even try to see if a bug you're seeing during testing is one of those ;)
[16:20] <elfy> ummm
[16:21] <elfy> Error message
[16:21] <elfy> Invalid bug list, bug numbers must be made of digits and separate by commas.
[16:21] <elfy> drag and drop and it takes the whole thing http://blah - needs to be just the number
[16:25] <elfy> sorry balloons - but you did ask me to break it if I could :)
[16:25] <elfy> nice idea though
[16:28] <balloons> elfy, argh..it works on the dev version
[16:30] <elfy> sorry :(
[16:32] <balloons> elopio, thanks for the uitk bugs about flickables on calendar!
[16:33] <elopio> balloons: any ideas about how to tell if we are swiping on the wrong flickable?
[16:34] <balloons> elopio, my brain is so scattered this week.. ;-) So many things in-progress again. Anyways, I'm sure we can workaround the issues you pinpointed. There's a new new event UI design coming for calendar
[17:00] <elfy> balloons: just noticed a thing, don't know if it's a fix or not, but if you go to http://iso.qa.ubuntu.com/qatracker/reports/testers - the date filter actually works there :)
[17:07] <om26er> elopio, Hi!
[17:07] <elopio> om26er: hello
[17:08] <om26er> elopio, regarding dashboard, do you think I should look at 'Running' test build or only look at those that have published all results ?
[17:08] <elopio> om26er: you can get some information out of the running ones, but it's not always complete.
[17:09] <elopio> if the test suite is synching, you won't get the full logs and artifacts. But if you can reproduce it on your phone, then it's useful.
[17:12] <om26er> elopio, right I get that. What I had initially in mind was that is it good practice to start working on build before *all* its results are published
[17:12] <om26er> ?
[17:13] <elopio> om26er: it would be better to wait for a complete run. But as it is now, we don't have any, so it's ok to look at the incomplete ones.
[17:14] <elopio> do a quick run on your phone, see if you can reproduce it and gather information locally. If you can't, then leave it for a future run that might give you better info about how to reproduce it.