Re: [Qemu-devel] [PATCH for-2.8] qemu-iotests: avoid spurious failure on test 109

2016-11-09 Thread Jeff Cody
On Wed, Nov 09, 2016 at 05:20:07PM +0100, Paolo Bonzini wrote: > In some cases it is possible that query-io-status is called just > before the job is completed, causing > > -{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, > "event": "BLOCK_JOB_COMPLETED", "data": {"device":

Re: [Qemu-devel] [PATCH for-2.8] qemu-iotests: avoid spurious failure on test 109

2016-11-09 Thread Jeff Cody
On Wed, Nov 09, 2016 at 05:20:07PM +0100, Paolo Bonzini wrote: > In some cases it is possible that query-io-status is called just > before the job is completed, causing > > -{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, > "event": "BLOCK_JOB_COMPLETED", "data": {"device":

[Qemu-devel] [PATCH for-2.8] qemu-iotests: avoid spurious failure on test 109

2016-11-09 Thread Paolo Bonzini
In some cases it is possible that query-io-status is called just before the job is completed, causing -{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "BLOCK_JOB_COMPLETED", "data": {"device": "src", "len": 31457280, "offset": OFFSET, "speed": 0, "type": "mirror",