qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Auger Eric <eric.auger@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Sphinx UnpicklingError (was Re: [Patchew-devel] Fwd: Re: [PATCH v4] migration: Support gtree migration)
Date: Fri, 11 Oct 2019 11:44:47 +0200	[thread overview]
Message-ID: <f706cb24-6eae-db2b-beb8-5b01eb1562b6@redhat.com> (raw)
In-Reply-To: <4ae9a7e2-6446-29cc-a1b6-2d614cf3fa05@redhat.com>

Peter, this UnpicklingError from Sphinx seems to be caused by building
manuals in parallel.  Can you take a look?

Thanks,

Paolo

On 11/10/19 07:20, Auger Eric wrote:
> Hi,
> 
> This failure looks unrelated to this series; and the above script
> succeeds on my side.
> 
> Best Regards
> 
> Eric
> 
> 
> -------- Forwarded Message --------
> Subject: Re: [PATCH v4] migration: Support gtree migration
> Date: Fri, 11 Oct 2019 07:19:29 +0200
> From: Auger Eric <eric.auger@redhat.com>
> To: qemu-devel@nongnu.org, no-reply@patchew.org
> CC: quintela@redhat.com, peterx@redhat.com, dgilbert@redhat.com,
> eric.auger.pro@gmail.com
> 
> Hi,
> 
> On 10/11/19 1:51 AM, no-reply@patchew.org wrote:
>> Patchew URL: https://patchew.org/QEMU/20191010205242.711-1-eric.auger@redhat.com/
>>
>>
>>
>> Hi,
>>
>> This series failed the docker-mingw@fedora build test. Please find the testing commands and
>> their output below. If you have Docker installed, you can probably reproduce it
>> locally.
>>
>> === TEST SCRIPT BEGIN ===
>> #! /bin/bash
>> export ARCH=x86_64
>> make docker-image-fedora V=1 NETWORK=1
>> time make docker-test-mingw@fedora J=14 NETWORK=1
>> === TEST SCRIPT END ===
>>
>>   CC      block/nbd.o
>>   CC      block/sheepdog.o
>>   CC      block/accounting.o
>> make: *** [Makefile:994: docs/interop/index.html] Error 2
> 
> 
>> make: *** Deleting file 'docs/interop/index.html'
>> make: *** Waiting for unfinished jobs....
>> Traceback (most recent call last):
>> ---
>>     raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=b0665a6b133e47c781238452d53aabf1', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-f9u21j2v/src/docker-src.2019-10-10-19.48.45.2708:/var/tmp/qemu:z,ro', 'qemu:fedora', '/var/tmp/qemu/run', 'test-mingw']' returned non-zero exit status 2.
>> filter=--filter=label=com.qemu.instance.uuid=b0665a6b133e47c781238452d53aabf1
>> make[1]: *** [docker-run] Error 1
>> make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-f9u21j2v/src'
>> make: *** [docker-run-test-mingw@fedora] Error 2
>>
>> real    2m25.181s
>> user    0m7.455s
>>
>>
>> The full log is available at
>> http://patchew.org/logs/20191010205242.711-1-eric.auger@redhat.com/testing.docker-mingw@fedora/?type=message.
>> ---
>> Email generated automatically by Patchew [https://patchew.org/].
>> Please send your feedback to patchew-devel@redhat.com
>>
> 
> _______________________________________________
> Patchew-devel mailing list
> Patchew-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/patchew-devel
> 



  parent reply	other threads:[~2019-10-11  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 20:52 [PATCH v4] migration: Support gtree migration Eric Auger
2019-10-10 23:51 ` no-reply
2019-10-11  5:19   ` Auger Eric
     [not found]     ` <4ae9a7e2-6446-29cc-a1b6-2d614cf3fa05@redhat.com>
2019-10-11  9:44       ` Paolo Bonzini [this message]
2019-10-11  5:31 ` Peter Xu
2019-10-11 10:18 ` Juan Quintela
2019-10-11 11:44   ` Auger Eric

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=f706cb24-6eae-db2b-beb8-5b01eb1562b6@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=peter.maydell@linaro.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).