Re: make[1]: *** wait: No child processes during make -j8 check

2017-01-17 Thread Jeff Law
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

Re: make[1]: *** wait: No child processes during make -j8 check

2017-01-17 Thread David Edelsohn
On Tue, Jan 17, 2017 at 11: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

Re: make[1]: *** wait: No child processes during make -j8 check

2017-01-17 Thread Martin Sebor
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

Re: make[1]: *** wait: No child processes during make -j8 check

2017-01-17 Thread Jeff Law
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

Re: make[1]: *** wait: No child processes during make -j8 check

2017-01-16 Thread Andrew Pinski
On Mon, Jan 16, 2017 at 4: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

make[1]: *** wait: No child processes during make -j8 check

2017-01-16 Thread Martin Sebor
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