QA/Meetings/20090429

From FedoraProject

Jump to: navigation, search

Contents

Attendees

  • Will Woods (wwoods)
  • Adam Williamson (adamw)
  • James Laska (jlaska)

Previous meeting follow-up

Autoqa update

  • wwoods noted there have been no updates since last week
  • jlaska said that Jon Stanley enabled the TRAC instance on http://autoqa.fedorahosted.org and will begin adding tasks for the issues discussed during last autoqa meeting w/ jkeating and wwoods
  • jlaska+wwoods confirmed that things were on track for enabling automated test results sent to autoqa-results by F-11-GA

F-11-GA Prep

jlaska expressed interest in trying to identify a more specific date QA can plan for a hand-off from releng. The current schedule has a big window for "prepare and test" from 2009-05-12 to 2009-05-21. Wwoods noted that it depends on what the blocker list looks like, there's no reason to build a RC if there are known blocker bugs. Jlaska agreed, but noted it's difficult to plan QA time for testing the RC without specifics.

There was discussion around the F11Blocker bug and several strategies for reviewing the ~76 blocker bugs in the next 2 weeks. Consensus was to divide up the bugs by component groups, which is currently what adamw has been doing for xorg-x11 bugs. The agreed components to review were:

  • SELinux - wwoods
  • pulseaudio driver issues - wwoods
  • installer - jlaska
  • xorg-x11 - adamw
  • Volume control - adamw

Call for Virtualization test cases

jlaska noted that the upcoming Virtualization test day needs volunteers to help define test cases for the test areas already specified. Adamw recommended putting a call out to fedora-test-list for volunteers.

Open discussion

Failing disk icon

