From: Wei Yang <richard.weiyang@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
qemu-devel@nongnu.org, richardw.yang@linux.intel.com,
fam@euphon.net, quintela@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
Date: Thu, 2 May 2019 22:34:00 +0000 [thread overview]
Message-ID: <20190502223400.kr57ek4fogabniin@master> (raw)
In-Reply-To: <20190502083550.GA2853@work-vm>
On Thu, May 02, 2019 at 09:35:50AM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richard.weiyang@gmail.com) wrote:
>> On Wed, May 01, 2019 at 09:24:06PM -0700, no-reply@patchew.org wrote:
>> >Patchew URL: https://patchew.org/QEMU/20190430034412.12935-1-richardw.yang@linux.intel.com/
>> >
>> >
>> >
>> >Hi,
>> >
>> >This series failed the asan 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
>> >time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
>> >=== TEST SCRIPT END ===
>> >
>> > COPY RUNNER
>> > RUN test-debug in qemu:fedora
>> >container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"The maximum number of active connections for UID 0 has been reached\""
>> >/usr/bin/docker-current: Error response from daemon: oci runtime error: The maximum number of active connections for UID 0 has been reached.
>> >Traceback (most recent call last):
>> > File "./tests/docker/docker.py", line 615, in <module>
>> > sys.exit(main())
>> >
>>
>> May I ask how I can reproduce this?
>
>To me this just looks like patchew having a problem, I don't think it's
>a real qemu bug.
Ah, thanks.
>
>Dave
>
>> >
>> >The full log is available at
>> >http://patchew.org/logs/20190430034412.12935-1-richardw.yang@linux.intel.com/testing.asan/?type=message.
>> >---
>> >Email generated automatically by Patchew [https://patchew.org/].
>> >Please send your feedback to patchew-devel@redhat.com
>>
>> --
>> Wei Yang
>> Help you, Help me
>--
>Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Wei Yang
Help you, Help me
WARNING: multiple messages have this Message-ID (diff)
From: Wei Yang <richard.weiyang@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: fam@euphon.net, quintela@redhat.com, qemu-devel@nongnu.org,
Wei Yang <richard.weiyang@gmail.com>,
richardw.yang@linux.intel.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c
Date: Thu, 2 May 2019 22:34:00 +0000 [thread overview]
Message-ID: <20190502223400.kr57ek4fogabniin@master> (raw)
Message-ID: <20190502223400.1EVlgESDODhWNB9IG3N1SNbPRnqncN9lhaqI9KQLwbg@z> (raw)
In-Reply-To: <20190502083550.GA2853@work-vm>
On Thu, May 02, 2019 at 09:35:50AM +0100, Dr. David Alan Gilbert wrote:
>* Wei Yang (richard.weiyang@gmail.com) wrote:
>> On Wed, May 01, 2019 at 09:24:06PM -0700, no-reply@patchew.org wrote:
>> >Patchew URL: https://patchew.org/QEMU/20190430034412.12935-1-richardw.yang@linux.intel.com/
>> >
>> >
>> >
>> >Hi,
>> >
>> >This series failed the asan 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
>> >time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
>> >=== TEST SCRIPT END ===
>> >
>> > COPY RUNNER
>> > RUN test-debug in qemu:fedora
>> >container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"The maximum number of active connections for UID 0 has been reached\""
>> >/usr/bin/docker-current: Error response from daemon: oci runtime error: The maximum number of active connections for UID 0 has been reached.
>> >Traceback (most recent call last):
>> > File "./tests/docker/docker.py", line 615, in <module>
>> > sys.exit(main())
>> >
>>
>> May I ask how I can reproduce this?
>
>To me this just looks like patchew having a problem, I don't think it's
>a real qemu bug.
Ah, thanks.
>
>Dave
>
>> >
>> >The full log is available at
>> >http://patchew.org/logs/20190430034412.12935-1-richardw.yang@linux.intel.com/testing.asan/?type=message.
>> >---
>> >Email generated automatically by Patchew [https://patchew.org/].
>> >Please send your feedback to patchew-devel@redhat.com
>>
>> --
>> Wei Yang
>> Help you, Help me
>--
>Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-05-02 22:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 3:44 [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c Wei Yang
2019-04-30 3:44 ` Wei Yang
2019-04-30 3:44 ` [Qemu-devel] [PATCH 1/3] migration/ram.c: start of migration_bitmap_sync_range is always 0 Wei Yang
2019-04-30 3:44 ` Wei Yang
2019-05-14 14:15 ` Dr. David Alan Gilbert
2019-05-14 14:27 ` Dr. David Alan Gilbert
2019-05-15 6:41 ` Wei Yang
2019-05-15 8:04 ` Dr. David Alan Gilbert
2019-05-15 8:54 ` Wei Yang
2019-04-30 3:44 ` [Qemu-devel] [PATCH 2/3] migration/ram.c: start of cpu_physical_memory_sync_dirty_bitmap " Wei Yang
2019-04-30 3:44 ` Wei Yang
2019-05-14 14:21 ` Dr. David Alan Gilbert
2019-05-31 0:54 ` Wei Yang
2019-06-21 7:43 ` Wei Yang
2019-07-17 1:13 ` Wei Yang
2019-07-17 9:16 ` Paolo Bonzini
2019-07-18 1:07 ` Wei Yang
2019-04-30 3:44 ` [Qemu-devel] [PATCH 3/3] ram: RAMBlock->offset is always aligned to a word Wei Yang
2019-04-30 3:44 ` Wei Yang
2019-07-17 9:17 ` Paolo Bonzini
2019-07-18 1:11 ` Wei Yang
2019-05-01 22:53 ` [Qemu-devel] [PATCH 0/3] Cleanup migration/ram.c no-reply
2019-05-01 22:53 ` no-reply
2019-05-02 0:10 ` Wei Yang
2019-05-02 0:10 ` Wei Yang
2019-05-02 4:24 ` no-reply
2019-05-02 4:24 ` no-reply
2019-05-02 5:32 ` Wei Yang
2019-05-02 5:32 ` Wei Yang
2019-05-02 8:35 ` Dr. David Alan Gilbert
2019-05-02 8:35 ` Dr. David Alan Gilbert
2019-05-02 22:34 ` Wei Yang [this message]
2019-05-02 22:34 ` Wei Yang
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=20190502223400.kr57ek4fogabniin@master \
--to=richard.weiyang@gmail.com \
--cc=dgilbert@redhat.com \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richardw.yang@linux.intel.com \
/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).