On Fri, Aug 14, 2015 at 11:25:41AM -0700, Kevin Hilman wrote: > On Fri, Aug 14, 2015 at 11:24 AM, kernelci.org bot <bot@xxxxxxxxxxxx> wrote: > > stable-queue boot: 48 boots: 2 failed, 46 passed (v3.10.86-20-g7c711fb80b94) > > > > Full Boot Summary: http://kernelci.org/boot/all/job/stable-queue/kernel/v3.10.86-20-g7c711fb80b94/ > > Full Build Summary: http://kernelci.org/build/stable-queue/kernel/v3.10.86-20-g7c711fb80b94/ > > > > Tree: stable-queue > > Branch: local/linux-3.10.y-queue > > Git Describe: v3.10.86-20-g7c711fb80b94 > > Git Commit: 7c711fb80b945f1a5c9b6c99b288889ec7b10a8c > > Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-stable.git > > Tested: 30 unique boards, 13 SoC families, 15 builds out of 137 > > > > Boot Failures Detected: http://kernelci.org/boot/?v3.10.86-20-g7c711fb80b94&fail > > > > arm: > > > > imx_v6_v7_defconfig: > > imx6q-sabrelite: 1 failed lab > > imx6q-sabrelite_rootfs:nfs: 1 failed lab > > FYI... these two boots are (somewhat) expected failures as that board > has become unstable. Any chance of removing that board from the test harness? :) thanks, 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