From Fedora Project Wiki
| Fedora Test Day | |
|---|---|
| |
| Kernel 4.17 | |
| Date | 2018-06-12 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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.
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.17
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - jforbes (jforbes)
- Quality Assurance - Adam Williamson (admaw), Kamil Páral (kparal), Sumantro Mukherjee (sumantrom), Geoff (coremodule)
Prerequisites for Test Day
- A fully updated [XYZ 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 [XYZ 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 in the results page. Please include the vulnerability output at the end of the test suite in the comments.
If you don't see it, please file a new bug to Bugzilla, probably against kernel component. 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
Test results will be transferred once the test day is complete.