From: "kernelci.org bot" <bot@kernelci•org>
To: linux-next@vger•kernel.org
Subject: next/pending-fixes boot: 186 boots: 3 failed, 178 passed with 5 untried/unknown (v5.5-rc5-445-gecb24723e078)
Date: Fri, 10 Jan 2020 04:15:24 -0800 (PST) [thread overview]
Message-ID: <5e186adc.1c69fb81.4f04c.94e1@mx.google.com> (raw)
next/pending-fixes boot: 186 boots: 3 failed, 178 passed with 5 untried/unknown (v5.5-rc5-445-gecb24723e078)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.5-rc5-445-gecb24723e078/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.5-rc5-445-gecb24723e078/
Tree: next
Branch: pending-fixes
Git Describe: v5.5-rc5-445-gecb24723e078
Git Commit: ecb24723e078820b92525fd2bc07cc2daff2ac94
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 67 unique boards, 18 SoC families, 26 builds out of 214
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
omap3-beagle-xm:
lab-baylibre: new failure (last pass: v5.5-rc2-432-g9eed7d73a938)
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-q200:
lab-baylibre: new failure (last pass: v5.5-rc5-266-ga617565a3afb)
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
meson-g12a-sei510:
lab-baylibre: new failure (last pass: v5.5-rc5-266-ga617565a3afb)
meson-g12b-a311d-khadas-vim3:
lab-baylibre: new failure (last pass: v5.5-rc5-266-ga617565a3afb)
meson-sm1-sei610:
lab-baylibre: new failure (last pass: v5.5-rc5-266-ga617565a3afb)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
msm8998-mtp: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-q200: 1 failed lab
arm:
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
---
For more info write to <info@kernelci•org>
reply other threads:[~2020-01-10 12: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=5e186adc.1c69fb81.4f04c.94e1@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