[OS-BUILD PATCH 0/3] redhat/Makefile: Clean up dist-configs and
related
targets
by GitLab Bridge on behalf of prarit
From: prarit on gitlab.com
The 'dist-configs' is not working properly as it only creates ELN
configs. The
'rh-configs' and 'fedora-configs' targets are not working properly and
should
be creating ELN and Fedora configs but they only create some
temporary/intermediate build files. These targets should output final
.config
files for each supported arch. The code has been modified to output
final
.config files.
While fixing this I noticed a few other things that needed to be fixed.
- The TARGET and DIST_TARGET variables in redhat/Makefile are
unused.
- 'make fedora-configs' fails due to a config mismatch on
CONFIG_FORCE_MAX_ZONEORDER
- The configs/process_configs.sh script left *.orig files lying
around
The code has been modified to fix these as well.
Signed-off-by: Prarit Bhargava prarit(a)redhat.com
Cc: dzickus(a)redhat.com
Cc: jforbes(a)redhat.com
Cc: mleitner(a)redhat.com
Cc: jbenc(a)redhat.com
3 years, 8 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: 0a589609738c - [redhat] kernel-5.9.0-0.rc1.20200821gitda2968ff879b.1
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.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 compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 8 months
✅ PASS: Test report for kernel 5.7.16-200.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.7.16-200.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=49633439
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
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
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
ppc64le:
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
🚧 ⚡⚡⚡ kdump - sysrq-c
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 4:
✅ Boot test
🚧 ❌ kdump - sysrq-c
s390x:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
x86_64:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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, 8 months
❌ FAIL: Test report for kernel 5.8.2-300.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.2-300.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=49636032
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
s390x:
❌ LTP
ppc64le:
❌ LTP
aarch64:
❌ LTP
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
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
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
✅ ACPI table test
❌ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
ppc64le:
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
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ CIFS Connectathon
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 4:
✅ Boot test
❌ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
s390x:
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
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ CIFS Connectathon
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
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
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ CIFS Connectathon
Host 4:
✅ Boot test
❌ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
x86_64:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
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, 8 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: 55593bde3e04 - [redhat] kernel-5.9.0-0.rc1.20200819git18445bf405cb.1
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.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 compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 8 months
[OS-BUILD PATCH] [redhat] New configs in drivers/nvme
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_NVME_TARGET_PASSTHRU:
This enables target side NVMe passthru controller support for the
NVMe Over Fabrics protocol. It allows for hosts to manage and
directly access an actual NVMe controller residing on the target
side, incuding executing Vendor Unique Commands.
If unsure, say N.
Symbol: NVME_TARGET_PASSTHRU [=n]
Type : bool
Defined at drivers/nvme/target/Kconfig:19
Prompt: NVMe Target Passthrough support
Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
Location:
-> Device Drivers
-> NVME Support
-> NVMe Target support (NVME_TARGET [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_NVME_TARGET_PASSTHRU | 1 +
.../generic/CONFIG_NVME_TARGET_PASSTHRU | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
diff --git a/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
new file mode 100644
index 000000000000..12bf02e23a41
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_NVME_TARGET_PASSTHRU
@@ -0,0 +1 @@
+# CONFIG_NVME_TARGET_PASSTHRU is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU b/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
deleted file mode 100644
index 2795e2bb3e5e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_NVME_TARGET_PASSTHRU
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_NVME_TARGET_PASSTHRU:
-#
-# This enables target side NVMe passthru controller support for the
-# NVMe Over Fabrics protocol. It allows for hosts to manage and
-# directly access an actual NVMe controller residing on the target
-# side, incuding executing Vendor Unique Commands.
-#
-# If unsure, say N.
-#
-# Symbol: NVME_TARGET_PASSTHRU [=n]
-# Type : bool
-# Defined at drivers/nvme/target/Kconfig:19
-# Prompt: NVMe Target Passthrough support
-# Depends on: NVME_TARGET [=m] && (NVME_CORE [=m]=y || NVME_CORE [=m]=NVME_TARGET [=m])
-# Location:
-# -> Device Drivers
-# -> NVME Support
-# -> NVMe Target support (NVME_TARGET [=m])
-#
-#
-#
-# CONFIG_NVME_TARGET_PASSTHRU is not set
--
GitLab
3 years, 8 months
[OS-BUILD PATCH] [redhat] New configs in drivers/video
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_FB_MODE_HELPERS:
This enables functions for handling video modes using the
Generalized Timing Formula and the EDID parser. A few drivers rely
on this feature such as the radeonfb, rivafb, and the i810fb. If
your driver does not take advantage of this feature, choosing Y will
just increase the kernel size by about 5K.
Symbol: FB_MODE_HELPERS [=n]
Type : bool
Defined at drivers/video/fbdev/Kconfig:192
Prompt: Enable Video Mode Handling Helpers
Depends on: HAS_IOMEM [=y] && FB [=y]
Location:
-> Device Drivers
-> Graphics support
-> Frame buffer Devices
-> Support for frame buffer devices (FB [=y])
Selected by [n]:
- FB_CLPS711X [=n] && HAS_IOMEM [=y] && FB [=y] && (ARCH_CLPS711X || COMPILE_TEST [=n])
- FB_IMX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_MXC [=n] || COMPILE_TEST [=n])
- FB_UVESA [=n] && HAS_IOMEM [=y] && FB [=y] && CONNECTOR [=y]
- FB_ATMEL [=n] && FB [=y] && OF [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (HAVE_FB_ATMEL [=n] || COMPILE_TEST [=n])
- FB_NVIDIA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_RIVA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_I740 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_I810 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86_32 && AGP_INTEL [=n]
- FB_LE80578 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86
- FB_INTEL [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86 && AGP_INTEL [=n] && EXPERT [=n] && !DRM_I915 [=n]
- FB_RADEON [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_SAVAGE [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_NEOMAGIC [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_3DFX [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_TRIDENT [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
- FB_VT8500 [=n] && HAS_IOMEM [=y] && FB [=y]=y && ARM && ARCH_VT8500
- FB_WM8505 [=n] && FB [=y]=y && HAS_IOMEM [=y] && (ARCH_VT8500 || COMPILE_TEST [=n])
- FB_PXA [=n] && HAS_IOMEM [=y] && FB [=y] && ARCH_PXA && OF [=y]
- FB_FSL_DIU [=n] && HAS_IOMEM [=y] && FB [=y] && FSL_SOC
- FB_SMSCUFX [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
- FB_UDL [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
- FB_DA8XX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST [=n])
- FB_SM750 [=n] && STAGING [=n] && FB [=y] && PCI [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_FB_MODE_HELPERS | 1 +
.../generic/CONFIG_FB_MODE_HELPERS | 46 -------------------
2 files changed, 1 insertion(+), 46 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_FB_MODE_HELPERS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_FB_MODE_HELPERS
diff --git a/redhat/configs/common/generic/CONFIG_FB_MODE_HELPERS b/redhat/configs/common/generic/CONFIG_FB_MODE_HELPERS
new file mode 100644
index 000000000000..e9eb6ec4ffe9
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_FB_MODE_HELPERS
@@ -0,0 +1 @@
+# CONFIG_FB_MODE_HELPERS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_FB_MODE_HELPERS b/redhat/configs/pending-common/generic/CONFIG_FB_MODE_HELPERS
deleted file mode 100644
index 07dc319d681d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_FB_MODE_HELPERS
+++ /dev/null
@@ -1,46 +0,0 @@
-# CONFIG_FB_MODE_HELPERS:
-#
-# This enables functions for handling video modes using the
-# Generalized Timing Formula and the EDID parser. A few drivers rely
-# on this feature such as the radeonfb, rivafb, and the i810fb. If
-# your driver does not take advantage of this feature, choosing Y will
-# just increase the kernel size by about 5K.
-#
-# Symbol: FB_MODE_HELPERS [=n]
-# Type : bool
-# Defined at drivers/video/fbdev/Kconfig:192
-# Prompt: Enable Video Mode Handling Helpers
-# Depends on: HAS_IOMEM [=y] && FB [=y]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Frame buffer Devices
-# -> Support for frame buffer devices (FB [=y])
-# Selected by [n]:
-# - FB_CLPS711X [=n] && HAS_IOMEM [=y] && FB [=y] && (ARCH_CLPS711X || COMPILE_TEST [=n])
-# - FB_IMX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_MXC [=n] || COMPILE_TEST [=n])
-# - FB_UVESA [=n] && HAS_IOMEM [=y] && FB [=y] && CONNECTOR [=y]
-# - FB_ATMEL [=n] && FB [=y] && OF [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (HAVE_FB_ATMEL [=n] || COMPILE_TEST [=n])
-# - FB_NVIDIA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_RIVA [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_I740 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_I810 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86_32 && AGP_INTEL [=n]
-# - FB_LE80578 [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86
-# - FB_INTEL [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y] && X86 && AGP_INTEL [=n] && EXPERT [=n] && !DRM_I915 [=n]
-# - FB_RADEON [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_SAVAGE [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_NEOMAGIC [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_3DFX [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_TRIDENT [=n] && HAS_IOMEM [=y] && FB [=y] && PCI [=y]
-# - FB_VT8500 [=n] && HAS_IOMEM [=y] && FB [=y]=y && ARM && ARCH_VT8500
-# - FB_WM8505 [=n] && FB [=y]=y && HAS_IOMEM [=y] && (ARCH_VT8500 || COMPILE_TEST [=n])
-# - FB_PXA [=n] && HAS_IOMEM [=y] && FB [=y] && ARCH_PXA && OF [=y]
-# - FB_FSL_DIU [=n] && HAS_IOMEM [=y] && FB [=y] && FSL_SOC
-# - FB_SMSCUFX [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
-# - FB_UDL [=n] && HAS_IOMEM [=y] && FB [=y] && USB [=y]
-# - FB_DA8XX [=n] && FB [=y] && HAVE_CLK [=y] && HAS_IOMEM [=y] && (ARCH_DAVINCI_DA8XX || SOC_AM33XX || COMPILE_TEST [=n])
-# - FB_SM750 [=n] && STAGING [=n] && FB [=y] && PCI [=y]
-#
-#
-#
-# CONFIG_FB_MODE_HELPERS is not set
--
GitLab
3 years, 8 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: 7e5c3863430d - [redhat] kernel-5.9.0-0.rc1.20200818git06a4ec1d9dc6.1
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.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 compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 8 months