|
From: Julian S. <js...@ac...> - 2008-10-20 23:03:14
|
> As I don't have that many machines available, if you have a PPC32/64, > or even an x86-64 or x86-32 I would love to receive the the regression > tests results for that machine, It's essentially impossible to make all the tests pass on any specific platform. Some tests require functionality which doesn't work so well on platforms different from x86/x86_64: * recognition/handling of atomic instructions and atomic instruction sequences * tracking function entry/exit (I think callgrind has difficulties on ppc). exp-ptrcheck too. * relating stack addresses to source level variables (memcheck/tests/varinfo*) Additionally the entire test suite is very sensitive to changes in glibc, since many of the backtraces it produces go into glibc. It is also sensitive to different gcc versions, since different gccs make different inlining decisions (particularly in glibc), and so that also affects the backtraces. I wish we had a test system that was more robust, but it's not obvious how to do that. I suggest you make tests work in the following order: none memcheck cachegrind massif and then maybe drd,callgrind The results below are what I get for a run on suse 11.0 (amd64). What this means is, for all the 469-11-3 tests that didn't fail, the results should match the .stdout.exp and at least one of the .stderr.exp* files, for each test. J == 469 tests, 11 stderr failures, 3 stdout failures, 1 post failure == memcheck/tests/file_locking (stderr) memcheck/tests/fprw (stderr) memcheck/tests/malloc_free_fill (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_exit_group (stderr) memcheck/tests/x86/scalar_supp (stderr) massif/tests/overloaded-new (post) none/tests/cmdline2 (stdout) none/tests/mremap2 (stdout) none/tests/shell (stderr) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) |