Re: ❌ FAIL: Test report for kernel 5.3.8-rc1-740177d.cki (stable)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Xiong, the generic/402 test is failing for both ext4/xfs tests with upstream kernels, including
previous reports. Is this a test issue related to moving to F31 distro or something else ?
Also, the kaslr memory test is failing, but I have seen it fail in previous upstream reports,
hoping someone from the MM-QE@ team can follow up here ?

Thanks,
Rachel
Running test generic/402
#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2016 Deepa Dinamani.  All Rights Reserved.
#
# FS QA Test 402
#
# Test to verify filesystem timestamps for supported ranges.
#
# Exit status 1: test failed.
# Exit status 0: test passed.
FSTYP         -- ext4
PLATFORM      -- Linux/aarch64 apm-mustang-ev3-31 5.3.8-rc1-740177d.cki #1 SMP Sun Oct 27 20:49:25 UTC 2019
MKFS_OPTIONS  -- /dev/sda4
MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:nfs_t:s0 /dev/sda4 /mnt/xfstests/mnt2

generic/402	- output mismatch (see /var/lib/xfstests/results//generic/402.out.bad)
    --- tests/generic/402.out	2019-10-27 17:58:14.916322247 -0400
    +++ /var/lib/xfstests/results//generic/402.out.bad	2019-10-27 18:14:39.392150403 -0400
    @@ -1,2 +1,4 @@
     QA output created by 402
    +15032385535;15032385535 != 15032385536;15032385536
    +15032385535;15032385535 != -2147483648;-2147483648
     Silence is golden
    ...
    (Run 'diff -u /var/lib/xfstests/tests/generic/402.out /var/lib/xfstests/results//generic/402.out.bad'  to see the entire diff)
Ran: generic/402
Failures: generic/402
Failed 1 of 1 tests

Uploading generic-402.full .done
Uploading generic-402.out.bad .done
Uploading generic-402.out.bad.diff .done
** ext4:generic/402 FAIL Score:0
Uploading resultoutputfile.log .done


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   kaslr-compare
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 19:02:29 ] :: [   PASS   ] :: to next state after_r_nokaslr_snapshot (Expected 0, got 0)
:: [ 19:02:29 ] :: [   FAIL   ] :: _text should be non-default (Assert: "ffffffff81000000" should not equal "ffffffff81000000")
:: [ 19:02:30 ] :: [   PASS   ] :: Kernel_code should be non-default (Assert: "01000000" should not equal "8d000000")


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::   kaslr-compare
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 19:02:29 ] :: [   PASS   ] :: to next state after_r_nokaslr_snapshot (Expected 0, got 0)
:: [ 19:02:29 ] :: [   FAIL   ] :: _text should be non-default (Assert: "ffffffff81000000" should not equal "ffffffff81000000")

On 10/27/19 11:26 PM, CKI Project wrote:
Hello,

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

        Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
             Commit: 740177dc0d52 - Linux 5.3.8-rc1

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/251766

