From Fedora Project Wiki

Revision as of 22:59, 20 February 2018 by Jforbes (talk | contribs) (fix koji url)

Fedora Test Day
Echo-testing-48px.png
Kernel 4.15

Date 2018-02-22
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Kernel 4.15

Who's available?

The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...

Prerequisites for Test Day

  • A fully updated test day image or Fedora 28 Workstation/Server installation, either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
  • The 4.15 kernel for Fxx from updates testing or koji if not using the test day image.
  • Enough free space on HDD

How to test?

Run the tests

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Reporting bugs

If you have problems with any of the tests, have a look at the list of reported bugs in Bugzilla and in the results page. If you don't see it, please file a new bug to Bugzilla, probably against kernel component. Add bug 1308538 to the Blocks: field. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.

Test Results

This is usually filled with the exported results from Test day app after the test day happens