[11:45] <flocculant> balloons: so that was bizarre ... aborted an install, then the stick which I'd used wouldn't boot the second time
[11:46] <flocculant> also could you approve https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1511324/+merge/276102
[11:46] <knome> https://www.youtube.com/watch?v=iNe5npkid-s
[11:46] <flocculant> always good :D
[11:47] <flocculant> knome: if you have a minute you could do that MP :)
[11:47] <knome> flocculant, shouldn't it be Ctrl+L and not Ctrl +L
[11:47] <knome> :P
[11:48] <flocculant> not as worried about that as someone digging porn out of that samples place :D
[11:49] <knome> well...
[11:49] <knome> ok
[11:49] <knome> :P
[11:49] <flocculant> I'll change the +L before I merge it
[11:49] <knome> i approced
[11:49] <knome> approved too
[11:49] <flocculant> ok doke thanks - I'll do the rest now
[11:50] <flocculant> bbs
[12:46] <balloons> Good morning
[12:48] <flocculant> hi balloons :)
[13:20] <flocculant> pitti: haven't reported it with xenial being new and not sure where it stands, but ... had to ln -fs /proc/self/mounts /etc/mtab just now
[13:22] <pitti> flocculant: that should happen automatically during boot via /usr/lib/tmpfiles.d/debian.conf
[13:22] <pitti> flocculant: what happened? did you end up without an /etc/mtab after boot?
[13:22] <pitti> flocculant: please do report such issues
[13:23] <pitti> flocculant: we have long stopped the "let's break everything now and try to fix half of it after feature freeze" approach :)
[13:23] <pitti> flocculant: indeed in xenial I replaced debian-fixup.service with that tmpfiles.d snippet, but except for being faster that shoudl be more or less the same
[13:23] <pitti> and I tested it with mtab being a file and absent
[13:29] <flocculant> mmm
[13:30] <flocculant> I can try again later with the same stick on a different partition and see if I get it again
[13:31] <flocculant> pitti: I didn't actually look to see if I ended up without that - though I did manage to boot the system with upstart
[13:32] <pitti> flocculant: oh - did it not  boot with systemd, and with some error "your /etc/mtab is a file"?
[13:32] <pitti> because that's a thing; I meant to send u-devel@ about that
[13:33] <flocculant> it failed with "/etc/mtab isn't a symlink  or not pointing to /proc/blah"
[13:33] <flocculant> pitti: ack - I'll mail the list then :)
[13:33] <pitti> flocculant: ok; what kind of install was that?
[13:33] <pitti> flocculant: this is precisely meant to find installer bugs etc. which still creates /etc/mtab as a file
[13:33] <flocculant> xubuntu 64bit
[13:34] <pitti> (I'll disable the hard failure after some weeks, but we really want to find those)
[13:34] <pitti> flocculant: oh, so a desktop install?
[13:34] <flocculant> pitti: do you want me to bug report it instead?
[13:34] <flocculant> yep
[13:34] <flocculant> to a pre-formatted partition
[13:34] <pitti> flocculant: yes, please; ubiquity for a desktop install will do fine; please give me the bug number, I'll add some additional info to it
[13:38] <flocculant> pitti: bug 1511376
[13:39] <flocculant> I'll link that from the iso tracker too - so hopefully people will see it
[13:40] <flocculant> no I won't - still no testcases there to report against ...
[13:40] <flocculant> balloons: ^^ when will there be testcases showing up for iso tracker?
[13:41] <flocculant> pitti: obviously - anything I can do or provide from here - just ask :)
[13:43] <pitti> flocculant: done now: https://lists.ubuntu.com/archives/ubuntu-devel/2015-October/038961.html
[13:44] <flocculant> pitti: I can post on the dev bit of the forum - do you want people to me too the bug I just reported - or report each time?
[13:44] <pitti> and bug updated
[13:45] <pitti> flocculant: nah, duplicates aren't necessary
[13:45] <flocculant> k - I'll link your mail and this bug then
[13:45] <pitti> me too is sufficient (althuogh this isn't platform specific at all)
[13:45] <pitti> flocculant: cheers!
[13:48] <flocculant> ok done that now
[14:06] <balloons> flocculant, on the images, I would have expected them by now
[14:09] <flocculant> balloons: yep - not looked any further than me and ubuntu, I've got 32bit no 64bit, ubuntu neither
[14:10] <balloons> it's a script that runs, but it should be daily
[14:10] <balloons> some only run once a week
[14:10] <balloons> let's see
[15:45] <balloons> I just saw this: https://code.launchpad.net/~pharmasolin/ubuntu-manual-tests/VLC_updated/+merge/275715
[15:46] <balloons> flocculant, how different is that from the xubuntu + orca experience?
[15:46] <flocculant> not sure - not had time to look properly
[15:46] <flocculant> but the experience won't be saying unity, nor hud for 2 :)
[15:47] <flocculant> shame he'd added the orca bit - the vlc was ready to deal with
[15:47] <balloons> I'm of the mind to merge it, but I understand your concerns
[15:48] <balloons> I'd rather it was more vague overall
[15:48] <flocculant> it's your baby L(
[15:48] <flocculant> :)
[15:48] <balloons> the specific wording may change
[15:48] <flocculant> I meant
[15:48] <balloons> I'll try leaving a comment
[15:48] <flocculant> tbh we don't test it anyway
[15:49] <flocculant> but unless it's something very specific like an xfce thing - imho tests should be agnostic
[15:49] <flocculant> ESPECIALLY something that's going to talk to you in some mad computer voice ;)
[15:49] <balloons> You and I agree on this
[15:49] <flocculant> I thought we did :)
[15:51] <balloons> flocculant, I'm going to land it, and update / file a bug for checking on the flavor support. I'd hate to lose the improvements, and the contributor is new
[15:51] <flocculant> yea
[15:52] <flocculant> balloons: or I'll land it
[15:52] <flocculant> might look better
[15:52] <balloons> flocculant, ohh.. that would be helpful, than kyou
[15:52] <flocculant> welcome :)
[15:52] <balloons> flocculant, yea, the first MP can be nicer.. if it was you, I'd make you fix it!
[15:52] <flocculant> :D
[15:56] <flocculant> pitti: re the mtab issue, just want to double check that it's expected in vm's - I assume so
[16:04] <flocculant> balloons: ok done all that, created a new bug to doublecheck orca - mentioned in that also the screenreader bug - could be done at the same time perhaps
[16:04] <flocculant> bug 1308687
[16:05] <pitti> flocculant: this shouldn't be hardware/platform specific at all, indeed
[16:05] <flocculant> ok cool - just wanted to make sure - I suspect we'll get lots of people noticing it now :D
[16:06] <balloons> flocculant, just looking at the buglist again, and seeing all those lubuntu bugs.
[16:06] <flocculant> well
[16:06] <flocculant> I see the studio ones :)
[16:08] <balloons> and myth.. just agreeing they are quite cluttered
[16:08] <flocculant> yea
[16:08] <flocculant> I did clear out the edubuntu ones
[16:09] <flocculant> and zequence is trying to push the studio stuff
[16:43] <flocculant> balloons: I'd quite like to get that bug list cleaned up so it's just got real ones left this cycle
[16:43] <balloons> agreed
[16:48] <flocculant> I'll manage one way or the other to do that :p
[17:49] <wxl> hey folks. are we aware of the fact that the testcases are no where to be found on the tracker?
[17:53] <balloons> wxl, we are
[17:53] <balloons> but only the isotracker to be fair
[17:53] <wxl> i didn't get a notice that there was a build failure or anything. what's the deal?
[17:53] <wxl> balloons: ↑
[17:54] <balloons> well, if you'll notice there's no images for today: http://cdimage.ubuntu.com/daily-live/
[17:54] <balloons> so I'm assuming we'll builds once a new image that passes gating occurs
[17:54] <wxl> oh uh weird
[17:55] <wxl> but there are images listed on the tracker??
[17:55] <wxl> like our images are there http://cdimage.ubuntu.com/lubuntu/daily-live/20151029/
[17:57] <wxl> well the ubuntu images aren't there it seems balloons, but there are valid images
[17:57] <wxl> and those valid images don't have testcases
[17:57] <balloons> I'm not sure what you mean
[17:57] <balloons> ahh right
[17:58] <wxl> if you look at the tracker there are images for the 29th for kubuntu, lubuntu, ubuntu core, etc
[17:58] <wxl> there are no images since the 27th for ubuntu desktop
[17:58] <wxl> i think that's a separate issue
[17:58] <wxl> because no image listed has a testcase associated with it
[17:59] <wxl> release team (cjwatson no less) had no clue so i'm assuming it has something to do with either tracker management or with the testcase repo
[18:03] <flocculant> almost - for some reason my 32bit does have
[18:04] <balloons> ohh, so silly
[18:05] <balloons> i misunderstood what you meant until now, hah
[18:06] <wxl> who you guys talking to? XD
[18:06] <flocculant> balloons: what I meant?
[18:06] <flocculant> wxl: I was talking to you perhaps :D
[18:06] <flocculant> but earlier balloons and I were discussing it :)
[18:06] <balloons> you should look at lubuntu
[18:06] <wxl> flocculant: well i can assure you my question is directed at both you and balloons but other than that i don't know XD
[18:07] <flocculant> :p
[18:07] <flocculant> I *do* have a 32 bit one for some reason
[18:07] <wxl> OH
[18:07] <wxl> you do!
[18:07] <flocculant> now I think that balloons might have see what's up
[18:07] <flocculant> yep
[18:07] <wxl> i didn'
[18:07] <wxl> t scroll down that far XD
[18:08] <flocculant> have done for days
[18:08] <flocculant> wxl: scroll?
[18:08] <wxl> on the tracker, flocculant
[18:08] <flocculant> I don't see anyone but mine unless I enable them :D
[18:08] <wxl> right right
[18:08] <wxl> i usually look at them all when there are problems
[18:08] <flocculant> oh I do that
[18:10] <balloons> so normally the testsuites are copied over for a new cycle from the previous cycle. However, this is done by a handrun script
[18:10] <wxl> balloons: by qa or release?
[18:10] <balloons> as product manager, you can always edit it yourself if you wish to change
[18:11] <balloons> it's something stephane used to do. Technically, it should be set I suppose by each product manager
[18:11] <wxl> well yes but if it's universally a problem… XD
[18:11] <wxl> well if you want to make it a thing that each product manager does, i guess an email needs to go out
[18:11] <wxl> maybe with instructions if everyone's not clear on the process
[18:12] <flocculant> that'd be useful - cos most of the tracker is clear as mud :p
[18:13] <wxl> flocculant: incidentially, that was implied XD
[18:13] <flocculant> :)
[18:13] <wxl> in fact i'm desperately trying to figure out how to do this as we speak XD
[18:13] <flocculant> I can do most of what I need to now without breaking my stuff
[18:14] <flocculant> I'm also convinced I don't see all the tracker admin options
[18:14] <flocculant> 6 tabs including the empty summary one
[18:15] <wxl> yeah i'm clueless here balloons
[18:16] <wxl> or maybe mine is set right?
[18:16] <wxl> here's the testsuites associated with xenial http://iso.qa.ubuntu.com/qatracker/series/56/testsuites
[18:17] <wxl> also fwiw someone needs to edit the contacts for kubuntu :/
[18:18] <flocculant> how do you get that view?
[18:18] <wxl> flocculant: main tracker page; click on testsuites in the xenial section
[18:20] <flocculant> oic - that's just the list of all the tests that people see
[18:20] <flocculant> was looking at admin stuff
[18:21] <balloons> wxl, http://iso.qa.ubuntu.com/admin/config/services/qatracker/products/218/testsuites
[18:21] <balloons> wxl, it's something you can always change, but it's been done for everyone each cycle, so I don't see why we'd change now
[18:21] <wxl> okie dokie. thanks balloons
[18:21] <balloons> I trust at times you have changed your testsuite :-)
[18:22] <wxl> not in a while!
[18:23] <flocculant> balloons: I get The resource you tried to access doesn't exist. for that
[18:24] <balloons> flocculant, yep, it's wx's
[18:24] <balloons> you would have to manage your own
[18:24] <wxl> ok now i can go back to my regular work
[18:24] <wxl> thanks all :)
[18:24] <balloons> flocculant, like http://iso.qa.ubuntu.com/admin/config/services/qatracker/products/40/testsuites
[18:24] <flocculant> I try - but I can never find the manual :p
[18:24] <balloons> wxl, btw, any lubuntu sessions happening for uos"?
[18:25] <wxl> balloons: i haven't had time to arrange anything yet. if we did anything, it might be a planning session, but we're pretty good about communication throughout the team and working through emails/irc/etc, so that may not be too useful
[18:26] <wxl> balloons: as far as show and tell sort of stuff is concerned, i think we'll plan on doing one for 16.10 as that's when we hope to release lxqt
[18:26] <flocculant> balloons: so mine are set up?
[18:26] <balloons> wxl, ok. Always nice to see something
[18:26] <balloons> flocculant, I think they might all be yes
[18:26] <wxl> balloons: is flexiondotorg doing one on his pi2 images?
[18:26] <flocculant> cos I thought I'd done what was needed
[18:26] <balloons> wxl, yes
[18:27] <wxl> balloons: good, because otherwise i'd do one for him XD
[18:27] <balloons> wxl, :-) SHowing up in support is a good idea then too
[18:27] <wxl> yep
[18:29] <flocculant> balloons: so why do I only have 32 bit stuff - or am I now just waiting for something to finish cooking?
[18:30] <balloons> flocculant, you have testsuites set for amd64 and i386
[18:32] <balloons> flocculant, we need an upgrade from trusty testcase ;-)
[18:32] <flocculant> k - I looked in the manual but couldn't find that :(
[18:32] <flocculant> balloons: where abouts :P
[18:34] <flocculant> there really should be something written down about this :p
[18:34] <balloons> found'em. http://iso.qa.ubuntu.com/qatracker/testcases/1636/info and http://iso.qa.ubuntu.com/qatracker/testcases/1635/info
[18:36] <flocculant> right
[18:37] <flocculant> balloons: really - how to set the isotracker up for flavours - assuming flavours can turn stuff one - should be documented somewhere
[18:38] <flocculant> mostly I just worked along clicking things and hoping for the best :[
[18:38] <flocculant> :p
[19:20] <balloons> I remember there was an admin guide on the wiki
[19:20] <balloons> but I never can find it
[19:20] <balloons> it's like 3 tabs you can see
[19:20] <balloons> I think, right
[19:20] <balloons> ??
[19:21] <flocculant> I can see 5 useful ones
[19:22] <flocculant> I managed to beat it into submission now :)
[19:22] <flocculant> core had no testcases in it
[19:37] <flocculant> Pharmasolin: re Orca, if you're not sure then leave it - someone else will pick it up :)
[20:14] <knome> balloons, like 7 for me...
[20:27] <flocculant> which is why I wonder what's up with all that
[22:33] <flocculant> nuclearbob: hey - so I always feel bad about asking cos I can't do anything to actually help - but what's the status/prognosis on the jenkins for flavour effort?
[22:33] <flocculant> unless you're still not too good
[22:33] <flocculant> I do read the backlog ;)
[23:37] <flocculant> cyphermox: who's the best person to talk to about how apport works?
[23:38] <flocculant> I'm confused as to why when it gets turned on the crashdb.conf gains a #
[23:39] <flocculant> also we tell people to add Crash to ‘problem_types’: [‘Bug’, ‘Package’] so we see them
[23:40] <flocculant> and not cyphermox at all - but anyone in ubuntu-qa - what real reason is there for not being able to ubuntu-bug foo when you've a PPA?
[23:41] <flocculant> because some teams like us, have official PPAs which we use to test fixes out in - and having to have bizarre bug reporting doesn't help us at all
[23:42] <flocculant> balloons: I'm assuming that qa-team does ping them still?