[PATCH v5 03/20] test: Pass stderr to stdout
Simon Glass
sjg at chromium.org
Fri Aug 30 03:06:36 CEST 2024
Hi Tom,
On Thu, 29 Aug 2024 at 10:48, Tom Rini <trini at konsulko.com> wrote:
>
> On Thu, Aug 29, 2024 at 09:01:11AM -0600, Simon Glass wrote:
> > Hi Neil,
> >
> > On Thu, 29 Aug 2024 at 08:22, <neil.armstrong at linaro.org> wrote:
> > >
> > > On 29/08/2024 00:08, Simon Glass wrote:
> > > > Some tests may output things to stderr. Ensure that this output is not
> > > > dropped, by redirecting it to stdout
> > >
> > > Can't you make sure to output all labgrid output to stdout in the hook script instead ?
> >
> > Possibly. Do you mean having the hook script redirect stderr to stdout?
>
> This gets back to one of the points I was making. In this case, "some
> tests" is what? And then, what's even going on? Are we missing output
> that we should be parsing? Are we not catching errors? Or is this just
> related to how today we have for say the filesystem tests so many
> try/except things that we inadvertently need a series of failures?
When Labgrid crashes for some reason, the output is currently lost, so
it is not clear what happened. I suppose Labgrid is not supposed to
crash, but...
As a starting point I have erred on the side of more output rather
than less. I have found that to be very helpful when developing it,
but I am sure we can refine it once it is stable.
Regards,
Simon
More information about the U-Boot
mailing list