From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable/linux-3.16.y boot: 43 boots: 39 failed, 0 passed with 4 untried/unknown (v3.16.83)
Date: Tue, 28 Apr 2020 18:43:10 -0700 (PDT) [thread overview]
Message-ID: <5ea8dbae.1c69fb81.db559.73d4@mx.google.com> (raw)
stable/linux-3.16.y boot: 43 boots: 39 failed, 0 passed with 4 untried/unknown (v3.16.83)
Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-3.16.y/kernel/v3.16.83/
Full Build Summary: https://kernelci.org/build/stable/branch/linux-3.16.y/kernel/v3.16.83/
Tree: stable
Branch: linux-3.16.y
Git Describe: v3.16.83
Git Commit: 92f17c867833bbfdaced034629afb8e30a19e882
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Tested: 18 unique boards, 6 SoC families, 10 builds out of 186
Boot Failures Detected:
i386:
i386_defconfig:
gcc-8:
qemu_i386: 2 failed labs
x86_64:
x86_64_defconfig:
gcc-8:
minnowboard-turbot-E3826: 1 failed lab
qemu_x86_64: 2 failed labs
arm:
omap2plus_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
omap3-beagle-xm: 1 failed lab
omap4-panda: 2 failed labs
multi_v7_defconfig:
gcc-8:
am335x-boneblack: 1 failed lab
imx27-phytec-phycard-s-rdk: 1 failed lab
imx6dl-riotboard: 1 failed lab
imx6q-sabrelite: 2 failed labs
omap3-beagle-xm: 1 failed lab
omap4-panda: 2 failed labs
qemu_arm-virt-gicv2: 2 failed labs
qemu_arm-virt-gicv3: 2 failed labs
sun4i-a10-olinuxino-lime: 1 failed lab
sun5i-a13-olinuxino-micro: 1 failed lab
sun7i-a20-cubieboard2: 2 failed labs
sun7i-a20-cubietruck: 1 failed lab
tegra124-jetson-tk1: 2 failed labs
imx_v6_v7_defconfig:
gcc-8:
imx27-phytec-phycard-s-rdk: 1 failed lab
imx6dl-riotboard: 1 failed lab
tegra_defconfig:
gcc-8:
tegra124-jetson-tk1: 2 failed labs
multi_v5_defconfig:
gcc-8:
imx27-phytec-phycard-s-rdk: 1 failed lab
imx_v4_v5_defconfig:
gcc-8:
imx27-phytec-phycard-s-rdk: 1 failed lab
sunxi_defconfig:
gcc-8:
sun4i-a10-olinuxino-lime: 1 failed lab
sun5i-a13-olinuxino-micro: 1 failed lab
sun7i-a20-cubieboard2: 2 failed labs
sun7i-a20-cubietruck: 1 failed lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2020-04-29 1:43 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=5ea8dbae.1c69fb81.db559.73d4@mx.google.com \
--to=bot@kernelci.org \
--cc=stable@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).