search for: use_lit_shell

...\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/cgi-bin/mailman/listinfo/llvm-dev > Email had 1 attachm...

...n >> > 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/cgi-b...

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

On Sat, Jul 8, 2017 at 10:07 AM Daniel Dunbar <daniel_dunbar at apple.com> wrote: > > > On Jul 8, 2017, at 7:32 AM, David Blaikie <dblaikie at gmail.com> wrote: > > Ideally/the better integration with Buildbot would be to have these > outputs referenced as "associated files" (it's been a while since I played > with buildbot - I remember finding this

.../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/test/lit.site.cfg.py.in How can I create a lit.si...

...it/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/test/lit.site.cfg...

...quot;, 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 1...

...is 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 auxiliary inputs for various tests in their parent +#...

...; >> + >> +# 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...

...'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 auxiliary inputs for var...

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