[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20161027130420.GB10262@kroah.com>
Date: Thu, 27 Oct 2016 15:04:20 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: "kernelci.org bot" <bot@...nelci.org>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net,
shuah.kh@...sung.com, patches@...nelci.org,
ben.hutchings@...ethink.co.uk, stable@...r.kernel.org
Subject: Re: [PATCH 4.8 000/140] 4.8.5-stable review
On Thu, Oct 27, 2016 at 12:29:33AM -0700, kernelci.org bot wrote:
> stable-rc boot: 110 boots: 2 failed, 102 passed with 6 offline (v4.8.4-140-gc88a99a91d3e)
>
> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.8.4-140-gc88a99a91d3e/
> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.8.4-140-gc88a99a91d3e/
>
> Tree: stable-rc
> Branch: local/linux-4.8.y
> Git Describe: v4.8.4-140-gc88a99a91d3e
> Git Commit: c88a99a91d3ee65635a471133cc04a5dcbbe02eb
> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Tested: 27 unique boards, 11 SoC families, 24 builds out of 206
>
> Boot Failures Detected: https://kernelci.org/boot/?v4.8.4-140-gc88a99a91d3e&fail
>
> arm:
>
> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> vexpress-v2p-ca15-tc1: 1 failed lab
> vexpress-v2p-ca15_a7: 1 failed lab
This is the same error as before, so I can just ignore them, right?
thanks,
greg k-h
Powered by blists - more mailing lists