From: Jeff Law <law@redhat.com>
To: Martin Sebor <msebor@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: make[1]: *** wait: No child processes during make -j8 check
Date: Tue, 17 Jan 2017 17:54:00 -0000 [thread overview]
Message-ID: <71de8ffa-2ccb-1e04-6b5d-777051bf02db@redhat.com> (raw)
In-Reply-To: <a392d2c8-3f14-d875-daa4-7d26d43c8b4a@gmail.com>
On 01/17/2017 09:59 AM, Martin Sebor wrote:
> On 01/17/2017 08:30 AM, Jeff Law wrote:
>> On 01/16/2017 05:37 PM, Martin Sebor wrote:
>>> I've run into this failure during make check in the past with
>>> a very large make -j value (such as -j128), but today I've had
>>> two consecutive make check runs fail with -j12 and -j8 on my 8
>>> core laptop with no much else going on. The last thing running
>>> was the go test suite. Has something changed recently that
>>> could be behind it? (My user process limit is 62863.)
>> What version of make are you using? There was a bug where make could
>> lose track of children a while back. Ask Patsy -- she may remember the
>> RHEL BZ and from that we can probably extract the version #s that were
>> affected and see if they match the version you're running.
>
> I have make 4.0 and I'm running Fedora 23. I haven't changed
> anything on the machine in a while and used to be able to run
> make -j16. I still can bootstrap with that but make check
> has been failing recently. Three times yesterday (-12, -j8,
> and -j12 again), but then the last one with -j12 completed.
>
> The frustrating thing is that after the failure I have to
> restart make check from scratch, and so it can waste hours.
I went back and found the bug we recently fixed in RHEL, but it was a
make-3.8x issue.
Nothing useful in the RedHat/Fedora bug database.
jeff
prev parent reply other threads:[~2017-01-17 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 0:37 Martin Sebor
2017-01-17 1:27 ` Andrew Pinski
2017-01-17 15:30 ` Jeff Law
2017-01-17 16:59 ` Martin Sebor
2017-01-17 17:07 ` David Edelsohn
2017-01-17 17:54 ` Jeff Law [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=71de8ffa-2ccb-1e04-6b5d-777051bf02db@redhat.com \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).