One or more kernel tests failed:

     ppc64le:
      ❌ xfstests: ext4
      ❌ xfstests: xfs

     aarch64:
      ❌ xfstests: ext4
      ❌ xfstests: xfs

     x86_64:
      ❌ Memory function: kaslr
      ❌ xfstests: ext4
      ❌ xfstests: xfs

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 3 architectures:

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

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

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


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

   aarch64:
     Host 1:
        ✅ Boot test
        ❌ xfstests: ext4
        ❌ xfstests: xfs
        ✅ selinux-policy: serge-testsuite
        ✅ lvm thinp sanity
        ✅ storage: software RAID testing
        🚧 ✅ Storage blktests

     Host 2:
        ✅ Boot test
        ✅ Podman system integration test (as root)
        ✅ Podman system integration test (as user)
        ✅ LTP lite
        ✅ Loopdev Sanity
        ✅ jvm test suite
        ✅ Memory function: memfd_create
        ✅ Memory function: kaslr
        ✅ AMTU (Abstract Machine Test Utility)
        ✅ LTP: openposix test suite
        ✅ Ethernet drivers sanity
        ✅ Networking MACsec: sanity
        ✅ Networking socket: fuzz
        ✅ Networking sctp-auth: sockopts test
        ✅ Networking: igmp conformance test
        ✅ Networking route: pmtu
        ✅ Networking TCP: keepalive test
        ✅ Networking UDP: socket
        ✅ Networking tunnel: geneve basic test
        ✅ Networking tunnel: gre basic
        ✅ Networking tunnel: vxlan basic
        ✅ audit: audit testsuite test
        ✅ httpd: mod_ssl smoke sanity
        ✅ iotop: sanity
        ✅ tuned: tune-processes-through-perf
        ✅ ALSA PCM loopback test
        ✅ ALSA Control (mixer) Userspace Element test
        ✅ Usex - version 1.9-29
        ✅ storage: SCSI VPD
        ✅ stress: stress-ng
        ✅ trace: ftrace/tracer
        🚧 ✅ CIFS Connectathon
        🚧 ✅ POSIX pjd-fstest suites
        🚧 ✅ Networking bridge: sanity
        🚧 ✅ Networking route_func: local
        ✅ Networking route_func: forward
        🚧 ✅ L2TP basic test
        🚧 ✅ Networking vnic: ipvlan/basic
        🚧 ✅ storage: dm/common
        🚧 ✅ Networking ipsec: basic netns transport
        🚧 ✅ Networking ipsec: basic netns tunnel

   ppc64le:
     Host 1:
        ✅ Boot test
        ❌ xfstests: ext4
        ❌ xfstests: xfs
        ✅ selinux-policy: serge-testsuite
        ✅ lvm thinp sanity
        ✅ storage: software RAID testing
        🚧 ✅ Storage blktests

     Host 2:
        ✅ Boot test
        ✅ Podman system integration test (as root)
        ✅ Podman system integration test (as user)
        ✅ LTP lite
        ✅ Loopdev Sanity
        ✅ jvm test suite
        ✅ Memory function: memfd_create
        ✅ Memory function: kaslr
        ✅ AMTU (Abstract Machine Test Utility)
        ✅ LTP: openposix test suite
        ✅ Ethernet drivers sanity
        ✅ Networking MACsec: sanity
        ✅ Networking socket: fuzz
        ✅ Networking sctp-auth: sockopts test
        ✅ Networking route: pmtu
        ✅ Networking TCP: keepalive test
        ✅ Networking UDP: socket
        ✅ Networking tunnel: geneve basic test
        ✅ Networking tunnel: gre basic
        ✅ Networking tunnel: vxlan basic
        ✅ audit: audit testsuite test
        ✅ httpd: mod_ssl smoke sanity
        ✅ iotop: sanity
        ✅ tuned: tune-processes-through-perf
        ✅ ALSA PCM loopback test
        ✅ ALSA Control (mixer) Userspace Element test
        ✅ Usex - version 1.9-29
        ✅ trace: ftrace/tracer
        🚧 ✅ CIFS Connectathon
        🚧 ✅ POSIX pjd-fstest suites
        🚧 ✅ Networking bridge: sanity
        🚧 ✅ Networking route_func: local
        ✅ Networking route_func: forward
        🚧 ✅ L2TP basic test
        🚧 ✅ Networking ipsec: basic netns tunnel
        🚧 ✅ Networking vnic: ipvlan/basic
        🚧 ✅ storage: dm/common

   x86_64:
     Host 1:
        ✅ Boot test
        🚧 ✅ IPMI driver test
        🚧 ✅ IPMItool loop stress test

     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
        ✅ Podman system integration test (as root)
        ✅ Podman system integration test (as user)
        ⚡⚡⚡ LTP lite
        ✅ Loopdev Sanity
        ✅ jvm test suite
        ✅ Memory function: memfd_create
        ❌ Memory function: kaslr
        ✅ AMTU (Abstract Machine Test Utility)
        ✅ LTP: openposix test suite
        ✅ Ethernet drivers sanity
        ✅ Networking MACsec: sanity
        ✅ Networking socket: fuzz
        ✅ Networking sctp-auth: sockopts test
        ✅ Networking: igmp conformance test
        ✅ Networking route: pmtu
        ✅ Networking TCP: keepalive test
        ✅ Networking UDP: socket
        ✅ Networking tunnel: geneve basic test
        ✅ Networking tunnel: gre basic
        ✅ Networking tunnel: vxlan basic
        ✅ audit: audit testsuite test
        ✅ httpd: mod_ssl smoke sanity
        ✅ iotop: sanity
        ✅ tuned: tune-processes-through-perf
        ✅ pciutils: sanity smoke test
        ✅ ALSA PCM loopback test
        ✅ ALSA Control (mixer) Userspace Element test
        ✅ Usex - version 1.9-29
        ✅ storage: SCSI VPD
        ✅ stress: stress-ng
        ✅ trace: ftrace/tracer
        🚧 ✅ CIFS Connectathon
        🚧 ✅ POSIX pjd-fstest suites
        🚧 ✅ Networking bridge: sanity
        🚧 ✅ Networking route_func: local
        ✅ Networking route_func: forward
        🚧 ✅ L2TP basic test
        🚧 ✅ Networking vnic: ipvlan/basic
        🚧 ✅ storage: dm/common
        🚧 ✅ Networking ipsec: basic netns transport
        🚧 ✅ Networking ipsec: basic netns tunnel

     Host 3:
        ✅ Boot test
        ❌ xfstests: ext4
        ❌ xfstests: xfs
        ✅ selinux-policy: serge-testsuite
        ✅ lvm thinp sanity
        ✅ storage: software RAID testing
        🚧 ✅ IOMMU boot test
        🚧 ❌ Storage blktests

   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.






[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux