Re: mainline/master boot bisection: v5.2-rc1-172-g4dde821e4296 on meson-g12a-x96-max

From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: tomeu.vizoso@collabora.com, mgalka@collabora.com,
	Neil Armstrong <narmstrong@baylibre.com>,
	broonie@kernel.org, matthew.hart@linaro.org,
	enric.balletbo@collabora.com,
	Jerome Brunet <jbrunet@baylibre.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: mainline/master boot bisection: v5.2-rc1-172-g4dde821e4296 on meson-g12a-x96-max
Date: Sun, 26 May 2019 07:50:59 +0100	[thread overview]
Message-ID: <fef4eb85-cde7-6fb4-7586-cfd45b60365d@collabora.com> (raw)
In-Reply-To: <7hh89j1ze4.fsf@baylibre.com>

On 24/05/2019 19:27, Kevin Hilman wrote:
> Guillaume Tucker <guillaume.tucker@collabora.com> writes:
> 
>> On 24/05/2019 14:50, Kevin Hilman wrote:
>>> "kernelci.org bot" <bot@kernelci.org> writes:
>>>
>>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>>> * This automated bisection report was sent to you on the basis  *
>>>> * that you may be involved with the breaking commit it has      *
>>>> * found.  No manual investigation has been done to verify it,   *
>>>> * and the root cause of the problem may be somewhere else.      *
>>>> * Hope this helps!                                              *
>>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>>>
>>>> mainline/master boot bisection: v5.2-rc1-172-g4dde821e4296 on meson-g12a-x96-max
>>>>
>>>> Summary:
>>>>   Start:      4dde821e4296 Merge tag 'xfs-5.2-fixes-1' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
>>>>   Details:    https://kernelci.org/boot/id/5ce72c6259b514ed817a3640
>>>>   Plain log:  https://storage.kernelci.org//mainline/master/v5.2-rc1-172-g4dde821e4296/arm64/defconfig+CONFIG_RANDOMIZE_BASE=y/gcc-8/lab-baylibre/boot-meson-g12a-x96-max.txt
>>>>   HTML log:   https://storage.kernelci.org//mainline/master/v5.2-rc1-172-g4dde821e4296/arm64/defconfig+CONFIG_RANDOMIZE_BASE=y/gcc-8/lab-baylibre/boot-meson-g12a-x96-max.html
>>>>   Result:     11a7bea17c9e arm64: dts: meson: g12a: add pinctrl support controllers
>>>
>>> False alarm.
>>>
>>> This one is failing in one lab but passing in another:
>>> https://kernelci.org/boot/all/job/mainline/branch/master/kernel/v5.2-rc1-172-g4dde821e4296/
>>>
>>> I'll look into what's the difference between labs.
>>
>> Thanks for clarifying this.  I guess we should fix the logic
>> which detects regressions to discard cases where there is a
>> conflict between results in different labs.
> 
> Yes, we should.  If there are conflicts between labs, it's almost
> certainly not worth the effort to automatically bisect (or at least not
> worth it to send out the email.)

I've disabled bisections in lab-baylibre for now to stop the
misleading reports until lab conflicts are better handled.

Guillaume