On 13 May 2015 at 06:43, kernelci.org bot bot@kernelci.org wrote:

*next boot: 329 boots: 22 failed, 306 passed with 1 offline (next-20150513)* Full Boot Summary: http://kernelci.org/boot/all/job/next/kernel/next-20150513/Full Build Summary: http://kernelci.org/build/next/kernel/next-20150513/Tree: nextBranch: local/masterGit Describe: next-20150513Git Commit: b8c256259dfc016a70982a72b0307c3ff759c34fGit URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b8c256259dfc016a70982a72b0307c3ff759c34fTested: 82 unique boards, 23 SoC families, 28 builds out of 129*Boot Failures Detected: http://kernelci.org/boot/?next-20150513&fail http://kernelci.org/boot/?next-20150513&fail*arm:exynos_defconfig: exynos5422-odroidxu3_rootfs:mmc http://kernelci.org/boot/exynos5422-odroidxu3_rootfs:mmc/job/next/kernel/next-20150513/defconfig/exynos_defconfig/: 1 failed labmulti_v7_defconfig+CONFIG_PROVE_LOCKING=y:am335x-bone http://kernelci.org/boot/am335x-bone/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/: 1 failed labam335x-boneblack http://kernelci.org/boot/am335x-boneblack/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/: 2 failed labship04-d01 http://kernelci.org/boot/hip04-d01/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/: 1 failed labhisi-x5hd2-dkb http://kernelci.org/boot/hisi-x5hd2-dkb/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/: 1 failed labrk3288-evb-rk808 http://kernelci.org/boot/rk3288-evb-rk808/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_PROVE_LOCKING=y/: 1 failed labomap2plus_defconfig:am335x-bone http://kernelci.org/boot/am335x-bone/job/next/kernel/next-20150513/defconfig/omap2plus_defconfig/: 1 failed labam335x-boneblack http://kernelci.org/boot/am335x-boneblack/job/next/kernel/next-20150513/defconfig/omap2plus_defconfig/: 2 failed labsmulti_v7_defconfig+CONFIG_ARM_LPAE=y: exynos5422-odroidxu3_rootfs:mmc http://kernelci.org/boot/exynos5422-odroidxu3_rootfs:mmc/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+CONFIG_ARM_LPAE=y/: 1 failed labshmobile_defconfig:emev2-kzm9d http://kernelci.org/boot/emev2-kzm9d/job/next/kernel/next-20150513/defconfig/shmobile_defconfig/: 1 failed labmulti_v7_defconfig:am335x-boneblack http://kernelci.org/boot/am335x-boneblack/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig/: 2 failed labsexynos5422-odroidxu3_rootfs:mmc http://kernelci.org/boot/exynos5422-odroidxu3_rootfs:mmc/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig/: 1 failed labhip04-d01 http://kernelci.org/boot/hip04-d01/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig/: 1 failed labmvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y: armada-xp-openblocks-ax3-4 http://kernelci.org/boot/armada-xp-openblocks-ax3-4/job/next/kernel/next-20150513/defconfig/mvebu_v7_defconfig+CONFIG_CPU_BIG_ENDIAN=y/: 1 failed labmulti_v7_defconfig+tiny:am335x-boneblack http://kernelci.org/boot/am335x-boneblack/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+tiny/: 1 failed labhip04-d01 http://kernelci.org/boot/hip04-d01/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+tiny/: 1 failed labsun7i-a20-cubietruck http://kernelci.org/boot/sun7i-a20-cubietruck/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+tiny/: 1 failed labsun9i-a80-cubieboard4 http://kernelci.org/boot/sun9i-a80-cubieboard4/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+tiny/: 1 failed labsun9i-a80-optimus http://kernelci.org/boot/sun9i-a80-optimus/job/next/kernel/next-20150513/defconfig/multi_v7_defconfig+tiny/: 1 failed lab

─ For more info write to info@kernelci.org

---

Kernel-build-reports mailing list Kernel-build-reports@lists.linaro.org https://lists.linaro.org/mailman/listinfo/kernel-build-reports

The hip04-d01 failures (present in arm-soc and -next) have been reported[1]. The issue is being tracked here[2].

Tyler

[1] http://www.spinics.net/lists/arm-kernel/msg418232.html [2] https://github.com/kernelci/kernel-bugs/issues/26