summaryrefslogtreecommitdiff
path: root/blockdev-nbd.c
diff options
context:
space:
mode:
authorMax Reitz <mreitz@redhat.com>2017-11-09 21:30:24 +0100
committerMax Reitz <mreitz@redhat.com>2017-11-14 18:06:25 +0100
commitddc7093eec38c875a6a2ae18a9ecf563107d9ff0 (patch)
tree3bff65c64673a41ba0a7b728510646ca0a0ea898 /blockdev-nbd.c
parentbc11aee2acea2944d2cf685bf35956b860df49cd (diff)
downloadqemu-ddc7093eec38c875a6a2ae18a9ecf563107d9ff0.zip
iotests: Make 083 less flaky
083 has (at least) two issues: 1. By launching the nbd-fault-injector in background, it may not be scheduled until the first grep on its output file is executed. However, until then, that file may not have been created yet -- so it either does not exist yet (thus making the grep emit an error), or it does exist but contains stale data (thus making the rest of the test case work connect to a wrong address). Fix this by explicitly overwriting the output file before executing nbd-fault-injector. 2. The nbd-fault-injector prints things other than "Listening on...". It also prints a "Closing connection" message from time to time. We currently invoke sed on the whole file in the hope of it only containing the "Listening on..." line yet. That hope is sometimes shattered by the brutal reality of race conditions, so make the sed script more robust. Signed-off-by: Max Reitz <mreitz@redhat.com> Message-id: 20171109203025.27493-5-mreitz@redhat.com Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'blockdev-nbd.c')
0 files changed, 0 insertions, 0 deletions