Am 01.04.2021 um 15:28 hat Max Reitz geschrieben:
> The job may or may not be ready before the 'quit' is issued. Whether it
> is is irrelevant; for the purpose of the test, it only needs to still be
> there. Filter the job status change and READY events from the output so
> it becomes reliable.
01.04.2021 18:30, Max Reitz wrote:
On 01.04.21 16:37, Vladimir Sementsov-Ogievskiy wrote:
01.04.2021 17:37, Vladimir Sementsov-Ogievskiy wrote:
01.04.2021 16:28, Max Reitz wrote:
The job may or may not be ready before the 'quit' is issued. Whether it
is is irrelevant; for the purpose of the
On 01.04.21 16:37, Vladimir Sementsov-Ogievskiy wrote:
01.04.2021 17:37, Vladimir Sementsov-Ogievskiy wrote:
01.04.2021 16:28, Max Reitz wrote:
The job may or may not be ready before the 'quit' is issued. Whether it
is is irrelevant; for the purpose of the test, it only needs to still be
01.04.2021 17:37, Vladimir Sementsov-Ogievskiy wrote:
01.04.2021 16:28, Max Reitz wrote:
The job may or may not be ready before the 'quit' is issued. Whether it
is is irrelevant; for the purpose of the test, it only needs to still be
there. Filter the job status change and READY events from
01.04.2021 16:28, Max Reitz wrote:
The job may or may not be ready before the 'quit' is issued. Whether it
is is irrelevant; for the purpose of the test, it only needs to still be
there. Filter the job status change and READY events from the output so
it becomes reliable.
Reported-by: Peter
The job may or may not be ready before the 'quit' is issued. Whether it
is is irrelevant; for the purpose of the test, it only needs to still be
there. Filter the job status change and READY events from the output so
it becomes reliable.
Reported-by: Peter Maydell
Suggested-by: Vladimir
