This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: 'make check' does nothing?
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Subject: Re: 'make check' does nothing?
- From: Rob Savoye <rob at welcomehome dot org>
- Date: Mon, 21 May 2001 10:39:28 -0600
- Cc: Phil Edwards <pedwards at disaster dot jaj dot com>, Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>, Jason Merrill <jason_merrill at redhat dot com>, libstdc++ at gcc dot gnu dot org
- References: <20010521100211.A10581@disaster.jaj.com> <Pine.SOL.3.91.1010521114552.4798D@taarna.cygnus.com>
On Mon, May 21, 2001 at 11:46:47AM -0700, Benjamin Kosnik wrote:
> > Well, I don't think I can /prove/ they are not working. But I strongly
> > suspect they aren't, based on 1) the extraordinary thrashing that my
> > machine performs during the test runs (it hasn't done this since we
> > added the memory limits under the old mkcheck), and 2) from my limited
> > understanding of DejaGnu, and reading the libstdc++-v3.log file, it looks
> > like the ulimits are simply being called by themselves before anything else
> > runs, in separate subshells of their own. That won't effect later subshells.
Correct. The call to ulimit is being executed in a subshell, all to itself.
To work, this would need to be executed in the same invocation of
the shell used to run the test.
Along time ago, before the stty command was added to Expect, I had a hack
that did effect the subshell for exec. I'll have to dig around in ancient
sources to see if I can find how I did this before. (like 8 years ago...)
For now, you might want to do add the ulimit command to the same
line that executes the test case, seperated by a ';'. The ideal solution
would be to have a list of default shell commands that gets executed in the
same sub shell as the test case when remote_exec is called.
- rob -