This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ridiculous memory consumption in libstdc++ test suite
- To: "Zack Weinberg" <zackw at stanford dot edu>
- Subject: Re: ridiculous memory consumption in libstdc++ test suite
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- Date: 27 Apr 2001 15:38:58 +0200
- Cc: gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <20010427025021.Q11683@stanford.edu>
"Zack Weinberg" <zackw@stanford.edu> writes:
| My current libstdc++ test results (mainline):
|
| === libstdc++ tests ===
|
| FAIL: 21_strings/ctor_copy_dtor.cc (execution test), static
| FAIL: 21_strings/ctor_copy_dtor.cc (execution test), shared
| FAIL: 21_strings/insert.cc (execution test), static
| FAIL: 21_strings/insert.cc (execution test), shared
| FAIL: 22_locale/ctor_copy_dtor.cc (execution test), static
| FAIL: 22_locale/ctor_copy_dtor.cc (execution test), shared
| FAIL: 27_io/ios_members.cc (execution test), static
|
| === libstdc++ Summary ===
|
| # of expected passes 403
| # of unexpected failures 7
| # of expected failures 16
|
| All the 21_strings failures are because I had to shoot the test
| process after it chewed up all the RAM on the machine and well into
| swap. SIZE column in ps was >512MB in all cases. The machine has
| 256 megs of real RAM and a gigabyte of swap.
Zack,
This sort of is a known issue. We need the ability to tell DejaGnu to
set ulimits before running a particular testcase particular. In the
old non-DejaGnu days that was done by the shell script mkcheck.
-- Gaby
CodeSourcery, LLC http://www.codesourcery.com