✅ PASS: Test report for kernel 5.6.10-200.fc31 (fedora-31) - kernel - Fedora mailing-lists

4 May 2020


      Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.6.10-200.fc31
         Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=44087986
The results of these automated tests are provided below.
Overall result: PASSED
             Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawareh...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-.   ,-.
       ( C ) ( K )  Continuous
        `-',-.`-'   Kernel
          ( I )     Integration
           `-'
______________________________________________________________________________
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
       ⚡⚡⚡ lvm thinp sanity
       ⚡⚡⚡ stress: stress-ng
       🚧 ⚡⚡⚡ Storage blktests
Host 2:
       ✅ Boot test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Ethernet drivers sanity
       🚧 ✅ CIFS Connectathon
       🚧 ✅ LTP: openposix test suite
Host 3:
       ✅ Boot test
       ✅ xfstests - ext4
       ✅ xfstests - xfs
       ✅ lvm thinp sanity
       🚧 ✅ Storage blktests
ppc64le:
    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
       ⚡⚡⚡ LTP
       ✅ Loopdev Sanity
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Ethernet drivers sanity
       🚧 ✅ CIFS Connectathon
       🚧 ✅ LTP: openposix test suite
Host 2:
       ✅ Boot test
       ✅ xfstests - ext4
       ✅ xfstests - xfs
       ✅ lvm thinp sanity
       🚧 ❌ Storage blktests
s390x:
    Host 1:
       ✅ Boot test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory function: memfd_create
       ✅ Ethernet drivers sanity
       🚧 ✅ CIFS Connectathon
       🚧 ✅ LTP: openposix test suite
Host 2:
       ✅ Boot test
       ✅ stress: stress-ng
       🚧 ❌ Storage blktests
x86_64:
    Host 1:
       ✅ Boot test
       ✅ xfstests - ext4
       ✅ xfstests - xfs
       ✅ lvm thinp sanity
       ✅ stress: stress-ng
       🚧 ❌ Storage blktests
Host 2:
       ✅ Boot test
       ✅ LTP
       ✅ Loopdev Sanity
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Ethernet drivers sanity
       🚧 ✅ CIFS Connectathon
       🚧 ✅ LTP: openposix test suite
Test sources: https://github.com/CKI-project/tests-beaker
    💚 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 ⏱.