β
PASS: Test report for kernel 5.11.5-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.5-50.fc33
COPR build ID: 2062111
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
β
Boot test
β
selinux-policy: serge-testsuite
β
storage: software RAID testing
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
IPMI driver test
π§ β
IPMItool loop stress test
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
Host 2:
β
Boot test
β
ACPI table test
β
ACPI enabled test
β
LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
β
Networking bridge: sanity
β
Networking socket: fuzz
β
Networking: igmp conformance test
β
Networking route: pmtu
β
Networking route_func - local
β
Networking route_func - forward
β
Networking TCP: keepalive test
β
Networking UDP: socket
β
Networking tunnel: geneve basic test
β
Networking tunnel: gre basic
β
L2TP basic test
β
Networking tunnel: vxlan basic
β
Networking ipsec: basic netns - transport
β
Networking ipsec: basic netns - tunnel
β
Libkcapi AF_ALG test
β
pciutils: update pci ids test
β
ALSA PCM loopback test
β
ALSA Control (mixer) Userspace Element test
β
storage: SCSI VPD
β
trace: ftrace/tracer
π§ β
i2c: i2cdetect sanity
π§ β
CIFS Connectathon
π§ β
POSIX pjd-fstest suites
π§ β
Firmware test suite
π§ β
jvm - jcstress tests
π§ β
Memory function: kaslr
π§ β
Ethernet drivers sanity
π§ β
Networking cki netfilter test
π§ β audit: audit testsuite test
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years, 1Β month
β FAIL: Test report for kernel 5.11.5-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.5-50.fc33
COPR build ID: 2062111
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
aarch64:
β LTP
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
β
Boot test
β
selinux-policy: serge-testsuite
β
storage: software RAID testing
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
IPMI driver test
π§ β
IPMItool loop stress test
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
Host 2:
β
Boot test
β
ACPI table test
β
ACPI enabled test
β LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
β
Networking bridge: sanity
β
Networking socket: fuzz
β
Networking: igmp conformance test
β
Networking route: pmtu
β
Networking route_func - local
β
Networking route_func - forward
β
Networking TCP: keepalive test
β
Networking UDP: socket
β
Networking tunnel: geneve basic test
β
Networking tunnel: gre basic
β
L2TP basic test
β
Networking tunnel: vxlan basic
β
Networking ipsec: basic netns - transport
β
Networking ipsec: basic netns - tunnel
β
Libkcapi AF_ALG test
β
pciutils: update pci ids test
β
ALSA PCM loopback test
β
ALSA Control (mixer) Userspace Element test
β
storage: SCSI VPD
β
trace: ftrace/tracer
π§ β
i2c: i2cdetect sanity
π§ β
CIFS Connectathon
π§ β
POSIX pjd-fstest suites
π§ β
Firmware test suite
π§ β
jvm - jcstress tests
π§ β
Memory function: kaslr
π§ β
Ethernet drivers sanity
π§ β
Networking cki netfilter test
π§ β audit: audit testsuite test
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years, 1Β month
β FAIL: Test report for kernel 5.11.5-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.5-50.fc33
COPR build ID: 2062111
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
x86_64:
β Boot test
β Boot test
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
x86_64:
Host 1:
β Boot test
β‘β‘β‘ selinux-policy: serge-testsuite
β‘β‘β‘ storage: software RAID testing
π§ β‘β‘β‘ CPU: Idle Test
π§ β‘β‘β‘ xfstests - ext4
π§ β‘β‘β‘ xfstests - xfs
π§ β‘β‘β‘ xfstests - btrfs
π§ β‘β‘β‘ xfstests - nfsv4.2
π§ β‘β‘β‘ xfstests - cifsv3.11
π§ β‘β‘β‘ IPMI driver test
π§ β‘β‘β‘ IPMItool loop stress test
π§ β‘β‘β‘ power-management: cpupower/sanity test
π§ β‘β‘β‘ Storage blktests
π§ β‘β‘β‘ Storage block - filesystem fio test
π§ β‘β‘β‘ Storage block - queue scheduler test
π§ β‘β‘β‘ Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
Host 2:
β Boot test
β‘β‘β‘ ACPI table test
β‘β‘β‘ LTP
β‘β‘β‘ Loopdev Sanity
β‘β‘β‘ Memory: fork_mem
β‘β‘β‘ Memory function: memfd_create
β‘β‘β‘ AMTU (Abstract Machine Test Utility)
β‘β‘β‘ Networking bridge: sanity
β‘β‘β‘ Networking socket: fuzz
β‘β‘β‘ Networking: igmp conformance test
β‘β‘β‘ Networking route: pmtu
β‘β‘β‘ Networking route_func - local
β‘β‘β‘ Networking route_func - forward
β‘β‘β‘ Networking TCP: keepalive test
β‘β‘β‘ Networking UDP: socket
β‘β‘β‘ Networking tunnel: geneve basic test
β‘β‘β‘ Networking tunnel: gre basic
β‘β‘β‘ L2TP basic test
β‘β‘β‘ Networking tunnel: vxlan basic
β‘β‘β‘ Networking ipsec: basic netns - transport
β‘β‘β‘ Networking ipsec: basic netns - tunnel
β‘β‘β‘ Libkcapi AF_ALG test
β‘β‘β‘ pciutils: sanity smoke test
β‘β‘β‘ pciutils: update pci ids test
β‘β‘β‘ ALSA PCM loopback test
β‘β‘β‘ ALSA Control (mixer) Userspace Element test
β‘β‘β‘ storage: SCSI VPD
β‘β‘β‘ trace: ftrace/tracer
π§ β‘β‘β‘ i2c: i2cdetect sanity
π§ β‘β‘β‘ CIFS Connectathon
π§ β‘β‘β‘ POSIX pjd-fstest suites
π§ β‘β‘β‘ Firmware test suite
π§ β‘β‘β‘ jvm - jcstress tests
π§ β‘β‘β‘ Memory function: kaslr
π§ β‘β‘β‘ Ethernet drivers sanity
π§ β‘β‘β‘ Networking cki netfilter test
π§ β‘β‘β‘ audit: audit testsuite test
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years, 1Β month
[OS-BUILD PATCH] [redhat] Set CONFIG_MOUSE_SERIAL=n by default
by Patrick Talbert (via Email Bridge)
From: Patrick Talbert <ptalbert(a)redhat.com>
[redhat] Set CONFIG_MOUSE_SERIAL=n by default
Since !777 CONFIG_MOUSE_SERIAL is only enabled for x86. That's fine, but
the config item does not declare a default so we must unset it for the
default case.
Cc: Peter Robinson <pbrobinson(a)gmail.com>
Cc: Dan HorΓ‘k <dan(a)danny.cz>
Cc: Benjamin Tissoires <benjamin.tissoires(a)redhat.com>
Signed-off-by: Patrick Talbert <ptalbert(a)redhat.com>
diff a/redhat/configs/common/generic/CONFIG_MOUSE_SERIAL b/redhat/configs/common/generic/CONFIG_MOUSE_SERIAL
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MOUSE_SERIAL
@@ -0,0 +1 @@
+# CONFIG_MOUSE_SERIAL is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/957
3Β years, 1Β month
[OS-BUILD PATCH] common: fix WM8804 codec dependencies
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)redhat.com>
The WM8804 codec is required for Intel Apollo Lake support so enable it
as it's a supported RHEL for Edge platform.
Some minor cleanups for the WM8804 codec configs while we're at it.
Signed-off-by: Peter Robinson <pbrobinson(a)redhat.com>
---
.../generic/x86/CONFIG_SND_SOC_WM8804_I2C | 0
.../fedora/generic/CONFIG_SND_SOC_WM8804 | 1 -
.../fedora/generic/arm/CONFIG_SND_SOC_WM8804 | 1 -
.../x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH | 23 -------------------
.../fedora/generic/x86/CONFIG_SND_SOC_WM8804 | 1 -
5 files changed, 26 deletions(-)
rename redhat/configs/{fedora => common}/generic/x86/CONFIG_SND_SOC_WM8804_I2C (100%)
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804
delete mode 100644 redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804
delete mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH
delete mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804_I2C b/redhat/configs/common/generic/x86/CONFIG_SND_SOC_WM8804_I2C
similarity index 100%
rename from redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804_I2C
rename to redhat/configs/common/generic/x86/CONFIG_SND_SOC_WM8804_I2C
diff --git a/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804
deleted file mode 100644
index 074702b5ef5e..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SND_SOC_WM8804
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_SND_SOC_WM8804 is not set
diff --git a/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804
deleted file mode 100644
index 04b89d9ff78b..000000000000
--- a/redhat/configs/fedora/generic/arm/CONFIG_SND_SOC_WM8804
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SND_SOC_WM8804=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH
deleted file mode 100644
index bb7ee45866a6..000000000000
--- a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH:
-#
-# This adds support for ASoC machine driver for Intel platforms
-# with the Wolfson/Cirrus WM8804 I2S audio codec.
-# Say Y or m if you have such a device. This is a recommended option.
-# If unsure select "N".
-#
-# Symbol: SND_SOC_INTEL_SOF_WM8804_MACH [=n]
-# Type : tristate
-# Defined at sound/soc/intel/boards/Kconfig:329
-# Prompt: SOF with Wolfson/Cirrus WM8804 codec
-# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_MACH [=y] && SND_SOC_SOF_APOLLOLAKE [=m] && I2C [=y] && ACPI [=y] && (MFD_INTEL_LPSS [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> Sound card support (SOUND [=m])
-# -> Advanced Linux Sound Architecture (SND [=m])
-# -> ALSA for SoC audio support (SND_SOC [=m])
-# -> Intel Machine drivers (SND_SOC_INTEL_MACH [=y])
-# Selects: SND_SOC_WM8804_I2C [=n]
-#
-#
-#
-CONFIG_SND_SOC_INTEL_SOF_WM8804_MACH=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804 b/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804
deleted file mode 100644
index 04b89d9ff78b..000000000000
--- a/redhat/configs/fedora/generic/x86/CONFIG_SND_SOC_WM8804
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SND_SOC_WM8804=m
--
GitLab
3Β years, 1Β month
[OS-BUILD PATCHv2] redhat: allow running fedora-configs and
rh-configs targets
outside of redhat/
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
redhat: allow running fedora-configs and rh-configs targets outside of redhat/
Since the rename of all targets to dist-* targets, the specific config
target for RHEL configs do not work when called outside of the redhat directory:
the makefile filters only dist-% and distg-% targets, so it doesn't run against
redhat/Makefile and thus calling those targets do not work, unless you
cd into the redhat directory.
To allow running the specific config targets outside of redhat/
directory, we have two approaches: change makefile to accept those old
config targets, or create new ones starting with dist-*.
I chose the latter approach with this change: fedora-configs target
has a new dist-fedora-configs, while rh-configs target can now be
called as dist-rhel-configs. I also removed the old targets from the
help output replacing them in favour of the new ones.
v2: keep rh-configs and fedora-configs targets for compatibility, which
now calls the new dist-* ones.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff a/redhat/Makefile b/redhat/Makefile
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -135,11 +135,13 @@ dist-configs: dist-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh "$(FLAVOR)" 1; \
./process_configs.sh $(PROCESS_CONFIGS_OPTS) $(PACKAGE_NAME) $(KVERSION)
-fedora-configs: FLAVOR = fedora
-fedora-configs: dist-configs
+dist-fedora-configs: FLAVOR = fedora
+dist-fedora-configs: dist-configs
+fedora-configs: dist-fedora-configs
-rh-configs: FLAVOR = rhel
-rh-configs: dist-configs
+dist-rhel-configs: FLAVOR = rhel
+dist-rhel-configs: dist-configs
+rh-configs: dist-rhel-configs
dist-configs-check: dist-configs-prep
cd $(REDHAT)/configs; ./process_configs.sh $(PROCESS_CONFIGS_CHECK_OPTS) $(PACKAGE_NAME)
@@ -516,8 +518,8 @@ dist-full-help:
@echo ' dist-cross-<arch>-rpms - [x86_64 only] execute rpm builds for specified'
@echo ' <arch> using RHEL cross compiler.'
@echo ' See dist-cross-<arch>-build for the supported archs.'
- @echo ' rh-configs - build ELN configs'
- @echo ' fedora-configs - build Fedora configs'
+ @echo ' dist-rhel-configs - build ELN configs'
+ @echo ' dist-fedora-configs - build Fedora configs'
@echo ''
@echo 'kABI targets:'
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/953
3Β years, 1Β month
[OS-BUILD PATCH 0/7] Move all x86 legacy input options to that
architecture
by GitLab Bridge on behalf of pbrobinson
From: pbrobinson on gitlab.com
None of the non x86 architectures support PS2, AT keyboards, i8042
controllers and related bits. This cleans up a bunch of those options as
well as syncing some of the Fedora options on non x86 to be the same as
ARK by moving the ARK bits to generic.
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
3Β years, 1Β month
β
PASS: Test report for kernel 5.11.4-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.4-50.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=63345527
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
β‘ Internal infrastructure issues prevented one or more tests (marked
with β‘β‘β‘) from running on this architecture.
This is not the fault of the kernel that was tested.
β‘β‘β‘ Boot test
π§ β‘β‘β‘ xfstests - ext4
π§ β‘β‘β‘ xfstests - xfs
π§ β‘β‘β‘ xfstests - btrfs
π§ β‘β‘β‘ Storage blktests
π§ β‘β‘β‘ Storage block - filesystem fio test
π§ β‘β‘β‘ Storage block - queue scheduler test
π§ β‘β‘β‘ Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
Host 2:
β
Boot test
β
ACPI table test
β
LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
π§ β
CIFS Connectathon
π§ β
Ethernet drivers sanity
Host 3:
β
Boot test
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
ppc64le:
Host 1:
β
Boot test
β
LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
π§ β
CIFS Connectathon
π§ β
Ethernet drivers sanity
Host 2:
β
Boot test
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
s390x:
Host 1:
β
Boot test
β
LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
π§ β
CIFS Connectathon
π§ β
Ethernet drivers sanity
Host 2:
β
Boot test
π§ β
Storage blktests
π§ β
Storage nvme - tcp
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
x86_64:
Host 1:
β
Boot test
π§ β
xfstests - ext4
π§ β
xfstests - xfs
π§ β
xfstests - btrfs
π§ β
xfstests - nfsv4.2
π§ β
xfstests - cifsv3.11
π§ β
Storage blktests
π§ β
Storage block - filesystem fio test
π§ β
Storage block - queue scheduler test
π§ β
Storage nvme - tcp
π§ β
Storage: lvm device-mapper test
π§ β
Storage: swraid mdadm raid_module test
π§ β
stress: stress-ng
Host 2:
β
Boot test
β
ACPI table test
β
LTP
β
Loopdev Sanity
β
Memory: fork_mem
β
Memory function: memfd_create
β
AMTU (Abstract Machine Test Utility)
π§ β
CIFS Connectathon
π§ β
Ethernet drivers sanity
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years, 1Β month
[OS-BUILD PATCH] Disable bluetooth highspeed by default
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
Upstream has disabled BT_HS by disabled because it wasn't widely adopted.
It's also been referenced upstream by BleedingTooth vulnerability:
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa...
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
---
redhat/configs/common/generic/CONFIG_BT_HS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/redhat/configs/common/generic/CONFIG_BT_HS b/redhat/configs/common/generic/CONFIG_BT_HS
index e0151a2e9e0d..fbbd6bcf002f 100644
--- a/redhat/configs/common/generic/CONFIG_BT_HS
+++ b/redhat/configs/common/generic/CONFIG_BT_HS
@@ -1 +1 @@
-CONFIG_BT_HS=y
+# CONFIG_BT_HS is not set
--
GitLab
3Β years, 1Β month
β FAIL: Test report for kernel 5.11.4-50.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.4-50.fc33
COPR build ID: 2060604
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
x86_64:
β Boot test
β Boot test
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
x86_64:
Host 1:
β Boot test
β‘β‘β‘ ACPI table test
β‘β‘β‘ LTP
β‘β‘β‘ Loopdev Sanity
β‘β‘β‘ Memory: fork_mem
β‘β‘β‘ Memory function: memfd_create
β‘β‘β‘ AMTU (Abstract Machine Test Utility)
β‘β‘β‘ Networking bridge: sanity
β‘β‘β‘ Networking socket: fuzz
β‘β‘β‘ Networking: igmp conformance test
β‘β‘β‘ Networking route: pmtu
β‘β‘β‘ Networking route_func - local
β‘β‘β‘ Networking route_func - forward
β‘β‘β‘ Networking TCP: keepalive test
β‘β‘β‘ Networking UDP: socket
β‘β‘β‘ Networking tunnel: geneve basic test
β‘β‘β‘ Networking tunnel: gre basic
β‘β‘β‘ L2TP basic test
β‘β‘β‘ Networking tunnel: vxlan basic
β‘β‘β‘ Networking ipsec: basic netns - transport
β‘β‘β‘ Networking ipsec: basic netns - tunnel
β‘β‘β‘ Libkcapi AF_ALG test
β‘β‘β‘ pciutils: sanity smoke test
β‘β‘β‘ pciutils: update pci ids test
β‘β‘β‘ ALSA PCM loopback test
β‘β‘β‘ ALSA Control (mixer) Userspace Element test
β‘β‘β‘ storage: SCSI VPD
β‘β‘β‘ trace: ftrace/tracer
π§ β‘β‘β‘ i2c: i2cdetect sanity
π§ β‘β‘β‘ CIFS Connectathon
π§ β‘β‘β‘ POSIX pjd-fstest suites
π§ β‘β‘β‘ Firmware test suite
π§ β‘β‘β‘ jvm - jcstress tests
π§ β‘β‘β‘ Memory function: kaslr
π§ β‘β‘β‘ Ethernet drivers sanity
π§ β‘β‘β‘ Networking cki netfilter test
π§ β‘β‘β‘ audit: audit testsuite test
Host 2:
β Boot test
β‘β‘β‘ selinux-policy: serge-testsuite
β‘β‘β‘ storage: software RAID testing
π§ β‘β‘β‘ CPU: Frequency Driver Test
π§ β‘β‘β‘ CPU: Idle Test
π§ β‘β‘β‘ xfstests - ext4
π§ β‘β‘β‘ xfstests - xfs
π§ β‘β‘β‘ xfstests - btrfs
π§ β‘β‘β‘ xfstests - nfsv4.2
π§ β‘β‘β‘ xfstests - cifsv3.11
π§ β‘β‘β‘ IPMI driver test
π§ β‘β‘β‘ IPMItool loop stress test
π§ β‘β‘β‘ power-management: cpupower/sanity test
π§ β‘β‘β‘ Storage blktests
π§ β‘β‘β‘ Storage block - filesystem fio test
π§ β‘β‘β‘ Storage block - queue scheduler test
π§ β‘β‘β‘ Storage nvme - tcp
π§ β‘β‘β‘ Storage: lvm device-mapper test
π§ β‘β‘β‘ Storage: swraid mdadm raid_module test
π§ β‘β‘β‘ stress: stress-ng
Test sources: https://gitlab.com/cki-project/kernel-tests
π Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with β‘β‘β‘.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with π§. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with β±.
3Β years, 1Β month