All of lore.kernel.org
 help / color / mirror / Atom feed
From: CKI Project <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: ✅ PASS: Stable queue: queue-5.2
Date: Mon, 16 Sep 2019 13:53:34 -0400	[thread overview]
Message-ID: <cki.A1549FEC70.PUGPO9WRRJ@redhat.com> (raw)


Hello,

We ran automated tests on a patchset that was proposed for merging into this
kernel tree. The patches were applied to:

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
            Commit: 6e282ba6ff6b - Linux 5.2.15

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:

  https://artifacts.cki-project.org/pipelines/168287

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
           `-'
______________________________________________________________________________

Merge testing
-------------

We cloned this repository and checked out the following commit:

  Repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
  Commit: 6e282ba6ff6b - Linux 5.2.15


We grabbed the b3793b83d825 commit of the stable queue repository.

We then merged the patchset with `git am`:

  bridge-mdb-remove-wrong-use-of-nlm_f_multi.patch
  cdc_ether-fix-rndis-support-for-mediatek-based-smartphones.patch
  ipv6-fix-the-link-time-qualifier-of-ping_v6_proc_exit_net.patch
  isdn-capi-check-message-length-in-capi_write.patch
  ixgbe-fix-secpath-usage-for-ipsec-tx-offload.patch
  ixgbevf-fix-secpath-usage-for-ipsec-tx-offload.patch
  net-fix-null-de-reference-of-device-refcount.patch
  net-gso-fix-skb_segment-splat-when-splitting-gso_size-mangled-skb-having-linear-headed-frag_list.patch
  net-phylink-fix-flow-control-resolution.patch
  net-sched-fix-reordering-issues.patch
  sch_hhf-ensure-quantum-and-hhf_non_hh_weight-are-non-zero.patch
  sctp-fix-the-link-time-qualifier-of-sctp_ctrlsock_exit.patch
  sctp-use-transport-pf_retrans-in-sctp_do_8_2_transport_strike.patch
  tcp-fix-tcp_ecn_withdraw_cwr-to-clear-tcp_ecn_queue_cwr.patch
  tipc-add-null-pointer-check-before-calling-kfree_rcu.patch
  tun-fix-use-after-free-when-register-netdev-failed.patch
  net-ipv6-fix-excessive-rtf_addrconf-flag-on-1-128-local-route-and-others.patch
  ipv6-addrconf_f6i_alloc-fix-non-null-pointer-check-to-is_err.patch
  net-fixed_phy-add-forward-declaration-for-struct-gpio_desc.patch
  sctp-fix-the-missing-put_user-when-dumping-transport-thresholds.patch
  net-sock_map-fix-missing-ulp-check-in-sock-hash-case.patch

Compile testing
---------------

We compiled the kernel for 4 architectures:

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

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

    s390x:
      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 [0]
         ✅ Podman system integration test (as root) [1]
         ✅ Podman system integration test (as user) [1]
         ✅ jvm test suite [2]
         ✅ AMTU (Abstract Machine Test Utility) [3]
         ✅ LTP: openposix test suite [4]
         ✅ Ethernet drivers sanity [5]
         ✅ Networking socket: fuzz [6]
         ✅ Networking sctp-auth: sockopts test [7]
         ✅ Networking TCP: keepalive test [8]
         ✅ audit: audit testsuite test [9]
         ✅ httpd: mod_ssl smoke sanity [10]
         ✅ iotop: sanity [11]
         ✅ tuned: tune-processes-through-perf [12]
         ✅ stress: stress-ng [13]
         🚧 ✅ LTP lite [14]
         🚧 ✅ Networking bridge: sanity [15]
         🚧 ✅ Networking route: pmtu [16]
         🚧 ✅ Networking route_func: local [17]
         🚧 ✅ Networking route_func: forward [17]

      Host 2:
         ✅ Boot test [0]
         ✅ selinux-policy: serge-testsuite [18]

  ppc64le:
      Host 1:
         ✅ Boot test [0]
         ✅ Podman system integration test (as root) [1]
         ✅ Podman system integration test (as user) [1]
         ✅ jvm test suite [2]
         ✅ AMTU (Abstract Machine Test Utility) [3]
         ✅ LTP: openposix test suite [4]
         ✅ Ethernet drivers sanity [5]
         ✅ Networking socket: fuzz [6]
         ✅ Networking sctp-auth: sockopts test [7]
         ✅ Networking TCP: keepalive test [8]
         ✅ audit: audit testsuite test [9]
         ✅ httpd: mod_ssl smoke sanity [10]
         ✅ iotop: sanity [11]
         ✅ tuned: tune-processes-through-perf [12]
         🚧 ✅ LTP lite [14]
         🚧 ✅ Networking bridge: sanity [15]
         🚧 ✅ Networking route: pmtu [16]
         🚧 ✅ Networking route_func: local [17]
         🚧 ✅ Networking route_func: forward [17]

      Host 2:
         ✅ Boot test [0]
         ✅ selinux-policy: serge-testsuite [18]

  s390x:
      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 [0]
         ⚡⚡⚡ selinux-policy: serge-testsuite [18]

      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 [0]
         ⚡⚡⚡ Podman system integration test (as root) [1]
         ⚡⚡⚡ Podman system integration test (as user) [1]
         ⚡⚡⚡ jvm test suite [2]
         ⚡⚡⚡ LTP: openposix test suite [4]
         ⚡⚡⚡ Ethernet drivers sanity [5]
         ⚡⚡⚡ Networking sctp-auth: sockopts test [7]
         ⚡⚡⚡ Networking TCP: keepalive test [8]
         ⚡⚡⚡ audit: audit testsuite test [9]
         ⚡⚡⚡ httpd: mod_ssl smoke sanity [10]
         ⚡⚡⚡ iotop: sanity [11]
         ⚡⚡⚡ tuned: tune-processes-through-perf [12]
         ⚡⚡⚡ stress: stress-ng [13]
         🚧 ⚡⚡⚡ LTP lite [14]
         🚧 ⚡⚡⚡ Networking bridge: sanity [15]
         🚧 ⚡⚡⚡ Networking route: pmtu [16]
         🚧 ⚡⚡⚡ Networking route_func: local [17]
         🚧 ⚡⚡⚡ Networking route_func: forward [17]

  x86_64:
      Host 1:
         ✅ Boot test [0]
         ✅ Podman system integration test (as root) [1]
         ✅ Podman system integration test (as user) [1]
         ✅ jvm test suite [2]
         ✅ AMTU (Abstract Machine Test Utility) [3]
         ✅ LTP: openposix test suite [4]
         ✅ Ethernet drivers sanity [5]
         ✅ Networking socket: fuzz [6]
         ✅ Networking sctp-auth: sockopts test [7]
         ✅ Networking TCP: keepalive test [8]
         ✅ audit: audit testsuite test [9]
         ✅ httpd: mod_ssl smoke sanity [10]
         ✅ iotop: sanity [11]
         ✅ tuned: tune-processes-through-perf [12]
         ✅ pciutils: sanity smoke test [19]
         ✅ stress: stress-ng [13]
         🚧 ✅ LTP lite [14]
         🚧 ✅ Networking bridge: sanity [15]
         🚧 ✅ Networking route: pmtu [16]
         🚧 ✅ Networking route_func: local [17]
         🚧 ✅ Networking route_func: forward [17]

      Host 2:
         ✅ Boot test [0]
         ✅ selinux-policy: serge-testsuite [18]

  Test source:
    💚 Pull requests are welcome for new tests or improvements to existing tests!
    [0]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/kpkginstall
    [1]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/container/podman
    [2]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/jvm
    [3]: https://github.com/CKI-project/tests-beaker/archive/master.zip#misc/amtu
    [4]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/ltp/openposix_testsuite
    [5]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/driver/sanity
    [6]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/socket/fuzz
    [7]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/sctp/auth/sockopts
    [8]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/tcp/tcp_keepalive
    [9]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/audit/audit-testsuite
    [10]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/httpd/mod_ssl-smoke
    [11]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/iotop/sanity
    [12]: https://github.com/CKI-project/tests-beaker/archive/master.zip#packages/tuned/tune-processes-through-perf
    [13]: https://github.com/CKI-project/tests-beaker/archive/master.zip#stress/stress-ng
    [14]: https://github.com/CKI-project/tests-beaker/archive/master.zip#distribution/ltp-upstream/lite
    [15]: https://github.com/CKI-project/tests-beaker/archive/master.zip#networking/bridge/sanity_check
    [16]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/route/pmtu
    [17]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/networking/route/route_func
    [18]: https://github.com/CKI-project/tests-beaker/archive/master.zip#/packages/selinux-policy/serge-testsuite
    [19]: https://github.com/CKI-project/tests-beaker/archive/master.zip#pciutils/sanity-smoke

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.

             reply	other threads:[~2019-09-16 17:53 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 17:53 CKI Project [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-20  7:39 ✅ PASS: Stable queue: queue-5.2 CKI Project
2019-09-20  9:17 ` Veronika Kabatova
2019-09-20  6:17 CKI Project
2019-09-20  0:58 CKI Project
2019-09-19 20:05 CKI Project
2019-09-19 19:56 CKI Project
2019-09-19 18:02 CKI Project
2019-09-19 18:40 ` Major Hayden
2019-09-19 15:36 CKI Project
2019-09-18  4:57 CKI Project
2019-09-18  2:38 CKI Project
2019-09-18  0:29 CKI Project
2019-09-18  0:20 CKI Project
2019-09-17 20:29 CKI Project
2019-09-17 20:23 CKI Project
2019-09-17 12:09 CKI Project
2019-09-17 10:58 CKI Project
2019-09-16  4:52 CKI Project
2019-09-13  5:28 CKI Project
2019-09-11 14:08 CKI Project
2019-09-08 18:46 CKI Project
2019-09-08 14:49 CKI Project
2019-09-08  2:35 CKI Project
2019-09-06 15:20 CKI Project
2019-09-06  0:55 CKI Project
2019-09-05  3:19 CKI Project
2019-09-04 17:20 CKI Project
2019-09-04  9:43 CKI Project
2019-09-04  1:37 CKI Project
2019-09-04  0:50 CKI Project
2019-09-03 13:09 CKI Project
2019-09-03 12:21 CKI Project
2019-09-03  6:23 CKI Project
2019-09-02 23:04 CKI Project
2019-08-30 13:35 CKI Project
2019-08-29 19:35 CKI Project
2019-08-27  9:38 CKI Project
2019-08-27  1:47 CKI Project
2019-08-26 23:55 CKI Project
2019-08-26 23:50 CKI Project
2019-08-26 15:35 CKI Project
2019-08-26  6:14 CKI Project
2019-08-21  5:19 CKI Project
2019-08-21  4:23 CKI Project
2019-08-20 22:57 CKI Project
2019-08-19  7:50 CKI Project
2019-08-18  9:29 CKI Project
2019-08-16 13:31 CKI Project
2019-08-15  6:05 CKI Project
2019-08-15  3:24 CKI Project
2019-08-14  9:17 CKI Project
2019-08-14  2:15 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:
  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.A1549FEC70.PUGPO9WRRJ@redhat.com \
    --to=cki-project@redhat.com \
    --cc=stable@vger.kernel.org \
    /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 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.