From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S938571AbdAGNYr (ORCPT <rfc822;w@1wt.eu>);
        Sat, 7 Jan 2017 08:24:47 -0500
Received: from mail.linuxfoundation.org ([140.211.169.12]:47872 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751635AbdAGNYi (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 7 Jan 2017 08:24:38 -0500
Date: Sat, 7 Jan 2017 14:24:58 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "kernelci.org bot" <bot@kernelci.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
        akpm@linux-foundation.org, linux@roeck-us.net, shuah.kh@samsung.com,
        patches@kernelci.org, ben.hutchings@codethink.co.uk,
        stable@vger.kernel.org
Subject: Re: [PATCH 4.9 000/116] 4.9.2-stable review
Message-ID: <20170107132458.GB29406@kroah.com>
References: <20170106213908.681421800@linuxfoundation.org>
 <58707fc0.cf3fc20a.aa7e8.1fbd@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58707fc0.cf3fc20a.aa7e8.1fbd@mx.google.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Jan 06, 2017 at 09:42:24PM -0800, kernelci.org bot wrote:
> stable-rc boot: 513 boots: 4 failed, 489 passed with 20 offline (v4.9.1-117-ge3bc65e52a08)
> 
> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/
> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.9.1-117-ge3bc65e52a08/
> 
> Tree: stable-rc
> Branch: local/linux-4.9.y
> Git Describe: v4.9.1-117-ge3bc65e52a08
> Git Commit: e3bc65e52a086ea9bcc31605737bbf0476f9bcd3
> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Tested: 88 unique boards, 25 SoC families, 35 builds out of 206
> 
> Boot Regressions Detected:
> 
> arm:
> 
>     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
>         vexpress-v2p-ca15_a7:
>             lab-broonie: new failure (last pass: v4.9.1)
> 
> Boot Failures Detected:
> 
> arm:
> 
>     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y
>         vexpress-v2p-ca15_a7: 1 failed lab
> 
>     sunxi_defconfig
>         sun4i-a10-cubieboard: 1 failed lab
> 
>     exynos_defconfig
>         exynos5422-odroidxu3_rootfs:nfs: 1 failed lab
> 
> arm64:
> 
>     defconfig+CONFIG_CPU_BIG_ENDIAN=y
>         juno-r2: 1 failed lab

Are all of these really "failures"?  Some of them seem like they really
did boot, but the test system didn't detect it?

I don't know what to do with these reports, should I trust them that I
broke something, or just ignore them and let someone else dig into them
to determine if it's a false-positive or something like that?

thanks,

greg k-h