aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorLouis Dionne <ldionne@apple.com>2020-04-14 13:00:53 -0400
committerLouis Dionne <ldionne@apple.com>2020-04-15 10:53:37 -0400
commit7a6aaf9b23d6ac2fb8c11c00c73e55c0bc7aa2f0 (patch)
treedefd77125bbc50119bb4cfcac2e89eb3131dc211 /lldb/packages/Python/lldbsuite/test/configuration.py
parent443c244cff6ac43735654b2d2c74ca06e7bab102 (diff)
downloadllvm-7a6aaf9b23d6ac2fb8c11c00c73e55c0bc7aa2f0.zip
llvm-7a6aaf9b23d6ac2fb8c11c00c73e55c0bc7aa2f0.tar.gz
llvm-7a6aaf9b23d6ac2fb8c11c00c73e55c0bc7aa2f0.tar.bz2
[libc++] Remove workaround for .fail.cpp tests that don't have clang-verify markup
By renaming .fail.cpp tests that don't need clang-verify to .compile.fail.cpp, the new test format will not try to compile these tests with clang-verify, and the old test format will work just the same. However, this allows removing a workaround that requires parsing each test looking for clang-verify markup. After this change, a .fail.cpp test should always have clang-verify markup. When clang-verify is not supported by the compiler, we will just check that these tests fail to compile. When clang-verify is supported, these tests will be compiled with clang-verify whether they have markup or not (so they should have markup, or they will fail). This simplifies the test suite and also ensures that all of our .fail.cpp tests provide clang-verify markup. If it's impossible for a test to have clang-verify markup, it can be moved to a .compile.fail.cpp test, which are unconditionally just checked for compilation failure.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions