❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: f68da0b40e14 - [redhat] kernel-5.10.0-0.rc0.20201020git071a0578b0ce.48
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 5 months
❌ FAIL: Test report for kernel 5.8.16-200.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.16-200.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=53759724
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
aarch64:
❌ stress: stress-ng
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
❌ stress: stress-ng
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
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:
⚡ 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
⚡⚡⚡ stress: stress-ng
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
Host 4:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
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 nvme - tcp
Host 3:
⚡ 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
🚧 ⚡⚡⚡ kdump - sysrq-c
Host 4:
✅ Boot test
🚧 ✅ kdump - sysrq-c
s390x:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 2:
⚡ 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
✅ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ Ethernet drivers sanity
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
x86_64:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ 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, 5 months
[OS-BUILD PATCH] [redhat] New configs in drivers/acpi
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DPTF_PCH_FIVR:
This driver adds support for Dynamic Platform and Thermal Framework
(DPTF) PCH FIVR Participant device support. This driver allows to
switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
This participant is responsible for exposing:
freq_mhz_low_clock
freq_mhz_high_clock
To compile this driver as a module, choose M here:
the module will be called dptf_pch_fivr.
Symbol: DPTF_PCH_FIVR [=n]
Type : tristate
Defined at drivers/acpi/dptf/Kconfig:18
Prompt: DPTF PCH FIVR Participant
Depends on: ACPI [=y] && X86 [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3(a)redhat.com>
Cc: Lenny Szubowicz <lszubowi(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Cc: David Arcari <darcari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DPTF_PCH_FIVR | 1 +
.../generic/CONFIG_DPTF_PCH_FIVR | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
diff --git a/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR b/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
new file mode 100644
index 000000000000..e201b9b14135
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
@@ -0,0 +1 @@
+# CONFIG_DPTF_PCH_FIVR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR b/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
deleted file mode 100644
index 511d5616fbc6..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_DPTF_PCH_FIVR:
-#
-# This driver adds support for Dynamic Platform and Thermal Framework
-# (DPTF) PCH FIVR Participant device support. This driver allows to
-# switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
-# This participant is responsible for exposing:
-# freq_mhz_low_clock
-# freq_mhz_high_clock
-#
-# To compile this driver as a module, choose M here:
-# the module will be called dptf_pch_fivr.
-#
-# Symbol: DPTF_PCH_FIVR [=n]
-# Type : tristate
-# Defined at drivers/acpi/dptf/Kconfig:18
-# Prompt: DPTF PCH FIVR Participant
-# Depends on: ACPI [=y] && X86 [=y]
-# Location:
-# -> Power management and ACPI options
-# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
-#
-#
-#
-# CONFIG_DPTF_PCH_FIVR is not set
--
GitLab
3 years, 5 months
[OS-BUILD PATCH] [redhat] New configs in net/can
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_CAN_ISOTP:
CAN Transport Protocols offer support for segmented Point-to-Point
communication between CAN nodes via two defined CAN Identifiers.
As CAN frames can only transport a small amount of data bytes
(max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
segmentation is needed to transport longer PDUs as needed e.g. for
vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
This protocol driver implements data transfers according to
ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
If you want to perform automotive vehicle diagnostic services (UDS),
say 'y'.
Symbol: CAN_ISOTP [=n]
Type : tristate
Defined at net/can/Kconfig:58
Prompt: ISO 15765-2:2016 CAN transport protocol
Depends on: NET [=y] && CAN [=m]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
---
Cc: Jiri Benc <jbenc(a)redhat.com>
Cc: Marcelo Leitner <mleitner(a)redhat.com>
Cc: Davide Caratti <dcaratti(a)redhat.com>
Cc: Eric Garver <egarver(a)redhat.com>
Cc: Flavio Leitner <fbl(a)redhat.com>
Cc: Florian Westphal <fwestpha(a)redhat.com>
Cc: Guillaume Nault <gnault(a)redhat.com>
Cc: Hangbin Liu <haliu(a)redhat.com>
Cc: Ivan Vecera <ivecera(a)redhat.com>
Cc: Jarod Wilson <jarod(a)redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com>
Cc: Paolo Abeni <pabeni(a)redhat.com>
Cc: Phil Sutter <psutter(a)redhat.com>
Cc: Sabrina Dubroca <sdubroca(a)redhat.com>
Cc: Stefano Brivio <sbrivio(a)redhat.com>
Cc: Xin Long <lxin(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_CAN_ISOTP | 1 +
.../pending-common/generic/CONFIG_CAN_ISOTP | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CAN_ISOTP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
diff --git a/redhat/configs/common/generic/CONFIG_CAN_ISOTP b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
new file mode 100644
index 000000000000..2ebf8768a868
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
@@ -0,0 +1 @@
+# CONFIG_CAN_ISOTP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP b/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
deleted file mode 100644
index 58dd572e7fc7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_CAN_ISOTP:
-#
-# CAN Transport Protocols offer support for segmented Point-to-Point
-# communication between CAN nodes via two defined CAN Identifiers.
-# As CAN frames can only transport a small amount of data bytes
-# (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
-# segmentation is needed to transport longer PDUs as needed e.g. for
-# vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
-# This protocol driver implements data transfers according to
-# ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
-# If you want to perform automotive vehicle diagnostic services (UDS),
-# say 'y'.
-#
-# Symbol: CAN_ISOTP [=n]
-# Type : tristate
-# Defined at net/can/Kconfig:58
-# Prompt: ISO 15765-2:2016 CAN transport protocol
-# Depends on: NET [=y] && CAN [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> CAN bus subsystem support (CAN [=m])
-#
-#
-#
-# CONFIG_CAN_ISOTP is not set
--
GitLab
3 years, 5 months
[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_PINCTRL_MSM8226:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc MSM8226 platform.
Symbol: PINCTRL_MSM8226 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:65
Prompt: Qualcomm 8226 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=y]
---
Cc: David Arcari <darcari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PINCTRL_MSM8226 | 1 +
.../generic/CONFIG_PINCTRL_MSM8226 | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
diff --git a/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226 b/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
new file mode 100644
index 000000000000..3bc6adb7fe6e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
@@ -0,0 +1 @@
+# CONFIG_PINCTRL_MSM8226 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226 b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
deleted file mode 100644
index e89e5bdc2f79..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PINCTRL_MSM8226:
-#
-# This is the pinctrl, pinmux, pinconf and gpiolib driver for the
-# Qualcomm Technologies Inc TLMM block found on the Qualcomm
-# Technologies Inc MSM8226 platform.
-#
-# Symbol: PINCTRL_MSM8226 [=n]
-# Type : tristate
-# Defined at drivers/pinctrl/qcom/Kconfig:65
-# Prompt: Qualcomm 8226 pin controller driver
-# Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Pin controllers (PINCTRL [=y])
-# Selects: PINCTRL_MSM [=y]
-#
-#
-#
-# CONFIG_PINCTRL_MSM8226 is not set
--
GitLab
3 years, 5 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 677e8d09b1bf - [redhat] kernel-5.10.0-0.rc0.20201019git071a0578b0ce.47
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 5 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 4728ebb7a774 - [redhat] kernel-5.10.0-0.rc0.20201018git071a0578b0ce.46
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 5 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: dca63cf0fe05 - [redhat] kernel-5.10.0-0.rc0.20201017git071a0578b0ce.45
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 5 months
System no longer distributes load to multiple cores for long
running task
by stan
Hi,
It's been a while (6 months?) since I ran a python program that uses a
100% cpu core for hours. The last time I ran it, the task would migrate
from core to core to core, every second or so. I could see it doing so
in the various tops.
Now, it runs on only one core, and doesn't move.
This is more efficient from a computing perspective because there
aren't as many task switches, but it means that the core that is
running gets very hot. Since the rest of the cores are idle, I would
like to switch back to the previous behavior for this reason. Can
someone tell me how?
Thanks.
PS I'm copying devel in case this isn't a kernel issue, and also
because my posts to the kernel list just seem to disappear into the
ether.
3 years, 5 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 58b78f0035b6 - [redhat] kernel-5.10.0-0.rc0.20201016git9ff9b0d392ea.44
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 5 months