All of
 help / color / mirror / Atom feed
From: CKI Project <>
Subject: ✅ PASS: Test report for kernel 5.11.0-rc4 (arm-next)
Date: Tue, 19 Jan 2021 01:52:30 -0000	[thread overview]
Message-ID: <> (raw)


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

       Kernel repo:
            Commit: 1330e98ab831 - genirq: Export irq_check_status_bit()

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:

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:

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

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

    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
       ✅ 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

    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
       ✅ 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

  Test sources:
    💚 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

             reply	other threads:[~2021-01-19  1:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  1:52 CKI Project [this message]
2021-01-21  0:40 ✅ PASS: Test report for kernel 5.11.0-rc4 (arm-next) CKI Project

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.