public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: CKI Project <cki-project@redhat.com>
To: skt-results-master@redhat.com, linux-block@vger.kernel.org,
	axboe@kernel.dk
Cc: Memory Management <mm-qe@redhat.com>,
	Jianhong Yin <jiyin@redhat.com>, Zorro Lang <zlang@redhat.com>,
	Yi Zhang <yizhan@redhat.com>, Fine Fan <ffan@redhat.com>,
	Jeff Bastian <jbastian@redhat.com>, Xiong Zhou <xzhou@redhat.com>,
	Jan Stancek <jstancek@redhat.com>, Al Stone <ahs3@redhat.com>,
	Guangwu Zhang <guazhang@redhat.com>, Lin Li <lilin@redhat.com>,
	Marco Patalano <mpatalan@redhat.com>
Subject: ❌ FAIL: Test report for kernel 5.11.0 (block)
Date: Tue, 23 Feb 2021 13:30:14 -0000	[thread overview]
Message-ID: <cki.1891A5313F.9U2FASPBG7@redhat.com> (raw)


Hello,

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

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
            Commit: 5c351b75f71a - Merge branch 'io_uring-worker.v3' into for-next

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/02/23/624525

One or more kernel tests failed:

    s390x:
     ❌ Memory function: memfd_create
     ❌ AMTU (Abstract Machine Test Utility)

    ppc64le:
     ❌ storage: software RAID testing
     ❌ LTP
     ❌ Memory function: memfd_create
     ❌ AMTU (Abstract Machine Test Utility)

    aarch64:
     ❌ ACPI table test
     ❌ Memory function: memfd_create
     ❌ storage: SCSI VPD
     ❌ storage: software RAID testing

    x86_64:
     ❌ Storage SAN device stress - mpt3sas_gen1
     ❌ storage: software RAID testing
     ❌ Storage SAN device stress - lpfc driver
     ❌ Storage SAN device stress - qedf driver
     ❌ ACPI table test
     ❌ Memory function: memfd_create
     ❌ storage: SCSI VPD
     ❌ Storage SAN device stress - qla2xxx driver

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

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

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

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

    x86_64:
      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
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ❌ storage: SCSI VPD
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 2:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

  ppc64le:
    Host 1:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test

    Host 2:
       ✅ Boot test
       ❌ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ❌ AMTU (Abstract Machine Test Utility)
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

  s390x:
    Host 1:
       ✅ Boot test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ❌ AMTU (Abstract Machine Test Utility)
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 2:
       ✅ Boot test
       🚧 ❌ Storage blktests
       🚧 ✅ Storage nvme - tcp
       🚧 ❌ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

  x86_64:
    Host 1:
       ✅ Boot test
       ❌ Storage SAN device stress - mpt3sas_gen1

    Host 2:
       ✅ Boot test
       ❌ storage: software RAID testing
       🚧 ❌ xfstests - ext4
       🚧 ✅ xfstests - xfs
       🚧 ✅ xfstests - btrfs
       🚧 ✅ xfstests - nfsv4.2
       🚧 ✅ xfstests - cifsv3.11
       🚧 ❌ Storage blktests
       🚧 ✅ Storage block - filesystem fio test
       🚧 ✅ Storage block - queue scheduler test
       🚧 ✅ Storage nvme - tcp
       🚧 ✅ Storage: swraid mdadm raid_module test
       🚧 ❌ stress: stress-ng

    Host 3:
       ✅ Boot test
       ❌ Storage SAN device stress - lpfc driver

    Host 4:
       ✅ Boot test
       ❌ Storage SAN device stress - qedf driver

    Host 5:
       ✅ Boot test
       ❌ ACPI table test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ❌ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ❌ storage: SCSI VPD
       🚧 ❌ CIFS Connectathon
       🚧 ❌ POSIX pjd-fstest suites
       🚧 ✅ Ethernet drivers sanity

    Host 6:
       ✅ Boot test
       ❌ Storage SAN device stress - qla2xxx driver

  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 ⏱.


             reply	other threads:[~2021-02-23 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 13:30 CKI Project [this message]
     [not found] ` <CA+QYu4qihd=wkrknUjaLtGFa4AGpweMWL4Wg=ZPyn=_Mdsx_jg@mail.gmail.com>
2021-02-23 18:59   ` ❌ FAIL: Test report for kernel 5.11.0 (block) Jens Axboe
2021-02-24  8:52     ` Bruno Goncalves

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=cki.1891A5313F.9U2FASPBG7@redhat.com \
    --to=cki-project@redhat.com \
    --cc=ahs3@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=ffan@redhat.com \
    --cc=guazhang@redhat.com \
    --cc=jbastian@redhat.com \
    --cc=jiyin@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=lilin@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mm-qe@redhat.com \
    --cc=mpatalan@redhat.com \
    --cc=skt-results-master@redhat.com \
    --cc=xzhou@redhat.com \
    --cc=yizhan@redhat.com \
    --cc=zlang@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox