search for: testrunner

>From: Shashank Date <sdate@everestkc.net> >To: Daniel Berger <djberg96@hotmail.com>, phasis@nownuri.net >CC: win32utils-devel@rubyforge.org >Subject: Re: win32-service ideas >Date: Sun, 25 Jan 2004 10:49:03 -0600 > >Dan, Park, > > > Still nothing. The svc.log file never gets created. It''s definitely > > choking on the StartService() call.

...test directories, that is files ending with ".cpp", ".c" and ".m", synthesizes the targets by appending ".testresults". These targets are then built in parallel by a recursive invocation of $(MAKE). A build rule of form Output/%.testresults: % invokes the TestRunner.sh script. Depending on the verbosity asked for, more or less summary and error information is shown to the user. My measurements on a 4-processor machine have shown test time reduction of 60% when the tests were invoked as "make test -j8". In case of the llvm tests the situation is so...

...'", "/usr/local/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run''", "/usr/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each''", "/usr/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run''", "/usr/local/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:46:in `run_suite''", "/usr/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:67:in `start_mediator''", "/usr/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:41:in `start''", "/usr/local/lib/ruby/1.8/test/unit/ui/testrunnerut...

...e.rb:33:in `run'' /usr/local/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' /usr/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' /usr/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' /usr/local/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb: 46:in `run_suite'' /usr/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb: 67:in `start_mediator'' /usr/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb: 41:in `start'' /usr/local/lib/ruby/1.8/test/unit/ui/testrunnerutilities.rb:...

Hi, I am observing a deadlock with llvm-lit on windows 7. When I attached a debugger, the communicate() call is blocked. In file utils/lit/lit/TestRunner.py > # FIXME: There is probably still deadlock potential here. Yawn. > procData = [None] * len(procs) > procData[-1] = procs[-1].communicate() I am invoking python directly on windows to run the unit tests. C:\Python27\python.exe C:\build\llvm\Release\bin\llvm-lit.py -v -j...

...st/unit/testsuite.rb:33:in `run'' /opt/local/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' /opt/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' /opt/local/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' /opt/local/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:46:in `run_suite'' /opt/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:67:in `start_mediator'' /opt/local/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:41:in `start'' /opt/local/lib/ruby/1.8/test/unit/ui/testrunnerutilities.rb:29:in `run'&...

...#39; c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:53:in `run_suite'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:77:in `start_mediator'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:51:in `start'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:26:in `run'' c:/ruby/lib/ruby/...

