/srv/irclogs.ubuntu.com/2008/07/31/#ubuntu-testing.txt

davmor2morning everyone09:34
* davmor2 thinks the wiki still isn't quite right09:34
JonPackarddavmor2: Morning davmor2 :)09:52
davmor2morning :)09:55
JonPackarddavmor2: do you have the template you were working on ready? I want to add the link to the meeting summary09:56
davmor2JonPackard: https://wiki.ubuntu.com/Testing/Bug-Report-Layout I posted it to the qa list too :)09:56
JonPackardgreat thanks!09:57
persiadavmor2: A couple questions about that template: firstly, does the testing team always know the cause?09:58
persiaSecondly, 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.09:59
davmor2persia: 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:00
persiadavmor2: That makes sense.  I suppose it depends on the class of bug, but many of the ISO testing bugs are certainly explainable.10:01
davmor2persia: 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:03
persiadavmor2: 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:04
davmor2persia: No Probs :)10:05
davmor2ara: which channel did you let know about the wiki?10:10
aradavmor2: i didn't10:23
aradavmor2: someelse did10:23
davmor2ara: ah right thanks :)]10:23
stgraberdavmor2: I updated the wiki page layout a bit11:16
davmor2:)11:16
davmor2stgraber: how did you get the magic lines to appear ?11:25
stgraberyou put --- instead of ===11:27
davmor2D'oh I know I'd done something wrong I couldn't think what :)11:27
stgraberhehe :)11:27
davmor2Looks good ta stgraber :)11:29
cr3ara: hi there, would you like to spend a moment with that ldtp integration in hwtest?11:53
aracr3: sure11:53
aracr3: did you get the chance to try what i sent you?11:53
davmor2cgregan: bit twirly for you isn't it dude :)11:55
cgreganyep11:55
cgreganmeeting11:55
cgreganmobile IRC over on ubuntu-meeting in 511:56
cr3ara: nope, I had forgotten about that. give me a little moment11:56
persiacgregan: Well, no.  still 16:00 UTC this time.12:00
cgreganpersia: I thought dave moved it as of yesterday12:00
cgregangrrrr12:01
davmor2I didn't :P12:01
cgreganhehe12:01
persiacgregan: It was proposed.  Changing it requires consensus :p12:02
davmor2http://fridge.ubuntu.com/node/1576 no change here :)12:02
cgreganpersia...well then...I'm off to start my morning in a more traditional way. (30 more minutes of sleep, and breakfast)12:02
davmor2which is a shame :(12:03
cgregan:-)12:03
cr3ara: ok, I've checked your email. first, how do you typically run your ldtp tests?12:07
araI use ldtprunner12:07
cr3ara: right, what's the exact command?12:08
arait depends on the test you want to run12:08
arafor updatesystem, i.e.12:08
arahttps://wiki.ubuntu.com/Testing/Automation/LDTP/UpdateSystem12:08
arayou can do ldtprunner update_system.xml12:09
cr3ara: is that one test or a suite of tests for update system?12:09
aracr3: 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:10
cr3ara: cool, exactly what I needed to know :)12:11
aracr3: if you use openAll, there are test suites with more than one test case :-)12:11
cr3ara: in your ubuntu-tests project, where do you intend to install your xml files?12:13
cr3ara: maybe we should start packaging your project...12:13
aracr3: yes12:13
cr3ara: I could help with that, where do you want the files in the respective directories: gedit, openAll and updateSystem?12:14
aracr3: but you can suppose any shared folder12:14
cr3ara: /usr/share/ubuntu-tests?12:14
aracr3: yes12:14
cr3cool, mind if I try it out and then push to your branch?12:15
aracr3: and keeping the folder structure I think is a good idea12:15
cr3ara: do you want the package to be called ubuntu-tests or ubuntu-desktop-testing as we discussed in london?12:16
arammm, ubuntu-desktop-testing includes both ubuntu-tests and testing-library12:17
aracr3: and I think they should be different packages12:17
cr3ara: when you say "includes", you mean "requires" in packaging lingo, right?12:17
cr3ara: so you're working on three projects right now?12:18
aracr3: and maybe ubuntu-desktop-testing being a meta package that requieres both of them12:18
araubuntu-desktop-testing would be a metapkg12:18
cr3ara: what's the LP project for testing-library?12:18
aracr3: same12:18
aracr3: but another bzr branch12:19
cr3ara: evil! :)12:19
davmor2sbeattie: ping12:19
aracr3: :D12:20
cr3ara: you should either fold the code into the same branch, which could result in two packages anyways. or, you should create another project12:20
aracr3: ok. will think about it12:21
cr3ara: for now, I would lean towards the first option. we could always change our minds later12:21
cr3basically, keep things self contained as much as possible unless there is a specific use case12:22
araok, then I will fold the code into the same branch12:24
cr3ara: cool, please do that and I'll continue working on creating two packages from that branch. we could create a meta package afterwards if necessary12:25
cr3let me know when you've pushed your changes and where the changes reside12:25
aracr3: ok. will do. lunch time now :) will continue afterwards12:25
persiaHrm?  Why is it bad to have multiple branches in a project?12:26
cr3persia: unrelated branches, not just branches of the same code12:27
persiacr3: But in the same rough collection of stuff?12:27
cr3persia: for example, pushing a mozilla branch under the xorg project is uncool12:27
persiacr3: 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
cr3persia: not the same to the extent where merges can be done between the branches12:28
persiaI 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:29
cr3persia: 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 trunk12:30
cr3persia: furthermore, the concept of series is meant to have one main branch, typically called "trunk", per project12:31
cr3persia: err, one main branch per release. for example, there might be a 1.0 series for a particular release12:31
persiaAh, 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:31
cr3I 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 available12:34
cr3ara: 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 project12:52
cr3ara: so, all the code relating to desktop testing could be self contained in a single project and be decoupled appropriately in the form of packages12:53
cr3schwuk: ping, how does pyrering make use of those generated reports?13:13
schwukcr3: 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:16
aracr3: just got back13:19
aracr3: that sounds good13:19
cr3ara: have you got ubuntutesting and the ubuntu-tests under a single branch now?13:58
aranot, yet. will let you know13:58
aracr3: ^13:58
cr3ara: mind if I do it? I've got packaging done which you could review for me13:59
aracr3: sure13:59
cr3ara: see packaging branch under the ubuntu-testing project. you can run debuild in there to create the ubuntu-tests and testing-library packages14:01
cr3ara: please try installing those packages and let me know if they look good14:02
aracr3: ok14:03
davmor2So cgregan up for  real this time then :)14:21
cgregandavmor2: Yes....and feeling much better about it! :-)14:22
cgreganlarge cuppa and a little food.14:22
davmor2:)14:23
davmor2cody-somerville: Saturday's aren't good for me :(14:59
sbeattiedavmor2: pong15:24
davmor2sbeattie: How do what were you saying yesterday about the dl-iso-test script?15:43
sbeattieoh, right. the latest dl-ubuntu-test-iso script in the ubuntu-qa-tools bzr branch supports a "--versions" argument.15:45
sbeattieThis 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:45
sbeattie(Though looking now, it doesn't include the type of iso, livecd vs alternate)15:46
davmor2:) something to perfect then :)15:47
sbeattiethat's useful for after the fact gathering the build information to report in the bug.15:47
davmor2true.15:49
=== Adys is now known as Addybot
sbeattiedavmor2: I'd be curious if you can reproduce https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/24641217:14
ubottuLaunchpad bug 246412 in memtest86+ "[intrepid] memtest86+ broken on various hardware" [Undecided,Confirmed]17:14
davmor2That's good it just fails everything then dies17:17
sbeattieyou got the same result? I'm going to nominate it for intrepid then, so that hopefully someone looks at it.17:18
davmor2I've added a confirm to it anyway :)17:19
sbeattieheh, thanks. :-)17:19
cgreganogasawara: ping18:07
ogasawaracgregan: pong18:07
cgreganHello18:07
ogasawaracgregan: what's up18:07
cgreganI just ran your script for the test results.....worked great for the results....but it did something weird with the data it pulled18:08
cgreganIt grabbed the URL and put it as the section header, dropping the section header18:08
cgreganNot sure why....it was working fine the last time18:09
cgreganAt the sprint18:09
ogasawarahrm, can you paste bin it for me to look at?18:09
cgreganSure18:09
cgreganogasawara: https://pastebin.canonical.com/7804/18:11
cgreganogasawara: BTW....the customer is still happy....so thanks for working on this18:11
ogasawaracgregan: and can you refresh my memory for an example test case wiki to test with18:12
cgreganogasawara: https://wiki.ubuntu.com/cgregan/testing/sample-cases18:13
cgreganogasawara: 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
cgreganI would think moinmoin would translate the same way everywhere.....but I think we are using the raw text anyway18:20
ogasawaracgregan: 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 site18:21
cgregansure18:22
cgreganogasawara: https://pastebin.canonical.com/7805/18:23
ogasawaracgregan: do you mind if I temporarily edit the sample-cases wiki so I can test?18:27
cgregannot at all18:27
=== thekorn_ is now known as thekorn
ogasawaracgregan: 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:01
cgreganHmm.....Not that hard. moving to private19:02
ogasawaraok19:02

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!