diff options
author | Zachary Turner <zturner@google.com> | 2017-09-21 16:18:28 +0000 |
---|---|---|
committer | Zachary Turner <zturner@google.com> | 2017-09-21 16:18:28 +0000 |
commit | 71deeee593c40ff01e529a6a4b30fa5b55494b82 (patch) | |
tree | a7ece15b71fa17fde17b5887bca779a41170df3b /lldb/packages/Python/lldbsuite/test/example/TestSequenceFunctions.py | |
parent | fcd9697d72eee33614a4441d63526349d08710fa (diff) | |
download | bcm5719-llvm-71deeee593c40ff01e529a6a4b30fa5b55494b82.tar.gz bcm5719-llvm-71deeee593c40ff01e529a6a4b30fa5b55494b82.zip |
[lit] Add a test for the builtin config map.
Config map is not exposed through the command line, so testing this
is somewhat tricky. But basically we need a test that if a custom
driver builds a config map and passes it to main, it gets respected.
A config map allows config files in the source tree to be mapped
to alternate config files in the build tree. This particular test
works by having two config files in separate directories, and
setting up a config map to have that redirects A/lit.site.cfg
to B/altconfig. Then, we print a message in A/lit.site.cfg
and B/altconfig and check that we do see the output from B
but don't see the output from A. Additionally we test that
the test suite specified by A's config map is properly discovered.
Differential Revision: https://reviews.llvm.org/D38105
llvm-svn: 313887
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/example/TestSequenceFunctions.py')
0 files changed, 0 insertions, 0 deletions