On Sat, Aug 15, 2015 at 08:10:16AM -0700, Kevin Hilman wrote: > On Sat, Aug 15, 2015 at 8:08 AM, kernelci.org bot <bot@xxxxxxxxxxxx> wrote: > > stable-queue boot: 183 boots: 0 failed, 182 passed with 1 conflict (v3.14.50-44-g7a148040468f) > > > > Full Boot Summary: http://kernelci.org/boot/all/job/stable-queue/kernel/v3.14.50-44-g7a148040468f/ > > Full Build Summary: http://kernelci.org/build/stable-queue/kernel/v3.14.50-44-g7a148040468f/ > > > > Tree: stable-queue > > Branch: local/linux-3.14.y-queue > > Git Describe: v3.14.50-44-g7a148040468f > > Git Commit: 7a148040468f41b14d8c3859cde00d15318f83d5 > > Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-stable.git > > Tested: 48 unique boards, 16 SoC families, 23 builds out of 140 > > > > Conflicting Boot Failure Detected: (These likely are not failures as other labs are reporting PASS. Needs review.) > > > > arm: > > > > multi_v7_defconfig: > > am335x-boneblack: > > lab-khilman: PASS > > lab-cambridge: FAIL > > lab-tbaker: PASS > > The same board working in 2 of 3 labs usually indicates some > lab-specifiic issue, so this shouldn't be considered a new failure. > We'll look into the lab. Thanks for the testing. 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