Seems to be a commonly reported issue on fedora-test-list (see https://www.redhat.com/archives/fedora-test-list/2009-April/msg01593.html)

Updated preupgrade package

  • wwoods announced a new version of preupgrade
new version (1.1.0), some new code, lots of bugfixes
it now attempts to enable new versions of every [enabled] repo on your system
so you should get upgrades with updates + rpmfusion 
switched from bzr to git

Yum upgrades between Fedora releases

Adamw noted a https://bugzilla.redhat.com/show_bug.cgi?id=494046 which breaks yum upgrade from f10 to f11 within a gnome terminal. The bug is currently on the F11Target bug list.

wwoods discussed this issue with skvidal and indicated skvidal plans to get that bug onto the common bugs page. Wwoods will also be the lucky recipient of any future yum upgrade bugs.

jlaska asked if upgrading to a new fedora release was a documented upgrade path. According to the installation guide (http://docs.fedoraproject.org/install-guide/f10/en_US/sn-upgrade-tree.html) it is not. Jlaska also asked if it was worth adding a section about "Upgrading using yum" that would include a strong message advising against it. Wwoods felt this should be kept as an undocumented behavior.

Upcoming QA events

Action items

  • [jlaska] - transfer autoqa tasks into TRAC instance with milestones
  • [wwoods] - checking for a bug about an upgrade issue
  • [jlaska] - ensure the failing disk drive issue is tracked in bugzilla and get a Release note documented for running smartctl

F11Blocker bug review

  • [wwoods] - review SELinux bugs
  • [jlaska] - review anaconda bugs
  • [adamw] - continue review of X11 bugs and volume control issues


IRC Transcript

* | wwoods afk 1min Apr 29 12:01
--- | jlaska has changed the topic to: Fedora QA Meeting | gathering Apr 29 12:01
jlaska | show of $appendage for those in attendance Apr 29 12:02
* | wwoods waggles an elbow Apr 29 12:02
* | jlaska will need to learn that trick Apr 29 12:03
jlaska | adamw: around? Apr 29 12:04
adamw | ypupers Apr 29 12:04
adamw | just busy with some hockey trash talk Apr 29 12:04
adamw | :P Apr 29 12:04
jlaska | :) Apr 29 12:05
jlaska | okay, anyone else joining for teh QA meeting, say 'hi' for the logs Apr 29 12:05
--- | jlaska has changed the topic to: Fedora QA Meeting | agenda (https://www.redhat.com/archives/fedora-test-list/2009-April/msg01699.html) Apr 29 12:06
jlaska | okay, posted the agenda ... but would like to sprinkle the previous meeting follow up with some current events folks have been following Apr 29 12:06
jlaska | agenda - https://www.redhat.com/archives/fedora-test-list/2009-April/msg01699.html Apr 29 12:06
jlaska | minutes will be posted to - https://fedoraproject.org/wiki/QA/Meetings/20090429 Apr 29 12:06
--- | jlaska has changed the topic to: Fedora QA Meeting | previous meeting follow-up Apr 29 12:07
jlaska | adamw: I've got you down for the only action item I recorded from last weeks transcript Apr 29 12:07
--- | mbonnet_ is now known as mbonnet Apr 29 12:07
jlaska | [adamw] - post to fedora forums asking for feedback on pulseaudio issues Apr 29 12:07
jlaska | I think you've knocked this out of the park (and then some) Apr 29 12:07
adamw | oh, that's kinda separate from the mixer crap Apr 29 12:08
jlaska | or another analogy ... scored 2 goals in the final 2 minutes of the 3rd period of game 7 Apr 29 12:08
adamw | THIS would be: http://forums.fedoraforum.org/showthread.php?t=220343 Apr 29 12:08
adamw | wow, you'd almost think that analogy came from somewhere specific! :) Apr 29 12:08
jlaska | ;) Apr 29 12:08
adamw | that's the thread asking for pulse feedback - it's actually remarkably positive, no major issues Apr 29 12:08
adamw | so that's good news Apr 29 12:09
jlaska | interesting Apr 29 12:09
jlaska | yes definitely! Apr 29 12:09
adamw | not a lot of people took part in the thread, but that's quite normal - most don't bother to report success Apr 29 12:09
adamw | so the fact there's not a bunch of people complaining is a positive sign Apr 29 12:09
wwoods | yeah, I think those intel-8x0/intel-hda issues are about 95% squashed, with some mutant hardware remaining Apr 29 12:10
jlaska | staying on a similar topic, but moving into the "recent events" category ... Apr 29 12:10
jlaska | does this tie into the audio tracker bug? Apr 29 12:10
wwoods | still working with jaroslav on intel8x0 and we've got a reporter who's still getting weirdness with -hda, but his hardware has other problems too, so.. everything seems mostly better Apr 29 12:10
adamw | jlaska: AlsaVolume? not really Apr 29 12:11
adamw | AlsaVolume is for a very particular type of bug related to the Great Mixer Debate Apr 29 12:11
jlaska | heh, well titled Apr 29 12:11
jlaska | wwoods: anything else on the intel8x0 front that needs chasing down? Apr 29 12:12
adamw | if you have a card where maxing out all the volumes in gnome-volume-control still doesn't get you audio at a decent level, but dropping to alsamixer or something and adjusting a mixer element there solves the problem - that's an AlsaVolume bug Apr 29 12:12
adamw | anything else, no. Apr 29 12:12
jlaska | gotcha Apr 29 12:12
wwoods | jlaska: still working on some corner cases, but I had two test machines - one died, and the laptop HD appears to be failing Apr 29 12:12
wwoods | so I may hit a wall on this Apr 29 12:13
adamw | well, you can replace laptop hard disks usually.. Apr 29 12:13
wwoods | although the laptop HD might turn out to be a bug in the new SMART monitoring stuff Apr 29 12:13
* | jlaska makes a topic note "failing drive applet" Apr 29 12:14
--- | mbonnet is now known as mbonnet_ Apr 29 12:15
jlaska | any other follow-up from last week? Apr 29 12:15
wwoods | I'm definitely not the only one seeing that applet pop up and then noticing some ridiculous failure values - but I don't want to sidetrack things here. just a note that we need to investigate that further. Apr 29 12:15
jlaska | wwoods: yeah you're not ... I've seen it too Apr 29 12:15
jlaska | wwoods: I'm going to add that as an open-discussion topic, just to make sure someone is looking at it Apr 29 12:16
jlaska | okay, going to quick run through the agenda and we can come back to this Apr 29 12:17
--- | jlaska has changed the topic to: Fedora QA Meeting | autoqa update Apr 29 12:17
jlaska | wwoods: jds2001 enabled the trac space on the autoqa hosted site today (thanks jds2001!) Apr 29 12:17
jlaska | I've stubbed out a real *basic* start page ... https://fedorahosted.org/autoqa/ Apr 29 12:18
wwoods | I haven't touched the code since last meeting, sadly Apr 29 12:18
jlaska | I'd like to begin getting tickets in and creating milestones for the issues you, f13 and I outlined last week Apr 29 12:18
wwoods | definitely Apr 29 12:18
jlaska | we're sooooo close to getting automated mails sent to the results list Apr 29 12:19
wwoods | the TODO in the source tree is a good starting point, but you'll probably need my help in decoding those to useful tickets Apr 29 12:19
jlaska | wwoods: okay, I'll get a basic milestone targetting completion before F-11-GA ... and start adding in what we discusse Apr 29 12:19
jlaska | wwoods: you can definitely add in specific tasks/bugs too Apr 29 12:20
wwoods | right Apr 29 12:20
jlaska | the tasks we outlined seemed achievable for F-11-GA ... but if I'm aiming too aggressive, feel free to say so Apr 29 12:21
jlaska | since you've got the code know-how Apr 29 12:21
wwoods | remind me of what tasks those were? Apr 29 12:21
jlaska | > Next steps: Apr 29 12:22
jlaska | * [wwoods+jkeating] - update tests to consolidate mails (autoqa and watcher-* changes needed) Apr 29 12:22
jlaska | * [jkeating] - setup cronjob for checking out autoqa.git Apr 29 12:22
jlaska | * [jkeating] - setup cronjob for running 'watcher-*' scripts Apr 29 12:22
jlaska | * [jlaska] - update mailing list to accept mail from $USER Apr 29 12:22
jlaska | > create puppet managed local user Apr 29 12:22
jlaska | * [wwoods] - send patches to beaker-devel@ for rhtslib changes Apr 29 12:22
jlaska | Apr 29 12:22
jlaska | so for the cronjob parts, we may need to beg f13 for some cycles (which I gather the F-11-Preview sucked up) Apr 29 12:23
jlaska | but having them in trac will at least make it easier to see what's left/next etc... Apr 29 12:23
wwoods | right Apr 29 12:23
wwoods | yeah that all sounds reasonable Apr 29 12:23
jlaska | okay ... moving on for now ... Apr 29 12:24
wwoods | 2 weeks 'til the first RC Apr 29 12:24
wwoods | all I really have from now 'til then is autoqa and preupgrade Apr 29 12:24
--- | jlaska has changed the topic to: Fedora QA Meeting | F-11-GA Prep Apr 29 12:24
jlaska | wwoods: what's queued up on the preupgrade front/ Apr 29 12:24
--- | tibbs_ is now known as tibbs|h Apr 29 12:25
wwoods | new version (1.1.0), some new code, lots of bugfixes Apr 29 12:25
wwoods | it now attempts to enable new versions of every repo on your system Apr 29 12:25
wwoods | err, every enabled repo Apr 29 12:25
wwoods | so you should get upgrades with updates + rpmfusion Apr 29 12:25
jlaska | nice! Apr 29 12:26
wwoods | but this will require lots of testing, of course. Apr 29 12:26
wwoods | also we're rejecting /boot on mdraid now, since that never actually made any sense Apr 29 12:26
wwoods | current preupgrade code will require F11 Beta or later (which is fine with me) Apr 29 12:26
wwoods | so you can't preupgrade to F10 anymore Apr 29 12:26
wwoods | at least, not with the 1.1.x code Apr 29 12:27
jlaska | is this outlined on the preupgrade project page? Apr 29 12:27
wwoods | no Apr 29 12:27
wwoods | I'm not really sure where I'd put it Apr 29 12:27
wwoods | I'll put in tickets for TODO items and such when I have some time Apr 29 12:28
jlaska | sounds like a worthwhile update to announce, perhaps blog or a announce to fedora-test-list@ Apr 29 12:28
wwoods | oh, it switched from bzr to git (thanks jds2001) Apr 29 12:28
wwoods | yeah, as soon as I have something worth testing Apr 29 12:28
jlaska | okay ... swinging back to F-11-GA Apr 29 12:29
jlaska | as wwoods said, just about 2 weeks until the schedule has a possible RC tree landing Apr 29 12:29
* | jlaska looking at http://poelstra.fedorapeople.org/schedules/f-11/f-11-releng-tasks.html Apr 29 12:29
jlaska | there's a big window there for "prepare and test" 05-12 - 05-21 Apr 29 12:30
jlaska | I'd like to try and get a more specific date when we can expect a drop ... but that's somethign I'll need to ask for f13 for feedback on Apr 29 12:31
wwoods | that probably depends on the blocker list Apr 29 12:32
wwoods | there's not a lot of point in spending a day building images if you're just going to have to do it again the next day to pull in 5 blocker fixes Apr 29 12:32
wwoods | so that really needs to get cut down to size ASAP Apr 29 12:32
jlaska | yeah I agree Apr 29 12:32
adamw | weren't we going to have a blocker list review meeting? Apr 29 12:33
jlaska | if testing of the RC is needed, we need to reserve time to do it Apr 29 12:33
wwoods | the blocker list stands at 74 bugs right now Apr 29 12:33
wwoods | that's almost too long for a meeting Apr 29 12:33
jlaska | adamw: there are 2 blocker bug review days (2009-05-11 - 2009-05-12) Apr 29 12:33
adamw | some of which are actually other tracker bugs... Apr 29 12:33
adamw | jlaska: ah k Apr 29 12:34
wwoods | yes, 7/74, which still leaves 67 actual proposed blockers Apr 29 12:34
jlaska | adamw: but I'm with wwoods, it's fairly difficult to set aside time to review the list during a 'meeting' Apr 29 12:34
adamw | i mean, it's *more* than 74, not fewer Apr 29 12:34
jlaska | Are there other strategies to divide/conquer the list? Apr 29 12:34
adamw | sure, days is fine Apr 29 12:34
wwoods | round up by topic or sub-blocker - anaconda blicker, Xorg bugs, etc Apr 29 12:35
wwoods | (blicker?) Apr 29 12:35
jlaska | yeah the blocker bug theme has been used out the wazzoo so that might be a good approach Apr 29 12:35
jlaska | certainly let's one target a component set they might be most familiar with Apr 29 12:36
jlaska | a fair amount of MODIFIEDs on that list Apr 29 12:36
jlaska | I don't mind taking the ancaonda blocker list ... it's near and dear for me :) Apr 29 12:37
adamw | i just knocked one off the list, a dupe of the infamous grey-screen live usb bug Apr 29 12:38
jlaska | that's the wrong livecd-creator bug? Apr 29 12:38
jlaska | errr syslinux Apr 29 12:38
adamw | yeah Apr 29 12:38
jlaska | nice Apr 29 12:38
jlaska | okay, so should we plan to reserve those 2 days to walk this list and divide up by component areas? Apr 29 12:38
adamw | works for me Apr 29 12:39
jlaska | should we ping for retesting of the MODIFIEDs now? Apr 29 12:39
adamw | sounds sensible Apr 29 12:39
jlaska | any other ideas/concerns ? Apr 29 12:40
jlaska | what do we do with F11Target? Apr 29 12:40
jlaska | it'd be great to have the bugs listed by F11 Feature Apr 29 12:41
jlaska | I guess that's essentially what the blocker bugs have become Apr 29 12:42
wwoods | F11Target can probably use some triaging. Typically some of the bugs there can be fixed by F11 updates Apr 29 12:42
adamw | what do we do with f11target? not worry about it until f11blocker is doing better :) Apr 29 12:42
wwoods | and some of them will need to be moved to F12Blocker or F12Target Apr 29 12:42
jlaska | wwoods: so Target is just the holding area for things that aren't Blockers? Apr 29 12:42
wwoods | rarely do we move something from Target to Blocker, but I guess it's possible Apr 29 12:42
jlaska | "nice to have" vs "must have" Apr 29 12:42
wwoods | right Apr 29 12:42
jlaska | gotcha Apr 29 12:42
wwoods | "things we really really want fixed by F11". typically it means we'd be willing to break freeze for a fix for that bug Apr 29 12:43
wwoods | but we wouldn't delay the release over it Apr 29 12:43
jlaska | that's Target? Apr 29 12:44
wwoods | yeah Apr 29 12:45
* | jlaska wonders if we dropped 'Target' ... would people notice? Apr 29 12:45
wwoods | Blocker is for things we'd actually delay the release over Apr 29 12:45
jlaska | right, that makes sense Apr 29 12:45
jlaska | so I don't have any real action items out of this, but more just a heads up ... there's rougly 2 weeks until an release candidate tree will be provided by rel-eng Apr 29 12:46
jlaska | I'll take an action item to walk the anaconda bugs on that list Apr 29 12:46
jlaska | wwoods: you've already been monitoring sound issues Apr 29 12:47
wwoods | well, some specific sound issues that cause pulseaudio to crash Apr 29 12:47
jlaska | and adamw, you're pretty well plugged into X11 and the volume bugs Apr 29 12:47
wwoods | adamw is all over the volume control issues Apr 29 12:47
adamw | yeah, we should be good for the volume stuff Apr 29 12:47
adamw | x bugs i am continuing to monitor Apr 29 12:48
jlaska | eggsellent Apr 29 12:48
adamw | i used nouveau as a little test platform for priority/severity - i graded all open nouveau rawhide bugs using those fields Apr 29 12:48
adamw | so if you're interested you can do a search and order by priority or severity to see how that works out Apr 29 12:48
jlaska | awesome Apr 29 12:48
jlaska | did you get any feedback on that? Apr 29 12:48
adamw | intel and radeon i just added appropriate bugs to the blocker Apr 29 12:48
wwoods | I'll keep an eye on any selinux issues if that helps Apr 29 12:49
adamw | i mentioned it to ben, he says it's neat except he got a lot of emails Apr 29 12:49
jlaska | heh :) Apr 29 12:49
adamw | so i need to test if an email gets sent out if i do nothing but change priority/severity (no comments) Apr 29 12:49
jlaska | wwoods: ah good call, thanks (re: selinux) Apr 29 12:49
wwoods | gotta check to see if there's a bug about this upgrade thing Apr 29 12:49
--- | thomasj_ is now known as thomasj Apr 29 12:49
wwoods | should be fixed in policy -23 but that's not in preview Apr 29 12:49
wwoods | so we might get reports like "X stopped working after upgrade to Preview" Apr 29 12:50
adamw | wwoods: btw, skvidal is very pissed about a bug which breaks yum upgrade from f10 to f11 within a gnome terminal Apr 29 12:50
adamw | https://bugzilla.redhat.com/show_bug.cgi?id=494046 Apr 29 12:50
buggbot | Bug 494046: high, high, ---, besfahbo, ASSIGNED, updating fontconfig to rawhide then ANY font package causes gnome-terminal to segfault Apr 29 12:50
wwoods | adamw: yeah, well, you know my policy on yum upgrades Apr 29 12:50
adamw | i set it to blocker target rather than blocker because of your position on yum upgrades Apr 29 12:50
adamw | but he didn't like that Apr 29 12:50
wwoods | still worth fixing, but not a blocker Apr 29 12:50
adamw | just wanted to give a heads-up in case you encounter him on the rampage :) Apr 29 12:50
wwoods | also worth getting onto the f11 common bugs page until such time as we have a fix Apr 29 12:51
jlaska | yeah that's a good candidate for that bz Apr 29 12:51
wwoods | oh we had some words in #fedora-devel earlier. he says he'll get that bug onto the common bugs page and reassign all bugs about this to me Apr 29 12:51
wwoods | which is fine, I'm happy to say "don't do yum upgrades" over and over Apr 29 12:51
jlaska | is this caused by preupgrade? Apr 29 12:51
wwoods | no, it's caused by a yum upgrade Apr 29 12:51
wwoods | you have to be running the yum upgrade in gnome-terminal on a live system Apr 29 12:52
wwoods | and then gnome-terminal will crash and mess up your upgrade Apr 29 12:52
wwoods | certainly worth documenting and trying to fix Apr 29 12:52
wwoods | definitely not going to recommend delaying the release over it Apr 29 12:52
jlaska | do a _majority_ of people yum upgrade between major releases? Apr 29 12:52
jlaska | yeah that's seems very sane ... document the issue Apr 29 12:52
wwoods | I don't think we have any way of answering that question Apr 29 12:52
jlaska | yeah fair point Apr 29 12:53
wwoods | some people do, and it kinda works sometimes, except when things like this happen Apr 29 12:53
jlaska | I've just never had an expectation that it would seemlessly work, so never really try Apr 29 12:53
wwoods | we've explicitly told people that we don't support that method for years Apr 29 12:53
jlaska | but sounds like there are some adventurous folks out there :) Apr 29 12:53
wwoods | it's never seamless but it usually mostly works so people do it Apr 29 12:53
adamw | skvidal's comment on that was "who is we" :) Apr 29 12:53
jlaska | is a recommend path in the installation guide? Apr 29 12:54
wwoods | everyone who works on the installer or upgrade tools - including seth - is on record as saying that yum upgrades are a really bad idea Apr 29 12:54
adamw | good enough for me Apr 29 12:54
wwoods | if it's in the installation guide I'd be very surprised Apr 29 12:54
jlaska | http://docs.fedoraproject.org/install-guide/f10/en_US/sn-upgrade-tree.html Apr 29 12:54
jlaska | afaict ... we only document anaconda upgrades Apr 29 12:55
jlaska | we don't explicitly document *not* doing yum upgrades Apr 29 12:55
jlaska | which we can't really document all the negatives Apr 29 12:55
jlaska | is it worth requesting a blurb in the installation guide about "Upgrading Using yum" Apr 29 12:55
wwoods | it's undocumented, not recommended, and QA/anaconda team policy has been "don't do that" for years and years Apr 29 12:56
jlaska | with lots of cautionary text ... flames ... explosions etc..? Apr 29 12:56
wwoods | hell no Apr 29 12:56
wwoods | it's unofficial and undocumented and it should stay that way Apr 29 12:56
wwoods | unless FESCo and/or the board mandate that this needs to be supported Apr 29 12:57
wwoods | and write packaging policy for making scriptlets do the right thing in this case Apr 29 12:57
jlaska | okay, we'll just keep the URL for the prefered documented upgrade method handy for any daring users :) Apr 29 12:57
jlaska | any other thoughts on the upcoming F-11-GA? Apr 29 12:58
* | jlaska going to change topic ... Apr 29 12:58
wwoods | it's just not a supportable upgrade method. no other operating system allows anything of the sort Apr 29 12:58
wwoods | that way lies madness Apr 29 12:58
jlaska | wwoods: I agree 100% ... was just curious if it would be worth the effort to explicitly state it's a "buyer beware" method Apr 29 12:59
wwoods | every moment spent on making that work instead of improving the usability and reliability of sane upgrade methods Apr 29 12:59
wwoods | is a moment wasted, in my opinion Apr 29 12:59
--- | jlaska has changed the topic to: Fedora QA Meeting | Upcoming events Apr 29 12:59
wwoods | no, in my opinion it should remain an undocumented hack Apr 29 12:59
jlaska | okay Apr 29 13:00
jlaska | okay, didn't want to spend a lot of time on this, more just an FYI with an open question Apr 29 13:00
jlaska | * SSSD - on track - https://fedoraproject.org/wiki/Test_Day:2009-04-30 Apr 29 13:00
jlaska | the SSSD test day for tomorrow is on track ... I'm reposting the live images now with corrected kickstart Apr 29 13:00
jlaska | however ... Apr 29 13:00
jlaska | * Virtualization - needs QA - Apr 29 13:00
jlaska | https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization Apr 29 13:00
jlaska | I'm looking for volunteers to help organize test cases for the Virtualization test day next week Apr 29 13:01
adamw | how do you mean exactly 'organize'? Apr 29 13:01
fhornain | Belgian Guys ? Apr 29 13:02
wwoods | as in "write"? Apr 29 13:02
jlaska | we have a good list of high-level test areas Apr 29 13:02
jlaska | I'm looking for volunteers to help identify some high-level test cases for those test areas on the wiki , or if willing, stub out some test cases Apr 29 13:02
jlaska | doesn't necesarily have to be you guys, just open to ideas on how to solicit help Apr 29 13:03
adamw | is there a virtualization list? Apr 29 13:03
adamw | i know someone writes a virt section for fwn each week Apr 29 13:03
jlaska | there is a fedora-virt list ... and most of those guys are signed up thanks to markmc for organizing that Apr 29 13:03
jlaska | yeah that's markmc Apr 29 13:03
adamw | could ask them for help with the test cases Apr 29 13:03
adamw | otherwise it'd be the good old mail to fedora-test-list Apr 29 13:04
jlaska | yeah, I think that's the next best thing ... just see if anyone is interested in volunteering Apr 29 13:04
jlaska | alright, I'll drop something to the list to see if there are any takers Apr 29 13:05
--- | jlaska has changed the topic to: Fedora QA Meeting | Open Discussion Apr 29 13:05
jlaska | wwoods: do you want to talk about the failing disk icon? Apr 29 13:05
jlaska | Reported on fedora-test-list (see https://www.redhat.com/archives/fedora-test-list/2009-April/msg01593.html) Apr 29 13:05
wwoods | ah - spoleeba was just seeing this in #fedora-devel as well Apr 29 13:06
jlaska | I no longer see the failing disk icon on my system Apr 29 13:06
wwoods | I think there may be cases where we're getting false positives Apr 29 13:06
wwoods | there was a recent fix for (I think) libatasmart that may have fixed some of those Apr 29 13:07
jlaska | aaah Apr 29 13:07
wwoods | but we should investigate the possibility that we're going to get false positives from this new, untested code Apr 29 13:07
wwoods | and freak people out Apr 29 13:07
vincentvdk2 | fhornain: i'm ready Apr 29 13:07
wwoods | so! we need some info on how to check the data when the icon pops up Apr 29 13:07
wwoods | and see if it makes sense Apr 29 13:07
jlaska | christi mentioned some smart commands you can run on #fedora-qa before the meeting Apr 29 13:08
adamw | smartctl --all /dev/sda , i think Apr 29 13:08
wwoods | interesting Apr 29 13:08
jlaska | yeah Apr 29 13:08
wwoods | you can also view it all from palimpset Apr 29 13:08
jlaska | sounds like another candidate to 1) make sure there is a bugzilla for this, 2) get something into CommonBugs ? Apr 29 13:08
wwoods | but we'd want a way to doublecheck in F10/F9 to be sure Apr 29 13:09
wwoods | so smartctl commands would be helpful Apr 29 13:09
fhornain | Ok vincent Apr 29 13:09
fhornain | Did you finish the document ? Apr 29 13:09
jlaska | looks like we're getting some meeting overlap here Apr 29 13:10
wwoods | shall we retire to #fedora-qa? Apr 29 13:10
jlaska | I'll take an action item to chase down some bugs/relnotes for that one ... unless anyone else is jumping for that Apr 29 13:10
jlaska | yeah ... I'm going to reset /topic and we can continue open discussion in #fedora-qa Apr 29 13:10
jlaska | wwoods: adamw thanks for your time! Apr 29 13:11
vincentvdk2 | fhornain: sorry, but i didn't find the time Apr 29 13:11
adamw | alright Apr 29 13:11
vincentvdk2 | but i have some topics that i wrote down Apr 29 13:11
vincentvdk2 | i hope to finish it this evening Apr 29 13:11
--- | jlaska has changed the topic to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Meeting_channel for meeting schedule Apr 29 13:11

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