[09:34] morning everyone [09:34] * davmor2 thinks the wiki still isn't quite right [09:52] davmor2: Morning davmor2 :) [09:55] morning :) [09:56] davmor2: do you have the template you were working on ready? I want to add the link to the meeting summary [09:56] JonPackard: https://wiki.ubuntu.com/Testing/Bug-Report-Layout I posted it to the qa list too :) [09:57] great thanks! [09:58] davmor2: A couple questions about that template: firstly, does the testing team always know the cause? [09:59] Secondly, Do you think the tester shouldn't self-triage the reported bug? While more eyes are good, I'd think more streamlining would be a faster path to a fix. [10:00] persia: Sometimes yes, if you read the wiki page you'll see why I added it.. Nine times out of ten before I report a bug I'll go onto the relevant -devel channel and say this is happening most of the time I get an answer as to the cause. So I think it is useful to have it in there as a reminder to the dev's about the discussion. [10:01] davmor2: That makes sense. I suppose it depends on the class of bug, but many of the ISO testing bugs are certainly explainable. [10:03] persia: No one should triage there own bug. However I see no issue with the stuff me and stgraber were doing where by we confirmed each others bug's and then I believe slangasek add priorities etc to all the confirmed bugs :) [10:04] davmor2: Hmm. From a process point of view, that makes sense, although in many cases when one understands a bug well, and knows that all the information is provided, it's tempting. I think working in pairs sounds like a good solution. Thanks for the explanation. [10:05] persia: No Probs :) [10:10] ara: which channel did you let know about the wiki? [10:23] davmor2: i didn't [10:23] davmor2: someelse did [10:23] ara: ah right thanks :)] [11:16] davmor2: I updated the wiki page layout a bit [11:16] :) [11:25] stgraber: how did you get the magic lines to appear ? [11:27] you put --- instead of === [11:27] D'oh I know I'd done something wrong I couldn't think what :) [11:27] hehe :) [11:29] Looks good ta stgraber :) [11:53] ara: hi there, would you like to spend a moment with that ldtp integration in hwtest? [11:53] cr3: sure [11:53] cr3: did you get the chance to try what i sent you? [11:55] cgregan: bit twirly for you isn't it dude :) [11:55] yep [11:55] meeting [11:56] mobile IRC over on ubuntu-meeting in 5 [11:56] ara: nope, I had forgotten about that. give me a little moment [12:00] cgregan: Well, no. still 16:00 UTC this time. [12:00] persia: I thought dave moved it as of yesterday [12:01] grrrr [12:01] I didn't :P [12:01] hehe [12:02] cgregan: It was proposed. Changing it requires consensus :p [12:02] http://fridge.ubuntu.com/node/1576 no change here :) [12:02] persia...well then...I'm off to start my morning in a more traditional way. (30 more minutes of sleep, and breakfast) [12:03] which is a shame :( [12:03] :-) [12:07] ara: ok, I've checked your email. first, how do you typically run your ldtp tests? [12:07] I use ldtprunner [12:08] ara: right, what's the exact command? [12:08] it depends on the test you want to run [12:08] for updatesystem, i.e. [12:08] https://wiki.ubuntu.com/Testing/Automation/LDTP/UpdateSystem [12:09] you can do ldtprunner update_system.xml [12:09] ara: is that one test or a suite of tests for update system? [12:10] cr3: in that case it only contains one test. but to be specific, it is a test suite that contains 1 test for the time being :-) [12:11] ara: cool, exactly what I needed to know :) [12:11] cr3: if you use openAll, there are test suites with more than one test case :-) [12:13] ara: in your ubuntu-tests project, where do you intend to install your xml files? [12:13] ara: maybe we should start packaging your project... [12:13] cr3: yes [12:14] ara: I could help with that, where do you want the files in the respective directories: gedit, openAll and updateSystem? [12:14] cr3: but you can suppose any shared folder [12:14] ara: /usr/share/ubuntu-tests? [12:14] cr3: yes [12:15] cool, mind if I try it out and then push to your branch? [12:15] cr3: and keeping the folder structure I think is a good idea [12:16] ara: do you want the package to be called ubuntu-tests or ubuntu-desktop-testing as we discussed in london? [12:17] mmm, ubuntu-desktop-testing includes both ubuntu-tests and testing-library [12:17] cr3: and I think they should be different packages [12:17] ara: when you say "includes", you mean "requires" in packaging lingo, right? [12:18] ara: so you're working on three projects right now? [12:18] cr3: and maybe ubuntu-desktop-testing being a meta package that requieres both of them [12:18] ubuntu-desktop-testing would be a metapkg [12:18] ara: what's the LP project for testing-library? [12:18] cr3: same [12:19] cr3: but another bzr branch [12:19] ara: evil! :) [12:19] sbeattie: ping [12:20] cr3: :D [12:20] ara: you should either fold the code into the same branch, which could result in two packages anyways. or, you should create another project [12:21] cr3: ok. will think about it [12:21] ara: for now, I would lean towards the first option. we could always change our minds later [12:22] basically, keep things self contained as much as possible unless there is a specific use case [12:24] ok, then I will fold the code into the same branch [12:25] ara: cool, please do that and I'll continue working on creating two packages from that branch. we could create a meta package afterwards if necessary [12:25] let me know when you've pushed your changes and where the changes reside [12:25] cr3: ok. will do. lunch time now :) will continue afterwards [12:26] Hrm? Why is it bad to have multiple branches in a project? [12:27] persia: unrelated branches, not just branches of the same code [12:27] cr3: But in the same rough collection of stuff? [12:27] persia: for example, pushing a mozilla branch under the xorg project is uncool [12:28] cr3: Certainly. On the other hand, the ubuntu-dev-tools project has a lot of different little utilities, which are released together, but each could be developed separately. [12:28] persia: not the same to the extent where merges can be done between the branches [12:29] I think that for smaller projects, it might make sense to leave them together just to avoid namespacing issues, but perhaps that's just me. [12:30] persia: that's fine, the point of branches is that features can be developed independently. however, once these features are done, they should be merged into the trunk [12:31] persia: furthermore, the concept of series is meant to have one main branch, typically called "trunk", per project [12:31] persia: err, one main branch per release. for example, there might be a 1.0 series for a particular release [12:31] Ah, right. I've misread the backlog. I perceived the concept of identity between package and branch, but now see that there is one branch for multiple packages as a target, which works. [12:34] I kinda wish LP was a bit more opiniated in terms of project management, it's too easy to get confused with all the features made readily available [12:52] ara: let me know when you come back from lunch, I have another suggestion for you: hwtest integration could be provided as another package developed within the same project [12:53] ara: so, all the code relating to desktop testing could be self contained in a single project and be decoupled appropriately in the form of packages [13:13] schwuk: ping, how does pyrering make use of those generated reports? [13:16] cr3: AFAICT it doesn't. No reporting framework whatsoever. I suspect they will have something internally (after all can you imagine a Google *not* using a database of some kind?), but as far as Pyreing itself goes the reports are the end result. [13:19] cr3: just got back [13:19] cr3: that sounds good [13:58] ara: have you got ubuntutesting and the ubuntu-tests under a single branch now? [13:58] not, yet. will let you know [13:58] cr3: ^ [13:59] ara: mind if I do it? I've got packaging done which you could review for me [13:59] cr3: sure [14:01] ara: see packaging branch under the ubuntu-testing project. you can run debuild in there to create the ubuntu-tests and testing-library packages [14:02] ara: please try installing those packages and let me know if they look good [14:03] cr3: ok [14:21] So cgregan up for real this time then :) [14:22] davmor2: Yes....and feeling much better about it! :-) [14:22] large cuppa and a little food. [14:23] :) [14:59] cody-somerville: Saturday's aren't good for me :( [15:24] davmor2: pong [15:43] sbeattie: How do what were you saying yesterday about the dl-iso-test script? [15:45] oh, right. the latest dl-ubuntu-test-iso script in the ubuntu-qa-tools bzr branch supports a "--versions" argument. [15:45] This walks your ~/iso/ tree looking for files named *.iso and runs isoinfo on them to pull out and report the contents of /.disk/info which includes the specific build version. [15:46] (Though looking now, it doesn't include the type of iso, livecd vs alternate) [15:47] :) something to perfect then :) [15:47] that's useful for after the fact gathering the build information to report in the bug. [15:49] true. === Adys is now known as Addybot [17:14] davmor2: I'd be curious if you can reproduce https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/246412 [17:14] Launchpad bug 246412 in memtest86+ "[intrepid] memtest86+ broken on various hardware" [Undecided,Confirmed] [17:17] That's good it just fails everything then dies [17:18] you got the same result? I'm going to nominate it for intrepid then, so that hopefully someone looks at it. [17:19] I've added a confirm to it anyway :) [17:19] heh, thanks. :-) [18:07] ogasawara: ping [18:07] cgregan: pong [18:07] Hello [18:07] cgregan: what's up [18:08] I just ran your script for the test results.....worked great for the results....but it did something weird with the data it pulled [18:08] It grabbed the URL and put it as the section header, dropping the section header [18:09] Not sure why....it was working fine the last time [18:09] At the sprint [18:09] hrm, can you paste bin it for me to look at? [18:09] Sure [18:11] ogasawara: https://pastebin.canonical.com/7804/ [18:11] ogasawara: BTW....the customer is still happy....so thanks for working on this [18:12] cgregan: and can you refresh my memory for an example test case wiki to test with [18:13] ogasawara: https://wiki.ubuntu.com/cgregan/testing/sample-cases [18:20] ogasawara: One thing I noticed...not sure if it matters: When the ubuntu wiki translates === blah === it is a title without an underline. In the Canonical one it is bold and underlined. [18:20] I would think moinmoin would translate the same way everywhere.....but I think we are using the raw text anyway [18:21] cgregan: hrm, just testing here really quick with the sample-cases wiki and it worked. can you maybe grab me the raw wiki text of one of the actual test cases from Canonical site [18:22] sure [18:23] ogasawara: https://pastebin.canonical.com/7805/ [18:27] cgregan: do you mind if I temporarily edit the sample-cases wiki so I can test? [18:27] not at all === thekorn_ is now known as thekorn [19:01] cgregan: how hard would it be to get me a wiki login for harbour? I can't seem to reproduce what you guys are seeing. [19:02] Hmm.....Not that hard. moving to private [19:02] ok