From Fedora Project Wiki

< QA‎ | Meetings

m (Updated minutes)
m (internal link cleaning)
 
(4 intermediate revisions by one other user not shown)
Line 51: Line 51:
Jlaska asked what expectations people have around testing the release candidate images.  Having all MODIFIED bugs verified and a first pass at testing of the RC media?  F13 indicated having both would be nice, jlaska indicated that 1 to test and verify bugs was insufficient.  F13 pointed out that we may have  a few days based on the feedback for the remaining kernel KMS bug.
Jlaska asked what expectations people have around testing the release candidate images.  Having all MODIFIED bugs verified and a first pass at testing of the RC media?  F13 indicated having both would be nice, jlaska indicated that 1 to test and verify bugs was insufficient.  F13 pointed out that we may have  a few days based on the feedback for the remaining kernel KMS bug.


Discussion followed around the exact nature and cause of {{bz|502077}.  THe result was we need more test feedback against the koji-scratch build.  Jlaska was going to get in contact with Jeff Bastian who has matching hardware to help confirm the fix.
Discussion followed around the exact nature and cause of {{bz|502077}}.  THe result was we need more test feedback against the koji-scratch build.  Jlaska was going to get in contact with Jeff Bastian who has matching hardware to help confirm the fix.


Wwoods indicated a new build of preupgrade would be pushed to stable soon for F9, F10 and F11.
Wwoods indicated a new build of preupgrade would be pushed to stable soon for F9, F10 and F11.
Line 62: Line 62:


* How to request common bug? - [[Common_F11_bugs#My_Bug_Is_Not_Listed]]
* How to request common bug? - [[Common_F11_bugs#My_Bug_Is_Not_Listed]]
The meeting ran out of time to fully review this topic.  After the formal meeting, the team discussed issues they felt needed representation on the [[Common_F11_bugs]] list.  This included {{bz|502077}} and {{bz|495323}}


= Open discussion =
= Open discussion =
Line 67: Line 69:
== How to model RC1 test results wiki ==
== How to model RC1 test results wiki ==


* <code><your topic here></code>
Wwoods asked if the RC test results matrix would be cleared once the RC lands.  Jlaska indicated he wasn't a big fan of clearing the page since it loses history of previous results, but asked for ideas that could retain history but clearly outline the newly tested items.  Some ideas were:
* Just have a "Fedora 11 Final ... " results page
* Rename the current page to RC0, create a new RC1 page
* Clear out the WARN/FAIL results in the current page, await retesting
 
There wasn't a clear winner, the group indicated that having history was important to potentially spot regressions.  Jlaska would likely pull together a draft in the next day and send out to the list for review.


= Upcoming QA events =
= Upcoming QA events =
Line 79: Line 86:
= Action items =
= Action items =


* [wwoods] - update test matrix template with new upgrade test
* [wwoods] - create preupgrade test case and update test matrix template  
* [jlaska] - create new RC1 test results page
* [jlaska] - create new RC1 test results page
* [adamw] - create common bug entry for {{bz|502077}}


= IRC Transcript =
= IRC Transcript =
Line 143: Line 151:
|| [[#tMay 27 12:05:18|May 27 12:05]]  
|| [[#tMay 27 12:05:18|May 27 12:05]]  
|- id="tMay 27 12:05:41"
|- id="tMay 27 12:05:41"
| colspan="2" | --- | jlaska has changed the topic to: Fedora QA Meeting | previous meeting items (https://fedoraproject.org/wiki/QA/Meetings/20090527#Previous_meeting_follow-up)
| colspan="2" | --- | jlaska has changed the topic to: Fedora QA Meeting | previous meeting items ([[QA/Meetings/20090527#Previous_meeting_follow-up)]]
|| [[#tMay 27 12:05:41|May 27 12:05]]
|| [[#tMay 27 12:05:41|May 27 12:05]]
|- id="tMay 27 12:05:59"
|- id="tMay 27 12:05:59"
Line 272: Line 280:
|- id="tMay 27 12:16:09"
|- id="tMay 27 12:16:09"
! style="background-color: #42427e" | wwoods
! style="background-color: #42427e" | wwoods
| style="color: #42427e" | | https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_Encrypted_Root
| style="color: #42427e" | | [[QA:Testcase_Anaconda_Upgrade_Encrypted_Root]]
|| [[#tMay 27 12:16:09|May 27 12:16]]  
|| [[#tMay 27 12:16:09|May 27 12:16]]  
|- id="tMay 27 12:16:27"
|- id="tMay 27 12:16:27"

Latest revision as of 08:57, 18 September 2016

Attendees

  • Adam Williamson (adamw)
  • Will Woods (wwoods)
  • John Poelstra (poelcat)
  • James Laska (jlaska)
  • Jesse Keating (f13)

Previous meeting follow-up

Carry over from previous week:

  1. [adamw] - BugStatusWorkFlow - ask bugzilla guys to add a link from the bugzilla fields description page to the wiki page, for fedora
    • working w/ dkl for other related bugzilla items, will leave on for next week
  2. [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants
    • fail :( - keeping on the list for next week where coordinated surveys will go out
  3. [poelcat] - Check-in on F12 schedule updates
  4. [wwoods] - write a few more upgrade cases (encrypted root upgrade)

New items:

  1. [adamw] - clean up the Common_F11_bugs page to prime contributions from others
    • cleaned up and stubbed out several Xorg related issues
  2. [adamw] - ping fedora docs team for possible collaboration around common bug edits or translation
    • Spoke to docs team about how the common_f11_bugs page is being handled, they were happy about it. Did not get a definite on translation of the page yet, will re-ping
  3. [jlaska] - contribute installer issues to Common_F11_bugs
  4. [fcami+adamw] - contribute X and KMS issues to Common_F11_bugs
  5. [adamw] - contribute alsa/pulseaudio issues to Common_F11_bugs
    • All above topics have representation in the Common_F11_bugs page. adamw and jlaska suggested another sweep of the mailing list to add any common issues.
    • adamw noted he was waiting to hear back from fcami for an updates Radeon list

Autoqa update

F-11-GA Preparation

Jlaska expressed an interest in reviewing where we are in the schedule ... and discussion on any concerns around timing or next steps.

F13 pointed out that there are a ton of MODIFIED things that need to be verified since we got a new kernel, anaconda, mkinitrd, rhpl, policycoreutils. Currently, there are 9 MODIFIED bugs on the F11Blocker list (see http://tinyurl.com/pqeq6n).

Adamw pointed out that RHBZ #502077 was still in ASSIGNED, but has positive test results from a koji scratch build that disables KMS for the i865 VGA adapter.

Jlaska asked what expectations people have around testing the release candidate images. Having all MODIFIED bugs verified and a first pass at testing of the RC media? F13 indicated having both would be nice, jlaska indicated that 1 to test and verify bugs was insufficient. F13 pointed out that we may have a few days based on the feedback for the remaining kernel KMS bug.

Discussion followed around the exact nature and cause of RHBZ #502077. THe result was we need more test feedback against the koji-scratch build. Jlaska was going to get in contact with Jeff Bastian who has matching hardware to help confirm the fix.

Wwoods indicated a new build of preupgrade would be pushed to stable soon for F9, F10 and F11.

Jlaska expressed concern around only having 1 day in the schedule to verify the 9 MODIFIED bugs and revalidate the media. F13 suggested that if all MODIFIED bugs turn out to be fixed (and introduce no regressions), we are in good shape with the testing built up so far. Jlaska suggested that testing would need to continue beyond the 1 day for completeness, but the sync' process could start and the two could work in parallel. But there is risk should high severity non workaround-able issues turn up.

F-11 Common Bugs

Update from User:adamwill on the F11 Common Bugs page.

The meeting ran out of time to fully review this topic. After the formal meeting, the team discussed issues they felt needed representation on the Common_F11_bugs list. This included RHBZ #502077 and RHBZ #495323

Open discussion

How to model RC1 test results wiki

Wwoods asked if the RC test results matrix would be cleared once the RC lands. Jlaska indicated he wasn't a big fan of clearing the page since it loses history of previous results, but asked for ideas that could retain history but clearly outline the newly tested items. Some ideas were:

  • Just have a "Fedora 11 Final ... " results page
  • Rename the current page to RC0, create a new RC1 page
  • Clear out the WARN/FAIL results in the current page, await retesting

There wasn't a clear winner, the group indicated that having history was important to potentially spot regressions. Jlaska would likely pull together a draft in the next day and send out to the list for review.

Upcoming QA events

Next Meeting

  • 2009-06-03 16:00 UTC

Action items

  • [wwoods] - create preupgrade test case and update test matrix template
  • [jlaska] - create new RC1 test results page
  • [adamw] - create common bug entry for RHBZ #502077

IRC Transcript

--- | jlaska has changed the topic to: Fedora QA Meeting | gathering May 27 12:00
--- | danielsm1 is now known as danielsmw May 27 12:01
jlaska | Hey folks, QA meeting about to start ... May 27 12:01
wwoods | huzzah! May 27 12:02
jlaska | wwoods: greetings! May 27 12:02
jlaska | anyone else lurking, speak up for the logs May 27 12:02
BiloxiGeek | Lurk? May 27 12:03
adamw | morning May 27 12:03
jlaska | adamw: howdy May 27 12:03
jlaska | BiloxiGeek: greetings May 27 12:03
jlaska | okay, let's get started ... since some folks may have to drop off for a meeting in an hour May 27 12:04
jlaska | I'm going to quickly run through previous items, and I planned to spend most of our time discussing F11 Common Bugs and prep for the readiness meeting May 27 12:05
* | f13 May 27 12:05
jlaska | but will save time for open discussion May 27 12:05
jlaska | f13: hey there May 27 12:05
--- | jlaska has changed the topic to: Fedora QA Meeting | previous meeting items (QA/Meetings/20090527#Previous_meeting_follow-up) May 27 12:05
jlaska | adamw's first up ... May 27 12:05
jlaska | # [adamw] - BugStatusWorkFlow - ask bugzilla guys to add a link from the bugzilla fields description page to the wiki page, for fedora May 27 12:06
adamw | ...gack. why do I somehow keep missing that? sigh May 27 12:06
adamw | i've been talking to david about other stuff but managed to miss that one May 27 12:06
adamw | leave it on there and bug me next week :) May 27 12:06
* | jlaska actually thought you were talking to dkl about that ... oops, I misread too May 27 12:07
jlaska | okay, will leave on ... that's going to be trend for me too :) May 27 12:07
jlaska | # [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants May 27 12:07
jlaska | I'm keeping this on for me, May 27 12:07
jlaska | but haven't sent the survey out yet May 27 12:07
jlaska | spent too much time trying to get a handle on impact of teh install storage issues May 27 12:08
jlaska | so, will keep for next week and hopefully we'll have 2 surveys go out ... one to the fedora audience, and the same survey tailored for specific partners that engaged in some test days May 27 12:08
jlaska | I have poelcat up next, but I'm not sure if he's around May 27 12:09
jlaska | # [poelcat] - Check-in on F12 schedule updates May 27 12:09
poelcat | jlaska: done :) May 27 12:10
poelcat | http://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html May 27 12:10
poelcat | added some more granularity at the end May 27 12:10
poelcat | contemplating some others that might help too May 27 12:10
f13 | dammit I got disconnected May 27 12:10
jlaska | f13: just rolling through previous weeks items May 27 12:11
jlaska | poelcat: thanks for the link. May 27 12:11
jlaska | poelcat: are there any upcoming milestones wrt to the f12 schedule? May 27 12:11
poelcat | jlaska: start of development? ;-) May 27 12:12
jlaska | sorry, I guess I was thinking more about changes to the schedule, not yet the content it describes May 27 12:12
* | jlaska not familiar with formal schedule review process May 27 12:13
--- | stickster_afk is now known as stickster May 27 12:15
jlaska | poelcat: if it's okay, I'll catch up ith you out of meeting on that May 27 12:15
poelcat | i can propose it at the next releng meting May 27 12:15
poelcat | okay May 27 12:15
jlaska | roger May 27 12:15
jlaska | okay our last carry over from the previous previous meeting ... May 27 12:15
jlaska | # [wwoods] - write a few more upgrade cases (encrypted root upgrade) May 27 12:16
wwoods | QA:Testcase_Anaconda_Upgrade_Encrypted_Root May 27 12:16
wwoods | I was going to put it in the RC test result page but May 27 12:16
jlaska | sweet! May 27 12:16
wwoods | are we going to clear the RC page for the next RC May 27 12:16
--- | stickster is now known as stickster_afk May 27 12:16
wwoods | or just have a "Fedora 11 Final ... " results page? May 27 12:16
wwoods | also need to create a case for preupgrades (kickstart-based + stage2 on HD + special hd-repo case) May 27 12:17
jlaska | wwoods: good question ... I'm not a big fan of clearing the whole page May 27 12:17
wwoods | nor am I, really. rename old page to RC0 and create an RC1 page? May 27 12:17
jlaska | yeah that's not a bad idea ... I can take that if you don't mind adding your upgrade case to the template? May 27 12:18
wwoods | sure May 27 12:18
jlaska | another thought was to just clear our the warn/fail results for retesting May 27 12:18
f13 | jlaska: that's not a bad idea May 27 12:18
jlaska | but I guess that accomplishes the same thing as long as we clearly retain the test results we've accumulated May 27 12:18
poelcat | how do you know if you have a regression? May 27 12:19
poelcat | in the ones that passed May 27 12:19
jlaska | poelcat: yeah, that's part of why I want to retain old results May 27 12:20
jlaska | you can get it with the wiki history, but it's not super obvious (to me) how best to tag old versions May 27 12:20
mars_ | damn i gotto go May 27 12:20
f13 | I'm find with any way that we agree upon May 27 12:21
jlaska | unless folks have a strong preference I'll try to mock up a solution and send out for review on fedora-test-list May 27 12:21
jlaska | wwoods: nice use of the FedoraVersion wiki template May 27 12:22
jlaska | that's my new favorite :) May 27 12:22
jlaska | okay, moving on to last weeks items ... May 27 12:22
jlaska | # [adamw] - clean up the Common_F11_bugs page to prime contributions from others May 27 12:22
wwoods | jlaska: heh, yeah, I pulled that from the other upgrade cases, so credit to whoever wrote those May 27 12:23
adamw | so, well, it's done May 27 12:23
adamw | with useful contributions from paul and you and beland May 27 12:24
jlaska | adamw: yeah it's looking pretty good, we can talk more about the content that later in the meeting May 27 12:24
jlaska | adamw: I had an item down to ping the docs team for translation help too ... May 27 12:25
jlaska | # [adamw] - ping fedora docs team for possible collaboration around common bug edits or translation May 27 12:25
adamw | but yeah, the cleaning up was done and was non-controversial afaict May 27 12:25
adamw | i did talk to the docs team about the page and they're happy with how we're handling it, didn't get a definite answer on translation, i may try that again on the ml or something May 27 12:25
jlaska | adamw: yeah it helped me add stuff so I'm happy, not sure about others :) May 27 12:25
--- | nman64 is now known as nman64_away May 27 12:26
jlaska | adamw: okay May 27 12:26
jlaska | the last few items are all around adding content to the common bugs page May 27 12:26
jlaska | # [jlaska] - contribute installer issues to Common_F11_bugs May 27 12:26
jlaska | # [fcami+adamw] - contribute X and KMS issues to Common_F11_bugs May 27 12:26
jlaska | # [adamw] - contribute alsa/pulseaudio issues to Common_F11_bugs May 27 12:26
adamw | you're first :) May 27 12:27
jlaska | I've been adding installer issues from the test results matrix (and mailing list) this week, I would like to re-scan the mailing list to make sure frequently reported issues are listed May 27 12:27
jlaska | adamw: fcami isn't here today, but he did pass along his radeon known issues draft via email May 27 12:27
adamw | yeah...it wasn't finished, though, he said he was going to finish it, so i'm waiting for that May 27 12:29
adamw | if we get to GA and he hasn't finished it, I'll try and do it myself May 27 12:29
adamw | I've added the X / KMS issues that I'm aware of that are significant enough to get on there, I may do a second pass in a bit May 27 12:30
adamw | ditto for alsa / pulseaudio May 27 12:30
adamw | i'm also planning to add a special, general "intel sucks" section with general tips on how to poke the intel driver to try and improve things if you're stuck in one of the sucky cases May 27 12:30
jlaska | oh that'd be a big help May 27 12:31
adamw | nomodeset, and the various options from keithp's blog post May 27 12:31
jlaska | yesterday you also mentioned possibly adding a section just for installation issues ... did you want me to do that as I'm updating them? May 27 12:31
adamw | no, that's okay - i want to split the whole page up into sections May 27 12:32
jlaska | okay, all yours! May 27 12:32
adamw | i was just waiting a bit till we've got a decent mass of issues on there so i can hopefully design the section split sanely May 27 12:32
jlaska | okay ... unless any other updates ... going to come back to the common bugs shortly ... May 27 12:33
--- | jlaska has changed the topic to: Fedora QA Meeting | autoqa - revisit post-F11 May 27 12:34
jlaska | wwoods: I'm going to mark autoqa for a revisit post-F11 ... but shout if you want to go over anything specific today May 27 12:35
f13 | not really May 27 12:35
wwoods | not for today, no May 27 12:35
jlaska | okay May 27 12:35
wwoods | but yeah, ask again post-f11 (i.e. next week) May 27 12:35
f13 | although I decided to not run for the board again, nor FESCo so that I have more time to work on it May 27 12:36
jlaska | wwoods: roger May 27 12:36
jlaska | f13: okay, we'll revisit post F11, definitely keep coordinating any changes/ideas with wwoods (aka Mr. autoqa) May 27 12:37
--- | jlaska has changed the topic to: Fedora QA Meeting | F-11-GA Preparation May 27 12:38
wwoods | I prefer Cap'n Autoqa May 27 12:38
jlaska | wwoods: that may require a suite and hat to go with May 27 12:39
adamw | yarrrrrr May 27 12:39
jlaska | so for F11 GA Prep, I mostly wanted to review where we are in the schedule ... and discuss any concerns around timing or next steps May 27 12:39
jlaska | but of course open to other ideas/input May 27 12:39
jlaska | * Blocker bugs (by component) - http://tinyurl.com/pqeq6n (currently 2 OPEN issues remain) May 27 12:40
jlaska | * Schedule - http://fedoraproject.org/wiki/Releases/11/Schedule May 27 12:40
jlaska | * Installation test results - QA:Fedora_11_RC_Install_Test_Results May 27 12:40
jlaska | * Release readiness meeting planned for today May 27 12:40
jlaska | May 27 12:40
jlaska | </links> May 27 12:40
f13 | So right off, there are a ton of MODIFIED things that need to be verified since we got a new kernel, anaconda, mkinitrd, rhpl, policycoreutils May 27 12:41
adamw | the intel bug is effectively 'modified', since we have the no-kms kernel testing May 27 12:41
adamw | so there's really only one non-modified bug...so we need to focus on getting the modified ones closed up i guess May 27 12:42
f13 | hrm, 2.6.29.3-160 doesn't disable it does it? May 27 12:42
adamw | no, that's why it's not tagged as modified May 27 12:42
f13 | damnit May 27 12:42
adamw | the test build is a koji build, not in the main stream May 27 12:42
f13 | I thought we tagged the one that was disabled. May 27 12:42
jlaska | the one open anaconda bug has feedback now from the reporter bug#498553 May 27 12:42
f13 | shit shit May 27 12:42
buggbot | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=498553 medium, low, ---, anaconda-maint-list, NEW, FSError: filesystem has not been created May 27 12:42
adamw | s/koji build/koji scratch build/ May 27 12:43
jlaska | I need to follow up on that, because the feedback doesn't grok for me May 27 12:43
jlaska | * Selected "Use entire drive" from dropdown & clicked Next May 27 12:43
jlaska | * Clicked "Write changes to disk" on popup dialog May 27 12:43
jlaska | * Dialog went away May 27 12:43
jlaska | * Clicked Next on same page that showed "use entire drive" May 27 12:43
jlaska | * Crashed May 27 12:43
jlaska | the "Clicked Next on the same page" part is confusing, unless anyone has ideas, I'll try to get more feedback on that this afternoon May 27 12:44
f13 | sounds like there was a UI pause May 27 12:44
f13 | and he thought he needed to click next May 27 12:44
jlaska | oh I see May 27 12:45
f13 | that click may not have actually done anything May 27 12:45
jlaska | right ... that would make more sense May 27 12:45
f13 | and the crash just came from the attempt to write changes May 27 12:45
jlaska | anyone have an Acer aspire to test on? May 27 12:45
adamw | acer aspire is not sufficiently specific May 27 12:46
wwoods | waaait.. wasn't there a bug in Beta/Preview (maybe Live-specific?) where it would show you the custom partitioning screen twice? May 27 12:46
jlaska | "Acer Aspire One May 27 12:46
jlaska | netbook" May 27 12:46
adamw | they brand most of their laptops aspire May 27 12:46
jlaska | wwoods: eeew May 27 12:46
adamw | ok, that's more specific. :) i have one here, i may be able to test that if i can drag sammy away from his game for ten minutes May 27 12:46
jlaska | adamw: sorry, was missing the tail end of that May 27 12:46
adamw | (it's his laptop) May 27 12:46
f13 | wwoods: not that I remember. May 27 12:47
jlaska | adamw: would he be sufficiently upset to have it reinstalled on him? :) May 27 12:47
adamw | oh, i couldn't complete the install, if it needs that...well, maybe to a usb stick or something May 27 12:47
adamw | oh yeah, it needs 'use entire drive' :\ May 27 12:48
jlaska | adamw: that's the only specific info I can go off of in that report right now ... perhaps the error is tied to that netboot May 27 12:48
adamw | don't think i could do that. hum. unless i have a spare disk i could swap in. gr. May 27 12:48
jlaska | I can put out a request to fedora-test-list ... but that might take a bit May 27 12:48
jlaska | f13: howabout in terms of the f11 schedule, how are we looking for releasing next week May 27 12:48
f13 | I have to make the RC today May 27 12:49
f13 | if we're going to make our release date May 27 12:49
jlaska | and then the last date you can start the sync is end of day tomorrow? May 27 12:49
adamw | f13: we have one positive report on the kms-disabling kernel May 27 12:49
f13 | I'm asking kyle to do a real kernel build with the disabling of kms on some intel chips May 27 12:49
adamw | so we could throw that in as a real build now May 27 12:49
adamw | ...oh, ok, you beat me :) May 27 12:49
f13 | jlaska: yeah, and that's pushing it really hard May 27 12:49
jlaska | yeah that's not a lot of time to test ... we can probably get in a few physical media tests, and verification of the rc0.1 failures May 27 12:50
--- | fab_ is now known as fab May 27 12:50
f13 | nod May 27 12:50
jlaska | we can always do those things in parallel ... but there's always risk May 27 12:50
adamw | damn...i thought i did have a spare hard disk but now i can't find the damn thing May 27 12:51
jlaska | what expectations around testing are there for the RC ... 0 bugs in MODIFIED, or a first pass of test matrix verification May 27 12:51
jlaska | I mean, I can say my preference, but it probably wouldn't line up well with the schedule May 27 12:53
f13 | I'd prefer to have both May 27 12:53
f13 | but we may not be able to verify all the things in MODIFIED May 27 12:53
f13 | due to lack of hardware/etc.. May 27 12:53
jlaska | right, so that could very well take several days to confirm May 27 12:54
f13 | depending on how the kernel shakes out, you just might have that :/ May 27 12:54
jlaska | f13: ah okay, I'm not up to speed on the kernel issue May 27 12:55
f13 | there is disagreement on the disabling of KMS May 27 12:55
f13 | or rather the patch that kyle did May 27 12:55
poelcat | when did that patch get added? May 27 12:55
f13 | it didn't get added, a scratch build was done with it last night May 27 12:55
jlaska | is that something on the blocker list? May 27 12:56
adamw | what's the disagreement? May 27 12:56
adamw | jlaska: yes May 27 12:56
jlaska | ^^ oh that's the remaining intel issue? May 27 12:56
adamw | jlaska: yes May 27 12:56
jlaska | gotcha May 27 12:56
f13 | adamw: hard to follow, krh isn't convinced that the bugs are caused by kms, or not otherwise fixed by an intel driver update May 27 12:56
f13 | or which all chipsets to disable i ton May 27 12:57
f13 | basically we need to get krh back on IRC to get a final go/nogo on the patch or modification of the patch May 27 12:57
adamw | well, the only issue we really want to fix here is https://bugzilla.redhat.com/show_bug.cgi?id=502077, and that's specific to 865 May 27 12:57
buggbot | Bug 502077: medium, low, ---, krh, ASSIGNED, [KMS] Hangs on 82865G May 27 12:58
adamw | and it definitely is 'caused' by KMS, in the sense that disabling KMS fixes it May 27 12:58
adamw | i would be fine if kristian wants to just do it for 865 rather than other 8xx chips May 27 12:58
adamw | 502077 has existed for a while and been assigned to kristian and i haven't seen him comment or ask for info or provide a test fix, so... May 27 12:58
f13 | he was talking with kylem in #fedora-kernel this morning about it May 27 12:59
adamw | well, a week. but hey, a week's a while at release time :) May 27 12:59
f13 | <krh> [12:56] +kylem: also I think #502077 looks more like #498131. May 27 13:00
f13 | <kylem> [12:56] +(kms on i830) May 27 13:00
f13 | <krh> [12:56] +and I see he's testing with a xorg-x1-drv-intel from before that got fixed May 27 13:00
f13 | <kylem> [12:57] +https://bugzilla.redhat.com/show_bug.cgi?id=498131 May 27 13:00
f13 | <buggbot> [12:57] -Bug 498131: medium, low, ---, krh, CLOSED RAWHIDE, xorg-x11-drv-intel, Visiting webpage causes system lockup, except mouse cursor May 27 13:00
f13 | <kylem> [12:57] +care to follow up then? i'd buy that explaination. May 27 13:00
buggbot | Bug 498131: medium, low, ---, krh, CLOSED RAWHIDE, Visiting webpage causes system lockup, except mouse cursor May 27 13:00
buggbot | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=498131 medium, low, ---, krh, CLOSED RAWHIDE, Visiting webpage causes system lockup, except mouse cursor May 27 13:00
f13 | <krh> [12:58] +sure May 27 13:00
--- | Sparks is now known as Sparks_Meeting May 27 13:01
* | benedictus is here for fedora-be meeting May 27 13:01
biertie | hello benedictus May 27 13:01
benedictus | Hi biertie May 27 13:01
biertie | I think we should wait another 5minutes, so the QA team can close there meeting + wait for more belgians come in? May 27 13:02
benedictus | ok May 27 13:02
jlaska | okay, let's summarize and move over to #fedora-qa May 27 13:02
jlaska | the open issues ... we have 1 day to test MODIFIED bugs and retest failed test matrix issues (should be close 1-1 match here) May 27 13:02
jlaska | f13: wwoods adamw: $others: can we continue this over in #fedora-qa ... May 27 13:03
f13 | yeah May 27 13:03
wwoods | sure, as long as you're logging there as well May 27 13:03
<-- | BiloxiGeek [n=iceberg@24-116-55-163.cpe.cableone.net] has left #fedora-meeting ( ) May 27 13:03
jlaska | wwoods: good point ... I'll merge it in once we finish up May 27 13:03
--- | 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 May 27 13:04
--- | dwmw2 is now known as dwmw2_gone May 27 13:04
jlaska | okay ... QA folks, sorry for the switch :( ... let's continue this in #fedora-qa May 27 13:04
Continued in #fedora-qa
adamw | i don't see how 502077 can possible be 498131, since people are still experiencing 502077 with the packages that fix 498131. May 27 13:02
f13 | adamw: which people and where? May 27 13:04
--- | dwmw2 is now known as dwmw2_gone May 27 13:04
adamw | the reporters of 502077. May 27 13:05
--- | stickster_afk is now known as stickster May 27 13:05
adamw | one confirmation of the bug came in after 498131 was closed, and people following it haven't made any suggestion that it magically got fixed in the days since that fix went it May 27 13:05
adamw | i would've expected jeff bastian, for instance, to notice that May 27 13:05
f13 | well we need to confirm what intel driver version they're using, since there is only one mention of version in teh bug and it's the old version May 27 13:06
jlaska | so the summary I've got of outstanding issues is 502077 and the 1 day time to verify MODIFIED bugs and retest RC May 27 13:06
jlaska | are there other areas/issues you guys are concerned about for release? May 27 13:06
adamw | f13: yeah, i just added a comment for that. May 27 13:07
wwoods | I've requested that the preupgrade packages be moved to stable - people have tested and I've not seen any new problems May 27 13:08
jlaska | wwoods: is that for the preupgrade in .fc11 or .fc10? May 27 13:08
wwoods | 9, 10, and 11 May 27 13:08
jlaska | oh boy ... line 'em up :) May 27 13:09
wwoods | it's not useful in fc11, since there's nothing newer to upgrade to, but otherwise we break upgrade path May 27 13:09
jlaska | do you get enough bz's or mailing list questions where it would be useful to add blurbs in the common bugs? May 27 13:09
wwoods | but 9 and 10 can both upgrade to 11, so those needed to be pushed May 27 13:09
adamw | wwoods: wasn't there a thread in -devel-list recently about how you're supposed to version stable release updates so they don't break the upgrade path to later releases? May 27 13:10
wwoods | dunno. I don't read -devel-list anymore May 27 13:10
wwoods | but the updates are all the same version, other than the dist tag, so fc11 > fc10 > fc9 May 27 13:11
wwoods | as it should be May 27 13:11
adamw | k May 27 13:12
wwoods | jlaska: I can't think of anything off the top of my head for common bugs May 27 13:13
jlaska | wwoods: okay May 27 13:14
jlaska | I'm a bit worried about the 1 day time frame, and the KMS issue still open, so if changes are still coming on the kernel side I think that would likely impact the GA date May 27 13:14
jlaska | '1 day time frame' meaning 1 day to verify the RC May 27 13:15
jlaska | are there other concern areas (based on forum|mailing_list feedback) May 27 13:15
jlaska | or experience from previous releases (wwoods+f13) May 27 13:15
f13 | well, if we fix the things that are in MODIFIED, I think we're in great shape May 27 13:16
f13 | all the testing we've done up to this point help out May 27 13:16
f13 | but I agree, I'm a bit... concerned. May 27 13:16
jlaska | yeah, testing is definitely accumulative ... so that helps May 27 13:16
f13 | I think it'll look bad if we slip again, but honestly... maybe we do need the time May 27 13:16
f13 | I had hoped to wake up today and compose an RC, but that doesn't look like its going to happen May 27 13:17
jlaska | I've been involved in cases where we will continue testing the RC after having started staging ... but there's risk there ... so folks just need to know May 27 13:17
f13 | unless we decide that 502077 isn't a blocker. May 27 13:17
f13 | if 502077 isn't a blocker, I can start the compose now. May 27 13:17
jlaska | clumens: does this patch makes sense for this bug? https://bugzilla.redhat.com/show_bug.cgi?id=498553#c10 May 27 13:18
buggbot | Bug 498553: medium, low, ---, anaconda-maint-list, NEW, FSError: filesystem has not been created May 27 13:18
adamw | no, 502077 really needs to be a blocker. random hangs on an entire class of graphics cards stinks. May 27 13:23
f13 | *grumble* May 27 13:23
f13 | so, here's my call. If 502077 is a blocker, we're slipping. May 27 13:23
f13 | again. May 27 13:23
adamw | ug. why? because kristian and kyle are bashing heads? May 27 13:24
wwoods | wait, "an entire class of graphics cards"? May 27 13:24
adamw | i865 May 27 13:24
adamw | not just some particular model system with an i865 in it, but - by the looks of things - any i865 May 27 13:25
wwoods | just i865, or i8[456]5? May 27 13:25
adamw | which was a very popular chipset that shows up in all sorts of low-end desktops, and few-years-old laptops May 27 13:25
adamw | just i865 for this particular issue May 27 13:25
wwoods | so it affects one specific intel model. May 27 13:25
adamw | does anyone know jeff bastian? can get him on the phone or the cubiclenet? May 27 13:26
adamw | so he can test the patch kyle just threw up on the bug? May 27 13:26
jlaska | and the patch makes "nomodeset" the default for i865 systems? May 27 13:26
f13 | no May 27 13:28
wwoods | as far as I can tell, I'd characterize i865 as "uncommon" hardware. May 27 13:28
adamw | well, i wouldn't. but if i'm outvoted, fine. May 27 13:28
adamw | would you count i945 as uncommon? May 27 13:29
wwoods | no May 27 13:29
jlaska | can we grab smolt data to confirm? May 27 13:29
adamw | then would you count it as uncommon in two years? May 27 13:29
adamw | because all those systems will juist have been junked or something? May 27 13:29
wwoods | the statistics indicate that the i945 is >=10x more popular May 27 13:29
wwoods | http://smolts.org/static/stats/by_class_VIDEO.html May 27 13:29
f13 | the patch is i855 fixes, not disabling kms May 27 13:29
adamw | hmm, fair enough then May 27 13:29
adamw | there's battling patches May 27 13:29
adamw | initial pair of patches to disable kms May 27 13:30
wwoods | although it's unclear what chipset "Mobile Integrated Graphics Controller" represents May 27 13:30
adamw | the latest one purports to actually fix the pronlem May 27 13:30
wwoods | sure wish we could get data like: "what percentage of known systems match this range of vendor/device IDs" May 27 13:30
wwoods | but also the data doesn't make much sense when we have 1.2 million hosts listed (?) and video vendor data for ~30k May 27 13:31
adamw | yeah, smolt seems weirdly inimical to IDs, which are the only reliable way of tracking anything May 27 13:31
adamw | anyway, i repeat my q. - who is jeff bastian? do we know him? can we get him on the phone? May 27 13:32
wwoods | aaaand the "Search Devices" box doesn't work. whee. May 27 13:32
f13 | .fas bastian May 27 13:33
zodbot | f13: boa1978 'Bastian Angerstein' <hellmaster@slived.net> - sebas 'Sebastian Martínez' <sebasch@internet.com.uy> - sdz 'Sebastian Dziallas' <sebastian@when.com> - ageha 'Sebastian S.' <ageha666@googlemail.com> - ganoncl 'Sebastián Gana' <sebastian.gana@gmail.com> - spop 'Sebastian Pop' <sebpop@gmail.com> - bastian 'Bastian Rae Lukito' <bastiangtr@yahoo.com> - xuru 'paulo sebastian rojas vasquez' (5 more messages) May 27 13:33
* | Viking-Ice bloody Samba + AD + Winbind let me miss the fracking meeting May 27 13:34
clumens | jlaska: sure, if you don't want progress while mkfs is running May 27 13:36
jlaska | haha ... yeah I don't get it May 27 13:37
clumens | jlaska: it makes no sense that the progress thing is the problem. May 27 13:39
adamw | PCI ID for the 865 is 0x8086 0x2572 , if that helps anyone find him May 27 13:48
adamw | find it May 27 13:48
<-- | BiloxiGeek [n=iceberg@24-116-55-163.cpe.cableone.net] has left #fedora-qa ( ) May 27 13:49
jlaska | adamw: mmcgrath is doing some searches for us ... searching by pci id through the web ui isn't supported right now May 27 13:50
adamw | can we beat him with something until it is? =) May 27 13:51
adamw | and displaying the IDs from people's profiles too May 27 13:51
adamw | that way when i get people to link their smolt profiles in bug reports, it'd actually help May 27 13:51
adamw | this review: http://www.computerbuyer.co.uk/labs/198063/lenovo-thinkpad-t61-6466.html suggests the thinkpad t61 (that specific model variant, anyway) has/had 865 May 27 13:51
adamw | seems like some variants came with nvidia instead May 27 13:53
wwoods | I've never had any machines with i865 May 27 13:55
wwoods | here's a general release note: "Finishing Upgrade Process" takes a long time - sometimes as long as the upgrade process itself May 27 13:55
adamw | jlaska says searching by PCI ID indicates 2.2% of all machines in smolt have an i865 May 27 13:56
adamw | which is not insignificant imho May 27 13:56
wwoods | how's that compare to, say, intel as a whole? or i9xx? or nvidia? or ATI? May 27 13:57
adamw | does it matter? i'd say random hangs affecting 2.2% of our current userbase is rather important May 27 13:57
wwoods | conversely, this bug doesn't affect 97.8% of users May 27 13:57
adamw | i don't want to get too bogged down in the statistics... May 27 13:57
adamw | rather than working on the report May 27 13:57
adamw | trying to get in touch with jeff bastian to get some quick testing of the latest things on the report, jlaska is going to call him May 27 13:58
jlaska | left a msg May 27 14:01
adamw | :\ May 27 14:04
--- | kentb_afk is now known as kentb May 27 14:31
adamw | f13: jeff reports in 502077 that the 'real fix' from kyle seems to work May 27 15:20

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

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20090527&oldid=472340"