summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
diff options
context:
space:
mode:
authorTobias Grosser <tobias@grosser.es>2016-10-04 19:48:40 +0000
committerTobias Grosser <tobias@grosser.es>2016-10-04 19:48:40 +0000
commite84ee850d1f7fc2e8dac8d90c5856e8451ca3bbe (patch)
treedf55efc5a8a31a92fc0d956b7912aa9b538e4d40 /lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
parentc43fa4f23c44cf7b5946c94fb3886722cd56627e (diff)
downloadbcm5719-llvm-e84ee850d1f7fc2e8dac8d90c5856e8451ca3bbe.tar.gz
bcm5719-llvm-e84ee850d1f7fc2e8dac8d90c5856e8451ca3bbe.zip
Build and run isl_test as part of check-polly
Running isl tests is important to gain confidence that the isl build we created works as expected. Besides the actual isl tests, there are also isl AST generation tests shipped with isl. This change only adds support for the isl unit tests. AST generation test support is left for a later commit. There is a choice to run tests directly through the build system or in the context of lit. We choose to run tests as part of lit to as this allows us to easily set environment variables, print output only on error and generally run the tests directly from the lit command. Reviewers: brad.king, Meinersbur Subscribers: modocache, brad.king, pollydev, beanz, llvm-commits, mgorny Differential Revision: https://reviews.llvm.org/D25155 llvm-svn: 283245
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud