Re: [PATCH] tests/decode: Emit TAP

2023-05-25 Thread Paolo Bonzini
On 5/25/23 12:00, Peter Maydell wrote: At least some of its "missing quoting" complaints are also legitimate, notably on $PYTHON and $DECODETREE. $PYTHON could include command line options, so I don't think it should be quoted. Though we could stop insisting on using -B; either not doing any

Re: [PATCH] tests/decode: Emit TAP

2023-05-25 Thread Peter Maydell
On Thu, 25 May 2023 at 14:11, Richard Henderson wrote: > > On 5/25/23 03:00, Peter Maydell wrote: > > On Wed, 24 May 2023 at 18:38, Richard Henderson > > wrote: > >> > >> We currently print FAIL for the failure of a succ_* test, but don't > >> return a failure exit code. Instead, convert the scr

Re: [PATCH] tests/decode: Emit TAP

2023-05-25 Thread Richard Henderson
On 5/25/23 03:00, Peter Maydell wrote: On Wed, 24 May 2023 at 18:38, Richard Henderson wrote: We currently print FAIL for the failure of a succ_* test, but don't return a failure exit code. Instead, convert the script to emit Test Anything Protocol, which gives visibility into each subtest as

Re: [PATCH] tests/decode: Emit TAP

2023-05-25 Thread Peter Maydell
On Wed, 24 May 2023 at 18:38, Richard Henderson wrote: > > We currently print FAIL for the failure of a succ_* test, but don't > return a failure exit code. Instead, convert the script to emit > Test Anything Protocol, which gives visibility into each subtest > as well as not relying on exit code

[PATCH] tests/decode: Emit TAP

2023-05-24 Thread Richard Henderson
We currently print FAIL for the failure of a succ_* test, but don't return a failure exit code. Instead, convert the script to emit Test Anything Protocol, which gives visibility into each subtest as well as not relying on exit codes. Suggested-by: Paolo Bonzini Signed-off-by: Richard Henderson