/srv/irclogs.ubuntu.com/2009/06/17/#ubuntu-testing.txt

cr3I be out00:05
=== mrooney1 is now known as mrooney
=== asac_ is now known as asac
=== rmcbride_ is now known as rmcbride
=== swoody_ is now known as swoody
aramorning!07:28
=== mdz_ is now known as mdz
plarsara: so... no meeting then?16:03
arait is at 16:30UTC16:04
araso in 1 hour and a half16:04
araplars: ^16:05
araplars: what did you understand from my email?16:05
plarsara: oh, I'm not awake yet!16:06
araplars: ;-)16:06
* plars suddenly realizes that 1500 is in fact, NOT > 16:3016:06
plarsheh16:06
araplars: yes, these meetings around the globe are confusing16:07
eeejayhello lovely clowns17:09
aramorning eeejay!17:18
eeejayhi ara, nice to catch you awake :)17:18
araeeejay: I am missing you in my time zone17:18
eeejay:)17:19
arahello heno17:30
henohey ara17:30
aracgregan, jcollado, eeejay, plars: meeting ping17:31
jcolladoara: pong17:32
* plars is (mostly) awake17:32
* eeejay is here17:32
* heno waits for the wiki page to load17:32
jcolladoeeejay: Let's talk here, review messages in launchpad are getting messy17:33
eeejayjcollado: sure :)17:33
jcolladoeeejay: So would you prefer to have two different options? Filtering by file name and filtering by name in the XML file?17:34
eeejayjcollado: so before your changes, I was able to run mago from the build directory. This made me very happy.17:34
eeejayjcollado: yes!17:34
henoFor the general audience in the chan: we're starting a weekly desktop testing meeting in here17:34
henohttps://wiki.ubuntu.com/Testing/Automation/Desktop/Meetings17:35
jcolladoeeejay: OK. I can do that.17:35
arajcollado, eeejay: can you talk about that a bit later, please? or add an item to the agenda ;-)17:35
jcolladoara: OK17:35
henoindeed let's start17:36
henoeeejay: I just added an item for you to catch everyone up on your desktop test deployment work17:36
cgregando we have a mootbot here?17:37
heno#startmeeting17:37
heno?17:37
henono bot :(17:37
eeejayheno: you mean the first agenda item? yeah, i saw that17:37
henoeeejay: right, you've made some checkbox changes17:38
eeejayheno, yup17:38
eeejayi backed out of most of them17:38
eeejayjust for the sake of simplicity, it would still be nice to merge them in17:38
eeejaybut we don't want that to block17:38
eeejayright?17:38
henoand we agreed the tests would go in the checkbox-qa package17:39
eeejayyes17:39
eeejayi plan to talk to schwuk about it tomorrow17:39
henowhat would be blocked by that?17:39
araeeejay: is there any documentation about the work your doing? meeting minutes or something like that17:39
eeejayheno: pending checkbox core changes would block the mago plugin17:40
eeejayheno: if the plugin depended on the changes17:40
henook, I see17:40
eeejayara: https://wiki.ubuntu.com/QATeam/Specs/DailyDesktopTesting17:41
eeejayso the plugin should be complete this week17:41
araeeejay: thanks17:41
eeejaynext week is checkbox-qa, i guess17:41
eeejayand after that deployment17:41
eeejaywhere cr3 will need to hold my hand17:42
araeeejay: and is the changes your making on a public branch?17:42
eeejayara: https://code.launchpad.net/~eeejay/+junk/checkbox-mago17:42
henoeeejay: who is setting up checkbox-qa? cr3 or schwuk?17:42
eeejayheno, i understood from our chat that schwuk is, no?17:42
araeeejay, heno: and yet another question? is checkbox-qa a package meant to be in karmic, or just an internal thing?17:42
schwukheno: I'd planned to, with input from cr317:42
henook, great17:43
schwukara: in universe for karmic17:43
eeejayschwuk, i hope we could talk about it at tomorrow's meeting?17:43
henoara: in karmic17:43
araschwuk, heno: ta17:43
schwukeeejay: sure17:43
plarsand what is the purpose of checkbox-qa? this is the first I've heard about it, is it to satisfy the requirements for daily desktop testing?17:43
eeejayspeaking of.. is mago going into karmic universe?17:43
henohttps://wiki.ubuntu.com/QATeam/Specs/CheckboxExpandTestCoverage17:43
* heno afk17:44
plarsok, so is it just a temporary branch to do this, that will later be merged back into checkbox trunk? or is it assumed it will always be a separate project?17:44
araeeejay: mmm, no idea. We haven't planned that yet.17:45
* eeejay don't know17:46
araeeejay: is there a point of having checkbox-qa in karmic and not having mago in karmic?17:46
eeejayara: well, it seems like mago will be a checkbox-qa dependency, so i am just hoping it's packaged somewhere.17:46
schwukplars: https://wiki.ubuntu.com/QATeam/Specs/CheckboxEnhancements, about halfway down.17:47
eeejayalthough I would hate to see us constrained to the distro's schedule17:47
eeejaydon't want jcollado to be held back :)17:47
jcolladoeeejay: Thanks17:48
araeeejay: then a package is needed, indeed. I can take care of that task17:48
schwukeeejay: if checkbox-qa ends up in a PPA because of Mago, we can deal with that17:48
schwukOr (temporarily) have a checkbox-qa-mago until Mago is in the archives17:48
schwukBut I'd like to avoid that if possible17:48
eeejayall seem like viable alternatives17:48
schwukI'll add about the split package/PPA into the spec, just so it's captured.17:49
eeejayas we discussed at UDS, the additional non-default packages that are needed for testing should not be installed as packages, but be run from CWD17:49
* heno back17:49
* eeejay is talking about daily testing17:49
eeejaynot community and user checkbox usage17:50
schwukeeejay: got you17:50
henothanks eeejay17:51
eeejayso that's my report.17:51
henoany other topics?17:51
eeejayjcollado's branch17:51
araSuite discovery changes -- jcollado17:51
heno(is 30 min too short for this meeting?)17:51
jcolladoJust wanted to clarify how to remove the roadblocks for merging17:51
eeejayjcollado's branch is important for mago checkbox plugin17:51
cr3eeejay: me love hand holding long time17:51
eeejay:)17:52
jcolladoLet's talk about the XSL file17:52
cr3jcollado: roadblocks for merging? have you submitted some branch for review?17:52
jcolladoI think it would be a good idea to have a unique XSL file17:52
aracr3: he's talking about mago17:53
jcolladothat is easy to locate17:53
jcolladoto avoid the problems that you, eeejay, are having17:53
eeejayjcollado: this is one alternative17:54
jcolladoMaybe in a data subdirectory in the python module17:54
eeejayactually two:17:54
jcolladocould be a good place17:54
eeejay1. have MAGO_XSL in addition to MAGO_PATH17:54
eeejay2. instead of MAGO_PATH, have MAGO_SHARE that is not a ":" separated list, just one path17:55
eeejay2.1. that points to /usr/local/mago/share17:55
eeejay^ $(prefix)/share/mago17:55
jcolladoMAGO_PATH is for test suite discovery, but XSL file I think isn't part of the test cases it's something that should be part of the library17:56
eeejayjcollado: than maybe MAGO_SHARE in addition to MAGO_PATH17:56
cr3jcollado: couldn't MAGO_PATH be inferred by MAGO_SHARE? ie, something like $(MAGO_SHARE)/tests17:57
jcolladocr3: The idea is that MAGO_PATH contains multiple directories17:57
jcolladocr3: with test cases located anywhere17:57
eeejayjcollado: i kind of like that too17:57
cr3jcollado: gotcha, hence what you said about: MAGO_SHARE that is not a ":" separated list, just one path17:58
jcolladocr3: However, the XSL file is unique17:58
cr3s/you/eeejay17:58
eeejayhow about this17:58
jcolladoMaybe it's better to have MAGO_PATH and MAGO_XSL17:58
eeejayMAGO_PATH and MAGO_SHARE, where by default:17:58
cr3MAGO_SHARE seems reciprocal to CHECKBOX_SHARE, which seems to have worked well so far17:58
eeejayMAGO_PATH = $(MAGO_SHARE)/tests17:59
cr3eeejay: I like that17:59
henook, we need to wrap up, the main QA meeting is starting now in #ubuntu-meeting17:59
heno(but feel free continue here)18:00
jcolladoI don't really like to have the XSL file depend on an environment variable18:00
jcolladoIt's supposed to be something that isn't going to change frequently18:01
jcolladoIs not as the test cases that someone may try out different things18:01
cr3jcollado: I've found that having an environment variable like that makes it easier to be able to run the application from the source directory and then, when building the package, simply change that variable so that it can run from an installed package18:02
eeejayjcollado: the env variable should be an override to the defaults18:03
eeejayjcollado: they shouldn't be mandatory, nobody should know/use them18:03
eeejayjcollado: unless they are developing, like us18:03
jcolladoOk, maybe we can use MAGO_SHARE to point to the shared test cases (and the XSL file)18:04
jcolladoand MAGO_PATH for the extra test cases18:05
jcolladoMAGO_SHARE: single directory18:05
jcolladoMAGO_PATH: multiple directories18:05
jcolladoWould that be ok for you?18:05
* jcollado assumes everybody agrees18:07
cgregan:-)18:08
sbeattiecr3: that's just cause the IS team is out to get you. :-)18:12
=== fader is now known as fader|lunch
=== fader|lunch is now known as fader

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