[05:55] <MatthewAllen> balloons, you may want to have a look at https://bugs.launchpad.net/ubuntu-qa-website/+bug/1533472
[07:20] <flocculant> balloons: that's definitely something we need to sort out :p
[16:28] <balloons> yea, the tracker is updated and looks a bit different..
[17:00] <MatthewAllen> flocculant, wxl, tsimonq2 - I was talking to balloons about creating a terminal application (for a GCI Task) that allows you to set a testcase to monitor on the QA Tracker and the application will use desktop notifications to inform you when a new result is added and a preview of its data (eg. passed, comment, etc.) - Would you be interested in this? Or would it be a waste of my time to develop? Any specific
[17:00] <MatthewAllen> features that you guys would want?
[17:09] <MatthewAllen> If I'm disconnected by the time you guys see this, feel free to email me at whosdaz <at> gmail.com
[17:21] <flocculant> balloons: do you mean it is intentional to not be able to read things?
[17:21] <balloons> flocculant, no, not at all. I mean the change occured with the release
[17:21] <flocculant> oh ok - I was a bit confused by what you said :)
[17:21] <balloons> We'll have to dig into it and see what happened. If it's poor enough, we can rollback
[17:22] <flocculant> MatthewAllen: just this minute got home, will look at that very shortly
[17:25] <balloons> MatthewAllen, notice the critical bugs box flows under the bugs box at smaller window sizes: http://iso.qa.ubuntu.com/qatracker/milestones/351/builds/110281/testcases/1307/results
[17:26] <balloons> And the bugs box overflows the section
[17:26] <MatthewAllen> balloons, hmmm - I'd assume that is because they never resize
[17:27] <flocculant> MatthewAllen: not sure that I'd be at all interested in if I'm reading that right - I have about ~50 discrete testcases I'm worried about - that is a whole lot of setting up each time I reinstall the OS and given that I do that 3 or 4 times during a 6 month cycle - not going there
[17:27] <flocculant> I'd be interested in an RSS feed via the tracker which would rely on me being logged into it only
[17:27] <MatthewAllen> flocculant, all good - anything specific you can think of that would be useful? that could be implemented with the QA Tracker API
[17:31] <flocculant> MatthewAllen: well atm - I don't know if every thing we've been looking at is live, so a bit hard to tell
[17:32] <flocculant> mmm - why am I seeing path to testcases in the top bar?
[17:32] <flocculant> http://i.imgur.com/EL4RNdh.png
[17:32] <MatthewAllen> ..., that's my bad
[17:32] <MatthewAllen> will fix asap
[17:33] <flocculant> ok - just checking :)
[17:33] <MatthewAllen> good catch, thanks for pointing it out
[17:34] <MatthewAllen> that was left over from me testing while implementing the fix for the 404 link
[17:34] <flocculant> :)
[17:36] <MatthewAllen> balloons, for the bug mentioned above - should I just push a commit to the current merge for the 404? Can you sort it out from there?
[17:37] <MatthewAllen> fix pushed to https://code.launchpad.net/~whosdaz/ubuntu-qa-website/fix1194770
[17:55] <balloons> MatthewAllen, yes I can remerged the same branch
[17:55] <MatthewAllen> mmk, I've pushed the change to the same branch
[17:55] <MatthewAllen> so you can do it whenever
[17:56] <balloons> I'm thinking we might just rollback on this
[17:58] <damascene> Is the sluggishness during software update is normal thing?
[18:01] <damascene>  When I urn # sudo -u test sh -c "echo Hi" answer: Hi \n Sessions still open, not unmounting. Is it a bug? It does not forbid me from running the command but it throw an error that block the execution of local.rc
[18:03] <flocculant> damascene: this isn't a support channel - try #ubuntu
[18:03] <damascene> I'm not looking for support
[18:03] <damascene> I think it's a bug if you can confirm it. I'll file a bug
[18:06] <wxl> balloons: fwiw i'm in support of matthewallen's idea for the qa tracker notifications
[18:06] <balloons> damascene, we have no idea what test.sh, or what you mean by sluggishness
[18:07] <flocculant> wxl: but would you prefer something you don't have to set up each time you re-install?
[18:07] <flocculant> like an rss feed from the tracker
[18:07] <balloons> during installtion, the disk and cpu usage goes up. That will make your pc seem slower than before
[18:08] <wxl> flocculant: yes, definitely
[18:08] <flocculant> wxl: not that I'm particularly worried one way or the other - one I might use, the other I wouldn't :)
[18:08] <wxl> hehehe
[18:08] <wxl> actually i wouldn't mind even a daily report sent by email summarizing
[18:08] <flocculant> well - actually I would use rss feed if it was a general thing
[18:08] <wxl> personally, though, i'd want to do it per image rather than per testcase
[18:08] <wxl> i'm interested in ALL the testcases for our particular set of images (and sometimes, other images)
[18:09] <flocculant> I thought testcase number changed when new daily
[18:09] <wxl> i don't usually use rss feeds
[18:09] <wxl> which isn't to say i couldn't
[18:09] <flocculant> for images
[18:09] <damascene> balloons, in short I'm telling a command to run as user "test" here is what happening http://paste.ubuntu.com/14489006/
[18:13] <damascene> I do not want to go and file a bug then it turn out to be because of my mistake. I've searched different forums and did not find it common and did not understand what it mean
[18:14] <flocculant> balloons wxl - I'm under the impression that when the build changes then the url does http://iso.qa.ubuntu.com/qatracker/milestones/351/builds/110283/testcases wouldn't be 110283 tomorrow for instance
[18:14] <flocculant> not sure how matthew's tool would work
[18:15] <flocculant> anyway - enough of that from me - I'd not use it :)
[18:16] <balloons> why not? His tool would use the API, so it should be fine
[18:16] <balloons> and yes you are corect
[18:16] <flocculant> why not use it?
[18:17] <flocculant> or some other why not?
[18:17] <balloons> well, I wouldn't have him build something that's of no use, heh
[18:17] <balloons> no sense in that
[18:18] <flocculant> ok - well I did give him my reasoning ^^ - I'd not want to get notifications of ~50 things that I'm interested in
[18:18] <flocculant> and on milestone testing when I'm 'WILL YOU PLEASE TEST THIS FOR US' it'd be a nightmare :)
[18:18] <wxl> flocculant: that's why i'd suggest a daily report
[18:19] <flocculant> balloons: bug 1375456
[18:19] <wxl> right and see, that's for a whole PRODUCT
[18:19] <wxl> which is what i'm interested in
[18:19] <flocculant> yea
[18:19] <flocculant> basically I'd want to know about xubuntu iso.tracker and package.tracker
[18:20] <wxl> same here, for lubuntu
[18:20] <wxl> occassionally i might want to know about some other image because i'm tracking installer issues
[18:20] <wxl> but again, that can be a whole product
[18:20] <wxl> (probably better if it is, honestly)
[18:21]  * balloons is trying to figure out the course of action to take for the tracker
[18:22] <wxl> balloons: i think you, as head of QA, will need to make an executive decision about how this is going to manifest itself, but my vote is definitely in for a daily report on a set of user-selectable products
[18:24] <balloons> ahh.. The decision lies with the one with creates it
[18:25] <balloons> meritocracy my friend ;-)
[18:25] <wxl> balloons: that's why i gave you my vote
[18:26] <flocculant> ha ha ha
[18:26] <flocculant> I'm using the I won't use that method of backing quietly away from this issue :p
[18:28] <flocculant> from my perspective if there was an rss feed on 'product' then I suspect knome could add that to our tracker so anyone interested in xubuntu could see that
[18:30] <damascene> I couldn't reproduce the problem on 16.04 just in 15.04 for now
[18:31] <flocculant> damascene: well 15.04 is just about to EOL anyway
[18:31] <teward> ^
[18:32] <damascene> I should hurry up then and replace it :-)
[18:32] <flocculant> :)
[18:34] <wxl> balloons: is there any sort of community testing for snappy?
[18:35] <balloons> wxl, talk to elopio about that :-)
[18:35] <wxl> elopio: snappy community testing?
[19:15] <balloons> flocculant, wxl, also am I crazy or are we missing a lot of defects? http://iso.qa.ubuntu.com/qatracker/reports/defects
[19:17] <flocculant> balloons: nope - not crazy - that's closer to what I wanted - 12.04 is missing now :p
[19:18] <balloons> flocculant, ok so the only issues are the path print at the top (which is fixed in trunk) and the weird colors?
[19:18] <flocculant> nooo
[19:18] <balloons> flocculant, well for instance, we don't see daily
[19:18] <flocculant> there are a huge number of bugs missing
[19:20] <flocculant> dailies defintely - both xenial and trusty
[19:20] <flocculant> I guess we're not worried about any trusty version released
[19:23] <flocculant> no reason for qa to be interested in anything but current dev and lts dailies imo
[19:23] <flocculant> as far as the tracker goes I add :)
[19:31] <flocculant> balloons: did all the different merges land at the same time here?
[19:31] <balloons> flocculant, everything landed yesterday. I'm trying to decide on whether to push forward or rollback things
[19:31] <balloons> well, I mean everything as of yesterday landed. It landed early this morning for you
[19:32] <flocculant> right
[19:32] <flocculant> tbh - given the lack of anguished cries - I wonder if it is better to just fix the issues and not roll back
[19:33] <flocculant> 2 weeks to next milestone for flavours
[19:34] <balloons> well, indeed. Now is the time to fix.. Not during milestones :-)
[19:42] <flocculant> :D
[19:43] <flocculant> not sure you should roll back - just roll forward a bit quick :p
[19:48] <elopio> wxl: hello.
[19:49] <wxl> hai elopio
[19:49] <elopio> wxl: the most useful thing at the moment is to get people to try building snaps.
[19:49] <wxl> elopio: so less formal testing then?
[20:56] <teward> balloons: ping
[20:56] <teward> just to confirm: you said that 32bit Server ISO tests are effectively dead and no longer done by Ubuntu / Ubuntu Server QA?
[20:56] <balloons> teward, yes
[20:57] <teward> balloons: you may want to tell phillw that
[20:57] <teward> incoming PM of PM log snippets
[20:57] <teward> he reached out to me, since he knows I do stuff on the Server Team (nginx, general triage when i see it, etc.)
[21:00] <balloons> teward, the best folks to ask about 32-bit images of server are the people who own them -- #ubuntu-server
[21:01] <teward> indeed - was trying to find the release coordinator for Server, but never succeeded
[21:01] <balloons> I can't speak for them. But yes, obviously the tests are exactly the same
[21:01] <teward> will bring up @ next Server Team meeting
[21:04] <teward> right... but I think phill's complaint is that people still have 32bit kit/tech and that not having the tests is "stupid" (to put it very mildly)
[21:05] <balloons> I could certainly put tests there, but the product owners own those things
[21:06] <balloons> regardless, no one is telling you you can't test or use the images; as you've noted they are still being produced
[21:06] <teward> right, not saying otherwise, just trying to determine who I can poke to get phill off my [CENSORED]
[21:06] <flocculant> /ignore works
[21:07] <teward> lolol
[21:08] <flocculant> http://assets.amuniversal.com/acc8547087bf01332a64005056a9545d is apt
[21:25] <elopio> wxl: yes. More like exploring what's possible and reporting bugs about what's not possible.
[22:17] <wxl> balloons: white on grey is bad!!! http://iso.qa.ubuntu.com/qatracker/milestones/351/builds
[22:18] <flocculant> wxl: that's what we were talking about earlier - there is a bug for that
[22:18] <wxl> kthx flocculant
[22:20] <flocculant> well
[22:20] <flocculant> that's what we started talking about :D
[22:21] <flocculant> you know how it is, got the boss talking about stuff and it just goes anywhere :p
[22:21] <wxl> indeed :)