Stable Archive on lore.kernel.org
 help / color / Atom feed
* ❌ FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable)
@ 2020-01-15  6:06 CKI Project
  2020-01-16 16:02 ` [LTP] ??? " Cyril Hrubis
  0 siblings, 1 reply; 2+ messages in thread
From: CKI Project @ 2020-01-15  6:06 UTC (permalink / raw)
  To: Linux Stable maillist
  Cc: Memory Management, Jan Stancek, LTP Mailing List, Jianlin Shi,
	Jianwen Ji, Hangbin Liu, William Gomeringer


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: 5c903e10834d - Linux 5.4.12-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/382907

One or more kernel tests failed:

    ppc64le:
     ❌ LTP

    aarch64:
     ❌ Networking route_func: local
     ❌ Networking tunnel: geneve basic test
     ❌ Networking tunnel: gre basic
     ❌ Networking tunnel: vxlan 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 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:

       ⚡ 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

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

  ppc64le:
    Host 1:
       ✅ 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 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
       ✅ audit: audit testsuite test
       ✅ httpd: mod_ssl smoke sanity
       ✅ tuned: tune-processes-through-perf
       ✅ ALSA PCM loopback test
       ✅ ALSA Control (mixer) Userspace Element test
       ✅ 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
       🚧 ✅ IPMI driver test
       🚧 ✅ IPMItool loop stress test
       🚧 ✅ 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
       ✅ xfstests: ext4
       ✅ xfstests: xfs
       ✅ selinux-policy: serge-testsuite
       ✅ lvm thinp sanity
       ✅ storage: software RAID testing
       ✅ stress: stress-ng
       🚧 ❌ IOMMU boot test
       🚧 ✅ IPMI driver test
       🚧 ✅ IPMItool loop stress test
       🚧 ⚡⚡⚡ power-management: cpupower/sanity test
       🚧 ✅ Storage blktests

    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
       ⚡⚡⚡ Storage SAN device stress - mpt3sas driver

    Host 3:
       ✅ 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
       ✅ pciutils: sanity smoke test
       ✅ 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:

       ⚡ 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 - megaraid_sas

    Host 5:
       ✅ Boot test
       ✅ Storage SAN device stress - mpt3sas 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
       ⚡⚡⚡ Storage SAN device stress - megaraid_sas

  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.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [LTP] ??? FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable)
  2020-01-15  6:06 ❌ FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable) CKI Project
@ 2020-01-16 16:02 ` " Cyril Hrubis
  0 siblings, 0 replies; 2+ messages in thread
From: Cyril Hrubis @ 2020-01-16 16:02 UTC (permalink / raw)
  To: CKI Project
  Cc: Linux Stable maillist, Jianwen Ji, Hangbin Liu,
	Memory Management, Jianlin Shi, LTP Mailing List,
	William Gomeringer

Hi!
This looks like max_map_count failure again.

...
<<<test_output>>>
tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s
mem.c:817: INFO: set overcommit_memory to 2
mem.c:817: INFO: set max_map_count to 1024
max_map_count.c:198: PASS: 1024 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 2048
max_map_count.c:198: PASS: 2048 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 4096
max_map_count.c:198: PASS: 4096 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 8192
max_map_count.c:198: PASS: 8192 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 16384
max_map_count.c:198: PASS: 16384 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 32768
max_map_count.c:198: PASS: 32768 map entries in total as expected.
mem.c:817: INFO: set max_map_count to 65536
max_map_count.c:201: FAIL: 65273 map entries in total, but expected 65536 entries
mem.c:817: INFO: set max_map_count to 1024
max_map_count.c:198: PASS: 1024 map entries in total as expected.
...

-- 
Cyril Hrubis
chrubis@suse.cz

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15  6:06 ❌ FAIL: Test report for kernel 5.4.12-rc1-5c903e1.cki (stable) CKI Project
2020-01-16 16:02 ` [LTP] ??? " Cyril Hrubis

Stable Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://lore.kernel.org/stable \
		stable@vger.kernel.org
	public-inbox-index stable

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git