Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 40.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
From: Gerd Hoffmann on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2817
NOTE: Truncated patchset due to missing public @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the merge request to
retrigger sending the emails.
Need to support root filesystem on virtiofs.
Signed-off-by: Gerd Hoffmann <kraxel(a)redhat.com>
---
redhat/dracut-virt.conf | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
From: Scott Weaver <scweaver(a)redhat.com>
Add snd-hda-cirrus-scodec-test to mod-internal.list
This is a new kunit test that needs to be added to the mod-internal list
in order to be able to access the kunit symbols.
Signed-off-by: Scott Weaver <scweaver(a)redhat.com>
diff --git a/redhat/scripts/mod/mod-internal.list b/redhat/scripts/mod/mod-internal.list
index blahblah..blahblah 100644
--- a/redhat/scripts/mod/mod-internal.list
+++ b/redhat/scripts/mod/mod-internal.list
@@ -65,6 +65,7 @@ rocker
scftorture
siphash_kunit
slub_kunit
+snd-hda-cirrus-scodec-test
soc-topology-test
soc-utils-test
stackinit_kunit
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2816
From: Don Zickus <dzickus(a)redhat.com>
Fix s390 zfcpfdump bpf build failures for cgroups
BPF fails to build under s390's zfcpdump variant because cgroups is
disabled. Zfcpdump is a dump kernel and isn't expected to run bpf.
Just disable bpf for that kernel variant.
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
diff --git a/redhat/configs/pending-rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL b/redhat/configs/rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL
rename from redhat/configs/pending-rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL
rename to redhat/configs/rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL
index blahblah..blahblah 100644
--- a/redhat/configs/pending-rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL
+++ b/redhat/configs/rhel/generic/s390x/zfcpdump/CONFIG_BPF_SYSCALL
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2812
From: Justin M. Forbes on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2795
New kunit tests with 6.7 that need to be added to mod-internal list as
they need the kunit symbols.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
redhat/scripts/mod/mod-internal.list | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
Hi, we tested your kernel and here are the results:
Overall result: PASSED
Merge: OK
Compile: OK
Test: OK
Tested-by: CKI Project <cki-project(a)redhat.com>
Kernel information:
Brew / Koji Task ID: 108485780
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/112851
One or more kernel tests failed:
We also see the following known issues which are not related to your changes:
Issue: NFS Connectathon: SELinux prevents rpcbind
URL: https://bugzilla.redhat.com/1758147
Affected tests:
ppc64le - Filesystem - NFS Connectathon
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________