"kernelci.org bot" bot@kernelci.org writes:
soc/for-next boot: 200 boots: 6 failed, 194 passed (v5.3-rc7-842-ge84740aec31b)
Full Boot Summary: https://kernelci.org/boot/all/job/soc/branch/for-next/kernel/v5.3-rc7-842-ge... Full Build Summary: https://kernelci.org/build/soc/branch/for-next/kernel/v5.3-rc7-842-ge84740ae...
Tree: soc Branch: for-next Git Describe: v5.3-rc7-842-ge84740aec31b Git Commit: e84740aec31bc2d5e1464f0099311e91e41ec7c3 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git Tested: 51 unique boards, 18 SoC families, 20 builds out of 214
Boot Regressions Detected:
FYI... neither of these are real regressions.
arm:
multi_v7_defconfig: gcc-8: sun7i-a20-cubieboard2: lab-baylibre: new failure (last pass: v5.3-rc7-821-g5600d5662b76)
This one has some uboot-action fails, which we should detect as infra errors, not kernel errors.
arm64:
defconfig+CONFIG_CPU_BIG_ENDIAN=y: gcc-8: meson-gxl-s805x-libretech-ac: lab-baylibre: failing since 1 day (last pass: v5.3-rc7-795-g778fbdb7d4e0 - first fail: v5.3-rc7-821-g5600d5662b76)
And this one is repeated TFTP failures (also resulting in failures of uboot actions) that should be infra errors, not kernel errors.
Kevin