Skip to contentSkip to conversation

❌ FAIL: Test report for kernel 5.5.0-rc6-e31626d.cki (arm-next)

DISCUSSION CKI Project 3 participants 4 messages Jan 15, 2020

lore
Share & tools
lore
#0 lore raw

Hello,

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Commit: e31626d443db - Merge branches 'for-next/asm-annotations', 'for-next/cpufeatures', 'for-next/e0pd', 'for-next/kexec/cleanup', 'for-next/kexec/file-kdump', 'for-next/misc', 'for-next/nofpsimd' and 'for-next/perf' into for-kernelci

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

https://artifacts.cki-project.org/pipelines/383787

One or more kernel tests failed:

aarch64:
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic

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 1 architecture:

aarch64:
make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg

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
✅ Podman system integration test (as root) ✅ Podman system integration test (as user) ✅ 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 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 ⚡⚡⚡ audit: audit testsuite test
⚡⚡⚡ httpd: mod_ssl smoke sanity
⚡⚡⚡ tuned: tune-processes-through-perf ⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test ⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ jvm test suite
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ LTP: openposix test suite
🚧 ⚡⚡⚡ Networking vnic: ipvlan/basic
🚧 ⚡⚡⚡ iotop: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ storage: dm/common

Host 2:
✅ 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

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
⚡⚡⚡ Podman system integration test (as root) ⚡⚡⚡ Podman system integration test (as user) ⚡⚡⚡ 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 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 ⚡⚡⚡ audit: audit testsuite test
⚡⚡⚡ httpd: mod_ssl smoke sanity
⚡⚡⚡ tuned: tune-processes-through-perf ⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test ⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ jvm test suite
🚧 ⚡⚡⚡ Memory function: kaslr
🚧 ⚡⚡⚡ LTP: openposix test suite
🚧 ⚡⚡⚡ Networking vnic: ipvlan/basic
🚧 ⚡⚡⚡ iotop: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ storage: dm/common

Host 4:
✅ Boot test
✅ Podman system integration test (as root) ✅ Podman system integration test (as user) ✅ 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 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 ⏱ audit: audit testsuite test
⏱ httpd: mod_ssl smoke sanity
⏱ tuned: tune-processes-through-perf ⏱ ALSA PCM loopback test
⏱ ALSA Control (mixer) Userspace Element test ⏱ storage: SCSI VPD
⏱ trace: ftrace/tracer
⏱ CIFS Connectathon
⏱ POSIX pjd-fstest suites
⏱ jvm test suite
⏱ Memory function: kaslr
⏱ LTP: openposix test suite
⏱ Networking vnic: ipvlan/basic
⏱ iotop: sanity
⏱ Usex - version 1.9-29
⏱ storage: dm/common

Test sources: https://github.com/CKI-project/tests-beaker
💚 Pull requests are welcome for new tests or improvements to existing tests!

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 are marked with ⏱. Reports for non-upstream kernels have a Beaker recipe linked to next to each host.

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

#1 lore raw

Hi,

Quoted 14 lines · CKI Project

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Commit: e31626d443db - Merge branches 'for-next/asm-annotations', 'for-next/cpufeatures', 'for-next/e0pd', 'for-next/kexec/cleanup', 'for-next/kexec/file-kdump', 'for-next/misc', 'for-next/nofpsimd' and 'for-next/perf' into for-kernelci

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

Quoted 7 lines

https://artifacts.cki-project.org/pipelines/383787

One or more kernel tests failed:

aarch64:
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic

Hmm. If I look at the files corresponding to those tests in the logs linked to above, they all seem to have passed. For example:

https://artifacts.cki-project.org/pipelines/383787/logs/aarch64_host_1_Networking_tunnel__gre_basic_resultoutputfile.log

Am I missing something?

Cheers,

Will

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

#2 lore raw
Quoted 26 lines · Will Deacon

Hi,

Quoted 14 lines · CKI Project

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Commit: e31626d443db - Merge branches 'for-next/asm-annotations', 'for-next/cpufeatures', 'for-next/e0pd', 'for-next/kexec/cleanup', 'for-next/kexec/file-kdump', 'for-next/misc', 'for-next/nofpsimd' and 'for-next/perf' into for-kernelci

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

Quoted 7 lines
   https://artifacts.cki-project.org/pipelines/383787

One or more kernel tests failed:

aarch64:
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic

Quoted 6 lines

Hmm. If I look at the files corresponding to those tests in the logs linked to above, they all seem to have passed. For example:

https://artifacts.cki-project.org/pipelines/383787/logs/aarch64_host_1_Networking_tunnel__gre_basic_resultoutputfile.log

Am I missing something?

Hi Will,

This is an infrastructure problem with restraint harness, it's taking too long extracting the tests-beaker repo where our tests live and watchdog is aborting the tests during setup phase. We are actively debugging this problem. Feel free to ignore these failures, sorry for the noise!

-Rachel

Quoted 6 lines

Cheers,

Will

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

#3 lore raw

Hi Rachel,

Quoted 28 lines · Rachel Sibley
Quoted 27 lines · Will Deacon
Quoted 14 lines · CKI Project

We ran automated tests on a recent commit from this kernel tree:

Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
Commit: e31626d443db - Merge branches 'for-next/asm-annotations', 'for-next/cpufeatures', 'for-next/e0pd', 'for-next/kexec/cleanup', 'for-next/kexec/file-kdump', 'for-next/misc', 'for-next/nofpsimd' and 'for-next/perf' into for-kernelci

The results of these automated tests are provided below.

Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED

All kernel binaries, config files, and logs are available for download here:

Quoted 7 lines
   https://artifacts.cki-project.org/pipelines/383787

One or more kernel tests failed:

aarch64:
❌ Networking tunnel: geneve basic test
❌ Networking tunnel: gre basic

Hmm. If I look at the files corresponding to those tests in the logs linked to above, they all seem to have passed. For example:

Quoted 8 lines
Quoted 3 lines

https://artifacts.cki-project.org/pipelines/383787/logs/aarch64_host_1_Networking_tunnel__gre_basic_resultoutputfile.log

Am I missing something?

This is an infrastructure problem with restraint harness, it's taking too long extracting the tests-beaker repo where our tests live and watchdog is aborting the tests during setup phase. We are actively debugging this problem. Feel free to ignore these failures, sorry for the noise!

Okey doke, I'm more than happy to ignore them :)

Thanks for the quick reply.

Will

_______________________________________________
linux-arm-kernel mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel