❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

6 messages, 3 authors, 2021-01-22 · open the first message on its own page

❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: CKI Project <hidden>
Date: 2021-01-22 04:48:13

Hello,

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

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
            Commit: 3c50969f0be2 - Merge branches 'for-next/from-tip/irq/urgent', 'for-next/misc', 'for-next/perf', 'for-next/random', 'for-next/rng', 'for-next/selftests', 'for-next/stacktrace', 'for-next/topology' and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

    aarch64:
     ❌ LTP

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: make  -j30 INSTALL_MOD_STRIP=1 targz-pkg



Hardware testing
----------------
We booted each kernel and ran the following tests:

  aarch64:
    Host 1:
       ✅ 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
       🚧 ✅ CIFS Connectathon
       🚧 ✅ POSIX pjd-fstest suites
       🚧 ✅ Firmware test suite
       🚧 ✅ jvm - jcstress tests
       🚧 ✅ Memory function: kaslr
       🚧 ✅ Ethernet drivers sanity
       🚧 ✅ Networking firewall: basic netfilter test
       🚧 ✅ audit: audit testsuite test
       🚧 ✅ trace: ftrace/tracer
       🚧 ❌ kdump - kexec_boot

    Host 2:
       ✅ Boot test
       ✅ selinux-policy: serge-testsuite
       ✅ storage: software RAID testing
       ✅ stress: stress-ng
       🚧 ✅ 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: swraid mdadm raid_module 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 ⏱.


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: Will Deacon <will@kernel.org>
Date: 2021-01-22 11:51:09

On Fri, Jan 22, 2021 at 04:46:27AM -0000, CKI Project wrote:
We ran automated tests on a recent commit from this kernel tree:

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
            Commit: 3c50969f0be2 - Merge branches 'for-next/from-tip/irq/urgent', 'for-next/misc', 'for-next/perf', 'for-next/random', 'for-next/rng', 'for-next/selftests', 'for-next/stacktrace', 'for-next/topology' and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

    aarch64:
     ❌ LTP
Hmm, this seems to be as a result of this error:

     7	netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
     8	RTNETLINK answers: Operation not permitted
     9	netns_breakns 1 TBROK: unable to create veth pair devices
    10	Cannot find device "veth0"

(https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log)

which doesn't look immediately related to anything we've queued on the arm64
side. CKI folks -- have you seen this failure anywhere else, and is it
reproducible?

Thanks,

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: Rachel Sibley <hidden>
Date: 2021-01-22 15:00:50


On 1/22/21 6:49 AM, Will Deacon wrote:
On Fri, Jan 22, 2021 at 04:46:27AM -0000, CKI Project wrote:
quoted
We ran automated tests on a recent commit from this kernel tree:

        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
             Commit: 3c50969f0be2 - Merge branches 'for-next/from-tip/irq/urgent', 'for-next/misc', 'for-next/perf', 'for-next/random', 'for-next/rng', 'for-next/selftests', 'for-next/stacktrace', 'for-next/topology' and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

     aarch64:
      ❌ LTP
Hmm, this seems to be as a result of this error:

      7	netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
      8	RTNETLINK answers: Operation not permitted
      9	netns_breakns 1 TBROK: unable to create veth pair devices
     10	Cannot find device "veth0"

(https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log)

which doesn't look immediately related to anything we've queued on the arm64
side. CKI folks -- have you seen this failure anywhere else, and is it
reproducible?
The netns suite was recently rewritten upstream so most likely a result of an unstable test case, Li/Jan do you have more details ?
I'm attempting to reproduce it right now, will keep you you updated:

https://github.com/linux-test-project/ltp/commit/cc82df62b26f6bbf63a4f375a98019af44ae023d

Thanks,
Rachel
Thanks,

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: Rachel Sibley <hidden>
Date: 2021-01-22 19:40:44


On 1/22/21 9:57 AM, Rachel Sibley wrote:

On 1/22/21 6:49 AM, Will Deacon wrote:
quoted
On Fri, Jan 22, 2021 at 04:46:27AM -0000, CKI Project wrote:
quoted
We ran automated tests on a recent commit from this kernel tree:

        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
             Commit: 3c50969f0be2 - Merge branches 'for-next/from-tip/irq/urgent', 'for-next/misc', 'for-next/perf', 'for-next/random', 
'for-next/rng', 'for-next/selftests', 'for-next/stacktrace', 'for-next/topology' and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

     aarch64:
      ❌ LTP
Hmm, this seems to be as a result of this error:

      7    netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
      8    RTNETLINK answers: Operation not permitted
      9    netns_breakns 1 TBROK: unable to create veth pair devices
     10    Cannot find device "veth0"

(https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log) 


