search for: test_format

...cent call last): > File "C:/p/llvm/llvm\utils\lit\lit\TestingConfig.py", line 88, in > load_from_path > exec(compile(data, path, 'exec'), cfg_globals, None) > File "C:\p\llvm\llvm\tools\lld\test\lit.cfg.py", line 23, in <module> > config.test_format = lit.formats.ShTest(not > llvm_config.use_lit_shell) > AttributeError: 'NoneType' object has no attribute 'use_lit_shell' > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/c...

...C:/p/llvm/llvm\utils\lit\lit\TestingConfig.py", line 88, in >> > load_from_path >> > exec(compile(data, path, 'exec'), cfg_globals, None) >> > File "C:\p\llvm\llvm\tools\lld\test\lit.cfg.py", line 23, in <module> >> > config.test_format = lit.formats.ShTest(not >> > llvm_config.use_lit_shell) >> > AttributeError: 'NoneType' object has no attribute 'use_lit_shell' >> > >> > _______________________________________________ >> > LLVM Developers mailing list >> > llv...

Dear all, Recently I've considering using LIT for my benchmark testing framework, and the only reference for LLVM-LIT is the man page and some READMEs. I don't find any documentations on config, which seems to be quite important to the tool. If I use lit outside LLVM source tree and use on my own test files, LIT marks them as 'unresolved'. So are there any documentations I can

On Tue, Jul 10, 2018 at 10:12 PM Carlo Kok via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > That sounds quite reasaonable; how does one usually go about doing that? a repro zip that hits both asserts? > You can take inspiration from anything in lld/test, but basically either an assembly source (or multiple) passed through llvm-mc and then lld, or a YAML file passed to yaml2obj

...ck (most recent call last): File "/usr/lib/llvm-7/build/utils/lit/lit/TestingConfig.py", line 88, in load_from_path exec(compile(data, path, 'exec'), cfg_globals, None) File "/home/sdi/src/linux-kernel/clang/test/lit.cfg.py", line 25, in <module> config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) AttributeError: 'NoneType' object has no attribute 'use_lit_shell' Yes, I have a lit.cfg.py. $ LC_ALL=C ll clang/test/lit.* -rw-r--r-- 1 sdi sdi 5979 Apr 25 12:14 clang/test/lit.cfg.py -rw-r--r-- 1 sdi sdi 1906 Apr 25 12:14 clang...

...ir) invoice = {:invoice_date => Date.new(2006,9,20), :invoice_value => 44.50, :invoice_no => 45656, :invoice_to => ''Nev''} @index << invoice doc = @index[0].load doc.fields.each do |f| p f p doc[f].class p doc[f] end ========================== >ruby test_format.rb "0.10.6" :invoice_date String "2006-09-20" :invoice_value String "44.5" :invoice_no String "45656" :invoice_to String "Nev"

...t; File "/usr/lib/llvm-7/build/utils/lit/lit/TestingConfig.py", line > 88, in load_from_path > exec(compile(data, path, 'exec'), cfg_globals, None) > File "/home/sdi/src/linux-kernel/clang/test/lit.cfg.py", line 25, in > <module> > config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) > AttributeError: 'NoneType' object has no attribute 'use_lit_shell' > > Yes, I have a lit.cfg.py. > > $ LC_ALL=C ll clang/test/lit.* > -rw-r--r-- 1 sdi sdi 5979 Apr 25 12:14 clang/test/lit.cfg.py > -rw-r--r--...

...r1 (25040 of 25181) ******************** TEST 'lld-Unit :: CoreTests/CoreTests/Range.user1' FAILED ******************** Exception during script execution: Traceback (most recent call last): File "/src/llvm/utils/lit/lit/run.py", line 166, in execute_test result = test.config.test_format.execute(test, self.lit_config) File "/src/llvm/utils/lit/lit/formats/googletest.py", line 113, in execute cmd, env=test.config.environment) File "/src/llvm/utils/lit/lit/util.py", line 166, in executeCommand env=env, close_fds=kUseCloseFDs) File "/install/ppc6...

...******************** TEST 'lld-Unit :: > CoreTests/CoreTests/Range.user1' FAILED ******************** > Exception during script execution: > Traceback (most recent call last): > File "/src/llvm/utils/lit/lit/run.py", line 166, in execute_test > result = test.config.test_format.execute(test, self.lit_config) > File "/src/llvm/utils/lit/lit/formats/googletest.py", line 113, in > execute > cmd, env=test.config.environment) > File "/src/llvm/utils/lit/lit/util.py", line 166, in executeCommand > env=env, close_fds=kUseCloseFDs) > File &qu...

...'lld-Unit :: CoreTests/CoreTests/Range.user1' >> FAILED ******************** >> Exception during script execution: >> Traceback (most recent call last): >> File "/src/llvm/utils/lit/lit/run.py", line 166, in execute_test >> result = test.config.test_format.execute(test, self.lit_config) >> File "/src/llvm/utils/lit/lit/formats/googletest.py", line 113, in >> execute >> cmd, env=test.config.environment) >> File "/src/llvm/utils/lit/lit/util.py", line 166, in executeCommand >> env=env, close...

Hi Rui, et al., I was experimenting yesterday with building lld on my POWER7 PPC64/Linux machine, and ran into an unfortunate problem. When running the regressions tests under lit, almost all of the tests fail like this: terminate called after throwing an instance of 'std::system_error' what(): Resource temporarily unavailable ... 5 libc.so.6 0x00000080b7847238 abort +

.../lib/llvm-7/build/utils/lit/lit/TestingConfig.py", line >> 88, in load_from_path >> exec(compile(data, path, 'exec'), cfg_globals, None) >> File "/home/sdi/src/linux-kernel/clang/test/lit.cfg.py", line 25, in >> <module> >> config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) >> AttributeError: 'NoneType' object has no attribute 'use_lit_shell' >> >> Yes, I have a lit.cfg.py. >> >> $ LC_ALL=C ll clang/test/lit.* >> -rw-r--r-- 1 sdi sdi 5979 Apr 25 12:14 clang/test/lit...

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

...9;lit' test runner. + +# name: The name of this test suite. +config.name = 'debuginfo-tests' + +# testFormat: The test format to use to interpret tests. +# +# For now we require '&&' between commands, until they get globally killed and +# the test runner updated. +config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) + +# suffixes: A list of file extensions to treat as test files. +config.suffixes = ['.c', '.cpp', '.m'] + +# excludes: A list of directories to exclude from the testsuite. The 'Inputs' +# subdirectories contain aux...

...ttp://config.name/> = 'debuginfo-tests' >> + >> +# testFormat: The test format to use to interpret tests. >> +# >> +# For now we require '&&' between commands, until they get globally killed and >> +# the test runner updated. >> +config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) >> + >> +# suffixes: A list of file extensions to treat as test files. >> +config.suffixes = ['.c', '.cpp', '.m'] >> + >> +# excludes: A list of directories to exclude from the testsuite. The &...

...> +config.name <http://config.name/> = 'debuginfo-tests' > + > +# testFormat: The test format to use to interpret tests. > +# > +# For now we require '&&' between commands, until they get globally killed and > +# the test runner updated. > +config.test_format = lit.formats.ShTest(not llvm_config.use_lit_shell) > + > +# suffixes: A list of file extensions to treat as test files. > +config.suffixes = ['.c', '.cpp', '.m'] > + > +# excludes: A list of directories to exclude from the testsuite. The 'Inputs' >...

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