"kernelci.org bot" <bot@xxxxxxxxxxxx> writes: > stable-rc/linux-4.4.y boot: 101 boots: 2 failed, 84 passed with 12 offline, 2 untried/unknown, 1 conflict (v4.4.189-79-gf18b2d12bf91) TL;DR; All is well. > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.189-79-gf18b2d12bf91/ > Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.189-79-gf18b2d12bf91/ > > Tree: stable-rc > Branch: linux-4.4.y > Git Describe: v4.4.189-79-gf18b2d12bf91 > Git Commit: f18b2d12bf9162bef0b051e6300b389a674f68e1 > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > Tested: 47 unique boards, 19 SoC families, 14 builds out of 190 > > Boot Regressions Detected: > > arm: > > bcm2835_defconfig: > gcc-8: > bcm2835-rpi-b: > lab-baylibre-seattle: failing since 1 day (last pass: v4.4.189-75-g138891b71be5 - first fail: v4.4.189-80-gae3cc2f8a3ef) > > multi_v7_defconfig: > gcc-8: > exynos5800-peach-pi: > lab-collabora: new failure (last pass: v4.4.189-80-gae3cc2f8a3ef) > > qcom_defconfig: > gcc-8: > qcom-apq8064-cm-qs600: > lab-baylibre-seattle: failing since 7 days (last pass: v4.4.189 - first fail: v4.4.189-32-g35ba3146be27) > qcom-apq8064-ifc6410: > lab-baylibre-seattle: failing since 7 days (last pass: v4.4.189 - first fail: v4.4.189-32-g35ba3146be27) > > sama5_defconfig: > gcc-8: > at91-sama5d4_xplained: > lab-baylibre-seattle: failing since 1 day (last pass: v4.4.189-75-g138891b71be5 - first fail: v4.4.189-80-gae3cc2f8a3ef) Hmm, something's terribly wrong with our regression checker as these did not fail at all in this boot run. We'll check into this. > Boot Failures Detected: > > arm64: > defconfig: > gcc-8: > qcom-qdf2400: 1 failed lab This one looks like the boot firmware is not even starting the kernel. The Linaro/LKFT lab folks will need to have a look. > arm: > multi_v7_defconfig: > gcc-8: > stih410-b2120: 1 failed lab This board should be blacklisted for v4.4, I just fixed that. Kevin
