[Lldb-commits] [PATCH] D54056: Add SetAllowJIT (the SBExpressionOptions equivalent of "expression --allow-jit")

Davide Italiano via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Sat Nov 3 15:37:55 PDT 2018

davide added a comment.

In https://reviews.llvm.org/D54056#1286620, @jankratochvil wrote:

> It broke the testsuite for me:
>   $ time PYTHONPATH=$PWD/lib64/python2.7/site-packages:$PWD/lib64/python2.7/site-packages/lldb ../llvm-git/tools/lldb/test/dotest.py --executable $PWD/bin/lldb -C $PWD/bin/clang -t ../llvm-git/tools/lldb/packages/Python/lldbsuite/test/ 
>   WARNING:root:No valid FileCheck executable; some tests may fail...
>   WARNING:root:(Double-check the --filecheck argument to dotest.py)
>   LLDB library dir: /home/jkratoch/redhat/llvm-git-build-release-clang/bin
>   LLDB import library dir: /home/jkratoch/redhat/llvm-git-build-release-clang/bin
>   lldb version 8.0.0
>     clang revision 6974b990e13dfb4190a6dffdcc8bac9edbd1cde5
>     llvm revision 7fad5fb0d0d32beea4e95e239cc065a850733358
>   Libc++ tests will not be run because: Unable to find libc++ installation
>   Skipping following debug info categories: ['dsym', 'gmodules']
>   Traceback (most recent call last):
>     File "../llvm-git/tools/lldb/test/dotest.py", line 7, in <module>
>       lldbsuite.test.run_suite()
>     File "/home/jkratoch/redhat/llvm-git/tools/lldb/packages/Python/lldbsuite/test/dotest.py", line 1323, in run_suite
>       visit('Test', dirpath, filenames)
>     File "/home/jkratoch/redhat/llvm-git/tools/lldb/packages/Python/lldbsuite/test/dotest.py", line 965, in visit
>       raise Exception("Found multiple tests with the name %s" % name)
>   Exception: Found multiple tests with the name TestSampleTest.py
> As really there are now:
>   $ find -name TestSampleTest.py
>   ./packages/Python/lldbsuite/test/expression_command/dont_allow_jit/TestSampleTest.py
>   ./packages/Python/lldbsuite/test/sample_test/TestSampleTest.py

I don't think anybody will look at this until Monday, so if you want a quick fix you might consider renaming the test yourself.





More information about the lldb-commits mailing list