From: "kernelci.org bot" <bot@kernelci.org>
To: linux-gpio@vger.kernel.org, fellows@kernelci.org
Subject: linusw/for-next boot: 56 boots: 3 failed, 50 passed with 3 untried/unknown (gpio-v5.6-3-48-g7d52bac0fadc)
Date: Thu, 26 Mar 2020 02:15:16 -0700 (PDT) [thread overview]
Message-ID: <5e7c72a4.1c69fb81.45baa.4a5e@mx.google.com> (raw)
linusw/for-next boot: 56 boots: 3 failed, 50 passed with 3 untried/unknown (gpio-v5.6-3-48-g7d52bac0fadc)
Full Boot Summary: https://kernelci.org/boot/all/job/linusw/branch/for-next/kernel/gpio-v5.6-3-48-g7d52bac0fadc/
Full Build Summary: https://kernelci.org/build/linusw/branch/for-next/kernel/gpio-v5.6-3-48-g7d52bac0fadc/
Tree: linusw
Branch: for-next
Git Describe: gpio-v5.6-3-48-g7d52bac0fadc
Git Commit: 7d52bac0fadc072655373772f4ee9455039858e4
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/
Tested: 49 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 43 days (last pass: gpio-v5.5-4-45-gd18fddff061d - first fail: v5.6-rc1-12-g612e35e76ec8)
arm64:
defconfig:
gcc-8:
meson-g12b-a311d-khadas-vim3:
lab-baylibre: new failure (last pass: v5.6-rc3-38-gb3e741a0f776)
meson-gxl-s905x-khadas-vim:
lab-baylibre: new failure (last pass: v5.6-rc3-38-gb3e741a0f776)
meson-gxm-khadas-vim2:
lab-baylibre: new failure (last pass: v5.6-rc3-38-gb3e741a0f776)
sun50i-a64-pine64-plus:
lab-baylibre: new failure (last pass: v5.6-rc3-38-gb3e741a0f776)
sun50i-h5-libretech-all-h3-cc:
lab-baylibre: new failure (last pass: v5.6-rc3-38-gb3e741a0f776)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-8:
bcm2836-rpi-2-b: 1 failed lab
arm64:
defconfig:
gcc-8:
meson-gxl-s905x-khadas-vim: 1 failed lab
sun50i-a64-pine64-plus: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-03-26 9:15 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=5e7c72a4.1c69fb81.45baa.4a5e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.