which doesn't look immediately related to anything we've queued on the arm64
side. CKI folks -- have you seen this failure anywhere else, and is it
reproducible?
The netns suite was recently rewritten upstream so most likely a result of an unstable test case, Li/Jan do you have more details ?
I'm attempting to reproduce it right now, will keep you you updated:
I was unable to reproduce this, so maybe a transient error ? I added this failure to have our bot triager monitor it,
if it tags additional pipelines we can follow up and report and/or mask it going forward. Please feel free to ignore
for now, thank you!
https://github.com/linux-test-project/ltp/commit/cc82df62b26f6bbf63a4f375a98019af44ae023d

Thanks,
Rachel
quoted
Thanks,

Will

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: Will Deacon <will@kernel.org>
Date: 2021-01-22 19:51:43

On Fri, Jan 22, 2021 at 02:38:49PM -0500, Rachel Sibley wrote:
On 1/22/21 9:57 AM, Rachel Sibley wrote:
quoted
On 1/22/21 6:49 AM, Will Deacon wrote:
quoted
On Fri, Jan 22, 2021 at 04:46:27AM -0000, CKI Project wrote:
quoted
We ran automated tests on a recent commit from this kernel tree:

        Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
             Commit: 3c50969f0be2 - Merge branches
'for-next/from-tip/irq/urgent', 'for-next/misc',
'for-next/perf', 'for-next/random', 'for-next/rng',
'for-next/selftests', 'for-next/stacktrace', 'for-next/topology'
and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

     aarch64:
      ❌ LTP
Hmm, this seems to be as a result of this error:

      7    netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
      8    RTNETLINK answers: Operation not permitted
      9    netns_breakns 1 TBROK: unable to create veth pair devices
     10    Cannot find device "veth0"

(https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log)


which doesn't look immediately related to anything we've queued on the arm64
side. CKI folks -- have you seen this failure anywhere else, and is it
reproducible?
The netns suite was recently rewritten upstream so most likely a result of an unstable test case, Li/Jan do you have more details ?
I'm attempting to reproduce it right now, will keep you you updated:
I was unable to reproduce this, so maybe a transient error ? I added this failure to have our bot triager monitor it,
if it tags additional pipelines we can follow up and report and/or mask it going forward. Please feel free to ignore
for now, thank you!
Cheers, Rachel. If it comes back _and_ we have patches which look
potentially relevant then I'll reply to see if you can help me with the
triage.

Thanks,

WIll

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Re: ❌ FAIL: Test report for kernel 5.11.0-rc4 (arm-next)

From: Rachel Sibley <hidden>
Date: 2021-01-22 20:32:18


On 1/22/21 2:50 PM, Will Deacon wrote:
On Fri, Jan 22, 2021 at 02:38:49PM -0500, Rachel Sibley wrote:
quoted
On 1/22/21 9:57 AM, Rachel Sibley wrote:
quoted
On 1/22/21 6:49 AM, Will Deacon wrote:
quoted
On Fri, Jan 22, 2021 at 04:46:27AM -0000, CKI Project wrote:
quoted
We ran automated tests on a recent commit from this kernel tree:

         Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
              Commit: 3c50969f0be2 - Merge branches
'for-next/from-tip/irq/urgent', 'for-next/misc',
'for-next/perf', 'for-next/random', 'for-next/rng',
'for-next/selftests', 'for-next/stacktrace', 'for-next/topology'
and 'for-next/vdso' into for-next/core

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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/01/21/621932

One or more kernel tests failed:

      aarch64:
       ❌ LTP
Hmm, this seems to be as a result of this error:

       7    netns_breakns 1 TINFO: timeout per run is 0h 5m 0s
       8    RTNETLINK answers: Operation not permitted
       9    netns_breakns 1 TBROK: unable to create veth pair devices
      10    Cannot find device "veth0"

(https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/datawarehouse-public/2021/01/21/621932/build_aarch64_redhat%3A1078955/tests/LTP/9444882_aarch64_1_containers.fail.log)


which doesn't look immediately related to anything we've queued on the arm64
side. CKI folks -- have you seen this failure anywhere else, and is it
reproducible?
The netns suite was recently rewritten upstream so most likely a result of an unstable test case, Li/Jan do you have more details ?
I'm attempting to reproduce it right now, will keep you you updated:
I was unable to reproduce this, so maybe a transient error ? I added this failure to have our bot triager monitor it,
if it tags additional pipelines we can follow up and report and/or mask it going forward. Please feel free to ignore
for now, thank you!
Cheers, Rachel. If it comes back _and_ we have patches which look
potentially relevant then I'll reply to see if you can help me with the
triage.
Sounds good have a great weekend !
Thanks,

WIll

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help