search for: shtest

...9;s something more general to do with the configuration of the bot. James On 20 July 2018 at 03:52, Justin Bogner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > "Duncan P. N. Exon Smith via llvm-dev" <llvm-dev at lists.llvm.org> writes: > > Should "lit :: shtest-format.py" (from check-lit) be marked > > unsupported on PS4? It seems flakey there. > > I've had a suspicion for a while that it's unstable *everywhere*. At > least, I've seen it fail on out-of-tree bots intermittently but haven't > had time to investigate....

Should "lit :: shtest-format.py" (from check-lit) be marked unsupported on PS4? It seems flakey there. This evening, it failed on my commit, r337514, and I'm fairly confident it wasn't my commit's fault. Then it recovered on the next commit. http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-sc...

...-------------------------------------------------------------------- root at CPU_N:/fm/bbb> ls -l total 3 -rwxr-xr-x 1 root root 89 Jan 3 16:01 qmount.sh -rwxr-xr-x 1 root root 137 Jan 3 16:01 qumount.sh -rwxr-xr-x 1 root root 435 Jan 3 16:01 set_if.sh -rwxr-xr-x 1 root root 97 Jan 3 16:01 shtest.sh -rwxr-xr-x 1 root root 468 Jan 3 16:01 syslog_chg.sh -rwxr-xr-x 1 root root 46 Jan 3 16:01 testtest.sh root at CPU_N:/fm/bbb> df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda4 6594680 150216 6444464 3% /fm root at CPU_N:/fm/bbb> cp...

...le "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/cgi-bin/mailman/listin...

...it\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.o...

...ause it actually tests functionality that people use. I'd suggest bumping up the time limits. This is what I've done in the past. See commit 6dfcc78364fa3e8104d6e6634733863eb0bf4be8 Author: Dan Liew <dan at su-root.co.uk> Date: Tue May 22 15:06:29 2018 +0000 [lit] Try to make `shtest-timeout.py` test more reliable by using a larger timeout value. This really isn't very good because it will still be susceptible to machine performance. While we are here also fix a bug in validation of `maxIndividualTestTime` where previously it wasn't checked if the t...

...s with my implementation. Currently in lit you can set a global timeout for all of the tests but not for each individual test. The attached patches add * Support for a new ResultCode called TIMEOUT * A new command line option --max-individual-test-time * Support for running external and internal ShTests with a per test timeout * Support for running GTests with a per test timeout I wanted to get some initial feedback on the implementation. * If a timeout is requested the Python psutil module is required. This module does not ship with Python but is availble via pip (or on Linux your distribu...

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

...dual-test-time > > > I think you should call it `--timeout=`, and then say in the description that it's a per-test timeout. I agree a shorter name would be nicer. I'm worried about it being confused with --max-time though. > >> * Support for running external and internal ShTests with a per test timeout >> * Support for running GTests with a per test timeout >> > > This must be the missing piece... I couldn't get my implementation to work without resorting to Python 3.x features (which is incompatible with a 2.x minimum version). I did do brief test...

Hi, Me and my supervisor are interested in improving llvm's lit a little bit. Currently, there are few things, that seem to be not very convenient about the tool: * Having several RUN commands in a failing test, it's impossible to figure out, which of them actually caused the test to fail. We can output the number of the failing RUN line. * It would be nice to

The clang-cmake-armv8-lld (linaro-toolchain owners) buildbot is timing out trying to run some timeout tests (Dan Liew author): Pass: http://lab.llvm.org:8011/builders/clang-cmake-armv8-lld/builds/5672 Fail: http://lab.llvm.org:8011/builders/clang-cmake-armv8-lld/builds/5673 Is there anything we can do to the buildbot? Or the tests? (bump up the time limits or maybe remove the tests as

...t bumping up the time limits. > > This is what I've done in the past. See > > > > commit 6dfcc78364fa3e8104d6e6634733863eb0bf4be8 > > Author: Dan Liew <dan at su-root.co.uk> > > Date: Tue May 22 15:06:29 2018 +0000 > > > > [lit] Try to make `shtest-timeout.py` test more reliable by using a > > larger timeout value. This really isn't very good because it will > > still be susceptible to machine performance. > > > > While we are here also fix a bug in validation of > > `maxIndividualTestTime` wh...

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

> On May 31, 2017, at 4:06 AM, Pavel Labath <labath at google.com> wrote: > > Thank you all for the pointers. I am going to look at these to see if > there is anything that we could reuse, and come back. In the mean > time, I'll reply to Mathiass's comments: > > On 26 May 2017 at 19:11, Matthias Braun <mbraun at apple.com> wrote: >>> Based on a

...lvm-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...

...t/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-...

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

...#39;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' >&...

...p://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 co...