maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/utils/lldb-dotest/lldb-dotest.in

18 lines
484 B
Plaintext
Raw Normal View History

[test] Add dotest wrapper This adds a wrapper around dotest, similar to llvm-lit in llvm. The wrapper is created in the binary directory, next to LLDB and allows you to invoke dotest without having to pass any of the configuration arguments yourself. I think this could also be useful for re-running a particular test case when it fails, as an alternative to "Command Invoked". The motivation for this is that I'd like to replace the driver part of dotest with lit. As a first step, I'd like to have lit invoke dotest, which would just run the complete test suite, completely identical to what the CMake target does today. Once this is in place, we can have lit run dotest for the different test directories, and ultimately once per python file. Along the way we can strip out driver functionality from dotest where appropriate. https://reviews.llvm.org/D44002 llvm-svn: 326687
2018-03-05 18:03:44 +08:00
#!/usr/bin/env python
[dotest] Use subprocess.call to forward arguments in wrapper As suggested by Pavel on lldb-commits. Originally I picked os.system because it was so much more simple than the subprocess module, but that no longer holds true after yesterday's hack in r328020. This is what it should've been in the first place. Differential revision: https://reviews.llvm.org/D44728 llvm-svn: 328089
2018-03-21 19:13:56 +08:00
import subprocess
[test] Add dotest wrapper This adds a wrapper around dotest, similar to llvm-lit in llvm. The wrapper is created in the binary directory, next to LLDB and allows you to invoke dotest without having to pass any of the configuration arguments yourself. I think this could also be useful for re-running a particular test case when it fails, as an alternative to "Command Invoked". The motivation for this is that I'd like to replace the driver part of dotest with lit. As a first step, I'd like to have lit invoke dotest, which would just run the complete test suite, completely identical to what the CMake target does today. Once this is in place, we can have lit run dotest for the different test directories, and ultimately once per python file. Along the way we can strip out driver functionality from dotest where appropriate. https://reviews.llvm.org/D44002 llvm-svn: 326687
2018-03-05 18:03:44 +08:00
import sys
dotest_path = '@LLDB_SOURCE_DIR@/test/dotest.py'
[dotest] Use subprocess.call to forward arguments in wrapper As suggested by Pavel on lldb-commits. Originally I picked os.system because it was so much more simple than the subprocess module, but that no longer holds true after yesterday's hack in r328020. This is what it should've been in the first place. Differential revision: https://reviews.llvm.org/D44728 llvm-svn: 328089
2018-03-21 19:13:56 +08:00
dotest_args_str = '@LLDB_DOTEST_ARGS@'
[test] Add dotest wrapper This adds a wrapper around dotest, similar to llvm-lit in llvm. The wrapper is created in the binary directory, next to LLDB and allows you to invoke dotest without having to pass any of the configuration arguments yourself. I think this could also be useful for re-running a particular test case when it fails, as an alternative to "Command Invoked". The motivation for this is that I'd like to replace the driver part of dotest with lit. As a first step, I'd like to have lit invoke dotest, which would just run the complete test suite, completely identical to what the CMake target does today. Once this is in place, we can have lit run dotest for the different test directories, and ultimately once per python file. Along the way we can strip out driver functionality from dotest where appropriate. https://reviews.llvm.org/D44002 llvm-svn: 326687
2018-03-05 18:03:44 +08:00
if __name__ == '__main__':
[dotest] Use subprocess.call to forward arguments in wrapper As suggested by Pavel on lldb-commits. Originally I picked os.system because it was so much more simple than the subprocess module, but that no longer holds true after yesterday's hack in r328020. This is what it should've been in the first place. Differential revision: https://reviews.llvm.org/D44728 llvm-svn: 328089
2018-03-21 19:13:56 +08:00
wrapper_args = sys.argv[1:]
dotest_args = dotest_args_str.split(';')
# Build dotest.py command.
Use sys.executable in lldb-dotest Without that, dotest.py would be executed with the default python interpreter, which may not be the same one that lldb is built with. This still requires the user do know which python interpreter to use when running lldb-dotest, but now he is at least able to choose it, if he knows which one to use. llvm-svn: 354105
2019-02-15 15:41:17 +08:00
cmd = [sys.executable, dotest_path, '-q']
[dotest] Use subprocess.call to forward arguments in wrapper As suggested by Pavel on lldb-commits. Originally I picked os.system because it was so much more simple than the subprocess module, but that no longer holds true after yesterday's hack in r328020. This is what it should've been in the first place. Differential revision: https://reviews.llvm.org/D44728 llvm-svn: 328089
2018-03-21 19:13:56 +08:00
cmd.extend(dotest_args)
cmd.extend(wrapper_args)
[test] Exit lldb-dotest in a more Pythonic way. As suggested by Keith Smiley in: https://github.com/apple/swift-lldb/pull/486 llvm-svn: 328966
2018-04-02 18:44:36 +08:00
# Invoke dotest.py and return exit code.
[lldb-dotest] Print dotest.py invocation. In order to debug a failing python test, you need to debug Python instead of the wrapper. For a while I've been adding and removing this, but I think it could be useful for everyone. llvm-svn: 357554
2019-04-03 09:26:38 +08:00
print(' '.join(cmd))
[test] Exit lldb-dotest in a more Pythonic way. As suggested by Keith Smiley in: https://github.com/apple/swift-lldb/pull/486 llvm-svn: 328966
2018-04-02 18:44:36 +08:00
sys.exit(subprocess.call(cmd))