| Tuned | |
|---|---|
| |
| Date | 2024-09-09 to 2024-09-13 |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #test-day:fedoraproject.org |
| Mailing list | test |
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?[edit]
This Fedora Test Day will be focusing Testing Tuned
Who's available[edit]
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. Use #fedora-test-day channels on libera chat. In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.
- Development - Kate Hsuan, Jaroslav Škarvada
- Quality Assurance - Adam Williamson (adamw),coremodule (coremodule), Sumantro Mukherjee (sumantrom)
Prerequisite for Test Day[edit]
- A system (real or virtual) you can install Fedora to, and not mind if it breaks
How to test?[edit]
Install Fedora[edit]
Testing Tuned from a live environment is difficult and will likely wind up with the system exhausting available battery and failing in strange ways, so we recommend you install Fedora 41 VM for this Test Week.
Run the tests[edit]
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[edit]
If you have problems with any of the tests, report a bug to Bugzilla usually for the component tuned. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Test Results[edit]
The results will be transferred once the test day is over.