I've noticed some new failures have cropped up in the recent Debian build
testsuite run for gdc. These should be investigated, but my initial
thought is that it could be the C++ linker tests. We also don't have the
testsuite ran on the auto tester for gdc-4.8 yet, so there's no cross
checking there. :)
Current build:
=== gdc tests ===
Running target unix
=== gdc Summary for unix ===
# of expected passes 16026
# of unexpected failures 16
# of unresolved testcases 16
Running target unix/-fstack-protector
=== gdc Summary for unix/-fstack-protector ===
# of expected passes 16026
# of unexpected failures 16
# of unresolved testcases 16
Running target unix/-m32
=== gdc Summary for unix/-m32 ===
# of expected passes 16026
# of unexpected failures 16
# of unresolved testcases 16
Running target unix/-mx32
=== gdc Summary for unix/-mx32 ===
# of expected passes 16022
# of unexpected failures 20
# of unresolved testcases 16
=== gdc Summary ===
# of expected passes 64100
# of unexpected failures 68
# of unresolved testcases 64
/scratch/packages/gcc/4.8/gcc-4.8-4.8.2/build/gcc/testsuite/gdc/../../gdc
version 4.8.2 (Debian 4.8.2-19)
Previous build:
=== gdc tests ===
Running target unix
=== gdc Summary for unix ===
# of expected passes 12528
Running target unix/-fstack-protector
=== gdc Summary for unix/-fstack-protector ===
# of expected passes 12528
Running target unix/-m32
=== gdc Summary for unix/-m32 ===
# of expected passes 12528
Running target unix/-mx32
=== gdc Summary for unix/-mx32 ===
# of expected passes 12528
=== gdc Summary ===
# of expected passes 50112
/scratch/packages/gcc/4.8/gcc-4.8-4.8.2/build/gcc/testsuite/gdc/../../gdc
version 4.8.2 (Debian 4.8.2-18)
