From: Kevin Hilman <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, tomeu.vizoso@collabora.com,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
broonie@kernel.org, matthew.hart@linaro.org,
mgalka@collabora.com, enric.balletbo@collabora.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
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 [thread overview]
Message-ID: <7hh89j1ze4.fsf@baylibre.com> (raw)
In-Reply-To: <f01b812e-ee18-528b-1859-620dd8f0fb53@collabora.com>
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.)
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, tomeu.vizoso@collabora.com,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
broonie@kernel.org, matthew.hart@linaro.org,
mgalka@collabora.com, enric.balletbo@collabora.com,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
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 [thread overview]
Message-ID: <7hh89j1ze4.fsf@baylibre.com> (raw)
In-Reply-To: <f01b812e-ee18-528b-1859-620dd8f0fb53@collabora.com>
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.)
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Guillaume Tucker <guillaume.tucker@collabora.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: Fri, 24 May 2019 11:27:31 -0700 [thread overview]
Message-ID: <7hh89j1ze4.fsf@baylibre.com> (raw)
In-Reply-To: <f01b812e-ee18-528b-1859-620dd8f0fb53@collabora.com>
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.)
Kevin
next prev parent reply other threads:[~2019-05-24 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 5:52 mainline/master boot bisection: v5.2-rc1-172-g4dde821e4296 on meson-g12a-x96-max kernelci.org bot
2019-05-24 5:52 ` kernelci.org bot
2019-05-24 5:52 ` kernelci.org bot
2019-05-24 5:52 ` kernelci.org bot
2019-05-24 13:50 ` Kevin Hilman
2019-05-24 13:50 ` Kevin Hilman
2019-05-24 13:50 ` Kevin Hilman
2019-05-24 13:56 ` Guillaume Tucker
2019-05-24 13:56 ` Guillaume Tucker
2019-05-24 13:56 ` Guillaume Tucker
2019-05-24 18:27 ` Kevin Hilman [this message]
2019-05-24 18:27 ` Kevin Hilman
2019-05-24 18:27 ` Kevin Hilman
2019-05-26 6:50 ` Guillaume Tucker
2019-05-26 6:50 ` Guillaume Tucker
2019-05-26 6:50 ` Guillaume Tucker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hh89j1ze4.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=tomeu.vizoso@collabora.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.