Hi folks! Trying something a bit new here. I've nominated today's
Fedora 36 nightly compose for validation testing. We do this regularly
in any case, but I'm sending this out to a wider group and asking folks
to treat this nightly as it it were a release candidate, and try to
complete the *full* set of Final validation tests on it. The idea is to
try and make sure we get all the tests done well ahead of the Go/No-Go
Meeting, so we can identify any remaining blocker bugs *now*, not have
to try and deal with them in a hurry later.
Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/36 . You can use this
to prioritize tests that have not yet been run at all.
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
The individual test result pages are:
The goal is to try and hit every test marked as Basic, Beta or Final
(hitting the Optional ones too is great but not required). It'd be
particularly good to cover things that often don't get done until late
- aarch64 tests, Cloud tests in real clouds, and the full set of Server
Active Directory tests, for instance. If you hit a significant failure
in a test, please file a bug, and most likely propose it as a release
blocker using https://qa.fedoraproject.org/blockerbugs/propose_bug .
If you have any questions or need any help with testing or reporting
results, please contact us on the test@ list or the QA IRC/Matrix
channel (#fedora-qa on IRC, "Fedora QA (Quality Assurance)" on Matrix).
Thanks a lot, folks!
IRC: adamw | Twitter: adamw_ha
arm mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure