public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/pending-fixes boot: 230 boots: 9 failed, 221 passed (v5.3-13311-g8d0cc3a7f82f)
Date: Sun, 29 Sep 2019 20:26:41 -0700 (PDT)	[thread overview]
Message-ID: <5d9175f1.1c69fb81.63829.2be7@mx.google.com> (raw)

next/pending-fixes boot: 230 boots: 9 failed, 221 passed (v5.3-13311-g8d0cc3a7f82f)

Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.3-13311-g8d0cc3a7f82f/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.3-13311-g8d0cc3a7f82f/

Tree: next
Branch: pending-fixes
Git Describe: v5.3-13311-g8d0cc3a7f82f
Git Commit: 8d0cc3a7f82fcdc3db2980db674581fa85e5408a
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 54 unique boards, 16 SoC families, 21 builds out of 214

Boot Regressions Detected:

arm:

    bcm2835_defconfig:
        gcc-8:
          bcm2836-rpi-2-b:
              lab-collabora: new failure (last pass: v5.3-12689-gd20eeb14322b)
          bcm2837-rpi-3-b:
              lab-baylibre: new failure (last pass: v5.3-12689-gd20eeb14322b)

Boot Failures Detected:

arm:
    multi_v7_defconfig+kselftest:
        gcc-8:
            bcm2836-rpi-2-b: 1 failed lab
            rk3288-rock2-square: 1 failed lab

    bcm2835_defconfig:
        gcc-8:
            bcm2836-rpi-2-b: 1 failed lab
            bcm2837-rpi-3-b: 1 failed lab

arm64:
    defconfig+kselftest:
        gcc-8:
            qcom-qdf2400: 1 failed lab
            r8a7795-salvator-x: 1 failed lab
            r8a7796-m3ulcb: 2 failed labs
            rk3399-puma-haikou: 1 failed lab

---
For more info write to <info@kernelci•org>

                 reply	other threads:[~2019-09-30  3:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5d9175f1.1c69fb81.63829.2be7@mx.google.com \
    --to=bot@kernelci$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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