stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CKI Project <cki-project@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Subject: ❌ FAIL: Stable queue: queue-5.2
Date: Thu, 19 Sep 2019 08:42:43 -0400	[thread overview]
Message-ID: <cki.BCC66CB54E.K2A3YXEFWC@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3088 bytes --]


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: 1e2ba4a74fa7 - Linux 5.2.16

The results of these automated tests are provided below.

    Overall result: FAILED (see details below)
             Merge: OK
           Compile: FAILED

All kernel binaries, config files, and logs are available for download here:

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

We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:

           aarch64: FAILED (see build-aarch64.log.xz attachment)
           ppc64le: FAILED (see build-ppc64le.log.xz attachment)
             s390x: FAILED (see build-s390x.log.xz attachment)
            x86_64: FAILED (see build-x86_64.log.xz attachment)

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

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: 1e2ba4a74fa7 - Linux 5.2.16


We grabbed the b818dd317203 commit of the stable queue repository.

We then merged the patchset with `git am`:

  usb-usbcore-fix-slab-out-of-bounds-bug-during-device-reset.patch
  media-tm6000-double-free-if-usb-disconnect-while-streaming.patch
  phy-renesas-rcar-gen3-usb2-disable-clearing-vbus-in-over-current.patch
  net-hns3-adjust-hns3_uninit_phy-s-location-in-the-hns3_client_uninit.patch
  netfilter-nf_flow_table-set-default-timeout-after-successful-insertion.patch
  hid-wacom-generic-read-hid_dg_contactmax-from-any-feature-report.patch
  input-elan_i2c-remove-lenovo-legion-y7000-pnpid.patch
  sunrpc-handle-connection-breakages-correctly-in-call_status.patch
  media-stm32-dcmi-fix-irq-0-case.patch
  nfs-disable-client-side-deduplication.patch
  dma-direct-only-limit-the-mapping-size-if-swiotlb-could-be-used.patch
  powerpc-mm-radix-use-the-right-page-size-for-vmemmap-mapping.patch
  scripts-decode_stacktrace-match-basepath-using-shell-prefix-operator-not-regex.patch
  net-hns-fix-led-configuration-for-marvell-phy.patch
  net-aquantia-fix-limit-of-vlan-filters.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


[-- Attachment #2: build-s390x.log.xz --]
[-- Type: application/x-xz, Size: 23364 bytes --]

[-- Attachment #3: build-ppc64le.log.xz --]
[-- Type: application/x-xz, Size: 68840 bytes --]

[-- Attachment #4: build-aarch64.log.xz --]
[-- Type: application/x-xz, Size: 13592 bytes --]

[-- Attachment #5: build-x86_64.log.xz --]
[-- Type: application/x-xz, Size: 14036 bytes --]

             reply	other threads:[~2019-09-19 12:42 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 12:42 CKI Project [this message]
2019-09-19 12:57 ` ❌ FAIL: Stable queue: queue-5.2 Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2019-09-07 11:48 CKI Project
2019-09-04  5:31 CKI Project
2019-09-04 21:40 ` Rachel Sibley
2019-08-30 23:41 CKI Project
2019-08-28 12:36 CKI Project
2019-09-10  8:19 ` Hangbin Liu
2019-09-10  8:58   ` Greg KH
2019-09-10  9:30     ` Hangbin Liu
2019-09-10  9:40       ` Hangbin Liu
2019-09-10 10:52         ` Sasha Levin
2019-08-27 10:54 CKI Project
2019-08-26 22:06 CKI Project
2019-08-27 14:58 ` Rachel Sibley
2019-08-26 20:33 CKI Project
2019-08-26 21:00 ` Major Hayden
2019-08-25 14:37 CKI Project
2019-08-25 14:41 ` Greg KH
2019-08-26  8:23   ` Nikolai Kondrashov
2019-08-26  8:33     ` Greg KH
2019-08-26  9:13       ` Nikolai Kondrashov
2019-08-26  9:40         ` Nikolai Kondrashov
2019-08-26 11:12           ` Nikolai Kondrashov
2019-08-26 11:39             ` Nikolai Kondrashov
2019-08-26 13:33               ` Sasha Levin
2019-08-27 13:10                 ` Nikolai Kondrashov
2019-08-22 22:48 CKI Project
2019-08-22 23:37 ` Greg KH
2019-08-23  6:57   ` Jan Stancek
2019-08-23 15:38     ` Sasha Levin
2019-08-23  2:19 ` ? " Murphy Zhou
2019-08-18 21:09  " CKI Project
2019-08-18 14:27 CKI Project
2019-08-18 14:05 CKI Project
2019-08-18 14:20 ` Greg KH
2019-08-18 12:00 CKI Project
2019-08-18 16:59 ` Ondrej Mosnacek

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.BCC66CB54E.K2A3YXEFWC@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).