From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: mainline/master boot bisection: v5.2-rc1-172-g4dde821e4296 on meson-g12a-x96-max Date: Fri, 24 May 2019 11:27:31 -0700 Message-ID: <7hh89j1ze4.fsf@baylibre.com> References: <5ce78689.1c69fb81.58097.eacf@mx.google.com> <7hmujc0xnp.fsf@baylibre.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Guillaume Tucker Cc: tomeu.vizoso@collabora.com, mgalka@collabora.com, Neil Armstrong , broonie@kernel.org, matthew.hart@linaro.org, enric.balletbo@collabora.com, Jerome Brunet , Mark Rutland , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Rob Herring , linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org Guillaume Tucker writes: > On 24/05/2019 14:50, Kevin Hilman wrote: >> "kernelci.org bot" 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.) Kevin