Testsuite: Improve failure detection
The GCC testsuite now reliably detects test failures, preventing them from going unnoticed.
The GCC testsuite has been updated to improve the detection of test failures. The changes ensure that various ways a test can report a failure (e.g., abnormal exit, incorrect return code, abort signal) are correctly identified by the testing infrastructure. By adding new test cases that specifically trigger different failure mechanisms, the testsuite confirms that failures are not silently ignored. This enhancement increases the reliability of the testsuite, making it less likely for regressions to slip through undetected.
In Details
The GCC testsuite uses .exp files to define test cases and their expected outcomes. These tests exercise different aspects of the compiler and runtime. This commit adds new .c files (e.g., shouldfail-abort.c, shouldfail-exit-neg.c) designed to fail in specific ways and verifies that the test harness correctly flags them. This ensures that the test infrastructure robustly detects test failures.
For Context
A testsuite validates that a compiler behaves as expected by running a series of tests and comparing the results against expected outputs. If a test case produces an unexpected result or crashes, it's considered a failure. This commit enhances the GCC testsuite's ability to detect failures that might otherwise go unnoticed. By ensuring that all types of test failures are properly detected, the testsuite provides a more reliable measure of the compiler's correctness.