From: "kernelci.org bot" <bot@kernelci.org>
To: stable@vger.kernel.org
Subject: stable-rc/linux-4.4.y boot: 88 boots: 3 failed, 74 passed with 10 offline, 1 untried/unknown (v4.4.177-15-g67a012a513a1)
Date: Tue, 26 Mar 2019 00:20:13 -0700 (PDT) [thread overview]
Message-ID: <5c99d2ad.1c69fb81.b60f.eecd@mx.google.com> (raw)
stable-rc/linux-4.4.y boot: 88 boots: 3 failed, 74 passed with 10 offline, 1 untried/unknown (v4.4.177-15-g67a012a513a1)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.177-15-g67a012a513a1/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.177-15-g67a012a513a1/
Tree: stable-rc
Branch: linux-4.4.y
Git Describe: v4.4.177-15-g67a012a513a1
Git Commit: 67a012a513a15d73b57e75c24d459b89c6aa8acb
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 43 unique boards, 21 SoC families, 14 builds out of 190
Boot Regressions Detected:
arm:
multi_v7_defconfig:
gcc-7:
qcom-apq8064-cm-qs600:
lab-baylibre-seattle: new failure (last pass: v4.4.176-149-gf6187c866dff)
Boot Failures Detected:
arm:
multi_v7_defconfig:
gcc-7:
qcom-apq8064-cm-qs600: 1 failed lab
stih410-b2120: 1 failed lab
arm64:
defconfig:
gcc-7:
qcom-qdf2400: 1 failed lab
Offline Platforms:
arm:
tegra_defconfig:
gcc-7
tegra124-jetson-tk1: 1 offline lab
bcm2835_defconfig:
gcc-7
bcm2835-rpi-b: 1 offline lab
sunxi_defconfig:
gcc-7
sun5i-r8-chip: 1 offline lab
multi_v7_defconfig:
gcc-7
alpine-db: 1 offline lab
at91-sama5d4_xplained: 1 offline lab
socfpga_cyclone5_de0_sockit: 1 offline lab
sun5i-r8-chip: 1 offline lab
tegra124-jetson-tk1: 1 offline lab
sama5_defconfig:
gcc-7
at91-sama5d4_xplained: 1 offline lab
arm64:
defconfig:
gcc-7
apq8016-sbc: 1 offline lab
---
For more info write to <info@kernelci.org>
reply other threads:[~2019-03-26 7:20 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=5c99d2ad.1c69fb81.b60f.eecd@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 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.