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: 62 boots: 1 failed, 58 passed with 3 untried/unknown (v5.6-rc3-37-gef0c1aed2459)
Date: Fri, 20 Mar 2020 03:39:07 -0700 (PDT)	[thread overview]
Message-ID: <5e749d4b.1c69fb81.4a05b.17e0@mx.google.com> (raw)

linusw/for-next boot: 62 boots: 1 failed, 58 passed with 3 untried/unknown (v5.6-rc3-37-gef0c1aed2459)

Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/v5.6-rc3-37-gef0c1aed2459/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/v5.6-rc3-37-gef0c1aed2459/

Tree: linusw
Branch: for-next
Git Describe: v5.6-rc3-37-gef0c1aed2459
Git Commit: ef0c1aed2459f59f2aec13bcc97c68e0646ab0a2
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 54 unique boards, 15 SoC families, 3 builds out of 6

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          bcm2836-rpi-2-b:
              lab-collabora: failing since 37 days (last pass: gpio-v5.5-4-45-gd18fddff061d - first fail: v5.6-rc1-12-g612e35e76ec8)
          sun4i-a10-olinuxino-lime:
              lab-baylibre: new failure (last pass: gpio-v5.6-2-20-gee82ebf16ccb)

arm64:

    defconfig:
        gcc-8:
          meson-g12b-a311d-khadas-vim3:
              lab-baylibre: new failure (last pass: v5.6-rc3-27-g9cd0c5e02ee4)
          meson-gxl-s805x-p241:
              lab-baylibre: new failure (last pass: v5.6-rc3-27-g9cd0c5e02ee4)

Boot Failure Detected:

arm:
    multi_v7_defconfig:
        gcc-8:
            bcm2836-rpi-2-b: 1 failed lab

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

                 reply	other threads:[~2020-03-20 10:39 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=5e749d4b.1c69fb81.4a05b.17e0@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).