Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Daniel P . Berrangé
On Fri, Mar 03, 2023 at 04:49:36PM +0100, Thomas Huth wrote: > On 03/03/2023 14.06, Daniel P. Berrangé wrote: > > On Fri, Mar 03, 2023 at 10:45:40AM +, Daniel P. Berrangé wrote: > > > On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: > > > > On 02/03/2023 19.46, Daniel P. Berrangé

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Thomas Huth
On 03/03/2023 14.06, Daniel P. Berrangé wrote: On Fri, Mar 03, 2023 at 10:45:40AM +, Daniel P. Berrangé wrote: On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: On 02/03/2023 19.46, Daniel P. Berrangé wrote: 3) When I tried this last year, I had a weird problem that the

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Daniel P . Berrangé
On Fri, Mar 03, 2023 at 10:45:40AM +, Daniel P. Berrangé wrote: > On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: > > On 02/03/2023 19.46, Daniel P. Berrangé wrote: > > 3) When I tried this last year, I had a weird problem that > >the terminal sometimes gets messed up ... I

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Daniel P . Berrangé
On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: > On 02/03/2023 19.46, Daniel P. Berrangé wrote: > 3) When I tried this last year, I had a weird problem that >the terminal sometimes gets messed up ... I wasn't able >to track it down back then - could you check by running >

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Thomas Huth
On 03/03/2023 09.53, Daniel P. Berrangé wrote: On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: On 02/03/2023 19.46, Daniel P. Berrangé wrote: To just repeat the patch 5 description... Currently meson registers a single test that invokes an entire group of I/O tests, hiding the

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Daniel P . Berrangé
On Fri, Mar 03, 2023 at 08:53:32AM +, Daniel P. Berrangé wrote: > On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: > > On 02/03/2023 19.46, Daniel P. Berrangé wrote: > > > To just repeat the patch 5 description... > > > > > > Currently meson registers a single test that invokes an

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Daniel P . Berrangé
On Fri, Mar 03, 2023 at 09:30:39AM +0100, Thomas Huth wrote: > On 02/03/2023 19.46, Daniel P. Berrangé wrote: > > To just repeat the patch 5 description... > > > > Currently meson registers a single test that invokes an entire group of > > I/O tests, hiding the test granularity from meson. There

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-03 Thread Thomas Huth
On 02/03/2023 19.46, Daniel P. Berrangé wrote: To just repeat the patch 5 description... Currently meson registers a single test that invokes an entire group of I/O tests, hiding the test granularity from meson. There are various downsides of doing this * You cannot ask 'meson test' to

Re: [PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-02 Thread Daniel P . Berrangé
On Thu, Mar 02, 2023 at 06:46:01PM +, Daniel P. Berrangé wrote: > To just repeat the patch 5 description... > > Currently meson registers a single test that invokes an entire group of > I/O tests, hiding the test granularity from meson. There are various > downsides of doing this > > * You

[PATCH 0/5] iotests: make meson aware of individual I/O tests

2023-03-02 Thread Daniel P . Berrangé
To just repeat the patch 5 description... Currently meson registers a single test that invokes an entire group of I/O tests, hiding the test granularity from meson. There are various downsides of doing this * You cannot ask 'meson test' to invoke a single I/O test * The meson test timeout