From: "kernelci.org bot" <bot@kernelci.org>
To: linux-next@vger.kernel.org
Subject: next/pending-fixes boot: 224 boots: 7 failed, 194 passed with 20 offline, 2 untried/unknown, 1 conflict (v5.3-rc3-474-g2c5a544f82b3)
Date: Wed, 07 Aug 2019 07:53:15 -0700 (PDT) [thread overview]
Message-ID: <5d4ae5db.1c69fb81.ad2a5.0bfc@mx.google.com> (raw)
next/pending-fixes boot: 224 boots: 7 failed, 194 passed with 20 offline, 2 untried/unknown, 1 conflict (v5.3-rc3-474-g2c5a544f82b3)
Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/pending-fixes/kernel/v5.3-rc3-474-g2c5a544f82b3/
Full Build Summary: https://kernelci.org/build/next/branch/pending-fixes/kernel/v5.3-rc3-474-g2c5a544f82b3/
Tree: next
Branch: pending-fixes
Git Describe: v5.3-rc3-474-g2c5a544f82b3
Git Commit: 2c5a544f82b3ae9a0bc0fbb28f37ff64233802ce
Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Tested: 85 unique boards, 28 SoC families, 22 builds out of 222
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
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8:
rk3399-firefly: 1 failed lab
arm:
qcom_defconfig:
gcc-8:
qcom-apq8064-cm-qs600: 1 failed lab
qcom-apq8064-ifc6410: 1 failed lab
multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y:
gcc-8:
exynos4412-odroidx2: 1 failed lab
Offline Platforms:
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
mt7622-rfb1: 1 offline lab
defconfig+CONFIG_CPU_BIG_ENDIAN=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
defconfig+CONFIG_RANDOMIZE_BASE=y:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab
meson-gxbb-odroidc2: 1 offline lab
mt7622-rfb1: 1 offline lab
arm:
multi_v7_defconfig:
gcc-8
alpine-db: 1 offline lab
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
bcm4708-smartrg-sr400ac: 1 offline lab
sun5i-r8-chip: 1 offline lab
sama5_defconfig:
gcc-8
at91-sama5d4_xplained: 1 offline lab
at91-sama5d4ek: 1 offline lab
bcm2835_defconfig:
gcc-8
bcm2835-rpi-b: 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-linaro-lkft: FAIL (gcc-8)
lab-drue: PASS (gcc-8)
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-08-07 14:53 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=5d4ae5db.1c69fb81.ad2a5.0bfc@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.