[09:02] <flexiondotorg> elfy, cyphermox I remember the /etc/passwd 0600 thing. I'll check my notes...
[09:04] <flexiondotorg> elfy, cyphermox That was mentioned in relation to Language selection not being available in Ubiquity.
[13:49] <elopio> ping jibel. I set up snappy on a kvm to get started, this is easy in case you want to give it a try: http://www.ubuntu.com/cloud/tools/snappy#snappy-local
[14:03] <elopio> fgimenez: brendand: rhuddie: vila: stand up?
[14:04] <brendand> elopio, i knew i forgot someone :)
[14:07] <jibel> Hey elopio, thanks for the link. I'll give it a try
[14:24] <elopio> jibel: now I'm looking at this: http://www.wefearchange.org/2015/04/creating-python-snaps.html
[14:24] <elopio> Looks nice to get started with the packaging.
[14:24] <elfy> flexiondotorg: thanks
[14:24] <elopio> vila: ^ you might want to take a look too, for the sprint.
[14:24] <elfy> and good afternoon quality channel peeps :)
[14:35] <vila> elopio: I read it indeed a few days ago
[16:45] <flexiondotorg> elfy, Are you about?
[16:47] <flexiondotorg> infinity, Regarding - https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1434579
[16:47] <flexiondotorg> infinity, I've just tested because it is marked a Fix Released, but it is not fixed as far as I can tell :(
[16:47] <infinity> flexiondotorg: Hey, yeah, got distracted a bit, will be working on it shortly.
[16:47] <infinity> flexiondotorg: The only part that's Fixed Released was the kernel task. :P
[16:48] <infinity> flexiondotorg: There are several more bits that need fixing.
[16:48] <flexiondotorg> infinity, Oh. OK, fair enough :)
[16:49] <flexiondotorg> infinity, How are High and Critical bugs "handled"? Is there someone who collates a list of important stuff and monitors progress?
[16:49] <flexiondotorg> infinity, Just wondering who has visibility.
[16:50] <infinity> flexiondotorg: There are some tags for release tracking (See: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html), but this bug isn't so tagged, since I was working on it anyway.
[16:50] <flexiondotorg> infinity, Don't get me wrong. I was not referring to this bug.
[16:50] <infinity> flexiondotorg: As much as it would be nice to track by "high" and "critical" there are too many of those to get a handle on most of the time.
[16:51] <flexiondotorg> infinity, It was a general question. I realise there are many High and Critical bugs.
[16:52] <flexiondotorg> infinity, I'm trying to work out how to help progress some of the Critical bugs that have been picked up in QA.
[16:53] <infinity> flexiondotorg: So, that tag tracking page is what some Canonical teams use internally.  But there are as many ways to slice the bug database as there are ways to break a computer, so others are welcome to come up with their own views and find things that need escalating within their own teams (or to us).
[16:53] <flexiondotorg> infinity, Understood.
[16:54] <infinity> flexiondotorg: bdmurray probably has a better handle on how we do all of this more formally, I tend to just sort of wing it when people bring me things on IRC that sound appropriately scary enough to be worth panicking about, or small enough to be worth spending five minutes fixing.
[16:57] <flexiondotorg> infinity, Thanks for explaining.
[16:58] <elopio> zsombi: how can we help?
[16:59] <zsombi> elopio: I tried to create the JSON file under ~/.config/url-dispatcher/urls for the temp app, but somehow I failed to get the app launched...
[17:01] <elopio> zsombi: we need two apps. The first one opens, but when you click the link on that one, the second one doesn't open. Is that right?
[17:01] <zsombi> elopio: so, in order to launch the app thru url-dispatcher, we must drop an <appid>.urldispatcher file in the path I mentioned. I failed to do that :(
[17:01] <zsombi> elopio: we don't necessarily need two apps, or maybe yes... cannot teh AP launcher do the job?
[17:02] <elopio> zsombi: there is a command line tool url-dispatcher that can do it.
[17:02] <zsombi> elopio: like the current app launcher has also a url parameter, wouldn't that do the job in this case?
[17:04] <elopio> wow, it's really hard to remember. One of you guys was working with uri parameters. The other was working with URL dispatcher.
[17:04] <elopio> zsombi: can you tell me again what was the test you were doing?
[17:04] <zsombi> elopio: I've added you to the SDK trello board/card
[17:05] <zsombi> elopio: I was trying to extend the test branch kalikiana gave me on the StateSaver branch, but wasn't successful
[17:05] <zsombi> elopio: and btw, the feature only works on the device
[17:05] <zsombi> elopio: no support on desktop QPA :(
[17:06] <elopio> right, I remember that.
[17:07] <elopio> zsombi: at the moment, I can't spend much time in this because I have to finish the tasks for our sprint. You need to talk with brendand so we plan some time to spend in this.
[17:07] <elopio> the sprint finishes on thursday, so this is a good time.
[17:08] <zsombi> elopio: ok, thx
[17:08] <zsombi> brendand: r u with us? :)
[17:21] <PaulW2U> bdrc
[17:49] <elfy> flexiondotorg: on and off
[17:55] <brendand> zsombi, hello
[17:56] <zsombi> brendand: hello, I need elopio's help - or someone else's - on the url-dispatcher tests in uitk
[17:57] <brendand> zsombi, can you attend our prioritization meeting tomorrow?
[17:57] <zsombi> brendand: time?
[17:57] <brendand> zsombi, it's at 1600UTC
[17:57] <zsombi> brendand: uuuhh... I can try... that's 7pm for me...
[17:58] <brendand> jfunk, the sdk team need some time to work on url-dispatcher tests
[17:59] <jfunk> brendand: needs help from us, or time to do it themselves
[17:59] <brendand> jfunk, some of our time, i meant
[17:59] <zsombi> brendand: jfunk: more precisely on a FW in UITK launcher where we can launch an app as it would have been invoked by url-dispatcher
[18:00] <brendand> jfunk, zsombi is not sure he will be able to attend the prio meeting
[18:00] <jfunk> FW
[18:00] <jfunk> ?
[18:01] <zsombi> jfunk: there are two ways to launch an app in toolkit AP, the old way (the QML app is an embedded string) or the new way - the QML app is a physical file
[18:01] <zsombi> jfunk: sorry, I call it as fw, though it's a CPO :D
[18:02] <zsombi> jfunk: so, the string version as well as teh file version creates some desktop file with fake exec line in ~/.shared/..... folder
[18:03] <zsombi> jfunk: tedg said an <appid>.urldispatcher file must be created in ~/.config/url-dispatcher/urls which would list the protocols the app can handle
[18:03] <zsombi> jfunk: I tried that, and nothing happened :/
[18:05] <jfunk> zsombi: brendand: is this a confirmed bug in AP?
[18:06] <jfunk> sounds like the tests are not what is needing help, however testability enablement
[18:06] <zsombi> jfunk: I don't think it is, tbh all teh apps are click-packed, which are launched well with AP
[18:07] <zsombi> jfunk: what I'd need is a solution for temporary test apps
[18:07] <brendand> zsombi, jfunk - doesn't sound like a whole story, but you just need a little help to figure this out?
[18:07] <zsombi> brendand: kinda yes...
[18:07] <brendand> if anything there's an issue with url-dispatcher i think
[18:07] <zsombi> brendand: I'd need it to test the StateSaver behavior with url-dispatcher
[18:07] <elopio> it could be a problem with how we make the test application.
[18:08] <zsombi> brendand: well... the fake exec line may also be a problem, and I'm not that familiar with AP so I could dig that out
[18:08] <jfunk> brendand: elopio: has anyone spend the "1-hr vanguard" investigation time?
[18:08] <elopio> or a url dispatcher problem. Or we are missing one step to make it work.
[18:09] <jfunk> if it ends up taking more I'll create a card
[18:09] <brendand> jfunk, i don't think so
[18:09] <zsombi> elopio: that ~/.config/... path thing is also for testing, and has not been used for years...
[18:09] <zsombi> so it may not even work...
[18:09] <brendand> elopio, can you spend an hour and co-ordinate with jfunk if a whole story is needed
[18:09] <jfunk> who is vanguard right now>
[18:09] <elopio> jfunk: I think it will take more than one hour to understand what it's going on. More like 3.
[18:10] <brendand> jfunk, it would be elopio since everyone else if (officially) eod
[18:10] <jfunk> ok, well, 3 hours is a little long
[18:10] <brendand> obviously i'm here but just going to have dinner and eod
[18:10] <om26er> ubuntu-qa I have been trying to run autopilot tests on my device and have consistently had issues. phablet-click-test-setup fails with http://paste.ubuntu.com/10764820/
[18:10] <jfunk> zsombi: how urgently do you need
[18:11] <om26er> adt-run on the other throws dbus permission errors
[18:11] <elopio> jfunk: brendand: yes, I'm vanguard. But I would prefer to have a card for this, so somebody works with zsombi and tedg early on the next sprint.
[18:11] <zsombi> jfunk: we have a pretty high priority bug on it, blocking messaging app, and bfiller
[18:11] <brendand> om26er, are you running on rtm?
[18:12] <elopio> om26er: report a bug to phablet-tools?
[18:12] <jfunk> zsombi: which bug, what milestone is it targeted at?
[18:12] <jfunk> bfiller: ^
[18:12] <om26er> brendand, yes
[18:12] <jfunk> bfiller: do you concur that this is urgent enough that is cannot wait unti mid-week next?
[18:12] <brendand> om26er, you need to tell it that
[18:12] <zsombi> jfunk: seems it had not been prioritized for system images... https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1429899
[18:13] <brendand> om26er, --distro=ubuntu-rtm --series=14.09
[18:13] <jfunk> zsombi: so you're saying it can wait for help unti mid-week next?
[18:14] <zsombi> jfunk: so it looks like...
[18:15] <om26er> brendand,  oh boy, that seems to be downloading atleast
[18:24] <bfiller> jfunk, zsombi : it's blocking a story that is supposed to land end of week, but it can wait till mid-next week if you guys are busy
[18:24] <bfiller> so not super critical but would like to get it done soon
[18:25] <jfunk> bfiller: ack, we'll create a spike story to investigate start of next week
[18:25] <davmor2> om26er: did you try the adt way of running them that seems to work atleast
[18:26] <om26er> davmor2, both adt and direct from device give me this: http://paste.ubuntu.com/10764980/
[18:26] <om26er> elopio, ^
[18:26] <davmor2> om26er: no idea then
[18:28] <elopio> om26er: do you have the latest adt-run?
[18:28] <elopio> om26er: and when running directly from the device, did you do the dbus probe?
[18:28] <om26er> elopio, 3.12ubuntu1
[18:30] <om26er> elopio, no, I hadn't, doing now.
[18:31] <elopio> adt-run should do it for you. So report a bug affecting autopkgtest, gallery-app and autopilot. If you have time, debug it to understand why it's not working.
[18:33] <om26er> elopio, the problem I found with adt-run was on each run it tried to re-download the source, makes things kind of slow
[18:33] <om26er> also I did dbus probe and I am still having the same problem
[18:33] <om26er> elopio, how can I duplicate whats running in the lab do you know ?
[18:37] <elopio> om26er: http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[18:37] <elopio> om26er: sounds like a problem in autopilot or the gallery then.
[18:38] <om26er> elopio, thanks for the link. I'll flash clean just to be sure.
[19:00] <tedg> elopio, I'm back, sounds like things were punted, but I can answer questions if needed.
[20:47] <ToyKeeper> ubuntu-qa, where can we find screenshot artifacts after a failed automated sanity test run?  I see some mentioned in the test log but can't seem to find the actual files.
[20:48] <veebers> ToyKeeper: it will be available in the subunit file
[20:49] <veebers> ToyKeeper: I suggest using the trv tool that thomi created to view the file
[21:29] <dobey> they *should* be in the subunit file
[21:30] <dobey> but the version of testtools in ubuntu is quite outdated and has many bugs, one of which results in often things not being attached in the subunit file, as they should be
[21:30] <dobey> but the testtools in ppa:dobey/testtools makes it much better
[21:31] <dobey> it only has packages for trusty and vivid though, at the moment
[21:32] <dobey> so probably won't be very helpful on rtm :-/
[21:32] <dobey> anyway, time for me to go
[22:57] <elopio> veebers: nuclearbob: lets make the schedule for the vanguard during the second part of the day.
[22:57] <elopio> here comes a proposal...
[22:59] <elopio> elopio: 17:00 UTC - 20:00 UTC
[22:59] <elopio> nuclearbob: 20:00 UTC - 23:00 UTC
[22:59] <elopio> veebers: 23:00 UTC - 2:00 UTC
[22:59] <elopio> I'm not sure if that's too late for you nuclearbob. We can switch if so.
[23:02] <veebers> elopio: good idea, works for me
[23:13] <elopio> veebers: nuclearbob: I'm making a new calendar.
[23:19] <elopio> veebers: do we have autolanding on the power branch?
[23:21] <veebers> elopio: oh good question, I can't remember asking for that to be setup, so probably not
[23:23] <elopio> veebers: I will add it as a task in the card to add unit tests.
[23:23] <elopio> doesn't make a lot of sense to have autolanding with no tests.
[23:24] <veebers> elopio: hmm, autolanding is nice as it takes care of the merging once 'Approved'
[23:25] <elopio> veebers: ok, I'll ping CI. I added on the card the task to make sure we tell CI to add the tests to the autolanding run.
[23:30] <veebers> coolio