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/devel boot: 61 boots: 2 failed, 58 passed with 1 untried/unknown (v5.6-rc1-32-ga28e1c0505a0)
Date: Tue, 24 Mar 2020 15:05:41 -0700 (PDT)	[thread overview]
Message-ID: <5e7a8435.1c69fb81.1961a.e4c3@mx.google.com> (raw)

linusw/devel boot: 61 boots: 2 failed, 58 passed with 1 untried/unknown (v5.6-rc1-32-ga28e1c0505a0)

Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/devel/kernel/v5.6-rc1-32-ga28e1c0505a0/
Full Build Summary: https://kernelci.org/build/linusw/branch/devel/kernel/v5.6-rc1-32-ga28e1c0505a0/

Tree: linusw
Branch: devel
Git Describe: v5.6-rc1-32-ga28e1c0505a0
Git Commit: a28e1c0505a09c3a2d81fed1c8453ac2d8d02b3a
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 53 unique boards, 14 SoC families, 3 builds out of 6

Boot Regressions Detected:

arm:

    multi_v7_defconfig:
        gcc-8:
          bcm2836-rpi-2-b:
              lab-collabora: failing since 40 days (last pass: gpio-v5.5-4-45-gd18fddff061d - first fail: v5.6-rc1-12-gb2929a9cb2fb)

arm64:

    defconfig:
        gcc-8:
          bcm2837-rpi-3-b:
              lab-baylibre: new failure (last pass: v5.6-rc1-31-g347ae6e29145)
          sun50i-a64-pine64-plus:
              lab-baylibre: failing since 4 days (last pass: v5.6-rc1-26-g5779925c23e1 - first fail: v5.6-rc1-31-g347ae6e29145)

Boot Failures Detected:

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

arm64:
    defconfig:
        gcc-8:
            bcm2837-rpi-3-b: 1 failed lab

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

                 reply	other threads:[~2020-03-24 22:05 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=5e7a8435.1c69fb81.1961a.e4c3@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).