#ubuntu-testing 2009-06-01 <ara> good morning :) <jpds> ara: \o/ morning <ara> jpds: hey! <jpds> No videos of your karaokes have surfaced (yet). <jpds> Hmm: http://www.youtube.com/user/boredandblogging <ara> eeejay: hey! how was your trip back? <eeejay> hey ara :) <eeejay> ara: good, back in israel, packing, working, saying goodbye to everyone. <ara> hey eeejay :) <ara> eeejay: when are you leaving to US? <eeejay> ara: early thursday morning <ara> eeejay: wow, lots of travelling ;-) <eeejay> ara: yup :) <ara> eeejay: I am working on the pidgin branch, creating a common API for buddy and modifying the scripts <eeejay> ara: excellent! you know what i am thinking? <ara> eeejay: I hope to be able to commit something working later today <ara> eeejay: what are you thinking? * ara is scared now <eeejay> ara: at uds i sat in IM session, and there is a decision to replace pidgin with empathy in karmic :) <eeejay> ara: and a good reason to be scared <ara> eeejay: hehehee <ara> eeejay: yes, I saw that decision as well <eeejay> ara: the good news is that we have the buddy code, which was the harder part <ara> eeejay: That's why I think this is the last thing I am going to work with pidgin by now <ara> eeejay: once the buddy api is working, bye, bye pidgin :D <ara> eeejay: also, it is very likely that banshee is going to replace rhythmbox in karmic <eeejay> ara: right. and more file moving.. we will move the buddy stuff out of pidgin to somewhere more general i guess? <eeejay> ara: hah, lucky we don't have a rhythmbox script, do we? <ara> eeejay: yes, to buddy.py and out of pidgin, I guess <ara> eeejay: yes :D <ara> eeejay: but yes, empathy automation is going to be more or less trivial, the worse part of these scripts is dealing with xmpp, msn, etc. libraries <ara> eeejay: and that's working (more or less.. .:P) <eeejay> ara: yeah, empathy uses telepathy, which is a solid and active upstream project, they might have some good unit tests on the actual transports that could be useful * eeejay looks <eeejay> ara: interesting, i just learned that python-twisted has packages for all these protocols <eeejay> python-twisted-words <eeejay> hm, i guess next time. <ara> eeejay: :D <eeejay> ara: xmpp/msn/icq/aim/icq <eeejay> er, irc <ara> eeejay: running your suite as <ara> PYTHON_PATH=. ./bin/ubuntu-desktop-test -f pidgin/pidgin_messaging.xml <ara> should be enough to get the paths correctly, shouldn't it? <eeejay> yeah <eeejay> ara: and we need to fix the paths thing too <ara> eeejay: I get the following error http://paste.ubuntu.com/185544/ * eeejay tries <eeejay> ara: PYTHONPATH, not PYTHON_PATH :) <ara> eeejay: hehehe <ara> :D <eeejay> hi schwuksy <eeejay> schwuk: aren't you on holiday today? <eeejay> schwuk: could i peak at your checkbox/udt branch for inspiration? <eeejay> headed out for a bit * ara -> lunch <cr3> hey dudes! <fader_> cr3: I guess the Spaniards let you out of the country after all? We had bets on you causing an international incident and getting arrested. <cr3> fader_: I had to bribe them with the netbooks manjo gave me, which turns out well because that means less work for me <fader_> Everybody wins! <eeejay> hello, clowns #ubuntu-testing 2009-06-02 <ara> morning :-) <eeejay> howdy ara <ara> morning eeejay <eeejay> ara: i didn't understand the Buddy derivative thing, but it doesn't really matter <ara> eeejay: ok :) <eeejay> ara: ok, i get it now :) <eeejay> ara: here is what i am thinking about, specifically <eeejay> ara: http://paste2.org/p/242046 <ara> eeejay: looks nice! a solution in between ;-) very diplomatic <ara> morning jcollado <eeejay> ara: thanks :) <eeejay> morning jcollado <MDMonster_> hello everone <MDMonster_> *everyone <eeejay> ara? <ara> hey eeejay <eeejay> hi ara. i am about to push a bunch of changes <ara> eeejay: cool <eeejay> ara: I almost got the MSN suite working too.. <ara> eeejay: hehehe <ara> eeejay: almostÂ¿? <eeejay> ara: it was my first attempt! <ara> eeejay: wow! <eeejay> pushed <ara> eeejay: cool, thanks! I will continue tomorrow with the msn suite <ara> eeejay: ta! <eeejay> ara: ta ta. the notify suite will need an update, too <ara> eeejay: ok, I will have a look as well #ubuntu-testing 2009-06-03 <ara> eeejay: xmpp fails to run for me <ara> eeejay: this is the error I get when trying to connect the buddy: http://paste.ubuntu.com/187222/ <eeejay> ara: looks bad <eeejay> ara: i'll msg you some credentials to try with <ara> eeejay: yes, because it looks like an internal xmpp error #ubuntu-testing 2009-06-04 <ara> good morning! * MaWaLe is away: brb * MaWaLe is back (gone 00:01:34) <tsunamii> hi #ubuntu-testing 2009-06-05 <bcurtiswx> can someone here test bug #384098.. (Kubuntu Karmic AMD64) ? <ubot4> Launchpad bug 384098 in openoffice.org "Some tables will not display" [Undecided,New] https://launchpad.net/bugs/384098 #ubuntu-testing 2009-06-08 <ara> good morning all <ara> jcollado: hi! <jcollado> ara: Buenos dÃ­as <ara> I haven't looked to the code of your merge request carefully, but just one question <ara> jcollado: if you no longer use the -f parameter, what happen if two suites do have the same name but different folders? <ara> jcollado: (and you just want to run one of them) <jcollado> You'll have to select the application to differentiate them <jcollado> ara: Anyway, the filtering with the -s option is done by file (with or without .xml file), not by suite name as stated in the .xml file so I think is quite the same, right? <ara> jcollado: yes, the -s is by filename, but without folder. So yes, the only way to differentiate them is by adding -a <application> <davmor2> Morning All #ubuntu-testing 2009-06-09 <ara> morning! <cr3> jcollado: hey dude, glad to hear you like my graph :) <jcollado> cr3: Yes, it's a nice help to figure out what's happening <ara> jcollado, cr3: what graph? <cr3> jcollado: I've emailed ara the graph png file <jcollado> cr3: I did also. <eeejay> howdy cr3 <cr3> eeejay: yo mama <eeejay> cr3: :) <eeejay> cr3, i need to start uploading this crap so you could look at it too <cr3> eeejay: just create a branch somewhere under your account on launchpad #ubuntu-testing 2009-06-10 <ara> jcollado: hey! <jcollado> ara: Hola <ara> jcollado: I just wanted to ask you about your comment on mago vs. libmago <ara> don't you really think it will be confusing to have both as "mago" <ara> ? <davmor2> hello all <jcollado> ara: What's the difference between mago and libmago? <ara> hey davmor2 <ara> jcollado: mago is the whole framework, meaning: the library, the runner and the tests. libmago would be just the library <jcollado> ara: Then we might use python-mago <ara> jcollado: yes, that's another possibility <jcollado> ara: Other thing to take into account if we proceed with the changes regarding the test suite discovery <jcollado> ara: is that the runner is now port of the library. Should we split the library in two different parts? <ara> jcollado: mmm, tricky... <ara> jcollado: here, the question behind would be: does it make sense to have the library installed without the runner? <ara> jcollado: I think it does <jcollado> ara: As long as it's possible to run the test cases without the runner, yes. <ara> jcollado: well, not the "test cases" as we use it now, but it would be possible to use the library as a standalone library to create scripts without the testcases library if people want to <ara> jcollado: not as something that we encourage to do, but as technically possible <jcollado> ara: Then the library should contain only the applications part, but not the runner and the test suite part <jcollado> ara: Do you agree? <ara> jcollado: I think that both solutions have pros and cons <jcollado> jcollado: Maybe we can move this discussion to the maillist so that everybody can think about it <jcollado> ara: ^ <ara> jcollado: :D <jcollado> Working at home is bad. You may eventually talk to yourself. <ara> jcollado: yes, but first I would like to merge the mago branch to trunk, announce it in the mailing list, and then discuss the rest of the stuff <jcollado> ara: OK. I understand the priorities <ara> jcollado: I will rename desktoptesting to mago, if you think is more appropriate, and then discuss the rest of the things <ara> jcollado: is that ok? <jcollado> ara: Sure * ara -> lunch <Opr8iVe> Good morning! <davmor2> hello <Opr8iVe> Was wondering if youall wanted install results for 9.04 unr on the brand new Dell Mini10v <Opr8iVe> if so, where would an apropriate place be to submit that? <persia> Opr8iVe, We've completed the test phase for the 9.04 images (which is why they are shipped). <persia> That said, if the overall experience is not so good, the best thing to do is file bugs. <Opr8iVe> Yes, but theres a list of known compatable / issues hardware there, and the new Dell Mini 10 series isnt listed <persia> If the overall experience is good, and you're up for reverifying it during the karmic cycle, so 9.10 can be even better, there's a wiki page. <Opr8iVe> The install went great! Once I figured out that Imagewriter chokes if theres spaces in the path to the image file. <persia> Which imagewriter did you use? <Opr8iVe> whatever 9.04 apt-get gave me <Opr8iVe> Im not at that computer right now, so I can't be sure <persia> OK. When you can find out, please file a bug. That should be fixed. <persia> If it works great, please add notes on https://wiki.ubuntu.com/HardwareSupport/Machines/Netbooks <Opr8iVe> ah.. cool.. thats what I was looking for.. Thanks! <persia> We'd appreciate it if you'd also volunteer to help test the Alpha and Beta images for the 9.10 release as they become available, to maintain the documentation on that model. <persia> (right now, Jaunty is the right thing to have documented. Come 9.10 beta (or maybe a bit earlier), there will be an effort to update the page. <persia> And, once there's so many models there it becomes hard to track, we'll drop the page, and no longer have to warn people that it may not work on some models. <Opr8iVe> Sure.. Tho, Im no *nix guru.. I've played with it for years on and off, but am comfortable with the cli <Opr8iVe> Been (almost) windows free for 1.5 years now <Opr8iVe> wife still needs some convertin' :) <persia> Excellent. The milestone schedule is at https://wiki.ubuntu.com/KarmicReleaseSchedule <persia> We usually start testing (in this channel) on the Tuesday for a given Thursday milestone, just to knock out the kinks. <charlie-tca> Is the tracker going to be updated for alpha 2? <persia> So, the Alpha 2 image testing ought start sometime soonish. <persia> charlie-tca, That's a good question. One hopes so, as it's that time. <Opr8iVe> Rather relentless schedual yall keep, heh.. <charlie-tca> My thought, exactly. Supposed to release tomorrow <persia> Opr8iVe, Well, we need to test quite a bit to be able to make sure that we have a decent release each six months. Most of the "Alpha" milestones generate *lots* of bugs, but as we get closer, it becomes more just making sure nothing big broke since last time, and the big bugs from last time are really closed. <charlie-tca> bbl <Opr8iVe> okay.. Im gonna fire up the ubuntu partition.. Probably be back later. <slangasek> alpha2 candidate images posted <slangasek> and back down again, grub-pc was missing from the disks <eeejay> hey cr3? <cr3> eeejay: yo <eeejay> cr3, i am having a hard time deciding how we should be harvesting mago results in checkbox <eeejay> cr3, should i have it embedded in test.description? <cr3> eeejay: can you pastebin or upload the output of mago? <eeejay> cr3, the test results in mago don't go to stdout, they are written to a result file <cr3> eeejay: right, that output :) <cr3> eeejay: I have a feeling it is similar in concept to lsb which also creates some result file in its own format <eeejay> cr3, first of all, this is the last log line, after running a mago script: http://paste2.org/p/258493 <cr3> eeejay: the solution is essentially to parse the result file and create new test instances for each test parsed: test = Test(None, name=entry["section_name"], description=entry["subsection_name"], plugin="lsb", suite=self.test.name) <cr3> eeejay: that example was taken from the lsb_prompt plugin in checkbox-certification <eeejay> cr3, ah. i will look more closely at that <cr3> eeejay: so, "yes" to your original question but, just to be clear, not necessarily through assignment (test.description = "foo") as much as through instantiation (above example) <eeejay> cr3, ok. gotcha * eeejay looks at lsb things <cr3> eeejay: you can then create a test result object like this: TestResult(test, status, entry["log"], entry["duration"]) <cr3> eeejay: to make things easier for you, simply search for _journal_entry_to_result <cr3> where "journal" is the name given by the lsb folks for their output file <cr3> eeejay: by the way, remember that you need to fire report-test and report-result evens so that other plugins might know about your new instances <eeejay> cr3, ah ok <eeejay> cr3, thanks for the png <eeejay> cr3, i hung it over my bed <cr3> eeejay: are you now settled in seattle? <eeejay> cr3, still looking for a house and such <cr3> eeejay: so when you say "bed", do you mean "cardboard box under a bridge"? :) <eeejay> cr3, no - we have homeless shelters here in seattle. <cr3> too bad, I have lots of good tips for living in a box <eeejay> cr3, hah <cr3> for example, gerbils are not only a good source of protein but they can also serve as entertainment too <eeejay> cr3, i think it will be cleaner if i subclass TestCommand in the MagoInfo plugin <eeejay> cr3, as opposed to MagoPrompt <eeejay> bye ara! <cr3> eeejay: that might preferable but it breaks my heart seeing integrators having to know so much about the core :( <eeejay> cr3, too late. i have a book deal with o'rielly <cr3> fortunately, the core isn't too big, but it's more than I feel comfortable exposing <cr3> "Checkbox: the good, the bad and the ugly" <cr3> make sure you have a good pic of me for the introduction to the "ugly" chapter <eeejay> "Control your Roomba with Checkbox" <eeejay> cr3: http://paste2.org/p/258692 <cr3> eeejay: yeah, SystemExit was evil <eeejay> cr3, SystemExit is my addition. on't know how you want to deal with it, but it would be nice to be able to kill checkbox when it has a lingering thread <cr3> eeejay: ah, I used to do sys.exit(1) when KeyboardInterrupt was caught. one moment, I'll check why I removed that <cr3> eeejay: I made a related fix for bug #327810 in revno 457 <ubot4> Launchpad bug 327810 in checkbox "Interrupt signal not handled properly for cli and gtk interfaces" [Medium,Fix released] https://launchpad.net/bugs/327810 <cr3> eeejay: I'll check if introducing that signal doesn't revert the bug <eeejay> cr3, Test.command is confusing <eeejay> cr3, it is a string for a second, and then a TestCommand instance <cr3> eeejay: yeah, Test.description too. not one of my proudest moments <eeejay> cr3, i have had some low moments myself, besides living in a homeless shelter <cr3> eeejay: what behavior changes when you wrap the thread.join call in a try/catch block? I'm running checkbox in cli and gtk mode and I'm not observing that much difference <cr3> I think what we want is for the parent thread to also exit in the event the child is killed <eeejay> cr3, right <eeejay> cr3, i press ctrl+c <eeejay> cr3, get a KeyboardInterrupt stack trace printed <eeejay> cr3, but all keeps running <cr3> it doesn't seem like the exception is being propagated though. if I hit ctrl-c in cli mode when pulsating, I get thrown to the final prompt <eeejay> cr3, and then i press ctrl+c a gazzilion times in anger, but nothing <cr3> I get a similar behavior when I kill the pulse window in gtk mode... final propmt <eeejay> cr3, ok. so we misunderstood each other <eeejay> a term signal should terminate the entire deal, imho <cr3> moment... call <eeejay> cr3, when i get this mago crap working you could experiment with that. they are more complex processes than the usual scripts checkbox runs <eeejay> cr3: https://code.launchpad.net/~eeejay/+junk/checkbox-mago <eeejay> cr3, i can't figure out how to fire report-result with the correct TestResult instance <eeejay> cr3: interface.show_test() returns a new instance that has little to do with the actual test <eeejay> cr3: lunch! <cr3> eeejay: ok, off the phone finally! <eeejay> cr3. finally! <cr3> eeejay: so, why do you grab the output of stderr in MagoCommand.post_execute? <eeejay> cr3, because that is where the log output is <cr3> eeejay: didn't you say mago created a log file? <cr3> 13:43 < eeejay> cr3, the test results in mago don't go to stdout, they are written to a result file <eeejay> cr3, there is the regular debug log, which goes to stderr, but the actual results are written to file <cr3> eeejay: ah, so you grab the debug log in order to find the results file, right? <eeejay> cr3, xactly! <cr3> eeejay: does mago support a -o or --output command line parameter to specify the path to the result file? <eeejay> cr3, now i got it doing "report-test" with the right results, but i don't know what happens now... <cr3> ... which could potentially take a dash (-) as argument to specify stdout? :) <eeejay> cr3, probably <eeejay> cr3, i doubt it supports dash <eeejay> cr3, but that is minutiae, i figured out how to populate result.data properly. <eeejay> cr3, it could be pretty, i'll work on that <eeejay> cr3, but now after report-test, what comes next? <eeejay> cr3, pushing more changes <cr3> eeejay: at that point, you probably want to look at shell_prompt.py for the MagoPrompt implementation <cr3> ie, you want to show a progress bar and run mago in a child thread <cr3> by the way: directory = Path(default="%(dt_path)s") <cr3> and you don't want to self._manager.reactor.fire("report-result", result) in MagoCommand <eeejay> cr3, i only et the right report if i fire it from MagoCommand <eeejay> cr3, show_test() returns the wrong result <eeejay> cr3, i already got the progress bar <cr3> eeejay: mago should be automated, so you shouldn't need to show anything other than the pulse bar <eeejay> cr3, oh.. so no wizardy pages? <cr3> eeejay: I suspect MagoPrompt might not even be needed. try changing the plugin from "mago" to "shell" when creating new test instances <eeejay> cr3, ok <cr3> eeejay: well, from my understanding of mago, those wizardy pages shouldn't really be necessary <eeejay> cr3, i wanted it to be an option, to run each individual mago suite interactively <cr3> eeejay: in that case, s/shell/manual/ :) * eeejay first tries shell <cr3> in other words, since you deriving MagoCommand, you can probably reuse the manual_prompt or shell_prompt plugins <cr3> base on your sample xml, I'm assuming each mago test has a single result. if this is not necessarily the case, that can be handled too <cr3> by the way, if you reuse the shell or manual prompt plugins, you shouldn't need to fire the report-result event in MagoCommand.post_execute anymore <cr3> and, therefore, you shouldn't need to pass the manager instance as an additional argument to the constructor... you might not even need to override the constructor at all <cr3> eeejay: I hope things are looking good... <eeejay> cr3, sorry, wifi issues here at the shelter <eeejay> cr3, everyone is back from lunch at the mission and trying to check e-mail <cr3> eeejay: I feel we're pretty close to having something working nicely so I might be getting overly excited * cr3 gets more coffee.. not bouncing off the walls enough <eeejay> cr3, if i don't explicitly fire report-result in post_execute(), i don't get the result in the final report <eeejay> cr3, i just get an empty "skip" result <eeejay> but if i fire the event, i get both <cr3> eeejay: can you try: 1. push the current state of your branch; 2. comment out the firing of report-result from post_execute; 3. run checkbox with the argument --log-level=debug; 4. pastebin the output <eeejay> um <eeejay> yeah? <cr3> that reminds me, I need to start using pastebinit <eeejay> cr3, http://dl.getdropbox.com/u/280491/submission.xml <eeejay> cr3, http://dl.getdropbox.com/u/280491/checkbox-mago.log <cr3> eeejay: aha! so, if you're running tests manually: 1. the result status will be taken from the radio buttons which is set to skip by default; 2. the result data will be taken from the comment box. <cr3> eeejay: try with plugin = "shell" just for kicks <cr3> perhaps an improvement could be that running the test should reset the radio buttons based on the status of the command <eeejay> cr3, yes! <eeejay> cr3, please <eeejay> cr3, before i run them as shell, i need to put whitelist blacklists in place <cr3> eeejay: I'll see if I can kick that change in the trunk quickly, one moment <eeejay> cr3, it is bizarre how in the gtk user interface in makes a new testresult instead of using the one from the test. <cr3> the preconception was that the manual feedback was the result <cr3> if the test outputs data and the user provides a comment, what to do? <eeejay> the test's result should populate the UI <eeejay> at least in half-manual tests <cr3> eeejay: so the comment box should be filled with the output of running the test? <cr3> I have considered that before but it felt weird to me. if it feels alright to other people, I'm easy <eeejay> cr3, more importantly the "yes"/"no" should be changed <cr3> eeejay: I'm done with the gtk interface, now doing the cli interface <cr3> eeejay: fix pushed <eeejay> i am off for a bit <cr3> eeejay: pip pip, cheerio #ubuntu-testing 2009-06-11 <ara> good morning! <persia> Has anyone else looked at the Ubuntu Studio alpha 2 builds? I can't seem to get the -rt kernel to boot post-install. <ara> persia: I haven't try <ara> tried, even <persia> ara, No worries. I'll bug the team. Might be that the images fail. <ara> jcollado, eeejay: people are already talking about mago in the list ;-) <persia> So, I'm trying to test something in a schroot. I've used schroot -p to get access to my environment (so X works, etc.). Unfortunately, /dev doesn't contain the device I seek. Does anyone happen to have a strategy to work around this? <sbeattie> persia: did you come up with a solution? I've not used schroot, but I've bind-mounted /dev successfully into other chroots before to solve that problem. <persia> sbeattie, I ended up finding a way to do my test without direct device access. I'll give bind-mounting a shot, although I worry about permissions (I tend to use schroot to run things I don't trust on my local system :) ) <sbeattie> you could bind mount just the specific device you need access to, rather than all of /dev <persia> Really? How does one do that? <stgraber> just like you would for a directory <sbeattie> yep; e.g. mount -o bind /dev/sdb1 /tmp/sdb1 (where you've touched /tmp/sdb1 to make it exist first) <persia> Oh, nifty. I'll definitely try that next time I launch, as it's minimally invasive. <henter> 0627 0627hii <slangasek> we could use some help testing kubuntu ISOs for alpha2, currently there are 0 test results reported in for any of the ISOs * fader does some kubuntu alternate amd64 testing <eeejay> hey cr3 <cr3> eeejay: yo homie <eeejay> cr3, it's looking good <eeejay> cr3, now i am at the stage where i am dealing with the test results <eeejay> cr3, is the launchpad_report xml format what we use? <cr3> eeejay: excellent, but are you still firing report-result in your MagoCommand? <eeejay> cr3, no, and that is another buggie <cr3> eeejay: ideally, you shouldn't be concerned with the resulting report and you should only have to fire a report-result event <eeejay> cr3, the whole "questions" concept is very manual testing <cr3> I'm not sure I understand <eeejay> cr3, right now i added a "prompt" option to the plugin's options <eeejay> cr3, when it is false, the tests are added as shell plugin tests <cr3> eeejay: can you push your latest code so that I can have a look at that? <eeejay> cr3, when true: "manual" <eeejay> cr3, it is pushed <cr3> eeejay: interesting... <eeejay> cr3, how bad is it? <eeejay> cr3, with prompt being true or false, I want the test results to have the same fields, namely: <cr3> eeejay: it's good, I really like how you can set the plugin on the fly like that :) <eeejay> 1. pass/fail/skip 2. duration 3. message <cr3> eeejay: hm, that's reasonable but I wanted to get someone else's point of view regarding #3 <cr3> fader: yo, got a minute? <fader> cr3: For you I've got three! <eeejay> cr3, the whole "comment" field is arbitrary for these kinds of tests. it is a nice addition, but that is not where the data should be attached <cr3> eeejay: by the way, correct me if I'm wrong but it doesn't seem like you need the mago_prompt plugin anymore, right? <eeejay> cr3, correct <eeejay> cr3, it is staying around - just in case :) <cr3> eeejay: so where should the data be attached then? <cr3> fader: so, in checkbox, when a manual test has a corresponding script which can be run from the "Test" button, would it be reasonable for the output of the command to populate the comment box? <eeejay> cr3, result.data is fine, but the way it is martialled in launchpad_report doesn't seem right <fader> cr3: From a simplicity of test creation point of view, sure. From a user-experience point of view, I don't like it. :( <fader> IMO the comments box should be for the user and for the user alone. If I start seeing stuff pop up in there I'm going to get nervous and wonder if it's safe to edit. <eeejay> cr3, fader, i think we might need to introduce a new UI for this. it doesn't match the manual testing experience <fader> Plus the cases where people will want to edit or delete the info that gets populated there... it just feels unsafe :( <fader> (Sorry, eejay) <cr3> fader: fyi, I have changed the behavior of the radio buttons to be set to pass/fail depending on the result of running the script. I thought that was reasonable though * eeejay agrees <fader> Yeah, I saw that discussion... that's a Good Thing. <eeejay> cr3, akshully, that might be problematic.. <fader> Nice little usability boost! <eeejay> let's say video test <eeejay> the gst script returns status 0 <charlie-tca> anyone else having issues restarting the desktop cd? <eeejay> doesn't mean the user saw the video correctly <fader> eeejay: It seems to me that as long as the user can change the value to 'fail' that's not a big deal <cr3> eeejay: for most cases though, it seems that the behavior is at least helpful to the user, not authoritative for the user. otherwise, the test wouldn't have to be manual anyways <fader> We're saying "Checkbox thinks this thing worked correctly. Did it really?" <eeejay> fader: cr3: i would like to see an alternative show_test() method, instead of changing the behavior of this one <cr3> eeejay: what you're asking for is a way to select the tests which the user may or may not want to run, right? <eeejay> fader: cr3: the radio button change is very subtle, not really noticeable <eeejay> cr3, yeah. but not upfront <eeejay> cr3, allow the user to watch the test <eeejay> cr3, and then populate a UI <fader> I forget.... what does the radiobutton default to now after a test? <eeejay> cr3, which could even be read-only, except for a comment field <cr3> fader: it remains in skip state <eeejay> .. which i think is the correct behavior for manual tests <cr3> eeejay: wait, are you saying you want the test to: 1. run automatically; 2. populate the ui; 3. ask for feedback from the user? <eeejay> cr3, 3 - give the user an _option_ for additional comments <cr3> eeejay: as provided by the current ui, right? <eeejay> cr3, just like the current manual plugin <eeejay> cr3, could we talk on the phone? <fader> Heh <eeejay> fader: cr3: skype conference? <fader> eeejay: You don't realize that cr3 has a direct brain-link to IRC :) <cr3> eeejay: that's what I once did but then I introduced hibernate and suspend tests, imagine the user experience then: user is running a test and then clicks the "Next" button. suddenly, his machine hibernates for no apparent reason :) <eeejay> cr3, brilliant :) <cr3> eeejay: my motivation at the time is that I found it redundant for the user to have to click on the "Test" button, so I thought it was helpful to just run the test :) <cr3> eeejay: ideally, I would like to solve both hibernate and mago use cases in a consistent way instead of introducing all kinds of variations <eeejay> cr3, i agree <cr3> eeejay: even in the case of mago tests, I think the user might get surprised if applications suddenly start popping up without their prior and explicit consent or, at least, some action on their part <eeejay> cr3, the action on their part is "run test", we could make it clearer <cr3> that being said, lets revisit the problems with the current manual user experience <eeejay> "run automated UI test" <eeejay> dunno <eeejay> cr3, the current manual experience is good, imho <eeejay> cr3, that is why i don't want to touch it, but create a new UI that matches mago tests <cr3> eeejay: I would have the description of the test be explicit but keep a consistent "Test" button which can consistently have the same shortcut (Alt-t) <eeejay> cr3, i am just going to come up with a patch as a proof of concept <eeejay> cr3, but first i will eat a sandwich <sbeattie> iiiinteresting, ubiquity just crashed on the kubuntu live installer. * fader wishes he could click a "give sandwich" button. <cr3> eeejay: I really don't see a problem with the description of the test saying something like: This will test gedit functionality. Click on the Test button to run the tests automatically. <cr3> fader: that would have to be run by the dbus backend so that you could also run: sudo give sandwich <fader> cr3: Wow, I should have seen that coming. <cr3> fader: that was pretty predictable indeed, I will try harder next time <fader> :) <fader> http://mirror.servut.us/kuvat/push%20button,%20receive%20bacon.jpg <cr3> fader: the problem is that the sign is probably for a dryer in the bathroom... even I can't come up with something to do with bacon in the bathroom * cr3 is lacking imagination :( <fader> cr3: "He doesn't know how to use the three shells!" <cr3> what the heck am I talking about, bacon is always good wherever you are <cr3> fader: very good point, I spent many a sleepless nights pondering those darn three shells <davmor2> fader: how are you dude? <fader> davmor2: brilliant and stunningly good-looking. You? * davmor2 picks myself up off the floor. <davmor2> Dude you really need to clean that mirror from time to time ;) <davmor2> Fine thanks. Racing around like a headless chicken but other than that okay :) <fader> Heh... it keeps you busy. Off the streets and out of trouble, right? <davmor2> fader: I know but I could do with being paid too :) * charlie-tca thinks some people want it all ;-) <davmor2> charlie-tca: eating helps you know it's true :) <charlie-tca> Once in a while, anyway <charlie-tca> I haven't eaten in two days, again <charlie-tca> I am thinking I need to, though <fader> I have a great idea for a company. Busy people can pay me to eat for them. (Naturally I'd want high-end clients who are just too busy to eat their five-star meals.) <charlie-tca> heh, just might work * davmor2 no good looking at me then :D <cr3> fader: you could also offer to go to the bathroom for them as an added bonus, no charge <charlie-tca> ohh, I would pay for that! <fader> cr3: Nah, I'm going to focus on my core competency here. I'll leave the add-ons for third parties. * fader mutters something about leveraging synergies to grow the brand... <cr3> fader: you're missing out on two potential customers in this channel: charlie-tca and myself <fader> cr3: I've seen what you eat. You couldn't pay me enough to go to the bathroom for you. <davmor2> cr3: he did say 5 star meals though dude ;) <fader> ;) <cr3> yeah, meow mix probably doesn't qualify as "5 start" <cr3> err, "star" even <davmor2> cr3: It might do if your a cat :D <fader> I'm definitely not going to the bathroom for cats. <charlie-tca> Seems cleaner than dogs <fader> Hey, does the kubuntu oem install normally have a desktop icon for 'prepare for shipping' the way the ubuntu (gnome) oem install does? <davmor2> fader: yes <fader> davmor2: Thanks, that's what I thought. <davmor2> it's normally in the desktop folder * fader is off to Launchpad. <davmor2> fader: first check and see if it's in the menu <fader> davmor2: Yeah, I didn't see it there unfortunately. <fader> There's also nothing in ~oem or ~oem/Desktop <fader> Er, there are things there but not oem-config related :) <cr3> pip pip, cheerio <persia> Anyone bored and feel like testing UNR? <fader> BRB, got to switch network connections here <fader> What did I miss? <davmor2> fader: just to double check you had installed the oem part right ;) <fader> Hehe yeah <fader> I had the same thought but was reassured when I realized I was logged in as 'oem' and it said 'oem temporary user' (or whatever it says) as my username <davmor2> i'm just confirming it for you :) * fader hugs davmor2. <davmor2> persia: just finished dling it <persia> davmor2, Then you've beaten me :) <persia> Apparently all the regular testers took a break for this alpha, which leaves the rest of us :) <davmor2> 20meg BB <davmor2> persia: no it's just I've been busy ;) <persia> Oh. I thought plars and StevenK usually did the UNR testing. Sorry to exclude you. <davmor2> Oh yes <davmor2> persia: I just throw my hat in the ring from time to time :) <davmor2> fader: can you try a resize on kubuntu against an existing install please <davmor2> with the existing having ext4 for the fs <fader> davmor2: Roger wilco... I'm just finishing up an install now so you have good timing <fader> davmor2: You don't mind if it's an alternate install rather than desktop do you? <davmor2> My issue is on live but it might be good to see if it affects alt too <fader> Huh, I don't seem to have the option. <fader> Maybe I munged something in my last install... let me play with this a bit. * sbeattie tries to reproduce as well. <sbeattie> davmor2: worked here. <davmor2> meh just me on hw then? <fader> Okay, resize has shown up for me this time with only a single partition. Does it not pop up if you have too complex a partition layout for it to handle? <fader> My internal clock is set to EAT... back in a bit <eeejay> hey fader <eeejay> fader, have you ever edited the checkbox glade file? <fader> eeejay: I don't believe so... why? <eeejay> fader, because there are custom widgets in it <fader> eeejay: cr3 might snap off my fingers if I started poking around at the internals of it <eeejay> fader: and i think you need a glade catalog file to compliment it <fader> eeejay: Yeah, I can't help you with that then :( <eeejay> fader: darns! <davmor2> fader: I got prepare for shipping in my kde <fader> davmor2: Is this with the alt CD? <eeejay> davmor2: where will you ship kde to? <fader> Hehe <davmor2> eeejay: endusers <davmor2> fader: no live <eeejay> davmor2: typical <fader> davmor2: Hmm, I'll try it again with the alt CD next <davmor2> eeejay: who else would you like kde to be shipped to ;) <eeejay> davmor2: the world's hungry <davmor2> eeejay: wouldn't they still be hungry <davmor2> I'd of thought food would of been better :) <fader> o_O <eeejay> i think they could use all the help they could get <slangasek> fader: I hear there may be something missing from the kubuntu alternate OEM stuff? <fader> slangasek: Yeah, I didn't get the 'prepare for shipping' icon <fader> I filed a bug but I will retest momentarily... I can't be sure it wasn't an ID10-T error. <slangasek> fader: does that mean the OEM install process fails? I'm not familiar with that icon <fader> slangasek: There was no way to finalize the install and prep it for the end-user to receive. It kept the 'oem' user and didn't present the first boot stuff that the user is supposed to get at first boot. <fader> First boot first boot <slangasek> fader: ok <fader> slangasek: I will retest and see if it was the crack I had for lunch :) <slangasek> I guess I'm inclined to pass on documenting this in the errata anyway, supposing that OEM mode is not a significant use case for our early-alpha testers #ubuntu-testing 2009-06-12 <fader> Yeah, I'd imagine you're probably right. :) Still seemed worth filing a bug though. <persia> I don't know if it's related, but r669 of oem-config has the comment "Declare GTK frontend as "NotShowIn=KDE;" rather than <persia> "OnlyShowIn=GNOME;XFCE;" (LP: #163518)." <persia> bug #163518 <ubot4> Launchpad bug 163518 in oem-config ".desktop files say OnlyShowIn=GNOME, should be NotShowIn=KDE;" [Wishlist,Fix committed] https://launchpad.net/bugs/163518 <fader> persia: I'm not sure if that's related or not. My guess is that the .desktop file for the 'prepare for shipping' icon should have been created in ~oem somewhere, but it wasn't on my system <fader> Does anyone have an OEM Kubuntu install still up? <persia> fader, Hrm. My reading of that was that the icon wasn't to show in KDE anyway. I presume someone is working on a proper KDE port of the tool, which would get it's own icon. <fader> persia: Yeah, tough to say without a system to compare it to. :/ Though it sounds like it worked for davmor2 on the live CD, so I'm leaning toward bug on the alternate <fader> Or user error, I still haven't ruled out that I munged something :) <persia> IF it worked on the alternate, than it may be that r669 hasn't been pushed into images yet. <persia> s/alternate/live/ <persia> Or there may already be a KDE front-end. <fader> Okay, rerunning the OEM install... let's see what happens. <eeejay> cr3, hey hey <cr3> eeejay: yo ho ho <eeejay> cr3: question: how do you edit the glade file? <fader> bork bork bork <eeejay> cr3: glade-3 effed it up <cr3> eeejay: glade-2 <cr3> <!DOCTYPE glade-interface SYSTEM "http://glade.gnome.org/glade-2.0.dtd"> <eeejay> cr3: for real? <eeejay> cr3: ok <cr3> eeejay: dude, that file dates back a long time <eeejay> cr3: so we could skip glade3 and go straight for gtkbuilder <cr3> eeejay: you know, I once considered making it possible for plugins to define their own glade in order to customize the interface <cr3> that got postponed because there wasn't that much need for it and I fear it might start making the interface inconsistent <cr3> I like the fact the user can predictably know that each manual test will look more or less the same <eeejay> cr3, i borked the glade file when i opened it in glade-3, so i started prototyping directly in pygtk <cr3> you could also prototype in gimp :) <eeejay> cr3: it will also cause a split between cli and gtk <eeejay> true <cr3> eeejay: that's another thing I like, the base UserInterface class provides a fixed set of user interactions which can be derived by each of the interface implementations, to which I'd like to add qt one of these days <eeejay> cr3: yeah, i like that setup too <cr3> if we get package testing useful enough for the kde folks, I should ask them for an implementation <fader> Allegedly QT Designer can import glade files. <cr3> eeejay: I tried to make the show_* methods in the UserInterface class kinda generic, with show_test as the only real exception <fader> It might not be too tough to get a KDE UI <fader> Hmm, still get the same issue with the alternate kubuntu CD in OEM mode <fader> persia: ^^ <fader> Outta here for the night... * fader waves. <ara> good morning all :) <eeejay> cr3, morning ho <cr3> eeejay: ya man <eeejay> cr3, would you be receptive of a checkbox branch that uses gtkbuilder? <cr3> eeejay: I'm not very familiar with gtkbuilder, is it like glade but more better? <eeejay> cr3, glade is being deprecated <eeejay> cr3, next GNOME release is supposed to have zero glade reliance <cr3> eeejay: such a branch would be quite welcome then :) <eeejay> cr3, excellent, thanks :) <cr3> eeejay: but before, I think heno and ara would prefer we land mago integration so that it can start being used <eeejay> cr3, it's a 30 minute deal, i spent time converting accerciser a while ago, so i know the tricks <cr3> eeejay: gtk-builder-convert and voila? :) <eeejay> cr3, a bit code massaging <cr3> eeejay: cool, could you push gtkbuilder migration as a branch separate from mago integration? <eeejay> cr3, of course <cr3> man, I wish I had to be converted so that I could get a massage too :( * cr3 steps out for grub, the other boot loader <Cut_em2_it> hello <Cut_em2_it> ? <cr3> Cut_em2_it: hi there <Cut_em2_it> on your testing page, it says that the next test is on March 30, 2009? <cr3> Cut_em2_it: oups, which page is that? <cr3> Cut_em2_it: sorry, I need to step out for a moment, back in a moment <Cut_em2_it> https://wiki.ubuntu.com/Testing/UbuntuTestingDay/20090330 <Cut_em2_it> k <cr3> Cut_em2_it: I'll send an email out to a couple people about that page and the parent page <Cut_em2_it> ok <Cut_em2_it> thanks <eeejay> hey cr3: more silly questions <eeejay> cr3: what are, and how do i use test attachements? <eeejay> cr3, it doesn't seem like any plugin uses them <cr3> eeejay: attachments: /etc/shadow <cr3> or attachments: cat /etc/shadow <cr3> it's just a newline separated list of files or commands <eeejay> cr3, yeah. i understood that from the code <eeejay> cr3, are attachments things that get attached after a test has run? <cr3> checkbox-certification/suites/bootchart.txt uses it * eeejay looks <cr3> it gets attached upon reporting. I'm not sure if launchpad supports that concept, I haven't implemented it anyhow <cr3> I only use it on the commercial side <eeejay> interesting concept <eeejay> cr3, so i think perhaps the mago log should be an attachment <cr3> eeejay: my original idea named the parameter "debug" because I thought it would be useful to attach supplementary debugging information to tests <eeejay> cr3, the problem being that it is singleton (ie. not associated with a set of results) <eeejay> cr3, but with the actual test <eeejay> cr3, so consecutive runs would overwrite it <cr3> eeejay: that should be fine, as long as it "overwrites" rather than "appends" <cr3> eeejay: err, maybe my understanding is premature: if mago will be run multiple times during one checkbox run, then that may pose a problem indeed <eeejay> cr3, yeah, but i am afraid a split might occur, between results and mago log <cr3> if that's the case, maybe I should reconsider associating attachments with results rather than tests <eeejay> zactly <cr3> just to make sure we understand each other, it would work if the logs were captured immediately after the test is run, right? <eeejay> cr3, what i started doing was making a structure in results.data <eeejay> yeah, that would be the idea <cr3> I didn't have a use case for associating attachments with results before but now I do, I'll report a bug and make the necessary changes soonish <cr3> it sounds like attachments are what you need rather than shoving everything in result.data <eeejay> cr3, yeah <eeejay> cr3, i would like to have an attachment, and a field for user comments <eeejay> cr3, so the comments would stay in data <cr3> eeejay: agreed, that's the way it ought to be <eeejay> cr3, did you see my gtkbuilder branch? does it kick ass? * eeejay uses test.attachment in the meantime. <cr3> eeejay: I've subscribed you to the bug I created, #386545 <cr3> eeejay: by the way, my current attachment implementation makes the assumption that if a test is skipped then attachments should be ignored. do you think that's reasonable? <eeejay> cr3, um kinda <eeejay> cr3, we have a mago concept of error <cr3> eeejay: I haven't noticed your gtkbuilder branch, have you submitted it for review? <eeejay> cr3, when things go horribly wrong in the automation <eeejay> cr3, yup <eeejay> cr3, anyway I thought of using "skip" with the error message <eeejay> cr3, https://code.launchpad.net/~eeejay/checkbox/gtkbuilder/+merge/7391 <cr3> eeejay: hm, that's an interesting use case but I'm not sure I agree <cr3> eeejay: but I don't really have a solution though <eeejay> cr3, it is not perfect. but that was my plan, re: your question <cr3> it seems like we need another status like "the test itself failed" <eeejay> cr3, yeah: "error"? <cr3> but I'm really afraid to introduce more statuses, I want to keep things freaking simple * eeejay agrees <cr3> I'll have a look at the some posix testing standard if I can find it, maybe it could convince me to have more statuses <cr3> eeejay: is there any problems in running the gtkbuilder version on older releases of ubuntu, like dapper or gutsy for example? <eeejay> cr3, possibly, yes <cr3> eeejay: dapper and gutsy are about to be eol, so we should at least make sure it runs on hardy and we could release soonish <cr3> I think dapper is going eol on July 1st, so I'd be comfortable releasing gtkbuilder on that date... assuming hardy works, of course <eeejay> cr3, ok <cr3> eeejay: your changes look good but I'll need to look deeper into the hypertextview part, it seems hairy <eeejay> cr3, yeah, i created a catalog for it <cr3> eeejay: I thought we'd dispense with glade altogether <eeejay> cr3, dispense? <cr3> grep -ri glade * || echo 'no more glade' #ubuntu-testing 2009-06-13 <eeejay> cr3, ah <eeejay> cr3, gladeui is good <eeejay> cr3, libglade is bad <eeejay> cr3, meaning the actual glade application is still called glade, and it is still used <eeejay> cr3, but the files it produces are gtkbuilder files <eeejay> cr3, do you have a last.fm profile? <cr3> eeejay: sorry dude, I need to jet. I hope we can pick this up either on Monday or this weekend <eeejay> yup <eeejay> cr3, don't play too hard <cr3> cool, pip pip #ubuntu-testing 2009-06-15 <ara> good morning! <davmor2> Morning All <cr3> is there a known problem with wired networking in the daily-live/current install? I installed on two systems, one with broadcom and another with intel ethernet controllers, and both have wired ethernet greyed out <cr3> (that kind of problem is going to be difficult to detect automatically :( <cr3> all testing and no networking makes cr3 a dull boy... <fader> cr3: There's a bug right now with the broadcom driver at least <fader> cr3: bug 384861 <ubot4> Launchpad bug 384861 in linux "Broadcom NetXtreme II (BCM5708) not detected by installer [karmic]" [High,In progress] https://launchpad.net/bugs/384861 <cr3> eth0 seems to come up though, in both cases, but it's not being assigned an address :( <fader> Hmm, not what I was seeing, but then I was also looking in the alternate rather than the live install #ubuntu-testing 2009-06-16 <ara> good morning! <xivulon> Hi all, would it be possible to test http://people.ubuntu.com/~evand/wubi/karmic/wubi-r136.exe as a stand alone application (letting it download and install the Jaunty ISO) <xivulon> Please report any bug in launchpad, tagging as r136 <eeejay> hi cr3, fader <cr3> eeejay: yo homie <fader> eeejay: Wassap, yo? <eeejay> cr3, fader: how do i get around having to provide a 15 alphanumy? <eeejay> cr3, fader: certify_prompt.py <cr3> eeejay: --config=checkbox-compatibility/plugins/blacklist=certify_prompt? :) <eeejay> cr3, brilliant <cr3> eeejay: slightly verbose but possible <cr3> "make common things easy, rare things possible" -- someone who knew what he was talking about <eeejay> "You've been leading a dog's life. Stay off the furniture." -- /usr/games/fortune <cr3> this is a question for all you qa guys who've probably reported a bug or two: I was reporting a new bug in launchpad and then I accidentally pasted outside the text area in firefox. that brought me to a new page and pressing back lost all my carefully crafted but report. wtf?! <fader> cr3: Don't do that. ;) <sbeattie> cr3: sometimes firefox remembers what you type, and sometimes not; I'm not sure if any of the plugins help with that. <eeejay> Phá» break <cr3> sbeattie: yeah, I noticed the "sometimes" part too <sbeattie> cr3: of course, you could install itsalltext and configure it to pop up vi in a terminal when you want to edit large blocks of text. <eeejay> later <sbeattie> eeejay: mmm, Phá». <sbeattie> eeejay: are you in seattle now? <cr3> eeejay: I thought you were mostly vegatarian... <eeejay> sbeattie: yup, seattle <eeejay> cr3, got a tofu version <fader> eeejay: Is that particular to that place or is it fairly common? <eeejay> fader: seems to be pretty common <fader> Indeed... I was just trying to figure out where to get vegetarian food for dinner tonight. You may have talked me into pho. <fader>
{'channel': 'ubuntu-testing', 'month': 6}