From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 241 boots: 6 failed, 221 passed with 12 offline, 1 untried/unknown, 1 conflict (v5.3-rc6-266-gebd24bbbf581)
Date: Wed, 28 Aug 2019 11:55:53 -0700 (PDT) [thread overview]
Message-ID: <5d66ce39.1c69fb81.80af6.00ae@mx.google.com> (raw)
next/pending-fixes boot: 241 boots: 6 failed, 221 passed with 12 offline, 1 untried/unknown, 1 conflict (v5.3-rc6-266-gebd24bbbf581)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.3-rc6-266-gebd24bbbf581/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.3-rc6-266-gebd24bbbf581/
Tree: next
Branch: pending-fixes
Git Describe: v5.3-rc6-266-gebd24bbbf581
Git Commit: ebd24bbbf581f70d34d42965b828b242bbb8d63a
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 88 unique boards, 26 SoC families, 20 builds out of 222
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-8:
sun5i-a13-olinuxino-micro:
lab-baylibre: new failure (last pass: v5.3-rc6-214-g30064e30ccb4)
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
rk3288-veyron-jaq:
lab-collabora: new failure (last pass: v5.3-rc6-214-g30064e30ccb4)
arm64:
defconfig:
gcc-8:
meson-gxm-khadas-vim2:
lab-baylibre: failing since 1 day (last pass: v5.3-rc5-221-g5995e3fbeb96 - first fail: v5.3-rc6-214-g30064e30ccb4)
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-khadas-vim2:
lab-baylibre: new failure (last pass: v5.3-rc6-214-g30064e30ccb4)
Boot Failures Detected:
arm64:
defconfig:
gcc-8:
apq8096-db820c: 1 failed lab
meson-gxm-khadas-vim2: 1 failed lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8:
meson-gxm-khadas-vim2: 1 failed lab
arm:
oxnas_v6_defconfig:
gcc-8:
ox820-cloudengines-pogoplug-series-3: 1 failed lab
multi_v7_defconfig+CONFIG_SMP=n:
gcc-8:
rk3288-veyron-jaq: 1 failed lab
sama5_defconfig:
gcc-8:
at91-sama5d4_xplained: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sun5i-r8-chip: 1 offline lab
qcom_defconfig:
gcc-8
qcom-apq8064-cm-qs600: 1 offline lab
qcom-apq8064-ifc6410: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.)
arm:
multi_v7_defconfig:
am57xx-beagle-x15:
lab-drue: PASS (gcc-8)
lab-linaro-lkft: FAIL (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-08-28 18:55 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=5d66ce39.1c69fb81.80af6.00ae@mx.google.com \
--to=bot@kernelci.org \
--cc=linux-next@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.