On 3/29/19 2:58 AM, Kevin Wolf wrote:
+seq="$(basename $0)"
+echo "QA output created by $seq"
+
+status=1 # failure is the default!
+
+nbd_unix_socket=$TEST_DIR/test_qemu_nbd_socket
+rm -f "${TEST_DIR}/qemu-nbd.pid"
>>>
>>> hmm, strange that we need to remove som
Am 28.03.2019 um 19:27 hat Eric Blake geschrieben:
> On 3/28/19 3:20 AM, Vladimir Sementsov-Ogievskiy wrote:
> > 28.03.2019 1:39, Eric Blake wrote:
> >> Add a test for the NBD client workaround in the previous patch. It's
> >> not really feasible for an iotest to assume a specific tracing engine,
On 3/28/19 3:20 AM, Vladimir Sementsov-Ogievskiy wrote:
> 28.03.2019 1:39, Eric Blake wrote:
>> Add a test for the NBD client workaround in the previous patch. It's
>> not really feasible for an iotest to assume a specific tracing engine,
>> so we can't really probe for the new
>> trace_nbd_parse_
28.03.2019 1:39, Eric Blake wrote:
> Add a test for the NBD client workaround in the previous patch. It's
> not really feasible for an iotest to assume a specific tracing engine,
> so we can't really probe for the new
> trace_nbd_parse_blockstatus_compliance to see if the server was fixed
> vs. wh
Add a test for the NBD client workaround in the previous patch. It's
not really feasible for an iotest to assume a specific tracing engine,
so we can't really probe for the new
trace_nbd_parse_blockstatus_compliance to see if the server was fixed
vs. whether the client just worked around the serve