...st): File "/Users/useruser/LLVM/llvm/utils/lit/lit.py", line 4, in ? import lit File "/Users/useruser/LLVM/llvm/utils/lit/lit/__init__.py", line 3, in ? from main import main File "/Users/useruser/LLVM/llvm/utils/lit/lit/main.py", line 12, in ? import TestRunner File "/Users/useruser/LLVM/llvm/utils/lit/lit/TestRunner.py", line 254 out += 'Command %d: %s\n' % (i, ' '.join('"%s"' % s for s in cmd.args)) ^ SyntaxError: invalid syntax make[1]: *** [chec...

...by $(MAKE) we will >> get the same output as before. Each of the makefiles >> shall create the .testresults files just like clang tests do. > >To be clear... do you plan to use the exisiting mechanism to execute the >"RUN" lines? This is much preferred over the TestRunner script and there >are many reasons why we transition away from using TestRunner. The RUN: lines will be executed in the same way as before. > >Also, will you preserve the ability to run a subset of tests via >TESTSUITE=X? > Yes. >Will dejagnu still produce one log file...

...#39; c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:53:in `run_suite'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:77:in `start_mediator'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:51:in `start'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:26:in `run'' c:/ruby/lib/ruby/...

...#39; c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:53:in `run_suite'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:77:in `start_mediator'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:51:in `start'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:26:in `run'' c:/ruby/lib/ruby/...

...m/779265 It seems like a redgreen or ZenTest error. I''m using Ubuntu10, Rails3, Ruby 1.9 and RVM. Any help is appriciated, thanks in advance, gezope ------ Error message: <internal:lib/rubygems/custom_require>:29:in `require'': no such file to load -- test/unit/ui/console/testrunner (LoadError) from <internal:lib/rubygems/custom_require>:29:in `require'' from /home/vadkant/.rvm/gems/ruby-1.9.2-p0/gems/redgreen-1.2.2/lib/ redgreen.rb:2:in `<top (required)>'' from <internal:lib/rubygems/custom_require>:33:in `require'' from <inter...

...#39; c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:34:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `each'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:33:in `run'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:53:in `run_suite'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:77:in `start_mediator'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:51:in `start'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:26:in `run'' c:/ruby/lib/ruby/...

...b/ruby/1.8/test/unit/testsuite.rb:32:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:31:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:32:in `run'' c:/ruby/lib/ruby/1.8/test/unit/testsuite.rb:31:in `run'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnermediator.rb:44:in `run_suite'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:65:in `start_mediato r'' c:/ruby/lib/ruby/1.8/test/unit/ui/console/testrunner.rb:39:in `start'' c:/ruby/lib/ruby/1.8/test/unit/ui/testrunnerutilities.rb:27:in `run''...

...y to do this sort of checking is by hacking into the > tool that actually interprets it (i.e. lit in this case). Considering > that lit is Python, it should be pretty easy to insert an ad-hoc regex > check (or even something substantially more sophisticated). E.g. > insert code into TestRunner.py's parseIntegratedTestScript function. Hi Sean, Let's try to work on that then. It'll be brilliant if we can make this work without churn in the test suite. I had some progress trying to get that working by building a source line table and moving substitutions to later in the pro...

...uation. The classic way to do this sort of checking is by hacking into the tool that actually interprets it (i.e. lit in this case). Considering that lit is Python, it should be pretty easy to insert an ad-hoc regex check (or even something substantially more sophisticated). E.g. insert code into TestRunner.py's parseIntegratedTestScript function. -- Sean Silva > > > Alp. > > -- > http://www.nuanti.com > the browser experts > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu...

...t; as well as I would like, switching the Linux x86_64 buildbot to it > dropped its cycle time by over 30% (just because running the tests got > about 3x faster). > 3. I've tried hard to make it easy to use, and will keep working in > this direction. Eventually I want to replace the TestRunner scripts as > well so that all that is needed to run a single test is 'lit > path/to/the/test'. I also would like to improve the output for > failures to be more informative (particularly when run via buildbot). > > See http://llvm.org/PR5217 for my TODO list before dropping D...

I was trying to install ferret 0.9.2 on solaris (SunOS 5.8) which does not have a sys/dir.h nix_io.c:5:21: sys/dir.h: No such file or directory make: *** [nix_io.o] Error 1 I couldn''t find an obvious way around this... any suggestions? Thanks, Rich Marisa Cornell Information Technologies Cornell University

...#39;t yet scale quite as well as I would like, switching the Linux x86_64 buildbot to it dropped its cycle time by over 30% (just because running the tests got about 3x faster). 3. I've tried hard to make it easy to use, and will keep working in this direction. Eventually I want to replace the TestRunner scripts as well so that all that is needed to run a single test is 'lit path/to/the/test'. I also would like to improve the output for failures to be more informative (particularly when run via buildbot). See http://llvm.org/PR5217 for my TODO list before dropping DejaGNU, feel free to add...

...working about two years ago. The general approach is to use rsh/ssh to remotely execute each test on the target, which outside of Apple requires jailbreaking. In the old test system, setting up REMOTE_CLIENT=ssh, REMOTE_PORT, etc. would automatically use ssh to run the tests. In lit, it looks like TestRunner.py has support for external shells that may be intended for this purpose; I can't tell. The test-suite and bugpoint code for working this way is still present. The problem with this setup is that it assumes that the target will be running the tests at the same paths as they were built on the h...