Great news. Are the RPI GPIOs expected to be working?
On 05/05/2022 01:37, Adam Williamson wrote:
> Subject:
> [fedora-arm] Fwd: [Test-Announce] Fedora 36 Candidate RC-1.5 Available
> Now!
> From:
> Adam Williamson <adamwill@fedoraproject.org>
> Date:
> 05/05/2022, 01:37
>
> To:
> desktop@lists.fedoraproject.org, kde@lists.fedoraproject.org,
> cloud@lists.fedoraproject.org, server@lists.fedoraproject.org,
> arm@lists.fedoraproject.org
>
>
> Hey folks! Please see attached. Due to some late-breaking blockers and
> fixes, we're now up to RC5 for F36 Final. Go/no-go is tomorrow. If
> folks can help with testing, that'd be great.
>
> Here's a quick summary of the changes between the RC composes:
>
> RC1 -> RC2
> gtk4-4.6.2-3.fc36 to fix #2071228
> clevis-pin-tpm2-0.5.2-1.fc36 rust-tpm2-policy-0.6.0-1.fc36 to fix FTBFS
>
> RC2 -> RC3
> wpa_supplicant-2.10-4.fc36 to fix #2072070
> tracker-miners-3.3.0-2.fc36 to fix #2079308
> mutter-42.0-6.fc36 to fix #2081070
> openssl-3.0.2-4.fc36 to fix #2069239
> gzip-1.11-3.fc36 to fix #2073312
> kernel-5.17.5-300.fc36 for #2080694
> snapper-0.10.1-1.fc36 for FTBFS
> selinux-policy-36.8-1.fc36 for #2065940
> livecd-tools-30.0-1.fc36 for #2007045
> xz-5.2.5-9.fc36 for #2080938
> xdg-desktop-portal-1.12.4-1.fc36 for #2060990
> sssd-2.7.0-1.fc36 for #2077856
> gr-osmosdr-0.2.3-21.20210217gita100eb02.fc36 to fix FTBFS
>
> RC3 -> RC4
> firefox-100.0-2.fc36 for #2081488
>
> RC4 -> RC5
> sushi-41.2-1.fc36 for #2067969
> gnome-photos-42.0-2.fc36 for #2079344 #2081291
> aws-2020-7.fc36 matreshka-20.1-10.fc36 templates_parser-11.8.0-30.fc36 for FTBFS
>
> So, RC3 had quite a lot of change in it. RC4 and RC5 are much more
> limited. So we can count most tests from RC3 or later as being valid
> for RC5; tests of Firefox, Nautilus and GNOME Photos should be re-
> confirmed.
>
> I have transferred results from RC3 and RC4 to RC5 in the matrix where
> appropriate, leaving out things that are considered 'sanity tests'
> (basic boot and install tests) which we try to run on every compose to
> rule out some kind of cosmic bit-flip unexpectedly breaking an image.
> So any spaces left on Basic/Beta/Final tests are ones we should try to
> fill.
>
> Special note on the Active Directory tests: it looks like tflink and
> sgallagh ran these on RC1, thanks a lot. Since we did get a new sssd
> between then and RC5 it would be*nice* if we could run them again, but
> if not we can probably run with the RC1 results in the end.
>
> Thanks again everyone!
> -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha
> https://www.happyassassin.net
>
> [Test-Announce] Fedora 36 Candidate RC-1.5.eml
>
> Subject:
> [Test-Announce] Fedora 36 Candidate RC-1.5 Available Now!
> From:
> rawhide@fedoraproject.org
> Date:
> 05/05/2022, 00:07
>
> To:
> test-announce@lists.fedoraproject.org
>
>
> According to the schedule [1], Fedora 36 Candidate RC-1.5 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/36
>
> 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_36_RC_1.5_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_36_RC_1.5_Security_Lab
>
> All RC priority test cases for each of these test pages [2] must
> pass in order to meet the RC Release Criteria [3].
>
> Help is available on #fedora-qa on libera.chat [4], or on the
> test list [5].
>
> Current Blocker and Freeze Exception bugs:
> http://qa.fedoraproject.org/blockerbugs/current
>
> [1]http://fedorapeople.org/groups/schedule/f-36/f-36-quality-tasks.html
> [2]https://fedoraproject.org/wiki/QA:Release_validation_test_plan
> [3]https://fedoraproject.org/wiki/Fedora_36_RC_Release_Criteria
> [4]https://web.libera.chat/?channels=#fedora-qa
> [5]https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/
> _______________________________________________
> test-announce mailing list --test-announce@lists.fedoraproject.org
> To unsubscribe send an email totest-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.fedoraproject.org
> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
>
> _______________________________________________
> arm mailing list --arm@lists.fedoraproject.org
> To unsubscribe send an email toarm-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/arm@lists.fedoraproject.org
> Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure
> Attachments:
>
> [Test-Announce] Fedora 36 Candidate RC-1.5.eml 10.3 kB
>
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-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/arm@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
No comments:
Post a Comment