linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next boot: 67 boots: 2 failed, 63 passed with 2 untried/unknown (v5.3-rc7-68-g07dec0b44925)
Date: Fri, 06 Sep 2019 13:28:40 -0700 (PDT)	[thread overview]
Message-ID: <5d72c178.1c69fb81.817f1.edb9@mx.google.com> (raw)

linusw/for-next boot: 67 boots: 2 failed, 63 passed with 2 untried/unknown (v5.3-rc7-68-g07dec0b44925)

Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/v5.3-rc7-68-g07dec0b44925/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/v5.3-rc7-68-g07dec0b44925/

Tree: linusw
Branch: for-next
Git Describe: v5.3-rc7-68-g07dec0b44925
Git Commit: 07dec0b449253479d66c4b6b274e8ce25677d139
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 47 unique boards, 15 SoC families, 3 builds out of 6

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          sun8i-h2-plus-orangepi-r1:
              lab-baylibre: new failure (last pass: v5.3-rc6-62-g0f40dd225a88)

arm64:

    defconfig:
        gcc-8:
          meson-gxl-s805x-p241:
              lab-baylibre: new failure (last pass: v5.3-rc6-62-g0f40dd225a88)
          meson-gxl-s905d-p230:
              lab-baylibre: failing since 2 days (last pass: v5.3-rc6-51-g1fc4f3c962b7 - first fail: v5.3-rc6-62-g0f40dd225a88)
          meson-gxm-khadas-vim2:
              lab-baylibre: new failure (last pass: v5.3-rc6-62-g0f40dd225a88)

Boot Failures Detected:

arm64:
    defconfig:
        gcc-8:
            meson-gxl-s905d-p230: 1 failed lab
            meson-gxm-khadas-vim2: 1 failed lab

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

                 reply	other threads:[~2019-09-06 20:28 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=5d72c178.1c69fb81.817f1.edb9@mx.google.com \
    --to=bot@kernelci.org \
    --cc=fellows@kernelci.org \
    --cc=linux-gpio@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).