✅ PASS: Test report for kernel 5.7.0-0.rc5.1.cki.fc33 (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: af1de3afb79d - [redhat] kernel-5.7.0-0.rc5.20200515git1ae7efb38854.1
The results of these automated tests are provided below.
Overall result: PASSED
Merge: OK
Compile: OK
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.
,-. ,-.
( 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=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
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
🚧 ⚡⚡⚡ kdump - sysrq-c
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
✅ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ stress: stress-ng
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ storage: iSCSI parameters
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)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking: ipv6/Fujitsu-socketapi-test
⚡⚡⚡ Networking sctp-auth: sockopts 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 - tunnel
⚡⚡⚡ Libkcapi AF_ALG test
⚡⚡⚡ pciutils: update pci ids test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ LTP: openposix test suite
🚧 ⚡⚡⚡ Networking firewall: basic netfilter test
🚧 ⚡⚡⚡ audit: audit testsuite test
🚧 ⚡⚡⚡ storage: dm/common
🚧 ⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Libhugetlbfs - version 2.2.1
Host 2:
✅ Boot test
🚧 ❌ kdump - sysrq-c
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
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests
s390x:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
⏱ Boot test
⏱ LTP
⏱ Loopdev Sanity
⏱ Memory function: memfd_create
⏱ Networking bridge: sanity
⏱ Ethernet drivers sanity
⏱ Networking MACsec: sanity
⏱ Networking: ipv6/Fujitsu-socketapi-test
⏱ Networking sctp-auth: sockopts 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
⏱ Usex - version 1.9-29
⏱ CIFS Connectathon
⏱ POSIX pjd-fstest suites
⏱ Memory function: kaslr
⏱ LTP: openposix test suite
⏱ Networking firewall: basic netfilter test
⏱ audit: audit testsuite test
⏱ storage: dm/common
⏱ trace: ftrace/tracer
Host 3:
⏱ Boot test
⏱ selinux-policy: serge-testsuite
⏱ stress: stress-ng
⏱ Storage blktests
x86_64:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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
✅ ACPI table test
✅ LTP
⚡⚡⚡ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking: ipv6/Fujitsu-socketapi-test
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ 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
⚡⚡⚡ Usex - version 1.9-29
⚡⚡⚡ storage: SCSI VPD
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ LTP: openposix test suite
🚧 ⚡⚡⚡ Networking firewall: basic netfilter test
🚧 ⚡⚡⚡ audit: audit testsuite test
🚧 ⚡⚡⚡ storage: dm/common
🚧 ⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Libhugetlbfs - version 2.2.1
🚧 ⚡⚡⚡ Tracepoints: operational test
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
⚡⚡⚡ ACPI table test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking: ipv6/Fujitsu-socketapi-test
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ 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
⚡⚡⚡ Usex - version 1.9-29
⚡⚡⚡ storage: SCSI VPD
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ LTP: openposix test suite
🚧 ⚡⚡⚡ Networking firewall: basic netfilter test
🚧 ⚡⚡⚡ audit: audit testsuite test
🚧 ⚡⚡⚡ storage: dm/common
🚧 ⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ Libhugetlbfs - version 2.2.1
🚧 ⚡⚡⚡ Tracepoints: operational test
Host 4:
⚡ 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
✅ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
✅ storage: software RAID testing
⚡⚡⚡ stress: stress-ng
🚧 ⚡⚡⚡ CPU: Frequency Driver Test
🚧 ⚡⚡⚡ CPU: Idle Test
🚧 ⚡⚡⚡ IOMMU boot test
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ power-management: cpupower/sanity test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ storage: iSCSI parameters
Test sources: https://github.com/CKI-project/tests-beaker
💚 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, 10 months
[OS-BUILD PATCH] configs: Disable Serial IR driver
by GitLab Bridge on behalf of prarit
From: Prarit Bhargava <prarit(a)redhat.com>
This is an old driver and no longer used. It can be disabled.
Disable the Serial IR driver.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
Cc: Jeff Bastian <jbastian(a)redhat.com>
---
redhat/configs/common/generic/CONFIG_IR_SERIAL | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/redhat/configs/common/generic/CONFIG_IR_SERIAL b/redhat/configs/common/generic/CONFIG_IR_SERIAL
index 53c7f1d81e8e..4da276f1e666 100644
--- a/redhat/configs/common/generic/CONFIG_IR_SERIAL
+++ b/redhat/configs/common/generic/CONFIG_IR_SERIAL
@@ -1 +1 @@
-CONFIG_IR_SERIAL=m
+# CONFIG_IR_SERIAL is not set
--
2.26.2
3 years, 10 months
❌ FAIL: Test report for kernel 5.6.13-300.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.6.13-300.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=44494871
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
x86_64:
❌ 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
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
❌ LTP
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
ppc64le:
Host 1:
✅ Boot test
❌ LTP
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ Storage blktests
s390x:
Host 1:
✅ Boot test
❌ LTP
✅ Memory function: memfd_create
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
x86_64:
Host 1:
✅ Boot test
❌ LTP
✅ 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
🚧 ✅ Storage blktests
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Test sources: https://github.com/CKI-project/tests-beaker
💚 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, 10 months
Re: [ARK PATCH 0/2] x86: Fix compile issues with rh_check_supported()
by Jeremy Cline
Sorry for the noise folks, there's a couple bugs in the comment bridge.
I've disabled it for the moment.
On Thu, May 14, 2020 at 08:42:50PM -0000, GitLab Bridge on behalf of ['author'] wrote:
> From: Jeremy Cline on gitlab.com
> https://gitlab.com/cki-project/kernel-ark/-/merge_requests/362#note_34283...
>
> stan <upaitag(a)zoho.com> commented via email:
> ```
> On Thu, 14 May 2020 20:20:52 -0000
> GitLab Bridge on behalf of dzickusrh <jcline(a)redhat.com> wrote:
>
> > From: Don Zickus <dzickus(a)redhat.com>
> >
> > Upstream status: RHEL only
> >
> > The variable x86_hyper_type is hidden behind a macro and not available
> > when guest mode is not config'd enabled.
> >
> > Update to use hypervisor_is_type() macro, available since
>
> Thanks for fixing this.
> ```
3 years, 10 months
RHEL to DIST?
by Prarit Bhargava
Jiri & I have noted that there are many mentions of the "RHEL" throughout the
ARK kernel patches and redhat directory.
In my previous patch jbenc noted:
>>> --- a/redhat/scripts/download_cross.sh
>>> +++ b/redhat/scripts/download_cross.sh
>>> @@ -26,7 +26,7 @@ fi
>>>
>>> # if we're not root, all we can do now is see what's installed
>>> if [ "$(whoami)" != "root" ]; then
>>> - echo "Checking for RHEL7 cross compile packages. If this fails, run \"make rh-cross-download\" as root."
>>> + echo "Checking for RHEL7 cross compile packages. If this fails, run \"make dist-cross-download\" as root."
>>
>> Please change the "RHEL7" as well.
And I replied:
> I noticed the RHEL7 (and other RHEL) mentions as well but felt that they are out of scope for this changeset. I was planning on coming to the list to ask what we should change the "RHEL" phrase to. Distribution?
>
> I'll start a new thread on that. There are other mentions throughout the kernel, for example, "RHEL_MAJOR" and "RHEL_MINOR", andsome of the patches include the phrase "RHEL only". We need to have a consistent policy at modifying all of those.
>
1. Does "DIST"/"Distribution"/"dist" work as a replacement?
2. Do we want to make that change across the kernel?
3. It makes sense to me to fix these in the redhat/ directory. Do we want to
change the "RHEL only" mentions in the patches to something else? "DIST only"
seems wonky.
4. We need to rename the redhat/ dir to something else as well.
P.
3 years, 10 months
✅ PASS: Test report for kernel 5.7.0-0.rc5.1.cki.fc33 (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: d3be85d80b25 - [redhat] kernel-5.7.0-0.rc5.20200513git24085f70a6e1.1
The results of these automated tests are provided below.
Overall result: PASSED
Merge: OK
Compile: OK
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.
,-. ,-.
( 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
kernel repo: https://xci32.lab.eng.rdu2.redhat.com/cki-project/cki-pipeline/-/jobs/836...
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
kernel repo: https://xci32.lab.eng.rdu2.redhat.com/cki-project/cki-pipeline/-/jobs/836...
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
kernel repo: https://xci32.lab.eng.rdu2.redhat.com/cki-project/cki-pipeline/-/jobs/836...
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
kernel repo: https://xci32.lab.eng.rdu2.redhat.com/cki-project/cki-pipeline/-/jobs/836...
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
🚧 ⚡⚡⚡ kdump - sysrq-c
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
✅ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ storage: software RAID testing
⚡⚡⚡ stress: stress-ng
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ storage: iSCSI parameters
ppc64le:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
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
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ 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
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ Storage blktests
s390x:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
⏱ Boot test
⏱ LTP
⏱ Loopdev Sanity
⏱ Memory function: memfd_create
⏱ Networking bridge: sanity
⏱ Ethernet drivers sanity
⏱ Networking MACsec: sanity
⏱ Networking: ipv6/Fujitsu-socketapi-test
⏱ Networking sctp-auth: sockopts 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
⏱ httpd: mod_ssl smoke sanity
⏱ net-snmp: tcp-transport test
⏱ tuned: tune-processes-through-perf
⏱ Usex - version 1.9-29
⏱ CIFS Connectathon
⏱ POSIX pjd-fstest suites
⏱ Memory function: kaslr
⏱ LTP: openposix test suite
⏱ Networking firewall: basic netfilter test
⏱ audit: audit testsuite test
⏱ iotop: sanity
⏱ storage: dm/common
⏱ trace: ftrace/tracer
Host 3:
⏱ Boot test
⏱ selinux-policy: serge-testsuite
⏱ stress: stress-ng
⏱ Storage blktests
x86_64:
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 - megaraid_sas
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
🚧 ⚡⚡⚡ kdump - sysrq-c - mpt3sas_gen1
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 4:
⚡ 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
⚡⚡⚡ Storage SAN device stress - mpt3sas_gen1
Host 5:
✅ Boot test
✅ Storage SAN device stress - qedf driver
Host 6:
⚡ 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
✅ selinux-policy: serge-testsuite
⚡⚡⚡ lvm thinp sanity
✅ storage: software RAID testing
⚡⚡⚡ stress: stress-ng
🚧 ⚡⚡⚡ CPU: Frequency Driver Test
🚧 ⚡⚡⚡ CPU: Idle Test
🚧 ⚡⚡⚡ IOMMU boot test
🚧 ⚡⚡⚡ IPMI driver test
🚧 ⚡⚡⚡ IPMItool loop stress test
🚧 ⚡⚡⚡ power-management: cpupower/sanity test
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ storage: iSCSI parameters
Test sources: https://github.com/CKI-project/tests-beaker
💚 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, 10 months
kernel-ark merge request 354
by Prarit Bhargava
Hey everyone,
I spoke with dzickus about this and he suggested I reach out to the list to get
an idea of how to fix this.
I originally pushed a branch "osnamechange" to gitlab and created merge request
354. That patch, as discussed in the other thread, caused CKI to fail.
jcline commented in 354 that I had to rebase and make changes to his new Sphinx
documentation. So I did
git fetch --all
git pull
git checkout osnamechange
git reset --hard upstream/os-build
<made my changes here and created _1_ patch>
git push -f git@gitlab.com:prarit/kernel-ark.git osnamechange
which logically made sense to me.
The result of this is that I now have 193 identified patches in the merge
request. It appears what has happened is that the reset pulled in all of the
changes from upstream.
So I have some questions ;)
1. What did I do wrong wrt to the kernel-ark workflow?
2. How do undo what I did ;)?
Since no one has reviewed the patch, I could just delete the branch and start
over. I'd rather know what I did wrong so I can avoid doing it in the future.
P.
3 years, 10 months
Fwd: kernel-ark | Pipeline #145379201 has failed for osnamechange |
1b1d4554 in !354
by Prarit Bhargava
jforbes,
My patch in merge request 354 changes the names of makefile targets from rh-* to
dist-* which will obviously cause the failures in the tests below. It looks
like I would have to also change the test code but cannot find a git repo for
it. Any idea where it is and is there a way to push both changes to the kernel
and tests simultaneously?
If that can't be done I guess I could commit a change that adds the dist-*
targets while keeping the rh-* targets, change the tests to use the dist-*
targets, and then another kernel change to remove the rh-* targets. Would that
work?
P.
-------- Forwarded Message --------
Subject: kernel-ark | Pipeline #145379201 has failed for osnamechange |
1b1d4554 in !354
Date: Wed, 13 May 2020 00:07:55 +0000
From: GitLab <gitlab(a)mg.gitlab.com>
Reply-To: GitLab <noreply(a)gitlab.com>
kernel-ark | Pipeline #145379201 has failed for osnamechange | 1b1d4554 in !354
GitLab
✖ Your pipeline has failed.
Project Prarit Bhargava <https://gitlab.com/prarit> / kernel-ark
<https://gitlab.com/prarit/kernel-ark>
Branch
osnamechange <https://gitlab.com/prarit/kernel-ark/-/commits/osnamechange>
Commit
1b1d4554
<https://gitlab.com/prarit/kernel-ark/-/commit/1b1d4554fc1b7f76a690fe9255a...>
in !354 <https://gitlab.com/cki-project/kernel-ark/-/merge_requests/354>
redhat: Change Makefile target names to dist- ...
Commit Author
Prarit Bhargava <https://gitlab.com/prarit>
Pipeline #145379201 <https://gitlab.com/prarit/kernel-ark/pipelines/145379201>
triggered by Prarit Bhargava <https://gitlab.com/prarit>
had 1 failed build.
Logs may contain sensitive data. Please consider before forwarding this email.
✖ test
test_os_build_rh_srpm <https://gitlab.com/prarit/kernel-ark/-/jobs/549546749>
$ eval "$CI_PRE_CLONE_SCRIPT"
Fetching changes with git depth set to 5...
Initialized empty Git repository in /builds/prarit/kernel-ark/.git/
Created fresh repository.
From https://gitlab.com/prarit/kernel-ark
* [new ref] refs/pipelines/145379201 -> refs/pipelines/145379201
* [new branch] osnamechange -> origin/osnamechange
Checking out 1b1d4554 as osnamechange...
Skipping Git submodules setup
Restoring cache
Downloading artifacts
Running before_script and script
Authenticating with credentials from job payload (GitLab Registry)
$ git config user.name "CKI@GitLab"
$ git config user.email "cki-project(a)redhat.com"
$ sed -i 's/=13/=11/g'
redhat/configs/fedora/generic/arm/aarch64/CONFIG_FORCE_MAX_ZONEORDER
$ make rh-srpm
make -C redhat rh-srpm
make[1]: Entering directory '/builds/prarit/kernel-ark/redhat'
fatal: Not a valid object name master
fatal: No names found, cannot describe anything.
BUILDID is ".test".
make[1]: *** No rule to make target 'rh-srpm'. Stop.
make[1]: Leaving directory '/builds/prarit/kernel-ark/redhat'
make: *** [makefile:12: rh-srpm] Error 2
Running after_script
Uploading artifacts for failed job
ERROR: Job failed: exit code 1
GitLab
You're receiving this email because of your account on gitlab.com. Manage all
notifications <https://gitlab.com/profile/notifications> · Help
<https://gitlab.com/help>
3 years, 10 months
Building custom kernel from src.rpm fails for kernel 5.7
by stan
Hi,
I build a custom kernel from the src.rpm for the development kernels,
currently 5.7, on FC31 for x86_64. The 5.6 kernels worked just fine,
but I can't seem to get 5.7 kernels to build.
I first got the multiple %files error because I build perf and tools,
but the [OS-BUILD PATCH] Fix "multiple %files for package kernel-tools"
fixed that. But now I get an rpmbuild error that stops the build, but
it doesn't give me any reason. The note occurs above this last stanza
without issue, so I don't think it has anything to do with the problem.
Can you think of any reason this might be occurring? Could there be
a dependency missing in the spec file? Is it the ar command failing?
Here is the last little bit of output:
./tools/objtool/objtool orc generate --no-fp --uaccess mm/memcontrol.o
if objdump -h mm/memcontrol.o | grep -q __ksymtab; then gcc -E -D__GENKSYMS__ -Wp,-MD,mm/.memcontrol.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/9/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -Wno-address-of-packed-member -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-
format-overflow -Wno-address-of-packed-member -O2 --param=allow-store-data-races=0 -fplugin=./scripts/gcc-plugins/latent_entropy_plugin.so -fplugin=./scripts/gcc-plugins/structleak_plugin.so -fplugin=./scripts/gcc-plugins/randomize_layout_plugin.so -fplugin=./scripts/gcc-plugins/stackleak_plugin.so -DLATENT_ENTROPY_PLUGIN -fplugin-arg-structleak_plugin-verbose -fplugin-arg-structleak_plugin-byref-all -DSTRUCTLEAK_PLUGIN -DRANDSTRUCT_PLUGIN -DSTACKLEAK_PLUGIN -fplugin-arg-stackleak_plugin-track-min-size=100 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fomit-frame-pointer -fno-var-tracking-assignments -fno-inline-functions-called-once -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-ma
p=./= -Wno-packed-not-aligned -DKBUILD_MODFILE='"mm/memcontrol"' -DKBUILD_BASENAME='"memcontrol"' -DKBUILD_MODNAME='"memcontrol"' mm/memcontrol.c | scripts/genksyms/genksyms -r /dev/null > mm/.tmp_memcontrol.ver; ld -m elf_x86_64 -z max-page-size=0x200000 -r -o mm/.tmp_memcontrol.o mm/memcontrol.o -T mm/.tmp_memcontrol.ver; mv -f mm/.tmp_memcontrol.o mm/memcontrol.o; rm -f mm/.tmp_memcontrol.ver; fi
rm -f mm/built-in.a; ar cDPrST mm/built-in.a mm/filemap.o mm/mempool.o mm/oom_kill.o mm/fadvise.o mm/maccess.o mm/page-writeback.o mm/readahead.o mm/swap.o mm/truncate.o mm/vmscan.o mm/shmem.o mm/util.o mm/mmzone.o mm/vmstat.o mm/backing-dev.o mm/mm_init.o mm/mmu_context.o mm/percpu.o mm/slab_common.o mm/compaction.o mm/vmacache.o mm/interval_tree.o mm/list_lru.o mm/workingset.o mm/debug.o mm/gup.o mm/highmem.o mm/memory.o mm/mincore.o mm/mlock.o mm/mmap.o mm/mmu_gather.o mm/mprotect.o mm/mremap.o mm/msync.o mm/page_vma_mapped.o mm/pagewalk.o mm/pgtable-generic.o mm/rmap.o mm/vmalloc.o mm/process_vm_access.o mm/page_alloc.o mm/shuffle.o mm/init-mm.o mm/memblock.o mm/madvise.o mm/page_io.o mm/swap_state.o mm/swapfile.o mm/swap_slots.o mm/frontswap.o mm/zswap.o mm/dmapool.o mm/hugetlb.o mm/mempolicy.o mm/sparse.o mm/sparse-vmemmap.o mm/mmu_notifier.o mm/ksm.o mm/slub.o mm/migrate.o mm/huge_memory.o mm/khugepaged.o mm/page_counter.o mm/memcontrol.o mm/vmpressure.o mm/swap_cgroup.o mm/
memory-failure.o mm/rodata_test.o mm/cleancache.o mm/page_isolation.o mm/zpool.o mm/zbud.o mm/zsmalloc.o mm/early_ioremap.o mm/memfd.o mm/ptdump.o
RPM build errors:
And here is the last little bit of error output:
mm/memcontrol.c: In function 'mem_cgroup_try_charge_swap':
mm/memcontrol.c:7036:23: note: byref variable will be forcibly initialized
7036 | struct page_counter *counter;
| ^~~~~~~
error: Bad exit status from /var/tmp/rpm-tmp.8rFEzz (%build)
Bad exit status from /var/tmp/rpm-tmp.8rFEzz (%build)
3 years, 10 months