This is the mail archive of the
mailing list for the libstdc++ project.
- From: Dan Kegel <dank at kegel dot com>
- To: libstdc++ at gcc dot gnu dot org
- Date: Sun, 20 Jul 2003 19:39:24 -0700
- Subject: testsuite issues
I've been building and testing gcc crosscompilers lately,
and have come across a couple issues with the libstdc++-v3
testsuite. All of these happen reliably on all targets
I've tried so far (sh4, ppc405, ppc750). My build scripts
are available at http://kegel.com/crosstool if you want to
check to see what kind of crack I'm smoking :-)
First, the issues I have fixes for:
1. The recent changes to set LD_LIBRARY_PATH seem to have
broken the ability to test libstdc++-v3 remotely.
2. Not sure when this started, but the testsuite invokes the
wrong compiler, and gets confused trying to find itself.
And the fixes:
I'd appreciate feedback on those patches. Are they good enough to submit?
Now, the issues I haven't solved yet:
FAIL: 27_io/filebuf_members.cc execution test
rsh output is filebuf_members.exe.7466: .../gcc-ss-3_3-20030714/libstdc++-v3/testsuite/27_io/filebuf_members.cc:62: void test_01(): Assertion `fb_01.is_open()' failed.
2. A whole bunch more of the same :-( I can provide details of
how these are failing if anyone's interested.
FAIL: 27_io/filebuf_virtuals.cc execution test
FAIL: 27_io/ifstream_members.cc execution test
FAIL: 27_io/istream_extractor_other.cc execution test
FAIL: 27_io/istream_seeks.cc execution test
FAIL: 27_io/istream_unformatted.cc execution test
FAIL: 27_io/ostream_inserter_other.cc execution test
I gather these aren't failing on x86 native builds. Is anyone
else seeing them?
3. The platforms I run the tests on have a very limited amount
of disk space available. I hear some of the tests create very
large files. This won't work well... there's probably a maximum
of 4MB of space available for each test to work with. I imagine
I'll find out if that's a problem soon.