/srv/irclogs.ubuntu.com/2009/02/24/#ubuntu-testing.txt

macohey guys, while you're running those jaunty live cds, can you follow the directions on https://wiki.ubuntu.com/Audio/AlsaInfoOutput ?01:05
benoxofthi everyone, i'm trying to install ubuntu netbook remix 9.04 but ubiquity does not see my hard drive03:04
benoxoftdoes anyone can help me?03:05
benoxoftubuntu detect it and mount it correctly but the partitionner does not show anything03:14
cjwatsonthat could well just be an installer semi-crash03:20
cjwatsonfile a bug and post /var/log/syslog, /var/log/partman, and /var/log/installer/debug03:20
benoxoftok i'll check that03:23
benoxoftthanks03:24
cjwatsonI just uploaded ubiquity 1.11.13, including some fixes from a colleague that might address this03:28
benoxoftis there is a way to test it now?03:30
benoxoftif i can download it, i can tell you if it works for me03:31
benoxofti installed ubiquity from the trunk and it did not work :<04:00
aragood morning everybody!07:31
davmor2ara: so how did the first testing day go other than unr and lvm not working ?08:37
aradavmor2: hehehehe08:38
aradavmor2: it went ok. kirkland was very responsive for his screen-profiles bugs08:38
aradavmor2: he fixed (and released) some08:38
aradavmor2: I was happy to see new people coming over08:39
aradavmor2: the lvm bug was also fixed, wasn't it?08:39
davmor2ara: I don't know if it was the big bug which mean that it won't boot but the bad numbering should be now08:40
aradavmor2: cool08:40
aradavmor2: thanks for testing that :)08:40
davmor2ara: did you have an issue with the wording in screen for changing from light to dark ?08:41
arawording?08:41
arawhat do you mean?08:41
davmor2let me get the screen up08:46
davmor2ara: right run screen then run select-screen-profile change to another one and it says 'Run "screen" to activate'  if you follow those instructions it does nothing.  You need to shutdown the terminal your in then open a new one then run screen for it to take effect08:52
aradavmor2: are you running the latest? today there was an update08:53
davmor2I'll try it in tty08:53
davmor2no that is from yesterday I'll try it in a second08:53
davmor2ara: Yay that's better :)09:03
davmor2see I knew it was just the wording :)09:03
aradavmor2: :)09:03
davmor2davmor21: hello evil twin09:05
=== mvo__ is now known as mvo
davmor2davmor21: moo ping and other things09:08
davmor2Bar humbug no notifyosd09:09
davmor2So notifyosd only works with chat and not irc.  So in order to test you just need 2 machines and bonjour setup09:36
davmor2bdmurray: When your up working on vfat install now10:10
=== mvo__ is now known as mvo
davmor2D'oh forgot windows fat can't handle drives over 32 GB10:50
* ara -> lunch12:37
aradavmor2: ping13:30
=== Panattan is now known as Kilin
=== Kilin is now known as kyrin
=== kyrin is now known as kylin
=== kylin is now known as kilin
rmcbrideAh, the updated ubiquity now gets past the whole partition setup and into the installation phase :) vast improvement over yesterday.13:59
ara\o/14:01
davmor2ara: pong14:06
rmcbrideeek! ubiquity blew up at ~90% install. getting apport stuffs now.14:19
rmcbridemeh. It won't complete collection because apparently grub is out of date now.14:20
davmor2cjwatson: ^14:24
cjwatsonrmcbride: could I get a syslog?14:25
davmor2rmcbride: get the logs together for cjwatson14:25
rmcbrideI just did dist-upgrade to put the newer grub into place. I'll get the logs together as well14:25
davmor2cjwatson: I'm about to start a bunch of tests too14:27
davmor2I'll see if I can confirm14:27
rmcbridecjwatson: syslog is at https://pastebin.canonical.com/1416114:29
cjwatsonok, though I'd recommend using paste.ubuntu.com in future where it doesn't need to be private14:30
cjwatsonok, that's the bug evand just fixed in bzr14:30
rmcbridecjwatson: didn't know about that one. thanks.14:30
rmcbrideOK cool14:30
cjwatsonrmcbride: delete the seds of $adjtimefile in /usr/lib/ubiquity/clock-setup/finish-install if you want to get past it14:31
rmcbridecjwatson: will do, thanks14:31
rmcbrideArgh. Installation completes but on reboot, grub throws error 22... if this is the same thing I ran into when I last built this machine I think it's because grub gets confused as to the partition numbers when being installed from USB stick in some cases. I should be able to boot off the live cd and re-edumacate the grub install... cjwatson there any useful info I could gather that would help fix this case? It seems to happen on15:15
rmcbridenetbooks with a 20 (really 4 + 16) GiB SSDs like the eee 90015:15
cjwatsonI doubt that the size is relevant15:16
cjwatson22 : No such partition15:17
cjwatson     This error is returned if a partition is requested in the device15:17
cjwatson     part of a device- or full file name which isn't on the selected15:17
cjwatson     disk.15:17
cjwatsonrmcbride: /etc/fstab /boot/grub/menu.lst and 'sudo vol_id -u' of the devices backing your / and /boot (if distinct) would be a start15:17
cjwatsonrmcbride: however to some extent this is a known general issue15:17
apwsc15:19
davmor2bdmurray: you about yet dude?15:20
apwschwuk, cr3, just pushed up an update to suspend_test for checkbox, proposed for merging: https://code.launchpad.net/~apw/checkbox/suspend-resume/+merge/390215:20
rmcbridecjwatson: OK I'll get those. WHat seems to be happening is that the device IDs are different when the USB drive is no longer present. I don't think it has so much to do with size as the fact that there are two SSDs on the system,15:20
cr3apw: cheers!15:20
rmcbrideor at least the way grub sees things15:21
cjwatsonrmcbride: right, at the moment there is unfortunately no good fix15:21
cr3apw: for which ubuntu releases might this script work?15:21
schwukapw: Excellent.15:22
cjwatsonrmcbride: grub has to locate its stage2 from its 446-byte stage1, and there isn't enough room in there to do proper dynamic detection, so it depends on what the Linux device <-> BIOS device mapping looked like during installtion15:22
cjwatsonrmcbride: I think we may, reluctantly, have to have some manual UI hack in ubiquity15:22
rmcbridecjwatson: ah. crap. Yea it's sounding like it.15:22
cjwatsonrmcbride: futzing with /boot/grub/device.map and rerunning grub-install is probably a viable workaround (and is what the implementation will have to look like)15:23
rmcbridecjwatson: yea that's what I had to do with my intrepid/unr alt install last time I installed on this hardware.15:24
cr3apw: would you mind if I report a bug so that the script doesn't depend on being run with sudo, and that it could instead be run as root?15:24
schwukapw: I've added you to the checkbox-dev group, so you can commit your changes directly.15:24
apwcr3, not at all ... that would preclude use of the dbus test15:24
apwbut in V6 that test is a separate 'category' so that would work15:24
apwcr3, got a use case?15:24
apw(purley curious)15:25
cr3apw: for interactive use within checkbox. if you have a command line script requiring to be run with sudo and which prompts for a password in the background, that breaks the flow of the application15:26
apwcr3, i am going to have to hack the script about to interface it to checkbox anyhow15:27
cr3apw: patch approved and merged with trunk15:27
apwand am planning on doing that bit next15:27
apwcr3, ta15:27
apwcr3, so explain to me, when running tests whome are we running as by default?15:27
cr3apw: if you interface it to checkbox, you could add "user: root" when defining your test15:27
cr3apw: by default, as the user running checkbox. however, this can be overridden with the "user:" option15:28
apwand how does it become root there15:28
cr3apw: through dbus15:28
apwie can i tell who the orignal user is?15:28
cr3apw: good use case! no, you can't tell who the original user is15:28
apwhmmm ... one of the tests at least needs to know that15:29
apwdo i have it as a variable in theere anywhere, as there is no trust issue15:29
cr3apw: I'll have to look at the script more closely but it would be nice to run it on server as well, as long as it's automated, which doesn't have dbus installed by default though15:29
apwyep, that test can and is disabled for server15:30
cr3apw: honnestly, I don't have an answer for you at this time, I'll have to think about it15:30
apwand we can simply ommit it for that one15:30
apwbut even if we only had $user as an option in the command strings to run that would15:30
cr3apw: I can appreciate your use case though, checkbox should be able to support knowing the user15:30
apwbe sufficient for this use case, right now i just use SUDO_USER cause i can15:30
apwcan i sub in environement variables?15:31
cr3apw: the problem is that when commands are run as root, a request is made to dbus telling it to run a test by name, not by command15:31
apwshame15:31
apwwell ... i'll let you think about that one15:31
apwthats one of a larger number of tests15:31
cr3apw: well, that's how it can remain secure, I wouldn't want to be able to send arbitrary commands to run as root by dbus :)15:32
apwand i can simply make that a manual test15:32
apwie say "press suspend dummy"15:32
cr3apw: when do you intend to work on the integration, I'd like to have a workaround ready for you before then15:32
apwcr3, soon ish15:32
apwbut it won't hold me up.  it might make more sense to do that test15:33
apwmanually now i think about it15:33
apwas the test is inherantly trying to test the end-to-end experience15:33
cr3I know I can pull some rabbit out of my... hat. I'd just like to make sure it materializes as a rabbit rather than a gerbil15:33
apwasking the user to hit suspend isn't such a bad idea15:33
cr3in case I'm not making sense, I'd like to find an acceptable solution rather than a hack15:33
cr3where acceptable == rabbit, hack == gerbil :)15:33
apwits actually a better test.  so for now i'd not worry about it, at least in the sense that it isn't a blocker for the work i want to do on the thing15:33
cr3apw: ok, so instead of reporting a bug against the suspend_test script, I'll report one against checkbox itself :)15:34
apwgood enough :)15:34
apwcr3, remind me, was there a reboot capable test yet?15:35
cr3apw: nope15:37
aracr3: ping15:38
apwon your plan list add coping with machine crashing as part of the test15:38
apwie. continuing after a reboot and sayign "that didn't work did it"15:38
cr3apw: reported bug #333884 and subscribed you15:39
ubot4Launchpad bug 333884 in checkbox "Some tests should be run as root but know the original user" [Undecided,New] https://launchpad.net/bugs/33388415:39
cr3ara: pong15:40
apwcr3 sounds good15:40
aracr3: is the checkbox ppa version newer than the one in jaunty?15:40
cr3apw: hm, other people have expressed interest in that usability issue where checkbox should continue from where it stopped in case of crash15:40
cr3ara: yep15:41
apwgiven suspend-resume is pants and blows up a lot15:41
apwand indeed there is only right now any point in 'did that work == YES' else they arn't there to hit it15:41
aracr3: then versioning is wrong15:41
aracr3: apt-get thinks jaunty one is newer15:41
aracr3: https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPAQuickStart#Versioning15:41
aracr3: to install the ppa i would need to uninstall checkbox and then install the ppa manually15:42
cr3schwuk: ^^^15:43
apwcr3, when i run checkbox-gtk it just whines that i need to be an adminstrator15:45
apwthats hopeless for a pleb to understand15:45
cr3apw: yeah, the version with policykit support has been in the core-dev queue since FF15:46
bdmurraydavmor2: I am!15:46
apwcr3, and it just crashed my X-server into the bargain.  top marks15:47
cr3apw: woohoo, it failed testing!15:47
cr3apw: seriously though, what test were you running which crashed X?15:47
apwnone, i was skipping them all, i ran exactly none15:48
apwi _think_ it was about to ask me about my wavelan prism2.5, but its gotten much further this time15:48
cr3apw: can you reproduce the problem consistently?15:48
apwso i can't be sure15:48
apwnot so far15:48
davmor2bdmurray: Yay. Right I've had a quick look at jaunty and umenu/wubi is still borked should be uploading shortly.  So I'm going to rub wubi from intrepid on a fat32 xp install is that alright for you?15:48
davmor2/s/rub/run15:48
bdmurraydavmor2: sure, that'd be great.  the bug is about kernel upgrading after the install15:48
apwcr3, can i tell it which suite to run ?15:49
cr3apw: the only thing that comes to mind is that one of the tests needs to run xrandr in order to display the question15:49
cr3apw: which suite: yes. which test specifically: no.15:49
apwyeah i want to say just my resume suite.  whats the option?15:50
apwthis manual page sucks15:50
cr3apw: for i in `seq 1 20`; do xrandr -q; done # does that reproduce the problem?15:50
cr3apw: --config=checkbox/plugins/suites_info/whitelist=name_of_suite_file.txt15:51
apwnope to the xrandr reproduce, and the test was that resolution test15:52
cr3apw: yeah, the resolution test simply runs xrandr to determine the resolution15:52
apwwell unless it happens again i'll put it down to an X update happening recentlly15:53
schwukara: The version in the PPA (0.5~ppa5) is the same as the one proposed for Jaunty (0.6).15:53
araschwuk: yes, but in jaunty now it is version 0.515:54
araschwuk: so if you try to install the ppa over 0.5, it should be possible, but it is not15:54
apwcr3, at the recent sprint we were introduced to checkbox and had some feedback on it15:54
schwukara: hmm15:54
apwlike on how you get the question before you have run the test15:54
araschwuk: https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPAQuickStart#Versioning15:54
apwis there now a way i should be encoding things to get that to happen right?15:55
apwor is that still in the works?15:55
apw(t15:55
cr3schwuk: dpkg --compare-versions 0.5~ppa5 gt 0.5 && echo "true" || echo "false"15:55
apw(this is for tests with a TEST button)15:55
apwfor sure, a ~NNN is before the thing its attached to15:56
cr3apw: man, did I make that introduction to checkbox? I remember making a presentation but only emmet was there :)15:56
apwheh no it was someone else, but i assume yo heard about all my pitiful whining15:56
schwukcr3: No, I did it, and yes I passed along some of the pitiful whining :)15:57
cr3apw: nope, I wish I did though. I love to hear whining, I actually do wdd (whining driven development)15:57
schwukara: We'll get that sorted out asap15:57
cr3schwuk: cool, my memory must be failing me once again15:57
apwso one thing was the fact that you get the question and answer bits before you have hit test which makes no sense15:58
araschwuk: cool, thanks15:58
cr3apw: by default, you get the question before running the test. isn't that what you're observing?15:58
apwand i wondered if that was jst cause i wasn't doing the definition of the test right15:58
apwyeah it says like "Hit test to suspend"  Did you resume sucessully?15:58
cr3apw: sure that makes sense. what if the test powers off your machine, that's quite a startling user experience.15:58
apwyep you need the first half the text, so in this case15:59
apw"Click on the test button to initiate a suspend.  Once the machine has gone to sleep, wake it up again"15:59
apwi'd like that to be there, then i hit test and i'd like the queston to appear either additionally or only in the box after the script completes16:00
apwkinda two phase16:00
apwcr3, anyhow, the short answer is, i am doing it right at the moment i think16:00
cr3apw: how about this: Hit the test button to suspend your machine which should power on automatically. Did your machine power on after a few seconds?16:00
apwwell thats kinda what it says already16:01
cr3apw: I'm not sure I follow your flow here: i'd like the queston to appear either additionally or only in the box after the script completes16:02
apwthe "did the machine resume?" and the yes/no/skip options are not valid until the Test button was pressed, well skip and only skip is16:03
apwthere are two things in the text presented.  the instructions "Do this/Hit TEST" and the question "Did you hear a beep?"16:04
apwand they are kinda separate16:04
apwone way to represent that might be to add the question and enable Y/N only after TEST has been hit say16:04
cr3apw: I'm reluctant to disable yes/no if the test button has not been pressed16:04
apwwell how can they answer if test has not been hit?16:05
cr3apw: because if I know the suspend works, I don't want to have to wait to test it again16:05
apwthey blatently can't knw the answer16:05
apwhmmm ...16:05
cr3apw: I might be suspending every day in the first place16:05
apwnow you are letting the user guess what my test does16:05
apwi may be suspending using some other mechanism, how would they know that16:05
apwan indeed i do do that, i suspend using dbus and also using pm-suspend16:05
apw"on suspend works, so this 100 suspend cycle test is clearly yes"16:06
apwis not a very safe option to put in a users hands IMO16:06
apwcr3 i am not at alll picky, honest16:07
cr3apw: this is an accuracy concern though, but duly noted16:08
apwright, testing is 100% useless if you don't know its veracity16:08
apwit is worse than no information at all16:08
apwdo we at least record that they didn't hit Test,  that is the politic middle ground16:09
apwcr3 what order do my tests in my suite run in?16:13
davmor2bdmurray: Right wubi installed I'll start the updates now16:15
bdmurraydavmor2: okay, if all goes well you shouldn't land at the lp bug filing page16:19
davmor2:)16:19
arastgraber: ping16:22
davmor2bdmurray: Meh Report A Problem Sorry, the package "linux-image-2.6.27-7-generic 2.6.27-7.16" failed to install or upgrade  I'm guessing this is what was already reported or do you need me to upload the apport report?16:24
apwcr3, got any suite fragments for non-manual tests?16:26
apwwhich plugin should i be using16:26
bdmurraydavmor2: try and upload it and see what happens16:26
cr3apw: plugin: shell16:29
davmor2bdmurray: Hmm there are a few bugs listed for it16:29
apwcr3, so there is no feedback at all on shell test16:30
bdmurraydavmor2: so it didn't say this problem has already been reported and show you bug 252900?16:30
ubot4Launchpad bug 252900 in wubi "vfat : wubi 8.04.1-rev506 kernel upgrade fails" [Medium,Confirmed] https://launchpad.net/bugs/25290016:30
apwis there a way to initiate a test which shows someone something, but requires no interaction16:30
apwi would like to tell them how far through they are and the like16:30
davmor2bdmurray: top of the list16:30
cr3apw: by default, the exit code of the given command determines whether the test passed (0) or failed (!0)16:31
davmor2bdmurray: next is 332476 and 332837 which look identical16:31
apwyeah but say there are two tests, a variable timing test and a repeated iteration test16:32
cr3apw: the shell tests are all run after the manual tests and a progress bar is displayed during that time16:32
bdmurraydavmor2: okay, apport should have caught it before letting you get that far16:32
apwi would like the box on the screen to show 'variable test pass 10' or something16:32
cr3apw: is the purpose to be able to identify which pass number failed, if that happens?16:33
davmor2bdmurray: I got the login page, next I got the summary description, then I got the bug list16:33
apwthe purpose is that the test is going to take 30 minutes and 30 mins of cylon isn't going to help them16:34
apwso i'd like it to have the normal box without the pass/fail on the bottom16:34
apwwith something helpful in it16:34
apweven if i have to do each pass as a separate test, if i had a non-interactive normal test like window16:34
cr3apw: my god man! 30 minutes just for suspend/resume?16:35
apwthen it could 'flick' from test to test16:35
apwcr3, heh, we do 24hour suspend resume tests on some h/w16:35
cr3apw: actually, a 30 minute test would be fine if it's interactive and the user can optionally skip it16:36
davmor2bdmurray: http://www.davmor2.co.uk/lp.png is the page I'm on if you want I can continue16:36
apwcr3, well right16:36
bdmurraydavmor2: is this something you could test later after I sort out my apport bit16:36
davmor2bdmurray: Yes no probs16:36
apwso i guess i have to do it as an interactive test, even thought its not16:36
apwand even then i don't have any feedback16:37
apwthats pretty poor16:37
cr3apw: well, what does the test do exactly? repeatedly suspend/resume the machine?16:37
davmor2bdmurray: I'll just wipe the wubi install and drop a base install back on so it's ready16:38
bdmurraydavmor2: if you were to perform the upgrade again right now you'd get the same error16:38
bdmurrayat least I think so16:38
apwcr3, yep in one it does it a lot of times, the other it does it with varying times awake16:39
bdmurraySo leaving as it is should be fine16:39
apwas that tickles bugs often16:39
cr3apw: if your concern is the poor user experience of showing a progress bar for 30 minutes, that could be solved16:39
apwso i guess i would be happy making the whole thing a single interactive test which said16:39
apw"this takes a damn long time"16:39
apwbut some feedback would be nice16:39
cr3apw: it could be non-interactive, because it's not really interactive as you said16:39
davmor2bdmurray: I want to make a back up of the windows install anyway so no issue there16:39
apwcr3, though as you say that is one people might want to skip16:40
cr3apw: I'm reluctant to have each test provide their own custom mechanism for providing feedback. so, how about this...16:40
apwso at least offering a skip is pretty important16:40
davmor2and I want the broken wubi install off before I do that :)16:40
apwcr3, right i don't want to do feedback in my code thanks :)16:40
cr3apw: what would you think if tests define a timeout and a reasonably high default. then, instead of showing a progress bar, I could show the maximum amount of time remaining which would slowly decrease as automated tests are completed.16:41
apwcr3, thats just bound to get it wrong and annoy people16:41
apwhow about a standard reporting form16:41
cr3apw: it's an upper bound though, which would never go over16:41
apwcommand_with_output: <command>16:41
cr3apw: it's annoying to people when the upper bound is not respected :)16:42
apwand that would display the stdout of the command in like an xterm style box16:42
apwthen we could display our current position in there16:42
cr3apw: ooo! that reminds me of the xterm box in gdebbi or somesuch16:42
cr3apw: very cool idea, I like it16:43
apwwell i'd hope you would put the panel in the same spot the test queston goes16:43
apwso that would just scroll up, but dunno how hard that is16:43
apwi presume i can fake it up for now with just an xterm16:43
cr3apw: the same spot would show the output of each of the automated tests being run, right?16:43
apwyeah16:44
apwwhile you think on that, i am going to cheat and use an xterm :)16:44
cr3apw: thanks, I'll report another bug for that because I really don't want to forget this one16:44
apwenjoy :)16:44
apwyou are going to come to hate working with me :)16:45
cr3apw: as long as you have reasonable requests, I might react quite the opposite and enjoy working with you very much16:47
apwcr3, heres hoping16:49
apwcr3, so is there a way to not run a test cause one previous didn't work or was skipped16:49
apwlike it makes sence to do a single automated sleep/resume cycle.  if that suceeds then its worth doing lots of repeats of it, else its madness16:50
=== fader_ is now known as fader
cr3apw: absolutely, depends: test_name17:07
cr3apw: are there specific requirements for running the tests by any chance, such as some kernel flag or some swap space or somesuch?17:08
davmor2bdmurray: Right off for tea but I'll be back latter and I'll give it a retry for you then17:09
cr3apw: in case you need more swap space than memory, you could also add, requires: swaptotal > memtotal17:10
=== fader is now known as fader|lunch
davmor2bdmurray: Right I'm back18:45
bdmurraydavmor2: thanks, it'll be a while before my bit is squared away18:45
davmor2sbeattie: ping19:15
sbeattiedavmor2: what's up?19:20
davmor2are you the controler for dl-ubuntu-test-iso?19:20
sbeattieI prefer to think of it as Chief Bug Producer, but yes.19:21
davmor2jeos and gobuntu aren't in anymore and is there away to get the mobile .imgs tied in?19:23
sbeattiedavmor2: jeos and gobuntu (and kubuntu-kde4) should be disabled by tip now (unless, ahem, I've produced another bug), though if you still have them in your config, it'll still try to pull them,19:26
sbeattieI'll peek at mobile imgs19:27
davmor2sbeattie: Sorry I was looking at base and not main19:27
=== fader|lunch is now known as fader
davmor2Right I'm off till tomorrow :)22:07

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