iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

[Peter Maydell]

I just got this iotest 260 failure processing an
unrelated merge on my x86-64 Ubuntu box. I assume
it's an intermittent (have just kicked off a retry) but
post the backtrace in case it's of interest:


  TEST    iotest-qcow2: 260 [fail]
QEMU          --
"/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/../../x86_64-softmmu/qemu-system-x86_64"
-nodefaults -display none -machine accel=qtest
QEMU_IMG      --
"/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/../../qemu-img"
QEMU_IO       --
"/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/../../qemu-io"
 --cache writeback -f qcow2
QEMU_NBD      --
"/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/../../qemu-nbd"
IMGFMT        -- qcow2 (compat=1.1)
IMGPROTO      -- file
PLATFORM      -- Linux/x86_64 e104462 4.15.0-60-generic
TEST_DIR      --
/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/scratch
SOCKET_SCM_HELPER --
/home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/socket_scm_helper

--- /home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/260.out
 2019-10-15 19:38:40.208504628 +0100
+++ /home/petmay01/linaro/qemu-for-merges/build/alldbg/tests/qemu-iotests/260.out.bad
  2019-10-15 20:01:22.658839136 +0100
@@ -1,52 +1,19 @@

 Testcase non-persistent without restart

-{"execute": "block-dirty-bitmap-add", "arguments": {"name":
"bitmap0", "node": "drive0", "persistent": false}}
-{"return": {}}
-initial bitmap: name=bitmap0 dirty-clusters=1
-{"execute": "blockdev-snapshot-sync", "arguments": {"device":
"drive0", "format": "qcow2", "snapshot-file": "TEST_DIR/PID-top"}}
-{"return": {}}
-check that no bitmaps are in snapshot: not found
-{"execute": "block-commit", "arguments": {"device": "drive0", "top":
"TEST_DIR/PID-top"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_READY", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-{"execute": "block-job-complete", "arguments": {"device": "drive0"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_COMPLETED", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-check bitmap after commit: name=bitmap0 dirty-clusters=2
-check updated bitmap: name=bitmap0 dirty-clusters=3
-
-Testcase persistent without restart
-
-{"execute": "block-dirty-bitmap-add", "arguments": {"name":
"bitmap0", "node": "drive0", "persistent": true}}
-{"return": {}}
-initial bitmap: name=bitmap0 dirty-clusters=1
-{"execute": "blockdev-snapshot-sync", "arguments": {"device":
"drive0", "format": "qcow2", "snapshot-file": "TEST_DIR/PID-top"}}
-{"return": {}}
-check that no bitmaps are in snapshot: not found
-{"execute": "block-commit", "arguments": {"device": "drive0", "top":
"TEST_DIR/PID-top"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_READY", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-{"execute": "block-job-complete", "arguments": {"device": "drive0"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_COMPLETED", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-check bitmap after commit: name=bitmap0 dirty-clusters=2
-check updated bitmap: name=bitmap0 dirty-clusters=3
-
-Testcase persistent with restart
-
-{"execute": "block-dirty-bitmap-add", "arguments": {"name":
"bitmap0", "node": "drive0", "persistent": true}}
-{"return": {}}
-initial bitmap: name=bitmap0 dirty-clusters=1
-{"execute": "blockdev-snapshot-sync", "arguments": {"device":
"drive0", "format": "qcow2", "snapshot-file": "TEST_DIR/PID-top"}}
-{"return": {}}
-check that no bitmaps are in snapshot: not found
-... Restart ...
-{"execute": "block-commit", "arguments": {"device": "drive0", "top":
"TEST_DIR/PID-top"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_READY", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-{"execute": "block-job-complete", "arguments": {"device": "drive0"}}
-{"return": {}}
-{"data": {"device": "drive0", "len": 65536, "offset": 65536, "speed":
0, "type": "commit"}, "event": "BLOCK_JOB_COMPLETED", "timestamp":
{"microseconds": "USECS", "seconds": "SECS"}}
-check bitmap after commit: name=bitmap0 dirty-clusters=2
-check updated bitmap: name=bitmap0 dirty-clusters=3
+Traceback (most recent call last):
+  File "260", line 87, in <module>
+    test(persistent=False, restart=False)
+  File "260", line 48, in test
+    vm.launch()
+  File "/home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/../../python/qemu/machine.py",
line 294, in launch
+    self._launch()
+  File "/home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/../../python/qemu/machine.py",
line 311, in _launch
+    self._pre_launch()
+  File "/home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/../../python/qemu/qtest.py",
line 103, in _pre_launch
+    super(QEMUQtestMachine, self)._pre_launch()
+  File "/home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/../../python/qemu/machine.py",
line 262, in _pre_launch
+    server=True)
+  File "/home/petmay01/linaro/qemu-for-merges/tests/qemu-iotests/../../python/qemu/qmp.py",
line 60, in __init__
+    self.__sock.bind(self.__address)
+OSError: AF_UNIX path too long
  TEST    iotest-qcow2: 265
  TEST    iotest-qcow2: 267
  TEST    iotest-qcow2: 268
Not run: 220
Failures: 260
Failed 1 of 109 iotests



thanks
-- PMM

Re: iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

[Max Reitz]

[-- Attachment #1.1: Type: text/plain, Size: 479 bytes --]

On 17.10.19 11:51, Peter Maydell wrote:
> I just got this iotest 260 failure processing an
> unrelated merge on my x86-64 Ubuntu box. I assume
> it's an intermittent (have just kicked off a retry) but
> post the backtrace in case it's of interest:

I hope it’s intermittent, although I presume it might not be.

In any case, I’ve recently sent a series to address this kind of issue
(https://lists.nongnu.org/archive/html/qemu-block/2019-10/msg00561.html)

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

[Peter Maydell]

On Thu, 17 Oct 2019 at 10:53, Max Reitz <mreitz@redhat.com> wrote:
>
> On 17.10.19 11:51, Peter Maydell wrote:
> > I just got this iotest 260 failure processing an
> > unrelated merge on my x86-64 Ubuntu box. I assume
> > it's an intermittent (have just kicked off a retry) but
> > post the backtrace in case it's of interest:
>
> I hope it’s intermittent, although I presume it might not be.

It has indeed failed again. Is there some way to get the
build to pick a shorter test directory name, or to get
'make check' to skip the iotests, so I can proceed with
testing until that fix lands?

thanks
-- PMM

Re: iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

[Max Reitz]

[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]

On 17.10.19 12:04, Peter Maydell wrote:
> On Thu, 17 Oct 2019 at 10:53, Max Reitz <mreitz@redhat.com> wrote:
>>
>> On 17.10.19 11:51, Peter Maydell wrote:
>>> I just got this iotest 260 failure processing an
>>> unrelated merge on my x86-64 Ubuntu box. I assume
>>> it's an intermittent (have just kicked off a retry) but
>>> post the backtrace in case it's of interest:
>>
>> I hope it’s intermittent, although I presume it might not be.
> 
> It has indeed failed again. Is there some way to get the
> build to pick a shorter test directory name, or to get
> 'make check' to skip the iotests, so I can proceed with
> testing until that fix lands?

Yes, you can set the $TEST_DIR environment variable to a shorter scratch
path.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: iotest 260 failure (linux host): "OSError: AF_UNIX path too long"

[Peter Maydell]

On Thu, 17 Oct 2019 at 11:20, Max Reitz <mreitz@redhat.com> wrote:
>
> On 17.10.19 12:04, Peter Maydell wrote:
> > On Thu, 17 Oct 2019 at 10:53, Max Reitz <mreitz@redhat.com> wrote:
> >>
> >> On 17.10.19 11:51, Peter Maydell wrote:
> >>> I just got this iotest 260 failure processing an
> >>> unrelated merge on my x86-64 Ubuntu box. I assume
> >>> it's an intermittent (have just kicked off a retry) but
> >>> post the backtrace in case it's of interest:
> >>
> >> I hope it’s intermittent, although I presume it might not be.
> >
> > It has indeed failed again. Is there some way to get the
> > build to pick a shorter test directory name, or to get
> > 'make check' to skip the iotests, so I can proceed with
> > testing until that fix lands?
>
> Yes, you can set the $TEST_DIR environment variable to a shorter scratch
> path.

Thanks, that works. It turns out that it wasn't "an unrelated
merge", I was confused. It's a merge that adds iotest 260,
which is why I hadn't seen the failure before.

-- PMM