On 16.05.19 18:11, Max Reitz wrote: > In 219, we wait for the job to make progress before we emit its status. > This makes the output reliable. > > Unfortunately, there is a bug: We do not wait for any more progress if > the job has already reached its total-progress. Right after the job has > been started, it is possible that total-progress is still 0, though. In > that case, we may skip the first progress-making step and keep ending up > 64 kB short. > > To fix that bug, we cab simply wait for total-progress to reach 4 MB > (the image size) after starting the job. > > Reported-by: Karen Mezick > Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1686651 > Signed-off-by: Max Reitz > --- > tests/qemu-iotests/219 | 13 ++++++++++--- > 1 file changed, 10 insertions(+), 3 deletions(-) Adjusted the commit message to what I understood John to mean, and applied to my block(-on-kevin) branch. (Thanks for the review!) Max