From: Max Reitz <mreitz@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: iotest 260 failure (linux host): "OSError: AF_UNIX path too long"
Date: Thu, 17 Oct 2019 12:20:11 +0200 [thread overview]
Message-ID: <1b52f4fb-c8e7-ecbd-9db4-32e7e9c5f1b5@redhat.com> (raw)
In-Reply-To: <CAFEAcA-0aYLbEoWf_ZeTxoLdKNaeFESyiuHi5KYG9kdUWaAJtg@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2019-10-17 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:51 iotest 260 failure (linux host): "OSError: AF_UNIX path too long" Peter Maydell
2019-10-17 9:53 ` Max Reitz
2019-10-17 10:04 ` Peter Maydell
2019-10-17 10:20 ` Max Reitz [this message]
2019-10-17 11:01 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b52f4fb-c8e7-ecbd-9db4-32e7e9c5f1b5@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).