stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Created: (STDCXX-683) implement notion of expected failures in the test suite
Date Tue, 18 Dec 2007 23:59:56 GMT
implement notion of expected failures in the test suite

                 Key: STDCXX-683
             Project: C++ Standard Library
          Issue Type: New Feature
          Components: Test Driver, Tests
    Affects Versions: 4.2.0
            Reporter: Martin Sebor
            Priority: Critical

Tests (or examples) that fail for known reasons that we haven't been able to deal with should
be distinguished from failures that haven't been analyzed yet. For example, an example program
that fails to compile on an older target platform because of a compiler bug that we can't
find a simple/elegant workaround should be flagged as such in the test results. Similarly,
a test that fails one or more assertions due to compiler or libc bugs on a specific platform
(or a set of platforms) that we are unable to work around should be reported as such.

This is important in order to reduce the currently fairly large number of unexpected failures
and to be able to make changes without having to worry about regressions as much.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message