From Fedora Project Wiki

< QA‎ | Meetings
Revision as of 15:58, 16 May 2011 by Jlaska (talk | contribs) (Updated notes)

Attendees

People present (lines said):

  1. jlaska (151)
  2. adamw (56)
  3. kparal (28)
  4. j_dulaney (21)
  5. brunowolff (16)
  6. tflink (14)
  7. vhumpa (12)
  8. pbrobinson (9)
  9. jsmith (5)
  10. Southern_Gentlem (4)
  11. rbergeron (3)
  12. satellit_ (3)
  13. fenrus02 (1)
  14. elad661 (1)
  15. Viking-Ice (1)
  16. msavy (1)

Unable to attend:

  1. Rhe (hopefully sleeping)
  2. Hongqing (hopefully sleeping)
  3. wutao85 (hopefully sleeping)
  4. jskladan

Agenda

Previous meeting follow-up

  1. tflink to follow-up with cloud sig for test day recap
    • mgoldmann or msavy will follow-up this week (conferences previous 2 weeks)
  2. jlaska to follow-up w/ halfline on bug#702650, kparal+jlaska to verify
    • Appears to be tested and resolved, thanks kparal and halfline
  3. adamw proposing patch for bug#697834
    • Done ... AcceptedNTH and available for walters if desired
  4. jlaska - file proposed NTH bugs for F14->F15
    • Done

F-15-Final-RC3 status

AutoQA update

  • kparal implemented package caching in AutoQA (optional, default off). When enabled, it drastically speeds up mainly depcheck runs.
  • jskladan introduced an algorithm to filter interesting information from depcheck log about why a particular package has broken dependencies
  • we started to nicely document our test cases. First piece is upgradepath (see https://fedoraproject.org/wiki/AutoQA_tests/Upgradepath)
  • tflink worked on issue of yum getting stuck in a loop that generated huge depcheck logs. When new yum builds land in stable repos, we should be have that handled. Tflink also noted the updates are still in 'updates-testing', pending additional positive karma.
  • vhumpa created a pretty text template for our future test reports (see http://vhumpa.fedorapeople.org/prettylog_upgradepath_example2.txt)
  • Jlaska reported that the log size issue appears under control. Compressing logs > 100M every 2 hours

Upcoming QA events

  1. Tuesday, May 17 - Go/NoGo meeting
  2. Tuesday, May 24 - Final (GA) release

Open Discussion - <your topic here>

Action items

IRC Log