Number of parallel test threads steadily decreases from 20 to 1

[marklsnyder]

I'm using TestNg version 5.9.0.5 from within eclipse. My testsuite
contains a range of dependencies, a few test classes are marked as
sequential however most aren't.

I configure my test suite of roughly 400 tests with thread-count="20"
parallel="methods" and things start off great, firing on all 20
cylinders so to speak; however the number of concurrently running
tests slowly dwindles such that after 200 completed tests or so, only
one test thread remains and the tests are being run sequentially.

I registered a Thread.UncaughtExceptionHandler to no avail - the test
threads are not dying. Many of the tests that are run after only one
test thread remains have no dependencies; so, I know that this
sequential behavior is not forced upon me by the dependency graph.

And so I hypothesize that this is based upon how the dependency graph
is traversed and that perhaps when multiple test threads converge on
and block on the same dependency only one test thread emerges?

Any ideas? Has anyone seen this sort of behavior before?

Thanks.

Mark.

[Cédric Beust ♔]

Hi Mark,

I completely rewrote the algorithm that allocates the threads for dependent methods in 5.11 (details here and here), is there any chance you could try with that version and let me know if you are still seeing this problem?

-- 

Cedric

--

You received this message because you are subscribed to the Google Groups "testng-users" group.
To post to this group, send email to testng...@googlegroups.com.
To unsubscribe from this group, send email to testng-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/testng-users?hl=en.

--

Cédric