Re: [Qemu-block] [Qemu-devel] [PATCH] iotests: Fix 219's timing

2018-06-06 Thread Max Reitz
On 2018-06-06 20:41, Peter Maydell wrote: > On 6 June 2018 at 19:37, Max Reitz wrote: >> 219 has two issues that may lead to sporadic failure, both of which are >> the result of issuing query-jobs too early after a job has been >> modified. This can then lead to different results based on whether

Re: [Qemu-block] [Qemu-devel] [PATCH] iotests: Fix 219's timing

2018-06-06 Thread Peter Maydell
On 6 June 2018 at 19:37, Max Reitz wrote: > 219 has two issues that may lead to sporadic failure, both of which are > the result of issuing query-jobs too early after a job has been > modified. This can then lead to different results based on whether the > modification has taken effect already or

Re: [Qemu-block] [Qemu-devel] [PATCH] iotests: Fix 219's timing

2018-06-04 Thread Max Reitz
On 2018-06-01 23:36, Eric Blake wrote: > On 06/01/2018 07:32 AM, Max Reitz wrote: >> 219 has two issues that may lead to sporadic failure, both of which are >> the result of issuing query-jobs too early after a job has been >> modified.  This can then lead to different results based on whether the

Re: [Qemu-block] [Qemu-devel] [PATCH] iotests: Fix 219's timing

2018-06-01 Thread Eric Blake
On 06/01/2018 07:32 AM, Max Reitz wrote: 219 has two issues that may lead to sporadic failure, both of which are the result of issuing query-jobs too early after a job has been modified. This can then lead to different results based on whether the modification has taken effect already or not. F