> But an unexpected failure suggests a new error. That should fail and > stop the build.
That impression is incorrect. An unexpected failure may or may not be a new error. If you are concerned about unexpected failures, you'd have to investigate them. Stopping the build is not appropriate, since every release of gcc had unexpected test failures - ever since the test suite was included, atleast on minority platforms. Those minority platforms would then never get any kind of C compiler. Regards, Martin
