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

faderYeah, I'd imagine you're probably right.  :)  Still seemed worth filing a bug though.00:00
persiaI don't know if it's related, but r669 of oem-config has the comment "Declare GTK frontend as "NotShowIn=KDE;" rather than00:01
persia"OnlyShowIn=GNOME;XFCE;" (LP: #163518)."00:01
persiabug #16351800:01
ubot4Launchpad bug 163518 in oem-config ".desktop files say OnlyShowIn=GNOME, should be NotShowIn=KDE;" [Wishlist,Fix committed] https://launchpad.net/bugs/16351800:01
faderpersia: 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 system00:03
faderDoes anyone have an OEM Kubuntu install still up?00:04
persiafader, 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.00:06
faderpersia: 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 alternate00:08
faderOr user error, I still haven't ruled out that I munged something :)00:08
persiaIF it worked on the alternate, than it may be that r669 hasn't been pushed into images yet.00:10
persias/alternate/live/00:10
persiaOr there may already be a KDE front-end.00:11
faderOkay, rerunning the OEM install... let's see what happens.00:26
eeejaycr3, hey hey00:37
cr3eeejay: yo ho ho00:37
eeejaycr3: question: how do you edit the glade file?00:37
faderbork bork bork00:37
eeejaycr3: glade-3 effed it up00:37
cr3eeejay: glade-200:37
cr3<!DOCTYPE glade-interface SYSTEM "http://glade.gnome.org/glade-2.0.dtd">00:38
eeejaycr3: for real?00:38
eeejaycr3: ok00:38
cr3eeejay: dude, that file dates back a long time00:38
eeejaycr3: so we could skip glade3 and go straight for gtkbuilder00:38
cr3eeejay: you know, I once considered making it possible for plugins to define their own glade in order to customize the interface00:39
cr3that got postponed because there wasn't that much need for it and I fear it might start making the interface inconsistent00:39
cr3I like the fact the user can predictably know that each manual test will look more or less the same00:40
eeejaycr3, i borked the glade file when i opened it in glade-3, so i started prototyping directly in pygtk00:40
cr3you could also prototype in gimp :)00:40
eeejaycr3: it will also cause a split between cli and gtk00:40
eeejaytrue00:41
cr3eeejay: 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 days00:41
eeejaycr3: yeah, i like that setup too00:42
cr3if we get package testing useful enough for the kde folks, I should ask them for an implementation00:42
faderAllegedly QT Designer can import glade files.00:43
cr3eeejay: I tried to make the show_* methods in the UserInterface class kinda generic, with show_test as the only real exception00:43
faderIt might not be too tough to get a KDE UI00:43
faderHmm, still get the same issue with the alternate kubuntu CD in OEM mode00:47
faderpersia: ^^00:48
=== asac_ is now known as asac
faderOutta here for the night...01:17
* fader waves.01:17
aragood morning all :)06:52
eeejaycr3, morning ho17:32
cr3eeejay: ya man17:32
eeejaycr3, would you be receptive of a checkbox branch that uses gtkbuilder?17:33
cr3eeejay: I'm not very familiar with gtkbuilder, is it like glade but more better?17:34
eeejaycr3, glade is being deprecated17:34
eeejaycr3, next GNOME release is supposed to have zero glade reliance17:35
cr3eeejay: such a branch would be quite welcome then :)17:36
eeejaycr3, excellent, thanks :)17:36
cr3eeejay: but before, I think heno and ara would prefer we land mago integration so that it can start being used17:36
eeejaycr3, it's a 30 minute deal, i spent time converting accerciser a while ago, so i know the tricks17:37
cr3eeejay: gtk-builder-convert and voila? :)17:38
eeejaycr3, a bit code massaging17:38
cr3eeejay: cool, could you push gtkbuilder migration as a branch separate from mago integration?17:38
eeejaycr3, of course17:39
cr3man, I wish I had to be converted so that I could get a massage too :(17:39
* cr3 steps out for grub, the other boot loader17:46
Cut_em2_ithello22:49
Cut_em2_it?22:49
cr3Cut_em2_it: hi there22:50
Cut_em2_iton your testing page, it says that the next test is on March 30, 2009?22:51
cr3Cut_em2_it: oups, which page is that?22:51
cr3Cut_em2_it: sorry, I need to step out for a moment, back in a moment22:51
Cut_em2_ithttps://wiki.ubuntu.com/Testing/UbuntuTestingDay/2009033022:51
Cut_em2_itk22:51
cr3Cut_em2_it: I'll send an email out to a couple people about that page and the parent page23:06
Cut_em2_itok23:09
Cut_em2_itthanks23:09
eeejayhey cr3: more silly questions23:15
eeejaycr3: what are, and how do i use test attachements?23:16
eeejaycr3, it doesn't seem like any plugin uses them23:16
cr3eeejay: attachments: /etc/shadow23:24
cr3or attachments: cat /etc/shadow23:25
cr3it's just a newline separated list of files or commands23:25
eeejaycr3, yeah. i understood that from the code23:25
eeejaycr3, are attachments things that get attached after a test has run?23:25
cr3checkbox-certification/suites/bootchart.txt uses it23:25
* eeejay looks23:26
cr3it gets attached upon reporting. I'm not sure if launchpad supports that concept, I haven't implemented it anyhow23:26
cr3I only use it on the commercial side23:27
eeejayinteresting concept23:27
eeejaycr3, so i think perhaps the mago log should be an attachment23:28
cr3eeejay: my original idea named the parameter "debug" because I thought it would be useful to attach supplementary debugging information to tests23:28
eeejaycr3, the problem being that it is singleton (ie. not associated with a set of results)23:28
eeejaycr3, but with the actual test23:28
eeejaycr3, so consecutive runs would overwrite it23:29
cr3eeejay: that should be fine, as long as it "overwrites" rather than "appends"23:29
cr3eeejay: err, maybe my understanding is premature: if mago will be run multiple times during one checkbox run, then that may pose a problem indeed23:30
eeejaycr3, yeah, but i am afraid a split might occur, between results and mago log23:30
cr3if that's the case, maybe I should reconsider associating attachments with results rather than tests23:30
eeejayzactly23:31
cr3just to make sure we understand each other, it would work if the logs were captured immediately after the test is run, right?23:31
eeejaycr3, what i started doing was making a structure in results.data23:31
eeejayyeah, that would be the idea23:31
cr3I 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 soonish23:32
cr3it sounds like attachments are what you need rather than shoving everything in result.data23:32
eeejaycr3, yeah23:32
eeejaycr3, i would like to have an attachment, and a field for user comments23:33
eeejaycr3, so the comments would stay in data23:33
cr3eeejay: agreed, that's the way it ought to be23:33
eeejaycr3, did you see my gtkbuilder branch? does it kick ass?23:34
* eeejay uses test.attachment in the meantime.23:35
cr3eeejay: I've subscribed you to the bug I created, #38654523:36
cr3eeejay: 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?23:36
eeejaycr3, um kinda23:36
eeejaycr3, we have a mago concept of error23:37
cr3eeejay: I haven't noticed your gtkbuilder branch, have you submitted it for review?23:37
eeejaycr3, when things go horribly wrong in the automation23:37
eeejaycr3, yup23:37
eeejaycr3, anyway I thought of using "skip" with the error message23:37
eeejaycr3, https://code.launchpad.net/~eeejay/checkbox/gtkbuilder/+merge/739123:38
cr3eeejay: hm, that's an interesting use case but I'm not sure I agree23:38
cr3eeejay: but I don't really have a solution though23:39
eeejaycr3, it is not perfect. but that was my plan, re: your question23:39
cr3it seems like we need another status like "the test itself failed"23:39
eeejaycr3, yeah: "error"?23:39
cr3but I'm really afraid to introduce more statuses, I want to keep things freaking simple23:39
* eeejay agrees23:39
cr3I'll have a look at the some posix testing standard if I can find it, maybe it could convince me to have more statuses23:40
cr3eeejay: is there any problems in running the gtkbuilder version on older releases of ubuntu, like dapper or gutsy for example?23:42
eeejaycr3, possibly, yes23:43
cr3eeejay: dapper and gutsy are about to be eol, so we should at least make sure it runs on hardy and we could release soonish23:44
cr3I think dapper is going eol on July 1st, so I'd be comfortable releasing gtkbuilder on that date... assuming hardy works, of course23:45
eeejaycr3, ok23:46
cr3eeejay: your changes look good but I'll need to look deeper into the hypertextview part, it seems hairy23:47
eeejaycr3, yeah, i created a catalog for it23:47
cr3eeejay: I thought we'd dispense with glade altogether23:49
eeejaycr3, dispense?23:49
cr3grep -ri glade * || echo 'no more glade'23:50

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