On Wed, May 18, 2016 at 9:23 AM, kernelci.org bot bot@kernelci.org wrote:
*next boot: 211 boots: 53 failed, 154 passed with 3 offline, 1 conflict (next-20160518)* Full Boot Summary: https://kernelci.org/boot/all/job/next/kernel/next-20160518/ Full Build Summary: https://kernelci.org/build/next/kernel/next-20160518/ Tree: next Branch: local/master Git Describe: next-20160518 Git Commit: 621a2a0fb6688af5dce47d60a6d4b5a19ae2c2e4 Git URL: https://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=621a2a0fb6688af5dce47d60a6d4b5a19ae2c2e4 Tested: 52 unique boards, 13 SoC families, 29 builds out of 143
*Boot Failures Detected: https://kernelci.org/boot/?next-20160518&fail https://kernelci.org/boot/?next-20160518&fail* arm64: defconfig+CONFIG_OF_UNITTEST=y: apm-mustang https://kernelci.org/boot/apm-mustang/job/next/kernel/next-20160518/defconfig/defconfig+CONFIG_OF_UNITTEST=y/: 1 failed lab apq8016-sbc https://kernelci.org/boot/apq8016-sbc/job/next/kernel/next-20160518/defconfig/defconfig+CONFIG_OF_UNITTEST=y/: 1 failed lab juno https://kernelci.org/boot/juno/job/next/kernel/next-20160518/defconfig/defconfig+CONFIG_OF_UNITTEST=y/: 1 failed lab
At least these failures are due to changes in unflatten_dt_node. A "fix" for one problem made things worse. I should have a fix by tomorrow.
Rob