search for: test_exec_root

Displaying 7 results from an estimated 7 matches for "test_exec_root".

2019 Aug 21
2
Cannot run LLVM unit tests doe to python error in lit
...ot;C:/Users/sergej/Developer/llvm-project/llvm\utils\lit\lit\TestingConfig.py", line 89, in load_from_path exec(compile(data, path, 'exec'), cfg_globals, None) File "C:\Users\sergej\Developer\llvm-project\llvm\test\Unit\lit.cfg.py", line 24, in <module> config.test_exec_root = os.path.join(config.llvm_obj_root, 'unittests') AttributeError: 'TestingConfig' object has no attribute 'llvm_obj_root' FAILED: test/CMakeFiles/check-llvm-unit From what I can see, the TestingConfig class (which can be found in llvm/utils/lit/lit/TestingConfig.py) doesn...
2017 Nov 25
2
PSA: debuginfo-tests workflow changing slightly
...tsuite. The 'Inputs' +# subdirectories contain auxiliary inputs for various tests in their parent +# directories. +config.excludes = ['Inputs'] + +# test_source_root: The root path where tests are located. +config.test_source_root = os.path.join(config.debuginfo_tests_src_root) + +# test_exec_root: The root path where tests should be run. +config.test_exec_root = config.debuginfo_tests_obj_root + +llvm_config.use_default_substitutions() + +llvm_config.use_clang() + +if config.llvm_use_sanitizer: + # Propagate path to symbolizer for ASan/MSan. + llvm_config.with_system_environment( +...
2017 Dec 06
3
PSA: debuginfo-tests workflow changing slightly
...y inputs for various tests in their parent >> +# directories. >> +config.excludes = ['Inputs'] >> + >> +# test_source_root: The root path where tests are located. >> +config.test_source_root = os.path.join(config.debuginfo_tests_src_root) >> + >> +# test_exec_root: The root path where tests should be run. >> +config.test_exec_root = config.debuginfo_tests_obj_root >> + >> +llvm_config.use_default_substitutions() >> + >> +llvm_config.use_clang() >> + >> +if config.llvm_use_sanitizer: >> + # Propagate path to...
2017 Dec 06
2
PSA: debuginfo-tests workflow changing slightly
...directories contain auxiliary inputs for various tests in their parent > +# directories. > +config.excludes = ['Inputs'] > + > +# test_source_root: The root path where tests are located. > +config.test_source_root = os.path.join(config.debuginfo_tests_src_root) > + > +# test_exec_root: The root path where tests should be run. > +config.test_exec_root = config.debuginfo_tests_obj_root > + > +llvm_config.use_default_substitutions() > + > +llvm_config.use_clang() > + > +if config.llvm_use_sanitizer: > + # Propagate path to symbolizer for ASan/MSan. > +...
2017 Sep 11
5
Different ways of running lit
What are all the different ways people run lit? I'm doing some refactoring and want to make sure I have all the based covered. Obviously you can use check-llvm. And you can also run llvm-lit.py in your bin directory and point it to your source tree. What else? Both of the aforementioned methods require running cmake first, is there any use case where someone runs lit without having run
2017 Nov 22
2
PSA: debuginfo-tests workflow changing slightly
I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure
2015 Nov 14
3
[lit] RFC: Per test timeout
Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently in lit you can set a global timeout for all of the tests but