On Wed, Nov 30, 2016 at 08:39:35AM -0800, Kevin Hilman wrote: > kernelci.org bot <bot@xxxxxxxxxxxx> writes: > > > stable-rc boot: 226 boots: 6 failed, 214 passed with 5 offline, 1 conflict (v4.8.11-37-g70e9fe5f6b13) > > > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8.11-37-g70e9fe5f6b13/ > > Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.8.11-37-g70e9fe5f6b13/ > > > > Tree: stable-rc > > Branch: local/linux-4.8.y > > Git Describe: v4.8.11-37-g70e9fe5f6b13 > > Git Commit: 70e9fe5f6b13b404a1575496b9727aed109b0fca > > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > Tested: 83 unique boards, 22 SoC families, 31 builds out of 207 > > > > Boot Regressions Detected: > > > > arm: > > > > multi_v7_defconfig+CONFIG_EFI=y: > > vexpress-v2p-ca15_a7: > > lab-broonie: new failure (last pass: v4.8.11) > > > > multi_v7_defconfig+CONFIG_LKDTM=y: > > vexpress-v2p-ca15-tc1: > > lab-broonie: new failure (last pass: v4.8.11) > > vexpress-v2p-ca15_a7: > > lab-broonie: new failure (last pass: v4.8.11) > > > > multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y: > > vexpress-v2p-ca15-tc1: > > lab-broonie: new failure (last pass: v4.8.11) > > vexpress-v2p-ca15_a7: > > lab-broonie: new failure (last pass: v4.8.11) > > These appear to be lab issues due to not waiting long enough for QEMU > jobs. Under investigation. > > (BTW, notice the new "regressions" section here. Hopefully this will be > more useful for seeing what's actually new failures.) Yes, that was nice, but I couldn't tell what the real problem was, thanks for digging into it. > > Boot Failures Detected: > > > > arm: > > > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y > > at91-sama5d4_xplained: 1 failed lab > > This is passing in another lab, so looks like a local lab issue. > > > multi_v7_defconfig > > omap5-uevm_rootfs:nfs: 1 failed lab > > Looks like local lab networking issue. > > IOW, interpretation: no blocking issues. Wonderful, thanks for letting me know. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html