Re: Only ~50 error messages get processed,

[Jack Howarth]

I am having problems trying to regression hunt this issue in dejagnu
git. Using the gcc test suite run...

make -k check-obj-c++ RUNTESTFLAGS="--target_board=unix'{-m32,-m64}'"

I get...

dejagnu 1.5.1


                === obj-c++ Summary for unix/-m32 ===

# of expected passes            3069
# of unexpected failures        39
# of expected failures          2
# of unresolved testcases       57
# of unsupported tests          68

                === obj-c++ Summary for unix/-m64 ===

# of expected passes            3002
# of unexpected failures        45
# of expected failures          18
# of unresolved testcases       60
# of unsupported tests          74

                === obj-c++ Summary ===

# of expected passes            6071
# of unexpected failures        84
# of expected failures          20
# of unresolved testcases       117
# of unsupported tests          142

but...

dejagnu 1.5.2

                === obj-c++ Summary for unix/-m32 ===

# of expected passes            128

                === obj-c++ Summary for unix/-m64 ===

# of expected passes            128

                === obj-c++ Summary ===

# of expected passes            6071
# of unexpected failures        84
# of expected failures          20
# of unresolved testcases       117
# of unsupported tests          142

I can reproduce the dejagnu 1.5.1 results with a build using...

git clone git://git.sv.gnu.org/dejagnu.git
cd dejagnu
git reset --hard 6bd8dddc81d8a5f2e835f148a9be1509f3edb147


which is the parent commit for
http://git.savannah.gnu.org/cgit/dejagnu.git/commit/?id=52dad3fd75c64d8e8cc0de5f8ca123c4aa7c32d2

however if try the same for the first commit in the gcc-1.5.2 branch...

http://git.savannah.gnu.org/cgit/dejagnu.git/commit/?h=dejagnu-1.5.2&id=d8912f7d0567831f425115eaeb6ee915e8ea5b21

using...

git reset --hard 33b71e46c0a27fee374a922eb0792b9c618c54a8

the build acts like 1.5.2 even though it should only have one
additional commit compared to the 1.5.1 release. Any clarifications on
how these git trees are arranged would be appreciated. So far I am
having no luck walking back in trunk to a point where the 1.5.1
behavior can be reproduced.
          Jack