According to [the schedule][1], Fedora 40 Candidate Beta-1.9 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Security_Lab
All Beta priority test cases for each of these [test pages][2] must pass in order to meet the [Beta Release Criteria][3].
Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6].
Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current
[1]: https://fedorapeople.org/groups/schedule/f-40/f-40-quality-tasks.html [2]: https://fedoraproject.org/wiki/QA:Release_validation_test_plan [3]: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria [4]: https://matrix.to/#/#quality:fedoraproject.org?web-instance%5Belement.io%5D=... [5]: https://discussion.fedoraproject.org/tags/c/project/7/quality-team [6]: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org 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://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproj... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Tue, 19 Mar 2024 12:41:48 +0000 (UTC) rawhide@fedoraproject.org wrote:
According to [the schedule][1], Fedora 40 Candidate Beta-1.9 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Security_Lab
All Beta priority test cases for each of these [test pages][2] must pass in order to meet the [Beta Release Criteria][3].
Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6].
Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current
the Cloud and Container image filenames miss the "Beta" string in the name, not sure, but someone might have mentioned it already ...
for example Fedora-Cloud-Base-Generic.ppc64le-40-1.9.qcow2 should be Fedora-Cloud-Base-Generic.ppc64le-40-Beta_1.9.qcow2 I believe. The checksum filename is correct.
Dan
On Wed, Mar 20, 2024 at 8:45 AM Dan Horák dan@danny.cz wrote:
On Tue, 19 Mar 2024 12:41:48 +0000 (UTC) rawhide@fedoraproject.org wrote:
According to [the schedule][1], Fedora 40 Candidate Beta-1.9 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Security_Lab
All Beta priority test cases for each of these [test pages][2] must pass in order to meet the [Beta Release Criteria][3].
Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6].
Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current
the Cloud and Container image filenames miss the "Beta" string in the name, not sure, but someone might have mentioned it already ...
for example Fedora-Cloud-Base-Generic.ppc64le-40-1.9.qcow2 should be Fedora-Cloud-Base-Generic.ppc64le-40-Beta_1.9.qcow2 I believe. The checksum filename is correct.
This is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2270197
We have an upstream fix to kiwi for this, but some code will need to be written for the koji plugin and pungi to resolve it.
On Wed, 20 Mar 2024 08:47:14 -0400 Neal Gompa ngompa13@gmail.com wrote:
On Wed, Mar 20, 2024 at 8:45 AM Dan Horák dan@danny.cz wrote:
On Tue, 19 Mar 2024 12:41:48 +0000 (UTC) rawhide@fedoraproject.org wrote:
According to [the schedule][1], Fedora 40 Candidate Beta-1.9 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/40
You can see all results, find testing instructions and image download locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Summary
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Base https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Server https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_40_Beta_1.9_Security_Lab
All Beta priority test cases for each of these [test pages][2] must pass in order to meet the [Beta Release Criteria][3].
Help is available on [the Fedora Quality chat channel][4], [the Fedora Quality tag on Discourse][5], or on [the test list][6].
Current Blocker and Freeze Exception bugs: https://qa.fedoraproject.org/blockerbugs/current
the Cloud and Container image filenames miss the "Beta" string in the name, not sure, but someone might have mentioned it already ...
for example Fedora-Cloud-Base-Generic.ppc64le-40-1.9.qcow2 should be Fedora-Cloud-Base-Generic.ppc64le-40-Beta_1.9.qcow2 I believe. The checksum filename is correct.
This is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2270197
We have an upstream fix to kiwi for this, but some code will need to be written for the koji plugin and pungi to resolve it.
thanks for the pointer. I have noticed it, because I am using https://github.com/sharkcz/tools/blob/master/check-compose to check what artifacts are actually available (limited to my "multi-arch" view).
Dan