search

google-code-export / js-test-driver

Automatically exported from code.google.com/p/js-test-driver
1 stars 0 forks source link

Slow on Linux when tests fail #60

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run Linux (tested on Centos 5.3 x86_64 and Debian i386 5.0)
2. Run the samples on
http://code.google.com/p/js-test-driver/wiki/GettingStarted multiplied 100
times. Leave the tests failing.

What is the expected output? What do you see instead?

The tests should run a 1-2 seconds.
They run about 2.5-4+ *minutes*.

What version of the product are you using? On what operating system?

Reproduced with version 1.2 on Centos 5.3 x86_64 + Java 1.6.0_14 and Debian
5.0 i386 + Java 1.6.0_12.

Please provide any additional information below.

Here are the app, test code and the detailed results:
http://github.com/gurdiga/test-drive-jtd .

Original issue reported on code.google.com by gurd...@gmail.com on 29 Oct 2009 at 10:46

GoogleCodeExporter commented 9 years ago 
interesting, was it on firefox? did you have firebug enabled?

We are only re-evaluating what has changed but because the old code is hanging 
around the memory might keep increasing, thus slowing down the js engine.

I might add an automatic reset every few runs and it might fix the issue. When 
your 
problem happens, could you check if refreshing the browser seems to fix the 
problem?

Original comment by jeremi...@google.com on 2 Nov 2009 at 3:15

GoogleCodeExporter commented 9 years ago 
Yes it was on Firefox, and we thought about Firebug: enabling/disabling did not 
make
any difference.

One more thing: the 1.1 Version behave roughly the same.

If you know of a specific test/configuration to run to get more helpful 
information
out of this situation, I'd be glad to try it.

Original comment by gurd...@gmail.com on 2 Nov 2009 at 6:43

GoogleCodeExporter commented 9 years ago 
could you check and refresh the page when it has really slowed down, and let me 
know
if after this it is fast again?

Original comment by toc...@gmail.com on 2 Nov 2009 at 6:46

GoogleCodeExporter commented 9 years ago 
It was a single run only most of the time. Like:
- start server
- capture browser
- run tests

"Hmm... does not look good. Let's try with different Java version, on a 
different
machine, or with different version of js-test-driver"

Stop everything (server, browser) and retry. And so on...

So, it looks like a refresh does not make much sense in this context.

I found one more thing that might be useful: the actual tests ran less than a 
second
as reported by the test driver:

[vgurdiga@tkdevvm(10.101.1.32) test-drive-jtd]$ java -jar 
../JsTestDriver-1.2.jar
--tests all
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Total 101 tests (Passed: 0; Fails: 101; Errors: 0) (829.00 ms)

but the total time between start and exit of "java -jar JsTestDriver-1.2.jar 
--tests
all" is 2.5 - 4 minutes.

Original comment by gurd...@gmail.com on 3 Nov 2009 at 10:07