On 09/21/2018 09:39 AM, Stephen Warren wrote:
On 09/20/2018 11:50 PM, Heinrich Schuchardt wrote:
On 09/21/2018 12:55 AM, Stephen Warren wrote:
From: Stephen Warren
After a test has failed, test/py drains the U-Boot console log to ensure
that any relevant output is captured. At this point, we
On 09/20/2018 11:50 PM, Heinrich Schuchardt wrote:
On 09/21/2018 12:55 AM, Stephen Warren wrote:
From: Stephen Warren
After a test has failed, test/py drains the U-Boot console log to ensure
that any relevant output is captured. At this point, we don't care about
detecting any additional error
On 09/21/2018 12:55 AM, Stephen Warren wrote:
> From: Stephen Warren
>
> After a test has failed, test/py drains the U-Boot console log to ensure
> that any relevant output is captured. At this point, we don't care about
> detecting any additional errors, since the test is already known to have
>
From: Stephen Warren
After a test has failed, test/py drains the U-Boot console log to ensure
that any relevant output is captured. At this point, we don't care about
detecting any additional errors, since the test is already known to have
failed, and U-Boot will be restarted. To ensure that the
4 matches
Mail list logo
