| Bootloader Test Day | |
|---|---|
| |
| Date | 2021-04-12 through 2021-04-13 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| 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?
This Test Day will focus on testing the new shim 15.4 and GRUB 2.06. This is an extremely important test day as the newly signed shim needs testing. Grub also gets an update and we would like to ensure that bootloaders works as intended.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - pjones (pjones), cmurf (cmurf)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.
Prerequisite for Test Day
- An installation of Fedora 34 (any Edition or Spin). Make sure to fully update your system with new shim and
grub2-2.06~rc1-3.fc34.src.rpmis installed. - An USB
How to test?
There is a pre-req for this test day:
- Check if your machine is running EFI/UEFI or BIOS by executing the following on terminal.
[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
- Check if [boot] is enabled by running
mokutil --sb-state
- Create Grub Backup just in case
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Reporting bugs
All bugs should be reported into Bugzilla, in most cases against the Grub component. If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above).
Test Results
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.