On 10/28/24 18:02, Simon Glass wrote:
Hi Heinrich,
On Mon, 28 Oct 2024 at 07:07, Heinrich Schuchardt <[email protected]
<mailto:[email protected]>> wrote:
>
> On 10/22/24 14:00, Simon Glass wrote:
> > This test checks console output so should have the UTF_CONSOLE
flag. Add
> > it.
> >
> > Signed-off-by: Simon Glass <[email protected] <mailto:[email protected]>>
> > ---
> >
> > (no changes since v1)
> >
> > test/boot/bootflow.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/test/boot/bootflow.c b/test/boot/bootflow.c
> > index 154dea70a59..cc894e804a4 100644
> > --- a/test/boot/bootflow.c
> > +++ b/test/boot/bootflow.c
> > @@ -370,7 +370,7 @@ static int bootflow_iter(struct unit_test_state
*uts)
> >
> > return 0;
> > }
> > -BOOTSTD_TEST(bootflow_iter, UTF_DM | UTF_SCAN_FDT);
> > +BOOTSTD_TEST(bootflow_iter, UTF_DM | UTF_SCAN_FDT | UTF_CONSOLE);
>
> The test invokes ut_assert_console_end(). But where does it check
> console output?
That is it. It is making sure that there is no console output. But the
flag is needed in order to do any console checking.
Regards,
Simon
Acked-by: Heinrich Schuchardt <[email protected]>
