From: Steve Ellcey <sellcey@caviumnetworks.com>
To: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Fix linknamespace parallel test failures [committed]
Date: Fri, 04 Nov 2016 17:28:00 -0000 [thread overview]
Message-ID: <1478280507.4630.20.camel@caviumnetworks.com> (raw)
In-Reply-To: <ef8a0111-75aa-771c-672f-3aa9d7486113@redhat.com>
On Fri, 2016-11-04 at 11:01 +0100, Florian Weimer wrote:
> On 11/03/2016 11:47 PM, Joseph Myers wrote:
> >
> > 2016-11-03  Joseph Myers  <joseph@codesourcery.com>
> >
> > * conform/Makefile ($(linknamespace-header-tests)): Also depend
> > on
> > $(linknamespace-symlists-tests).
> I tried this on a medium-to-large x86_64 machine (120 cores/240Â
> threads), and I had linknamespace failures before this commit, which
> are gone after it.  Thanks!
>
> Florian
It fixed the problem for me on my aarch64 box too. Â Thanks Joseph.
Steve Ellcey
prev parent reply other threads:[~2016-11-04 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 22:48 Joseph Myers
2016-11-04 10:02 ` Florian Weimer
2016-11-04 17:28 ` Steve Ellcey [this message]
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=1478280507.4630.20.camel@caviumnetworks.com \
--to=sellcey@caviumnetworks.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).