2024-04-29 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-04-29 15:00:01 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 15:00:05) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:05:13) * INFO: "adamw or kparal to follow up on https://pagure.io/fedora-qa/issue/773 after discussing it with the team" - Kamil Páral and lruzicka both weighed in on the topic, thanks folks (@adamwill:fedora.im, 15:05:57) * TOPIC: Fedora 40 post-release status and recap (@adamwill:fedora.im, 15:07:30) * TOPIC: Fedora 41 Change preview (@adamwill:fedora.im, 15:32:04) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:43:02) * INFO: call for Fedora 41 Test Days will be coming soon, stay tuned (@adamwill:fedora.im, 15:45:32) * TOPIC: Open floor (@adamwill:fedora.im, 15:45:50) Meeting ended at 2024-04-29 16:05:28 Action items People Present (lines said) --- * @adamwill:fedora.im (71) * @frantisekz:fedora.im (33) * @nielsenb:fedora.im (25) * @coremodule:fedora.im (11) * @amoloney:fedora.im (9) * @zodbot:fedora.im (7) * @meetbot:fedora.im (2) * @tflink:fedora.im (1) * @pboy:fedora.im (1) * @derekenz:fedora.im (1) * @lruzicka:matrix.org (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-29 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-29 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240415T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 post-release status and recap 3. Fedora 41 Change preview 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-29 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-29 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240415T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 post-release status and recap 3. Fedora 41 Change preview 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-15 - Fedora Quality Meeting - Minutes **CORRECTED VERSION**
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-04-15 15:00:41 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 15:00:45) * TOPIC: Previous meeting follow up (@adamwill:fedora.im, 15:08:49) * INFO: no action items from previous meeting (@adamwill:fedora.im, 15:09:30) * TOPIC: Fedora 40 status (@adamwill:fedora.im, 15:09:42) * INFO: RC-1.14 is the current test candidate, please help fill out the matrices - https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.14_Summary (@adamwill:fedora.im, 15:10:16) * INFO: it would also be good to have more folks test the proposed blocker https://bugzilla.redhat.com/show_bug.cgi?id=2275099 and see if they hit it (I just tried, and didn't) (@adamwill:fedora.im, 15:10:45) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:18:25) * INFO: Upgrade Test Day was on April 8 - https://testdays.fedoraproject.org/events/185 . looks like we had a good turnout, thanks to all testers (@adamwill:fedora.im, 15:22:25) * INFO: OpenCL test day was April 9 - https://testdays.fedoraproject.org/events/186 . smaller turnout there, but thanks to the folks who came! (@adamwill:fedora.im, 15:22:50) * INFO: there are no more events upcoming right now, we're focusing on the Fedora 40 release (@adamwill:fedora.im, 15:23:17) * TOPIC: Open floor (@adamwill:fedora.im, 15:27:41) * ACTION: adamw or kparal to follow up on https://pagure.io/fedora-qa/issue/773 after discussing it with the team (@adamwill:fedora.im, 15:37:00) Meeting ended at 2024-04-15 15:38:26 Action items * adamw or kparal to follow up on https://pagure.io/fedora-qa/issue/773 after discussing it with the team People Present (lines said) --- * @adamwill:fedora.im (41) * @tablepc:matrix.org (7) * @nielsenb:fedora.im (7) * @amoloney:fedora.im (5) * @zodbot:fedora.im (4) * @nhanlon:beeper.com (3) * @yattatux:fedora.im (2) * @meetbot:fedora.im (2) * @tflink:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-15 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-04-01 15:01:09 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 15:01:14) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:07:23) * INFO: no specific action items to follow up from last meeting (@adamwill:fedora.im, 15:08:18) * INFO: Beta was released last week, seems to be going fine (@adamwill:fedora.im, 15:10:10) * INFO: Final freeze is tomorrow (2024-04-02), first go/no-go date is 2024-04-11 (@adamwill:fedora.im, 15:10:52) * TOPIC: xz compromise discussion (@adamwill:fedora.im, 15:26:06) * INFO: there was a very significant compromise of the xz compression library. builds known to be potentially vulnerable to the currently-known exploit vector are 5.6.0-1.fc40, 5.6.0-2.fc40, 5.6.0- 1.fc41, 5.6.1-1.fc41 , 5.6.0-2.eln136 , 5.6.1-1.eln136 (@adamwill:fedora.im, 15:28:30) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:47:56) * INFO: FCOS test week starts today: http://fedoraproject.org/wiki/Test_Day:Fedora_40_CoreOS (@adamwill:fedora.im, 15:53:46) * INFO: kernel test week went ahead recently but was affected by a breakage in the app usually used for submitting results: https://pagure.io/fedora-qa/issue/771#comment-903726 (@adamwill:fedora.im, 15:54:07) * INFO: Podman test week went successfully with many results submitted: https://testdays.fedoraproject.org/events/183 (@adamwill:fedora.im, 15:54:35) * INFO: Upgrade test day, dnf5 upgrade test day, and Intel test day are coming soon (@adamwill:fedora.im, 15:55:03) * INFO: there will be video meetings as part of FCOS test week! see https://meet.google.com/uwb-enhy-evg?authuser=0 and https://hackmd.io/kwCRZ9fGTgWuMSh0HDwQJw?view (@adamwill:fedora.im, 15:56:26) * TOPIC: Open floor (@adamwill:fedora.im, 15:57:43) Meeting ended at 2024-04-01 16:05:51 Action items People Present (lines said) --- * @adamwill:fedora.im (58) * @geraldosimiao:matrix.org (22) * @nielsenb:fedora.im (15) * @sumantrom:fedora.im (13) * @jeffiscow:fedora.im (12) * @nhanlon:beeper.com (10) * @tablepc:matrix.org (9) * @zodbot:fedora.im (8) * @farribeiro:matrix.org (8) * @pboy:fedora.im (8) * @coremodule:fedora.im (4) * @meetbot:fedora.im (2) * @tflink:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: fc40 beta kernel update to 6.8.5-301 produces errors
On Sun, 2024-04-14 at 23:32 +, J C wrote: > Hi all, used Fedora a while, but my first thing to report so apologies if I > don't get process right here. Trying to give the feedback to help make a > better Fedora for all of us... > > Updated the subject fedora workstation today and got some errors. Copying > the terminal contents here for reference. > > Seems some missing file and library errors in addition to some things for > gnome-remote-desktop and systemctrl. > > `~$ sudo dnf check-update > ... > Last metadata expiration check: 0:06:30 ago on Sun 14 Apr 2024 04:52:10 PM > MDT. > > kernel.x86_64 > 6.8.5-301.fc40 fedora > kernel-core.x86_64 > 6.8.5-301.fc40 fedora > kernel-modules.x86_64 > 6.8.5-301.fc40 fedora > kernel-modules-core.x86_64 > 6.8.5-301.fc40 fedora > kernel-modules-extra.x86_64 > 6.8.5-301.fc40 fedora > ~$ sudo dnf distro-sync -y So, the problem likely isn't anything to do with the kernel, it's because you did a distro-sync, after upgrading from the fedora-repos that has updates-testing enabled (which is how we want things through most of the pre-release cycle) to the fedora-repos that has updates- testing disabled (which is how we want things for release and after). This means you wind up with a lot of downgrades, because you have packages from updates-testing installed, but now it's disabled. It's an unfortunate recurring issue, but I can't see an obvious way to resolve it. Downgrades aren't generally as tested or reliable as upgrades, so yeah, this can cause problems. The usual ways to avoid the problem are: re- enable updates-testing after the fedora-repos update that disables it (if you're fine with continuing to help test updates), or wait for the final release freeze to lift shortly before release (whereupon most of the updates that are currently stuck behind the freeze will go stable and you mostly won't get any downgrades when doing distro-sync any more). And, of course, you can just use `dnf update` or `dnf upgrade` instead of `distro-sync` while we're in this state. Sorry for the trouble! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-15 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-15 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 1 proposed blocker (kinda...) and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240415T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-15 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-15 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 1 proposed blocker (kinda...) and 4 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240415T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-15 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-15 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240415T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-15 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-15 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240415T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F40 Final test request: NVIDIA RTX 3000 GPUs
Hi folks! See also the thread between AV and Frantisek ("changes to
nouveau driver in kernel 6.8.2 and higher?")
Can anyone else who has a similar NVIDIA GPU please try booting the
Workstation live image -
https://dl.fedoraproject.org/pub/alt/stage/40_RC-1.13/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-40-1.13.iso
- and see if it works for you? Please post results here or in the bug
report. Thanks!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net
--
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: Fedora 40 Candidate RC-1.12 Available Now!
On Wed, 2024-04-10 at 12:50 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate RC-1.12 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_RC_1.12_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Security_Lab An update on this: we have RC-1.13 coming in a few hours, but it just fixes some filenames and updates uboot-tools from the RC to the final release. Most 1.12 testing will be valid, so please continue to test 1.12 while 1.13 is cooking. At Go/No-Go tomorrow we'll decide whether to ship 1.13 based on the testing of both. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Candidate RC-1.12 Available Now!
On Wed, 2024-04-10 at 12:50 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate RC-1.12 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_RC_1.12_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_40_RC_1.12_Security_Lab An update on this: we have RC-1.13 coming in a few hours, but it just fixes some filenames and updates uboot-tools from the RC to the final release. Most 1.12 testing will be valid, so please continue to test 1.12 while 1.13 is cooking. At Go/No-Go tomorrow we'll decide whether to ship 1.13 based on the testing of both. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for people to be stewards of rpminspect-data-fedora
On Tue, 2024-04-09 at 14:14 -0700, Kevin Fenzi wrote: > On Tue, Apr 09, 2024 at 01:55:41PM -0400, David Cantrell wrote: > > Hello all, > > > > I am looking for multiple people to help be upstream stewards of the > > rpminspect-data-fedora project. This is a project that contains config > > files and rules for running rpminspect on Fedora builds. It is a package > > containing distribution policy. It needs people to look over it and review > > and merge contributions from other developers, do occassional releases, and > > ensure that it is updated as new releases of Fedora are started (and we get > > new dist tags). > > > > The project currently lives here: > > > > https://github.com/rpminspect/rpminspect-data-fedora > > > > But absolutely can move depending on the desires of the individuals who > > take over maintenance. I created these rules files in the data package for > > rpminspect so that different vendors can customize how rpminspect runs and > > reacts to findings. Maintenance of the rules is independent of the > > software maintenance. > > > > If you are interested, please email me directly and we can get going on the > > logistics. If you have general questions, feel free to ask here. > > I wonder if this isn't something we should have the QE or releng teams > manage... ie, adding new branch info (releng), adjusting tests (qe)? potentially we can be involved in this, yes. I did not have time to look at it yet because of F40 release. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-08 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-08 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 4 proposed blockers and 5 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240408T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-08 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-08 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 4 proposed blockers and 5 proposed freeze exceptions for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240408T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Silverblue 40 behind a proxy
On Tue, 2024-04-02 at 14:01 +, julien.togna...@gmail.com wrote: > Hello all, > > I wanted to try silverblue for a long time, and I have now the opportunity to > try it with the release of Fedora 40 beta. > > I noticed some issues regarding proxy configuration. > I first configured the proxy for my user via Gnome Settings. I used the full > url with schema like: > HTTP Proxy > http://myproxy:8080 > HTTPS Proxy > http://myproxy:8080 > > but then I noticed that my bash environment was automatically populated with > the relevant proxy environment variables (which is good), but then the schema > appeared twice ! > > env | grep proxy > https_proxy=http://http://myproxy:8080/ > HTTPS_PROXY=http://myproxy:8080/ > HTTP_PROXY=http://http://myproxy:8080/ > http_proxy=http://http://myproxy:8080/ This doesn't seem like it would be obviously Silverblue-specific. Have you seen if Workstation behaves the same? > > I also noticed that the rpm-ostreed service needed to know about the proxy, > So I tried to configured the proxy with systemd with: > > cat /etc/systemd/system.conf.d/50-proxy.conf > [Manager] > DefaultEnvironment="HTTP_PROXY=http://myproxy:8080 > DefaultEnvironment="http_proxy=http://myproxy:8080 > DefaultEnvironment="HTTPS_PROXY=http://myproxy:8080 > DefaultEnvironment="https_proxy=http://myproxy:8080 > DefaultEnvironment="NO_PROXY=int, *.int" > DefaultEnvironment="no_proxy=int, *.int" > > But it did not seem to make rpm-ostreed happy. > So I used instead: The first four lines there are missing a closing quotation mark. Perhaps that could be the problem? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-01 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-04-01 15:01:09 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 15:01:14) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:07:23) * INFO: no specific action items to follow up from last meeting (@adamwill:fedora.im, 15:08:18) * INFO: Beta was released last week, seems to be going fine (@adamwill:fedora.im, 15:10:10) * INFO: Final freeze is tomorrow (2024-04-02), first go/no-go date is 2024-04-11 (@adamwill:fedora.im, 15:10:52) * TOPIC: xz compromise discussion (@adamwill:fedora.im, 15:26:06) * INFO: there was a very significant compromise of the xz compression library. builds known to be potentially vulnerable to the currently-known exploit vector are 5.6.0-1.fc40, 5.6.0-2.fc40, 5.6.0- 1.fc41, 5.6.1-1.fc41 , 5.6.0-2.eln136 , 5.6.1-1.eln136 (@adamwill:fedora.im, 15:28:30) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:47:56) * INFO: FCOS test week starts today: http://fedoraproject.org/wiki/Test_Day:Fedora_40_CoreOS (@adamwill:fedora.im, 15:53:46) * INFO: kernel test week went ahead recently but was affected by a breakage in the app usually used for submitting results: https://pagure.io/fedora-qa/issue/771#comment-903726 (@adamwill:fedora.im, 15:54:07) * INFO: Podman test week went successfully with many results submitted: https://testdays.fedoraproject.org/events/183 (@adamwill:fedora.im, 15:54:35) * INFO: Upgrade test day, dnf5 upgrade test day, and Intel test day are coming soon (@adamwill:fedora.im, 15:55:03) * INFO: there will be video meetings as part of FCOS test week! see https://meet.google.com/uwb-enhy-evg?authuser=0 and https://hackmd.io/kwCRZ9fGTgWuMSh0HDwQJw?view (@adamwill:fedora.im, 15:56:26) * TOPIC: Open floor (@adamwill:fedora.im, 15:57:43) Meeting ended at 2024-04-01 16:05:51 Action items People Present (lines said) --- * @adamwill:fedora.im (58) * @geraldosimiao:matrix.org (22) * @nielsenb:fedora.im (15) * @sumantrom:fedora.im (13) * @jeffiscow:fedora.im (12) * @nhanlon:beeper.com (10) * @tablepc:matrix.org (9) * @zodbot:fedora.im (8) * @farribeiro:matrix.org (8) * @pboy:fedora.im (8) * @coremodule:fedora.im (4) * @meetbot:fedora.im (2) * @tflink:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Outage alert: openQA result reporting (affects critical path gating), nightly page updating, candidate compose nominations
On Mon, 2024-04-01 at 08:53 -0700, Adam Williamson wrote: > Hi folks! I just discovered this so I'm still investigating it, but > wanted to give a quick heads-up. > > It looks like the message consumers on openqa01 all broke on Saturday > when a fedora-messaging update landed. This affects a lot of things, > but by far the most important is that openQA test results are not > getting reported to resultsdb. This will be causing all critpath > updates to be stuck in gating. > > I am going to investigate this urgently, of course, and as a stopgap I > will manually trigger submission of all reports from the last couple of > days shortly. Very sorry for the inconvenience. > > Also affected: https://openqa.fedoraproject.org/nightlies.html and > .json are not getting updated, validation test events are not being > created, check-compose emails not being generated, possibly something > else I've forgotten. OK, I've found the cause of this: a 'modernization' of the fedora- messaging spec caused the hashbang of /usr/bin/fedora-messaging to change so it is run with `python3 -sP`, which causes python not to use libraries from /usr/local/lib . This was a surprising and unexpected change in a stable release update, and it may affect other folks too. See https://bugzilla.redhat.com/show_bug.cgi?id=2272526 . I'll work around this for now and wait to see what comes of the bug report. The consumers will gradually catch up with all the stuff they should have been doing for the last two days over the next little while. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Outage alert: openQA result reporting (affects critical path gating), nightly page updating, candidate compose nominations
On Mon, 2024-04-01 at 08:53 -0700, Adam Williamson wrote: > as a stopgap I > will manually trigger submission of all reports from the last couple of > days shortly. correction: I won't do this right away, as there would be a flood of duplicate reports if I did then fix the consumers. If I can't fix the consumers relatively soon I'll bite that bullet and do it, though. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Outage alert: openQA result reporting (affects critical path gating), nightly page updating, candidate compose nominations
Hi folks! I just discovered this so I'm still investigating it, but wanted to give a quick heads-up. It looks like the message consumers on openqa01 all broke on Saturday when a fedora-messaging update landed. This affects a lot of things, but by far the most important is that openQA test results are not getting reported to resultsdb. This will be causing all critpath updates to be stuck in gating. I am going to investigate this urgently, of course, and as a stopgap I will manually trigger submission of all reports from the last couple of days shortly. Very sorry for the inconvenience. Also affected: https://openqa.fedoraproject.org/nightlies.html and .json are not getting updated, validation test events are not being created, check-compose emails not being generated, possibly something else I've forgotten. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-01 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-01 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 3 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240401T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-01 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-04-01 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 3 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240401T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-04-01 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-01 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240401T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status and Final planning 3. xz compromise discussion 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-04-01 @ 15:00 UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-04-01 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240401T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status and Final planning 3. xz compromise discussion 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: YubiKey and GPG observations for Fedora Silverblue 40 beta
On Wed, 2024-03-27 at 19:45 +, Fraser Tajima wrote: > 1. YubiKey is still not released by Fedora after boot when the YubiKey is > inserted at the time of boot up with the result that `gpg --card-status` > fails (a problem from Fedora Silverblue 39). `systemctl restart pcscd' is > still needed to get `gpg --card-status` to recognise the YubiKey. Windows > does not do this. > 2. `~/.gnupg/scdaemon.conf` setup by user in Fedora 39 seems to be gone in > Fedora 40? Pinentry errors in Kleopatra are emitted in Fedora 40 even when > `gpg --card-status` is fine, requiring re-creation of the `scdaemon.conf` > file with the entry 'reader-port Yubico Yubi` and a reboot (after which > Kleopatra is back to normal). see > (https://support.yubico.com/hc/en-us/articles/360013714479-Troubleshooting-Issues-with-GPG) > > Fedora 40 beta is very impressive overall! Could you please report these as bugs against the relevant packages? They seem very domain-specific and you're more likely to get a useful response from a bug report that will be assigned to a person who knows something about this domain, I think :) Thanks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: toolbox not working after upgrade to 40
On Wed, 2024-03-27 at 15:32 +1100, Ian Laurie wrote: > On 3/27/24 3:11 PM, Ian Laurie wrote: > > Upstream bug: > > > > https://github.com/containers/toolbox/issues/1348 > > Given that there is an upstream bug, and my toolbox test day results > link to it, do you still want me to file a RHBZ as well? It's not generally necessary, but if we wanted to get this fix into F40 Final and it did not land before Final freeze on Tuesday, it would need an FE bug. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Silverblue 40 testing - just minor issues
On Wed, 2024-03-27 at 00:42 +, zn...@znmeb.net wrote: > OK - it's fixed. I switched images to > "registry.fedoraproject.org/fedora-toolbox:40" and it works. P.S.: you might > want to talk to the Distrobox maintainers about getting the Fedora 40 images > into the `distrobox create -C` listing. There is also https://quay.io/repository/fedora/fedora-toolbox , which should always contain the same as registry.fp.o/fedora-toolbox (they are synced by the same script). it seems the 'toolbx-images' repository is from https://github.com/toolbx-images/images , which is not under our control. Your MAC address issue is a feature: https://fedoraproject.org/wiki/Changes/StableSSIDMACAddress -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Can no longer submit kernel regression test results
On Thu, 2024-03-21 at 09:21 -0700, Kevin Fenzi wrote: > On Thu, Mar 21, 2024 at 09:26:07PM +0530, Sumantro Mukherjee wrote: > > On Thu, Mar 21, 2024 at 3:19 PM Ian Laurie wrote: > > > > > > Performing kernel regression tests: > > > > > > https://fedoraproject.org/wiki/QA:Testcase_kernel_regression > > > > > > I am getting errors submitting as follows: > > > > > > Your log file is being submitted... > > > FAS password: > > > Traceback (most recent call last): > > >File "/root/kernel-tests/./fedora_submit.py", line 43, in > > > submitclient.login( > > >File > > > "/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py", > > > line 303, in login > > > response = openid_login( > > > ^ > > >File > > > "/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py", > > > line 138, in openid_login > > > raise AuthError(output['message']) > > > fedora.client.AuthError: Invalid request > > > > > > This is new [for me] from today. Is this a known issue or is it just me? > > > > > > Ian > > > -- > > > Ian Laurie > > > FAS: nixuser | IRC: nixuser > > > TZ: Australia/Sydney > > > > Can you log in to https://kerneltest.fedoraproject.org/ > > and manually upload the logs? > > see if that works. > > kerneltest was just upgraded, so likely the > https://pagure.io/kernel-tests.git needs adjustments for the new auth. > ;( > > Sorry about that, we were not aware there was anything else using it... > > Logging in on the site should work fine. I see Justin stealth-updated it from medical leave: https://pagure.io/kernel-tests/c/6ca1b0d46fa3ece0a8b24bad49ef83da531576a0?branch=master has that now been re-deployed and everything, can we tell folks it's ready to try again? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: update of instatalles F40 Beta fails
On Sun, 2024-03-24 at 13:00 -0700, Samuel Sieb wrote: > On 3/24/24 03:17, Joachim Backes wrote: > > I upgraded my F39 (Workstation) to the most recent F40 Beta without any > > problems. > > > > Now, I tried to perform an update of this F40 by dnf, but this process > > fails with ot lot of failures. > > For details, see the attached file > > Either you got a mirror that's not fully updated yet or the 64-bit > package hasn't been pushed for some reason. No, it shouldn't be that. You shouldn't ever be able to get *some* packages from one push but not others. I suspect what's happening is the deepin-dock issue is preventing other x86_64 packages, including those that match these i686 ones, from being updated. At least, I'd want to resolve that problem first. The problem there is that deepin-dock-onboard-plugin was removed from the package, but the packager did not correctly have anything Obsolete it: https://bugzilla.redhat.com/show_bug.cgi?id=2254320 Joachim, can you remove deepin-dock-onboard-plugin and try the update again? Thanks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-25 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-25 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 3 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240325T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-25 @ 16:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-25 # Time: 16:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 3 proposed blockers for Final. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240325T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Can no longer submit kernel regression test results
On Thu, 2024-03-21 at 20:48 +1100, Ian Laurie wrote: > Performing kernel regression tests: > > https://fedoraproject.org/wiki/QA:Testcase_kernel_regression > > I am getting errors submitting as follows: > > Your log file is being submitted... > FAS password: > Traceback (most recent call last): >File "/root/kernel-tests/./fedora_submit.py", line 43, in > submitclient.login( >File > "/usr/lib/python3.12/site-packages/fedora/client/openidbaseclient.py", > line 303, in login > response = openid_login( > ^ >File > "/usr/lib/python3.12/site-packages/fedora/client/openidproxyclient.py", > line 138, in openid_login > raise AuthError(output['message']) > fedora.client.AuthError: Invalid request > > This is new [for me] from today. Is this a known issue or is it just me? Someone on Discourse did report problems submitting results via relval, which seems knda similar: https://discussion.fedoraproject.org/t/do-i-need-to-setup-more-permissions-to-upload-relval-results/109085/4 not totally sure, though. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Invitation to Contribute to Fedora Test Days: Podman Desktop Testing
On Wed, 2024-03-20 at 23:33 +1100, Philip Rhoades via devel wrote: > People, > > I am happy to do some testing but what is "Podman Desktop"? - I don't > see anything like that to install "dnf list" . . I have been on F40 for > a while now and am a regular user of Podman. It's a GUI for Podman, basically. https://podman-desktop.io/ . That page and the test cases for the test day should have more info on how to install and test it. The point of the test day is to make sure Podman Desktop, installed on Fedora in a recommended way, is working well with all the underlying bits in Fedora (podman itself and the things it depends on). -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: Fedora 40 Candidate Beta-1.8 Available Now!
On Tue, 2024-03-19 at 05:58 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.8 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.8_Summary Note on this: a 1.9 will be coming which should be identical to 1.8 except with Cinnamon and Budgie fixed (they were broken by the GNOME 46 FE in 1.8, and their images are missing). Testing on 1.8 is still useful and can mostly be transferred to 1.9, but you might want to wait 6-7 hours for 1.9 to show up before starting testing. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Candidate Beta-1.8 Available Now!
On Tue, 2024-03-19 at 05:58 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.8 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.8_Summary Note on this: a 1.9 will be coming which should be identical to 1.8 except with Cinnamon and Budgie fixed (they were broken by the GNOME 46 FE in 1.8, and their images are missing). Testing on 1.8 is still useful and can mostly be transferred to 1.9, but you might want to wait 6-7 hours for 1.9 to show up before starting testing. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-18 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-03-18 15:00:41 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 15:00:46) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 15:06:33) * INFO: no action items from last meeting (@adamwill:fedora.im, 15:06:50) * TOPIC: Fedora 40 status (including Beta testing plans) (@adamwill:fedora.im, 15:07:37) * INFO: Beta-1.7 is, so far, looking like a viable candidate, much better than anything we had last week (@adamwill:fedora.im, 15:08:14) * INFO: dustymabe had worrying results with the new shim in CoreOS testing - https://github.com/coreos/fedora-coreos-tracker/issues/1694 (@adamwill:fedora.im, 15:08:45) * INFO: there are some significant known differences in the contents of at least one image now built by kiwi but formerly built by imagefactory - the container base image built with kiwi is missing gzip and sudo - and we haven't yet checked the others out fully (thanks Jeremy Linton for checking container base) (@adamwill:fedora.im, 15:09:56) * INFO: it seems sdubby may be getting installed instead of grubby in far too many cases - https://bugzilla.redhat.com/show_bug.cgi?id=2269992 (@adamwill:fedora.im, 15:10:22) * INFO: there's an update for GNOME 46 final builds of the core components (gnome-shell etc.) that we *may* want to pull in as an FE (@adamwill:fedora.im, 15:11:15) * INFO: travier wants to revert bootupd again - https://pagure.io/workstation-ostree-config/pull-request/498 (@adamwill:fedora.im, 15:11:42) * INFO: there is also a report of basic graphics mode not working - https://bugzilla.redhat.com/show_bug.cgi?id=2270128 (@adamwill:fedora.im, 15:18:56) * INFO: the pi 400 blocker is still outstanding - https://bugzilla.redhat.com/show_bug.cgi?id=2267968 . We did the candidate compose on the theory folks may want to waive it, but we should still try and get it fixed (@adamwill:fedora.im, 15:24:31) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 15:39:49) * INFO: Fedora IoT test week is this week: https://fedoraproject.org/wiki/Test_Day:2024-03-18_Fedora_40_IoT_Edition#Prerequisites_for_Test_Day and https://testdays.fedoraproject.org/events/178 (@adamwill:fedora.im, 15:41:21) * INFO: Podman Desktop test day with be 2024-03-20: https://fedoraproject.org/wiki/Test_Day:2024-03-20_Podman_Desktop (@adamwill:fedora.im, 15:42:43) * INFO: Podman 5 test day will be 2024-03-21: https://fedoraproject.org/wiki/Test_Day:2024-03-21_Podman_5 (@adamwill:fedora.im, 15:42:56) * INFO: Toolbx test day will be 2024-03-27: https://fedoraproject.org/wiki/Test_Day:2024-03-27_Toolbx (@adamwill:fedora.im, 15:43:13) * TOPIC: Open floor (@adamwill:fedora.im, 15:47:20) Meeting ended at 2024-03-18 15:53:46 Action items People Present (lines said) --- * @adamwill:fedora.im (49) * @nielsenb:fedora.im (13) * @kparal:matrix.org (9) * @geraldosimiao:matrix.org (9) * @nhanlon:beeper.com (5) * @zodbot:fedora.im (4) * @meetbot:fedora.im (2) * @tflink:fedora.im (2) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-18 @ **15:00** UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-03-18 # Time: **15:00** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. As a reminder, clocks went forward in North America last week, so the meeting is an hour earlier in UTC than it was before. If you have changed your clocks forward recently the meeting will be at the same local time as before, it not it will be earlier. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240318T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status (including Beta testing plans) 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-18 @ **15:00** UTC - Fedora Quality Meeting
# Fedora Quality Assurance Meeting # Date: 2024-03-18 # Time: **15:00** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. As a reminder, clocks went forward in North America last week, so the meeting is an hour earlier in UTC than it was before. If you have changed your clocks forward recently the meeting will be at the same local time as before, it not it will be earlier. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting=20240318T15=1440=1 If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status (including Beta testing plans) 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-04 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-03-04 16:00:47 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:00:51) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:07:44) * INFO: there are no action items from the previous meeting (@adamwill:fedora.im, 16:08:09) * TOPIC: Fedora 40 status (@adamwill:fedora.im, 16:16:06) * INFO: the anaconda webUI Change got deferred again, to Fedora 41 - https://pagure.io/fesco/issue/3169#comment-896412 (@adamwill:fedora.im, 16:16:58) * INFO: I have reverted/deferred all the wiki changes related to this, and the official image is back to behaving as it did in f39 and earlier (the osbuild image is still webui ATM, that should be fixed soon) (@adamwill:fedora.im, 16:17:55) * INFO: other than that, we're mostly looking solid for Fedora 40, though there's some concerning stuff on the blocker list that's relatively out of our hands - missing artwork, still no new signed shim build (unless one showed up this morning) (@adamwill:fedora.im, 16:24:01) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:31:48) * INFO: i18n Test Day is coming up today or tomorrow (2024-03-05): https://fedoraproject.org/wiki/Test_Day:2024-03-05_I18N_Test_Day , https://testdays.fedoraproject.org/events/177 (@adamwill:fedora.im, 16:37:00) * TOPIC: Open floor (@adamwill:fedora.im, 16:37:56) Meeting ended at 2024-03-04 16:46:27 Action items People Present (lines said) --- * @adamwill:fedora.im (38) * @nielsenb:fedora.im (9) * @pboy:fedora.im (6) * @zodbot:fedora.im (3) * @meetbot:fedora.im (2) * @kparal:matrix.org (1) * @tflink:fedora.im (1) * @nhanlon:beeper.com (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-18 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-18 # Time: ** 16:00 ** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 1 proposed freeze exception for Beta, and 10 proposed blockers for Final. As a reminder, clocks went forward in North America last week, so the meeting is an hour earlier in UTC than it was before. If you have changed your clocks forward recently the meeting will be at the same local time as before, it not it will be earlier. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240318T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-18 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-18 # Time: ** 16:00 ** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 1 proposed freeze exception for Beta, and 10 proposed blockers for Final. As a reminder, clocks went forward in North America last week, so the meeting is an hour earlier in UTC than it was before. If you have changed your clocks forward recently the meeting will be at the same local time as before, it not it will be earlier. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240318T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Candidate Beta-1.4 Available Now!
On Wed, 2024-03-13 at 19:26 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.4 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 Sorry for the flood of composes, folks. At this point we still have open issues to address, including https://bugzilla.redhat.com/show_bug.cgi?id=2269385 , so there's almost certainly going to be a 1.5 at some point. Testing on pretty much any of the composes so far is still welcome and useful and you can pretty much assume if you hit something that looks like a significant bug in any of them you should report it and propose it as a blocker if appropriate. We're going to reassess where we stand later tonight (US time) and then tomorrow morning (again US time) to decide if there's any realistic prospect of a go decision on Thursday, and run a new candidate if so. Otherwise we may hold fire for a bit to let things settle and land some FEs. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: Fedora 40 Candidate Beta-1.4 Available Now!
On Wed, 2024-03-13 at 19:26 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.4 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 Sorry for the flood of composes, folks. At this point we still have open issues to address, including https://bugzilla.redhat.com/show_bug.cgi?id=2269385 , so there's almost certainly going to be a 1.5 at some point. Testing on pretty much any of the composes so far is still welcome and useful and you can pretty much assume if you hit something that looks like a significant bug in any of them you should report it and propose it as a blocker if appropriate. We're going to reassess where we stand later tonight (US time) and then tomorrow morning (again US time) to decide if there's any realistic prospect of a go decision on Thursday, and run a new candidate if so. Otherwise we may hold fire for a bit to let things settle and land some FEs. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Candidate Beta-1.3 Available Now!
On Wed, 2024-03-13 at 13:24 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.3 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 For Deeply Technical Release Engineering Reasons (somebody forgot to update the right config file), 1.3 is effectively identical to 1.2. Please test either at your leisure, we'll treat results for both as interchangeable. There will be a 1.4 soon which should hopefully, really, really, really be built with kiwi and osbuild. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: Fedora 40 Candidate Beta-1.3 Available Now!
On Wed, 2024-03-13 at 13:24 +, rawh...@fedoraproject.org wrote: > According to [the schedule][1], Fedora 40 Candidate Beta-1.3 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 For Deeply Technical Release Engineering Reasons (somebody forgot to update the right config file), 1.3 is effectively identical to 1.2. Please test either at your leisure, we'll treat results for both as interchangeable. There will be a 1.4 soon which should hopefully, really, really, really be built with kiwi and osbuild. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Candidate Beta-1.2 Available Now!
On Wed, 2024-03-13 at 04:50 +, rawh...@fedoraproject.org wrote: > According to the schedule [1], Fedora 40 Candidate Beta-1.2 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 A quick heads-up here: a Beta-1.3 compose will likely follow shortly, because we wanted to build some Beta images using new tools - see https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages and https://fedoraproject.org/wiki/Changes/ArmMinimalImageOSBuild - but these were mistakenly not used for the Beta-1.2 compose, the images were all built with the older tool instead. We'll likely try and do a Beta-1.3 which should be identical to Beta-1.2 but with the Cloud, Container and ARM minimal disk images built with the new tools instead of the old one. Testing of both candidates will be useful. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: Fedora 40 Candidate Beta-1.2 Available Now!
On Wed, 2024-03-13 at 04:50 +, rawh...@fedoraproject.org wrote: > According to the schedule [1], Fedora 40 Candidate Beta-1.2 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 A quick heads-up here: a Beta-1.3 compose will likely follow shortly, because we wanted to build some Beta images using new tools - see https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages and https://fedoraproject.org/wiki/Changes/ArmMinimalImageOSBuild - but these were mistakenly not used for the Beta-1.2 compose, the images were all built with the older tool instead. We'll likely try and do a Beta-1.3 which should be identical to Beta-1.2 but with the Cloud, Container and ARM minimal disk images built with the new tools instead of the old one. Testing of both candidates will be useful. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 39 to 40 upgrades breaks yelp
On Sat, 2024-03-09 at 22:05 +1100, Ian Laurie wrote: > On 3/6/24 18:22, Adam Williamson wrote: > > > The problem is likely *somewhere* in the 3D > > rendering stack, from mutter down to the kernel. > > To cut a [very] long story short, I have "fixed" the issue on both a > native Rawhide box AND a native Fedora 40 beta branch box by > uninstalling > mesa-vulkan-drivers-24.0.0-2.fc40.x86_64/mesa-vulkan-drivers-24.0.2-1.fc41.x86_64. > > What I am not certain about is if there will be any negative > consequences of doing that. Can you please file a bug against mesa explaining the problem, how you worked around it, and whatever information you used along the way? Thanks a lot! I believe this may mean you're falling back on an older acceleration framework or even software acceleration, but IMBW. I don't keep super up to date on all the 3D acceleration stuff. Worth noting I'm using Intel hardware here too, though, and it's not affecting that... -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-11 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-11 # Time: ** 16:00 ** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 2 proposed blockers and 5 proposed freeze exceptions for Beta, and 4 proposed blockers for Final. Please note that summer time starts in most of North America on Sunday, and we follow that time for these meetings, so the meeting time in UTC has changed. If you put your clocks forward this Sunday, the meeting will be at the same local time as it was last week. If you do not, the meeting will be one hour *earlier* than it was last week. You can always run `date -u` to see the current UTC time and check, if you're not sure. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240311T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-11 @ ** 16:00 ** UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-11 # Time: ** 16:00 ** UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 2 proposed blockers and 5 proposed freeze exceptions for Beta, and 4 proposed blockers for Final. Please note that summer time starts in most of North America on Sunday, and we follow that time for these meetings, so the meeting time in UTC has changed. If you put your clocks forward this Sunday, the meeting will be at the same local time as it was last week. If you do not, the meeting will be one hour *earlier* than it was last week. You can always run `date -u` to see the current UTC time and check, if you're not sure. Here is a handy link which should show you the meeting time in your local time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+40+Blocker+review+meeting=20240311T16=1440=2 The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Nothing happened from Fedora-Everything-netinst-aarch64-Rawhide-20240305.n.0.iso
On Thu, 2024-03-07 at 10:13 +, Liang Qi wrote: > Tried with some other options during install, I can log into GNOME x11 now. > > BTW, KDE 6 haven't landed in Rawhide, right? Yes, it has. From your other mail and this one, it kinda sounds like you have issues with Wayland sessions, maybe? Are you using GNOME on X.org because GNOME on Wayland isn't working? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 39 to 40 upgrades breaks yelp
On Wed, 2024-03-06 at 13:07 +1100, Ian Laurie wrote: > On 3/5/24 9:09 AM, Ian Laurie wrote: > > > > zuke$ `GSK_RENDERER=cairo yelp` > > I/O error : Attempt to load network entity > > http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd > > I/O error : Attempt to load network entity > > http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd > > I/O error : Attempt to load network entity > > http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd > > zuke$ > > > > > > Atril brings up a blank yelp when you access help. > > > > My main concern isn't really yelp but rather what else may be broken > > that I've not struck yet, particularly on the first system that shows > > rather scary errors about missing stuff. > Well this is interesting... If I XRDP into my account on zuke, yelp > works in the XRDP session. Just fails on the console. > > In VirtualBox, activating VirtualBox 3D mode in the display settings > breaks yelp. > > Since yelp is a GNOME application this is starting to feel like another > GNOME/Wayland breakage to me. It has to be setup specific to some extent, yelp runs fine here (and in openQA). VirtualBox having graphics stack issues wouldn't be the first time that's happened, there is only a limited amount we can do about it on the guest OS side. The docbook errors relate to content, they have nothing to do with failure to render. The problem is likely *somewhere* in the 3D rendering stack, from mutter down to the kernel. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 39 to 40 upgrades breaks yelp
On Mon, 2024-03-04 at 17:56 +1100, Ian Laurie wrote: > On 3/3/24 16:33, Ian Laurie wrote: > > On 3/3/24 15:19, Ian Laurie wrote: > > > After upgrade to Fedora 40, applications in Xfce that use yelp for help > > > (GParted, Atril etc) can no longer bring up content. > > In VirtualBox VMs I can make yelp work again by disabling 3D > acceleration in the VirtualBox display settings. The fresh VM (not > upgraded) worked because coincidentally 3D was turned off. > > This sort of makes sense because GNOME no longer runs with 3D enabled in > VirtualBox, with all sorts of display artifacts, and lockups. > > However... I can't do that on native systems where yelp is still broken. > > A bit lost where to go from here. Does `GSK_RENDERER=cairo yelp` help? See https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 for context. Having said that, yelp works OK here without special prodding (bare metal system, Intel graphics). -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-19 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-02-19 16:00:35 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:00:41) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:12:10) * INFO: "adamw to email marian about LVM bugs" - I did that, and it looks like Peter Boy got some further information about why things are the way they are and is working on a plan to deal with them (this is about https://bugzilla.redhat.com/show_bug.cgi?id=2247872 as it affects Server on ARM) (@adamwill:fedora.im, 16:13:14) * INFO: further to above: Peter Boy is trying to work on required changes but needs some information from the ARM team (@adamwill:fedora.im, 16:19:50) * INFO: "adamw to try and talk to mcsontos about https://bugzilla.redhat.com/show_bug.cgi?id=2258764; - I think this was a clarification of the first action item, actually, so the result is the same: we've got a bit further along but still trying to work on it (@adamwill:fedora.im, 16:22:26) * INFO: "adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?)" - well, I didn't write anything down in any SOPs or anything, but I have been sending meeting announcements to discourse as well as mailing lists for the last couple of weeks (@adamwill:fedora.im, 16:23:13) * TOPIC: Fedora 40 status, including anaconda web UI test planning (@adamwill:fedora.im, 16:32:15) * INFO: the "web UI" new interface for anaconda (the installer) that is used on Workstation live images in Fedora 40 changed its backend for custom partitioning from blivet-gui (the same tool you can launch from the "gtk UI" current installer interface, as "Advanced Custom") to cockpit's storage backend (which has never been used in an installer context before). this landed in the anaconda package on 2023- 02-07 and in a successful compose on 2023-02-10, so it is rather late (@adamwill:fedora.im, 16:33:59) * INFO: there are a few places this is being discussed, including https://bugzilla.redhat.com/show_bug.cgi?id=2263964 and https://pagure.io/fesco/issue/3169 . We have a ticket for updating the criteria and test cases at https://pagure.io/fedora-qa/issue/763 and a ticket for atest day at https://pagure.io/fedora-qa/issue/764 (@adamwill:fedora.im, 16:35:16) * INFO: the "web UI" new interface for anaconda (the installer) that is used on Workstation live images in Fedora 40 changed its backend for custom partitioning from blivet-gui (the same tool you can launch from the "gtk UI" current installer interface, as "Advanced Custom") to cockpit's storage backend (which has never been used in an installer context before). this landed in the anaconda package on 2024- 02-07 and in a successful compose on 2024-02-10, so it is rather late (@adamwill:fedora.im, 16:35:28) * INFO: please test the new UI if you can, file any bugs you hit, and mark them as blocking bug 2231339 (@adamwill:fedora.im, 16:50:00) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:55:12) * INFO: the anaconda webui storage Test Week will be coming soon, tentative start date 2024-02-22 - follow https://pagure.io/fedora-qa/issue/764 for that (@adamwill:fedora.im, 16:56:04) * INFO: The KDE Plasma 6 happened https://testdays.fedoraproject.org/events/174 .. good amount of test runs :) (@adamwill:fedora.im, 16:56:59) * INFO: GNOME 46 Desktop and Core Apps happening now https://testdays.fedoraproject.org/events/175 (@adamwill:fedora.im, 16:57:06) * INFO: i8n will start March 5th https://testdays.fedoraproject.org/events/177 (@adamwill:fedora.im, 16:59:33) * TOPIC: Open floor (@adamwill:fedora.im, 16:59:37) Meeting ended at 2024-02-19 18:19:05 Action items People Present (lines said) --- * @adamwill:fedora.im (64) * @sumantrom:fedora.im (18) * @pboy:fedora.im (8) * @kparal:matrix.org (8) * @lruzicka:matrix.org (7) * @zodbot:fedora.im (2) * @meetbot:fedora.im (2) * @linuxfriend01:fedora.im (1) * @coremodule:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-05 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-02-05 16:01:02 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:01:05) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:11:13) * INFO: "adamw to contact bootloader folks about plans for shim in F40" - I did that. haven't heard anything definitive back yet, but I tried. Gerd Hoffman wrote back that the upstream shim repo got a bunch of updates which to him suggests there'll be a new release soon, but that's it (@adamwill:fedora.im, 16:11:59) * INFO: "adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?)" - we haven't entirely got around to this yet, sorry. we'll keep trying to get to it (@adamwill:fedora.im, 16:12:24) * INFO: "adamw to file a ticket suggesting a Test Day for https://fedoraproject.org/wiki/Changes/ModernizeLiveMedia; - done (and I *definitely* did it soon after the last meeting and not five minutes ago when I read the minutes) - https://pagure.io/fedora-qa/issue/762 (@adamwill:fedora.im, 16:12:47) * TOPIC: Fedora 40 check-in (@adamwill:fedora.im, 16:18:59) * TOPIC: Fedora 40 check-in (@bittin:fedora.im, 16:18:59) * INFO: Fedora 40 will branch on Tuesday 13th, hold on to your hats (@adamwill:fedora.im, 16:27:04) * INFO: the deadline for changes to be 'testable' is the same date (Tuesday 13th) (@adamwill:fedora.im, 16:27:47) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:37:29) * INFO: we had kernel 6.7 test week recently, and Plasma 6 test week is winding up today - last chance to get your tests in at https://testdays.fedoraproject.org/events/174 ) (@adamwill:fedora.im, 16:38:22) * INFO: Fedora i18n/l10n test week has a suggested week of the first week in March 2024 (@adamwill:fedora.im, 16:38:35) * INFO: https://pagure.io/i18n/issue/184#comment-894361 (@bittin:fedora.im, 16:38:46) * TOPIC: Open floor (@adamwill:fedora.im, 16:40:45) * ACTION: adamw to email marian about LVM bugs (@bittin:fedora.im, 16:51:04) * ACTION: adamw to try and talk to mcsontos about https://bugzilla.redhat.com/show_bug.cgi?id=2258764 (@adamwill:fedora.im, 16:51:08) Meeting ended at 2024-02-05 16:57:26 Action items * adamw to email marian about LVM bugs * adamw to try and talk to mcsontos about https://bugzilla.redhat.com/show_bug.cgi?id=2258764 People Present (lines said) --- * @adamwill:fedora.im (67) * @bittin:fedora.im (31) * @pboy:fedora.im (14) * @kparal:matrix.org (9) * @zodbot:fedora.im (5) * @frantisekz:fedora.im (5) * @coremodule:fedora.im (2) * @nhanlon:beeper.com (2) * @meetbot:fedora.im (2) * @tflink:fedora.im (1) * @salimma:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-01-22 - Fedora Quality Meeting - Minutes
= # #meeting:fedoraproject.org: Quality = Meeting started by @adamwill:fedora.im at 2024-01-22 16:01:52 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:02:00) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:09:27) * INFO: "adamw to contact bootloader folks about plans for shim in F40" - oops, I didn't get to this yet. I'll do it today (@adamwill:fedora.im, 16:10:25) * ACTION: adamw to contact bootloader folks about plans for shim in F40 (@adamwill:fedora.im, 16:10:31) * INFO: "adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?)" - yeah, uh, we didn't do that yet either, did we? at least I can share the blame for that! (@adamwill:fedora.im, 16:10:58) * ACTION: adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?) (@adamwill:fedora.im, 16:11:14) * INFO: "adamw to make sure sumantro is around next time" - he was intending to, but had an emergency and couldn't make it, I have an update from him for later (@adamwill:fedora.im, 16:15:54) * TOPIC: Fedora 40 Change review and check-in (@adamwill:fedora.im, 16:16:10) * INFO: F40 mass rebuild is in progress right now (@adamwill:fedora.im, 16:16:58) * INFO: there is a major bug affecting XFS installs to BIOS (including default Server installs) - https://bugzilla.redhat.com/show_bug.cgi?id=2259266 (@adamwill:fedora.im, 16:17:20) * INFO: all updates are currently failing openQA tests apparently due to accounts.fp.o being down (the web browser test uses it), I will rerun tests once it's back up, if it stays down for a long time I'll figure out a workaround (@adamwill:fedora.im, 16:18:11) * INFO: boost soname bump landed right before the mass rebuild, keep an eye out for any changes from that (@adamwill:fedora.im, 16:18:50) * INFO: accepted Changes are at https://fedoraproject.org/wiki/Releases/40/ChangeSet (@adamwill:fedora.im, 16:22:56) * ACTION: adamw to file a ticket suggesting a Test Day for https://fedoraproject.org/wiki/Changes/ModernizeLiveMedia (@adamwill:fedora.im, 16:35:29) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:42:27) * INFO: kernel test week is running 2021-01-21 to 2024-01-28 - https://fedoraproject.org/wiki/Test_Day:2024-01-21_Kernel_6.7_Test_Week and https://testdays.fedoraproject.org/events/173 (@adamwill:fedora.im, 16:43:19) * INFO: KDE/Plasma 6.0 test week will be 2024-01-29 through 2024- 02-05 - https://fedoraproject.org/wiki/Test_Day:2024-01-29_KDE_Plasma_6_Test_Week (@adamwill:fedora.im, 16:43:57) * TOPIC: Open floor (@adamwill:fedora.im, 16:49:33) * INFO: test info (@adamwill:fedora.im, 17:01:34) Meeting ended at 2024-01-22 19:26:56 Action items * adamw to contact bootloader folks about plans for shim in F40 * adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?) * adamw to file a ticket suggesting a Test Day for https://fedoraproject.org/wiki/Changes/ModernizeLiveMedia People Present (lines said) --- * @adamwill:fedora.im (85) * @bittin:fedora.im (28) * @nhanlon:beeper.com (16) * @geraldosimiao:matrix.org (14) * @coremodule:fedora.im (9) * @zodbot:fedora.im (7) * @kparal:matrix.org (6) * @tflink:fedora.im (5) * @farribeiro:matrix.org (5) * @meetbot:fedora.im (3) * @conan_kudo:matrix.org (1) * @amoloney:fedora.im (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-01-08 - Fedora QA Meeting - Minutes
= # #meeting:fedoraproject.org: fedora-qa = Meeting started by @adamwill:fedora.im at 2024-01-08 16:01:56 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:02:06) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:08:09) * INFO: no action items from the previous meeting, does anybody have anything that wasn't marked as an action item? (@adamwill:fedora.im, 16:08:35) * INFO: no action items from the previous meeting (@adamwill:fedora.im, 16:11:08) * TOPIC: Fedora 40 check-in (@adamwill:fedora.im, 16:11:23) * INFO: we have 4 proposed blockers and 6 accepted blockers for F40 (though 4 of the accepted blockers are image size bugs and we're in the process of lifting those limits). would be good for folks to vote on the proposals (@adamwill:fedora.im, 16:12:25) * ACTION: adamw to contact bootloader folks about plans for shim in F40 (@adamwill:fedora.im, 16:12:36) * INFO: there are still four more change proposals to come as they were proposed before deadlines over the holidays (@adamwill:fedora.im, 16:22:04) * INFO: in general F40 seems to be in solid shape at the moment, no major breakages (@adamwill:fedora.im, 16:38:43) * TOPIC: Communications overhaul: Discourse? (@adamwill:fedora.im, 16:42:51) * ACTION: adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?) (@adamwill:fedora.im, 17:01:20) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 17:05:34) * INFO: tabled as sumantro is not around (@adamwill:fedora.im, 17:05:54) * ACTION: adamw to make sure sumantro is around next time (@adamwill:fedora.im, 17:06:00) * TOPIC: Open floor (@adamwill:fedora.im, 17:06:05) Meeting ended at 2024-01-08 17:10:36 Action items * adamw to contact bootloader folks about plans for shim in F40 * adamw and kparal to come up with a plan to start directing 'official' messages to discourse as well as mailing lists (and possibly having the mailing list versions encourage use of discourse?) * adamw to make sure sumantro is around next time People Present (lines said) --- * @adamwill:fedora.im (75) * @kparal:matrix.org (20) * @nielsenb:fedora.im (17) * @amoloney:fedora.im (10) * @tflink:fedora.im (6) * @lruzicka:matrix.org (5) * @zodbot:fedora.im (4) * @pboy:fedora.im (3) * @nhanlon:beeper.com (2) * @meetbot:fedora.im (2) * @coremodule:fedora.im (2) * @nirik:matrix.scrye.com (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-12-11 - Fedora QA Meeting - Minutes
= # #meeting:fedoraproject.org: fedora-qa = Meeting started by @adamwill:fedora.im at 2023-12-11 16:00:33 Meeting summary --- * TOPIC: Roll Call (@adamwill:fedora.im, 16:00:49) * TOPIC: Previous meeting follow-up (@adamwill:fedora.im, 16:06:49) * INFO: "adamw to consider moving the meeting back to Matrix next time" - well, seems like that's working out so far :) (@adamwill:fedora.im, 16:07:21) * TOPIC: Fedora 40 check-in (@adamwill:fedora.im, 16:27:31) * INFO: 40 is looking mostly fine right now, tests are mostly passing with a few known issues and the mysterious GNOME bug where clicking on stuff in openQA sometimes doesn't work. please remember to keep testing the new installer UI (@adamwill:fedora.im, 16:35:08) * TOPIC: Communications overhaul: Discourse and Matrix? (@adamwill:fedora.im, 16:35:11) * TOPIC: Test Day / community event status (@adamwill:fedora.im, 16:50:41) * INFO: let's skip this for now as sumantro couldn't make it (family issues) (@adamwill:fedora.im, 16:50:53) * TOPIC: Open floor (@adamwill:fedora.im, 16:50:58) Meeting ended at 2023-12-11 16:57:44 Action items People Present (lines said) --- * @adamwill:fedora.im (93) * @nielsenb:fedora.im (53) * @nhanlon:beeper.com (11) * @kparal:matrix.org (8) * @lruzicka:matrix.org (4) * @coremodule:fedora.im (3) * @tflink:fedora.im (2) * @meetbot:fedora.im (2) * @ujjwalmahar:matrix.org (1) * @nscnt:matrix.org (1) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-11-27 - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 16:00:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2023-11-13/fedora-qa.2023-11-13-16.00.log.html . Meeting summary --- * Roll Call (adamw, 16:00:37) * Previous meeting follow-up (adamw, 16:11:22) * no action items from previous meeting (adamw, 16:11:41) * Fedora 39 and Fedora 40 check-ins (adamw, 16:12:57) * Fedora 39 was released last week, the release seems to be going over well (adamw, 16:13:10) * thanks to kparal for working on the common issues and everybody for all the testing of this release (adamw, 16:13:24) * also thanks to kparal96 (and kparals 2 through 95) (adamw, 16:15:52) * Fedora 40 seems mostly fine at this point, except for an annoying bug (possibly in mesa?) which is causing frequent failures in some openQA GNOME tests...now I'm back from vacation I'll be looking into that (adamw, 16:16:41) * Communications overhaul: Discourse and Matrix? (adamw, 16:27:17) * LINK: https://discussion.fedoraproject.org/tag/quality-team (adamw, 16:31:52) * adamw is planning to propose making matrix the official team chat for all purposes (including meetings as soon as the matrix bot is usable) and moving from mailing lists to discourse for async discussion. will send more detailed proposals out later (adamw, 16:37:15) * LINK: https://fedoramagazine.org/join-the-conversation/ seems to exist (adamw, 16:44:13) * Test Day / community event status (adamw, 16:47:36) * we are in the kernel 6.6 test week, so please help out with that: https://fedoraproject.org/wiki/Test_Day:2023-11-12_Kernel_6.6_Test_Week (adamw, 16:48:13) * the call for Fedora 40 Test Days is out: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/M2RH5A5CZEAEKX3UFW6JEKU6DEYXLXHE/ (adamw, 16:48:54) * Open floor (adamw, 16:50:16) * LINK: https://fedoraproject.org/wiki/Test_Day:2023-11-12_Kernel_6.6_Test_Week guess this week Kernel 6.6 for Fedora 39 and 38 is being tested (luna_, 16:56:45) Meeting ended at 17:15:01 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (60) * kparal (17) * luna_ (10) * pboy (9) * The_Exorcist (9) * zodbot (7) * coremodule (3) * kparal96 (2) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-11-13 - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 16:00:25 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2023-11-13/fedora-qa.2023-11-13-16.00.log.html . Meeting summary --- * Roll Call (adamw, 16:00:37) * Previous meeting follow-up (adamw, 16:11:22) * no action items from previous meeting (adamw, 16:11:41) * Fedora 39 and Fedora 40 check-ins (adamw, 16:12:57) * Fedora 39 was released last week, the release seems to be going over well (adamw, 16:13:10) * thanks to kparal for working on the common issues and everybody for all the testing of this release (adamw, 16:13:24) * also thanks to kparal96 (and kparals 2 through 95) (adamw, 16:15:52) * Fedora 40 seems mostly fine at this point, except for an annoying bug (possibly in mesa?) which is causing frequent failures in some openQA GNOME tests...now I'm back from vacation I'll be looking into that (adamw, 16:16:41) * Communications overhaul: Discourse and Matrix? (adamw, 16:27:17) * LINK: https://discussion.fedoraproject.org/tag/quality-team (adamw, 16:31:52) * adamw is planning to propose making matrix the official team chat for all purposes (including meetings as soon as the matrix bot is usable) and moving from mailing lists to discourse for async discussion. will send more detailed proposals out later (adamw, 16:37:15) * LINK: https://fedoramagazine.org/join-the-conversation/ seems to exist (adamw, 16:44:13) * Test Day / community event status (adamw, 16:47:36) * we are in the kernel 6.6 test week, so please help out with that: https://fedoraproject.org/wiki/Test_Day:2023-11-12_Kernel_6.6_Test_Week (adamw, 16:48:13) * the call for Fedora 40 Test Days is out: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/M2RH5A5CZEAEKX3UFW6JEKU6DEYXLXHE/ (adamw, 16:48:54) * Open floor (adamw, 16:50:16) * LINK: https://fedoraproject.org/wiki/Test_Day:2023-11-12_Kernel_6.6_Test_Week guess this week Kernel 6.6 for Fedora 39 and 38 is being tested (luna_, 16:56:45) Meeting ended at 17:15:01 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (60) * kparal (17) * luna_ (10) * pboy (9) * The_Exorcist (9) * zodbot (7) * coremodule (3) * kparal96 (2) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-10-16 - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 15:00:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2023-10-16/fedora-qa.2023-10-16-15.00.log.html . Meeting summary --- * Roll Call (adamw, 15:00:20) * previous meeting follow-up (adamw, 15:15:01) * "adamw to talk to IoT team and releng and websites about ensuring an IoT compose is ready for beta release" - I did that, and there was one (adamw, 15:15:48) * Fedora 39 status (adamw, 15:18:35) * Go/No-Go is scheduled for Thursday (adamw, 15:18:50) * there's a blocker review meeting at the top of the hour in #fedora-blocker-review . we still have blockers (adamw, 15:19:06) * LINK: https://koji.fedoraproject.org/koji/packageinfo?packageID=8 https://bodhi.fedoraproject.org/updates/?packages=kernel but asking jforbes in #fedora-kernel is better i think (luna_, 15:34:09) * Test Day / community event status (adamw, 15:39:42) * several test days happened since the last meeting, see https://testdays.fedoraproject.org/events (adamw, 15:43:06) * thanks to all who attended (adamw, 15:43:16) * there are no more planned in the near future as f39 schedule is ending (adamw, 15:43:25) * Open floor (adamw, 15:46:41) Meeting ended at 15:53:32 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (63) * luna_ (17) * zodbot (12) * geraldosimiao (12) * coremodule (7) * nielsenb (5) * jailbreak (4) * thebeanogamer (4) * tflink (2) * kparal (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-04 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-03-04 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-04 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-03-04 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-03-04 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-04 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 2 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-03-04 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-03-04 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 2 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora-40-20240217.n.0 won't install
On Thu, 2024-02-29 at 07:02 +1100, Ian Laurie wrote: > On 2/21/24 10:03, Ian Laurie wrote: > > The two fixes for this appear to be frozen in bodhi despite it being a > beta blocker bug. > > https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d99498b67 > https://bodhi.fedoraproject.org/updates/FEDORA-2024-682d6680ce They aren't, Bodhi just shows that box on all updates for a frozen release. It's not smart enough to know if they're blocker or FE fixes. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-26 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-02-26 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 7 proposed blockers and 4 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. I'll be on vacation on Monday, so Frantisek Zatloukal will be running the meeting, thanks Franta! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-02-26 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-02-26 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 7 proposed blockers and 4 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. I'll be on vacation on Monday, so Frantisek Zatloukal will be running the meeting, thanks Franta! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora-40-20240217.n.0 won't install
On Tue, 2024-02-20 at 16:29 +1100, Ian Laurie wrote: > On 2/19/24 10:46 AM, Ian Laurie wrote: > > On 2/18/24 2:33 PM, Ian Laurie wrote: > > > > [snip] > > > Apparently I'm not the only one: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2244744 > > > > > > > I tried to install a Fedora 40 ISO in VirtualBox on a Windows 10 host > > and the exact same failure occurred. > > > > I've updated the BZ but it is concerning the original reporter reported > > this blanket failure back in October 2023 and nothing has happened. > > > > This will be a show stopper for anyone running Fedora in VirtualBox, > > which would be the most common platform for Windows users because they > > don't have the QEMU/KVM option. > > Adding to the mystery, the Xfce Live images will install. I booted and > installed to HD the following images into a VirtualBox VM: > > Fedora-Xfce-Live-x86_64-40-20240219.n.0.iso > Fedora-Xfce-Live-x86_64-Rawhide-20240219.n.0.iso > > This doesn't prove anything, but it makes this less likely to be a > VirtualBox problem and more likely to be a compose issue with the > "Everything" ISO images. It doesn't really mean that. The difference is that live image installs perform no package transactions. They just, more or less, dump the live image onto the target disk. An install from the network install images actually downloads RPMs and performs a package transaction, and it's during this that you're hitting the problem. It's natural the same would not happen on a live install. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-02-19 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-02-19 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-02-19 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status, including anaconda web UI test planning 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-19 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-02-19 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 status, including anaconda web UI test planning 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
# F40 Blocker Review meeting # Date: 2024-02-19 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! It's time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 to 40 upgrade experience
On Fri, 2024-02-16 at 11:29 +1100, Ian Laurie wrote: > On 2/16/24 4:20 AM, Adam Williamson wrote: > > Before removing it, it would be useful if you could try and figure out > > what pulled it in. Does anything suggests: or recommends: it, or does > > it enhances: or supplements: anything else? > > I'm going to need help wielding that sort of command line magic. No need, your last idea gives us all the info we need. > > Meanwhile what I came up with: > > dnf repoquery --recommends weston > dnf repoquery --enhances weston > dnf repoquery --suggests weston > dnf repoquery --supplements weston > > All resulted in nothing. I did not yet remove it, but I wanted to see > what would be removed along with it in case it provides a hint (this is > an Xfce workstation): > > > Removing > weston > Removing dependent packages: > initial-setup-gui > initial-setup-gui-wayland-generic > Removing unused dependencies: > aml > anaconda-core > anaconda-gui > anaconda-tui > anaconda-widgets > blivet-data > blivet-gui-runtime > flatpak-libs > freerdp2-libs > initial-setup > libblockdev-dm > libblockdev-mpath > libei > liboeffis > libreport-anaconda > libseat > libwinpr2 > libxcvt > malcontent-libs > neatvnc > python3-blivet > python3-blockdev > python3-bytesize > python3-iso639 > python3-kickstart > python3-libmount > python3-meh > python3-meh-gui > python3-pid > python3-productmd > python3-pwquality > python3-pyparted > python3-pyudev > python3-requests-file > python3-requests-ftp > python3-simpleline > python3-xkbregistry > tecla > turbojpeg > weston-libs > xorg-x11-server-Xwayland > > A bit surprised to see anaconda on that list. Ahh, okay, yeah, so that more or less explains it. initial-setup-gui is the anaconda-based initial setup experience that gets installed in some package sets, and which you'd encounter on first boot if you didn't set up a user account on install. It only really needs to be there for that first boot after install, but we don't have a mechanism to get rid of it after that, so it will hang around on your system forever unless you manually uninstall it. I think it's been moved to run on Weston because we're trying to get rid of the anaconda industrial complex's X.org deps and have it always run on Wayland. anaconda is on the list because dnf is just trying to be neat. Note that "Removing unused dependencies" line. What that means is, dnf noticed that the packages being removed (initial-setup-gui and initial- setup-gui-wayland-generic) are the *only* packages you have installed that depend on that long laundry list of packages, so hey, why not get rid of those too? It's a configurable behaviour if you don't like it, but it does usually make sense. anaconda is on the list because initial-setup-gui is based on anaconda (so it requires it), and of course, nothing else on an installed system requires the installer. I'd say in this case it's totally fine to just go ahead. You don't need all those packages installed. I'm not sure we can "fix" this, really, so long as we don't have some kind of neat mechanism for cleaning up the initial setup tool and its dependencies once we're really sure you made it successfully through initial setup. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 39 to 40 upgrade experience
On Thu, 2024-02-15 at 18:05 +1100, Ian Laurie wrote: > Yes I know we're just a day from the branch... but I upgraded an Xfce > workstation/Intranet server today to see how things would go. A few > observations: > > (1) The upgrade required the --allowerasing option which uninstalled > intel-media-driver from RPM Fusion due to a conflict with a related > Fedora package. > > (2) Password needed to be updated as per what happened with Rawhide a > few weeks ago ~ login warning about my password expiring (it was set to > never expire). I'm guessing a file format changed somewhere? Would be > good if the upgrade could migrate the file rather than complaining the > password is about to expire. > > (3) Weston got installed without my permission as per what happened on > my virtual Rawhide instances a few weeks ago. On Rawhide I just got rid > of it without any known negative implications and will do the same for > Fedora 40... but I am assuming this install was not intended? It will > need fixing before the public beta or there will be much screaming. Before removing it, it would be useful if you could try and figure out what pulled it in. Does anything suggests: or recommends: it, or does it enhances: or supplements: anything else? -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Re: 2024-02-12 @ 17:00 UTC - Fedora 39 Blocker Review Meeting
On Sun, 2024-02-11 at 10:16 -0800, Adam Williamson wrote: > # F39 Blocker Review meeting > # Date: 2024-02-12 > # Time: 17:00 UTC > # Location: > https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Of course, this should say 'F40' and the subject should be 'Fedora 40 Blocker Review Meeting'. Sigh. Somehow I always miss *something* when editing these damn announcements. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-02-12 @ 17:00 UTC - Fedora 39 Blocker Review Meeting
# F39 Blocker Review meeting # Date: 2024-02-12 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Hi folks! Fedora 40 branches this coming week, and we have some blockers to check in on, so it seems like a good time for a blocker review meeting. We are still on standard time in places that use daylight savings, so the meeting is at 17:00 UTC. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-02-05 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-02-05 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-02-05 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-02-05 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
openQA Rawhide update failures - we're working on it!
Hi folks! I want to apologize to packagers who have Rawhide updates stuck on failed openQA tests, and provide an update. There were two big problems today. First, the Server base disk image used for some of the tests got regenerated (this happens weekly). Unfortunately, this meant it got affected by https://bugzilla.redhat.com/show_bug.cgi?id=2259266 , and no longer booted. I should have got that grub2 build untagged or the change reverted sooner - sorry. I was expecting the package to be fixed sooner, and it didn't occur to me that this image being regenerated was a risk. I've now got the package untagged, and forced a rebuild of the disk image using a grub2 build with the patch re-applied (otherwise I'd have had to wait for the next Rawhide compose to rebuild the image). I'm now working through re-running all affected tests. Second, shell-color-prompt was changed[0] to apply the color prompt to virtual consoles. This broke a large number of openQA tests, as they often need to do things at root consoles, and to do that they need to know when they've actually managed to log in to one, and they do this by screen matching the prompt. Any test which needed to know it was at a root console was failing. I've updated the 'needle' to match the color prompt, and am re-running all affected tests. I anticipate the mess should be cleaned up in about three or four hours (there are a lot of failures to re-run, and some of the tests take a while to run). Sorry again for the inconvenience. I'll probably propose adding shell-color-prompt to the critical path. That would mean openQA would have gated the update (allowing me to update the needles *before* it got pushed and broke tests for every other update), but it also just seems appropriate - theoretically, a bad change to the package could cause all sorts of consequences, since it fiddles with the default prompt. [0] https://src.fedoraproject.org/rpms/shell-color-prompt/c/1dd8c6c16d760cacfb9fd70a249b28a1fd853dd1?branch=rawhide -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-01-22 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-01-22 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 Change review and check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-01-22 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-01-22 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 Change review and check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2024-01-08 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-01-08 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org Greetings testers! It's time for the first QA meeting of 2024! Using Matrix went fine last time, so we'll do it again this time. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Communications overhaul: Discourse? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2024-01-08 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-01-08 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org Greetings testers! It's time for the first QA meeting of 2024! Using Matrix went fine last time, so we'll do it again this time. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Communications overhaul: Discourse? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] 2023-12-11 @ 16:00 UTC - Fedora QA Meeting
On Mon, 2023-12-11 at 11:31 -0500, pmkellly wrote: > Okay I give up. From what I'm reading Matrix is broken both in Element and > at the browser link https://chat.fedoraproject.org/ > > Thanks for trying to help. I do appreciate it. > I'll be looking forward to the next try. I'm not sure what the problem was, but I was using Element (the flatpak version) the whole time, and I've used the web client version for some time before that, via chat.fedoraproject.org . It definitely works. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-12-11 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-12-11 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org Greetings testers! It's time for the last QA meeting of the year! We're going to try moving back to Fedora Chat (Matrix) for this meeting, as the bot should be working there now. Remember, the IRC bridge is out of commission, so you'll really have to be on Matrix to join the meeting. You can log in with your Fedora account. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-12-11 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-12-11 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org Greetings testers! It's time for the last QA meeting of the year! We're going to try moving back to Fedora Chat (Matrix) for this meeting, as the bot should be working there now. Remember, the IRC bridge is out of commission, so you'll really have to be on Matrix to join the meeting. You can log in with your Fedora account. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Heads up: removed installer help release criterion and archived test case
On Thu, 2023-11-30 at 09:47 +0100, Kamil Paral wrote: > On Wed, Nov 29, 2023 at 9:19 PM Adam Williamson > wrote: > > > Hey folks! I just wanted to give a heads up - I've removed the > > installer help criterion from the Final release criteria: > > > > > > https://fedoraproject.org/w/index.php?title=Fedora_40_Final_Release_Criteria=695349=695347 > > > > why? well, the installer removed help: > > > > https://github.com/rhinstaller/anaconda/pull/5335 > > > > so, the criterion becomes useless. I decided to just go ahead and do > > this rather than proposing it, as it seems like a pretty clear-cut > > situation, but I did want to explain why it had happened. > > > > I will also mark the test case as obsolete, since...it is. > > > > In that case I also removed it from the installation matrix: > https://fedoraproject.org/w/index.php?title=Template%3AInstallation_test_matrix=revision=695372=689565 D'oh. I knew I forgot something. Thanks :) -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads up: removed installer help release criterion and archived test case
Hey folks! I just wanted to give a heads up - I've removed the installer help criterion from the Final release criteria: https://fedoraproject.org/w/index.php?title=Fedora_40_Final_Release_Criteria=695349=695347 why? well, the installer removed help: https://github.com/rhinstaller/anaconda/pull/5335 so, the criterion becomes useless. I decided to just go ahead and do this rather than proposing it, as it seems like a pretty clear-cut situation, but I did want to explain why it had happened. I will also mark the test case as obsolete, since...it is. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Test-Announce] Fedora 40 Rawhide 20231112.n.0 nightly compose nominated for testing
On Sun, 2023-11-12 at 15:26 -0500, Osama Albahrani via test wrote: > Hello, > > just wanted to note that https://openqa.fedoraproject.org/testcase_stats/40 > gives a “Not Found”. It takes a minute for it to kick over when we start testing a new release...should be there now, though. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-11-27 @ ** 16:00 ** UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-11-27 # Time: ** 16:00 ** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting on irc.libera.chat ** Greetings testers! It's time for another QA meeting. Note clocks have changed everywhere they change, by now. If you follow daylight savings time, the meeting should be at the same local time as usual. If you do not follow daylight savings time, the meeting will be one hour later than it was over the summer, in your local time. You can run `date -u` to see the current UTC time if you are unsure. As usual lately, please note this meeting will really be *on IRC*. Matrix may be ready for meeting purposes pretty soon, but I need to check on that before moving the meeting. So please use an IRC client or the web client - https://web.libera.chat/#fedora-meeting - to join. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. Note I have a partial conflict for the second half hour of the meeting slot, so might have to cut the meeting short or let someone take over. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in and Change review 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-11-27 @ ** 16:00 ** UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-11-27 # Time: ** 16:00 ** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting on irc.libera.chat ** Greetings testers! It's time for another QA meeting. Note clocks have changed everywhere they change, by now. If you follow daylight savings time, the meeting should be at the same local time as usual. If you do not follow daylight savings time, the meeting will be one hour later than it was over the summer, in your local time. You can run `date -u` to see the current UTC time if you are unsure. As usual lately, please note this meeting will really be *on IRC*. Matrix may be ready for meeting purposes pretty soon, but I need to check on that before moving the meeting. So please use an IRC client or the web client - https://web.libera.chat/#fedora-meeting - to join. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. Note I have a partial conflict for the second half hour of the meeting slot, so might have to cut the meeting short or let someone take over. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in and Change review 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-11-13 @ ** 16:00 ** UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-11-13 # Time: ** 16:00 ** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting on irc.libera.chat ** Greetings testers! It's time for another QA meeting. Note clocks have changed in North America, so the meeting time in UTC has also changed, as usual. If you follow daylight savings time and have already set your clock back, the meeting will be at the same local time as before. If you do not follow daylight savings time or have not yet set your clocks back, the meeting will be one hour later than before in your local time. You can run `date -u` to see the current UTC time if you are unsure. As usual lately, please note this meeting will really be *on IRC*. Matrix may be ready for meeting purposes pretty soon, but I need to check on that before moving the meeting. So please use an IRC client or the web client - https://web.libera.chat/#fedora-meeting - to join. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 39 and Fedora 40 check-ins 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
2023-11-13 @ ** 16:00 ** UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2023-11-13 # Time: ** 16:00 ** UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting on irc.libera.chat ** Greetings testers! It's time for another QA meeting. Note clocks have changed in North America, so the meeting time in UTC has also changed, as usual. If you follow daylight savings time and have already set your clock back, the meeting will be at the same local time as before. If you do not follow daylight savings time or have not yet set your clocks back, the meeting will be one hour later than before in your local time. You can run `date -u` to see the current UTC time if you are unsure. As usual lately, please note this meeting will really be *on IRC*. Matrix may be ready for meeting purposes pretty soon, but I need to check on that before moving the meeting. So please use an IRC client or the web client - https://web.libera.chat/#fedora-meeting - to join. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 39 and Fedora 40 check-ins 3. Communications overhaul: Discourse and Matrix? 4. Test Day / community event status 5. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
PSA: Rawhide Server (and other xfs) installs broken
Hey folks! Just a heads up that Rawhide Server installs are broken in today's Rawhide compose (and any custom install using xfs). This is because a new version of xfsprogs went into Rawhide and grub2 cannot detect filesystems made with it: https://bugzilla.redhat.com/show_bug.cgi?id=2247926 I've identified the patches needed in grub2, but I can't patch it myself as I'm not on the list of people who can build packages that need to be Secure Boot signed, and anyway, working on the grub2 package is a bit of a nightmare for non-maintainers due to the whole "hundreds of patches that are pulled from an alternative upstream git repo" thing. I've requested xfsprogs be untagged for now: https://pagure.io/releng/issue/11763 so if that gets done, things should work again after the next compose. Unfortunately openQA didn't catch this because we don't test xfs installs on updates :( Maybe I'll have to add a test somehow. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora Linux 39 Final Go/No-Go meeting tomorrow (Thursday)
The Fedora Linux 39 Final Go/No-Go[1] meeting is scheduled for Thursday 2 November at 1700 UTC in #fedora-meeting (on IRC, not Matrix). At this time, we will determine the status of F39 Final for the 7 November target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10627/?from_date=2023-10-30 [2] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
Heads up: another F39 compose is incoming
Hey folks! Just a heads up - a new F39 candidate will be appearing in a few hours. The main difference to RC-1.4 is that it will include Firefox 119 to address an important CVE - https://bugzilla.redhat.com/show_bug.cgi?id=2247311 . We've also taken the opportunity to tweak things a bit in releng to try and fix some images that failed the RC-1.4 compose, especially Kinoite and Silverblue on aarch64 and ppc64le. Most RC-1.4 results should remain valid for the new compose, of course as much testing as we can do on it would be great. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] 2023-10-30 @ 16:00 UTC - Fedora 39 Blocker Review Meeting
# F39 Blocker Review meeting # Date: 2023-10-30 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat (*NOT* Matrix) Hi folks! Currently there are two proposed Final freeze exception issues to review, so let's have a meeting on Monday (where we can also check on the state of accepted blockers). The meeting will on IRC only due to the ongoing lack of a Matrix <-> IRC bridge and a meeting bot on the Matrix side. If you no longer have an IRC setup you can join via webIRC: https://web.libera.chat/ , enter a nickname and put #fedora-blocker-review in the Channel box. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F39 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good day and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] Fedora Linux 39 Final is NO-GO (#3)
Due to outstanding blocker bugs[1], F39 Final RC-1.2 was declared NO-GO in today's Go/No-GO meeting[2]. The next Fedora Linux 39 Final Go/No-Go meeting[3] will be held at 1700 UTC on Thursday 2 November in #fedora-meeting. We will aim for the "target date #3" milestone of 7 November. The release schedule[4] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/39/final/buglist [2] https://meetbot-raw.fedoraproject.org/fedora-meeting/2023-10-26/f39-final-go_no_go-meeting.2023-10-26-17.00.html [3] https://calendar.fedoraproject.org/meeting/10627/?from_date=2023-10-30 [4] https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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, report it: https://pagure.io/fedora-infrastructure/new_issue
