You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2015/06/01 23:14:18 UTC
[jira] [Created] (LUCENE-6516) Split monster tests in
Test2BSortedDocValues out into their own suites so that they can be run in
parallel
Steve Rowe created LUCENE-6516:
----------------------------------
Summary: Split monster tests in Test2BSortedDocValues out into their own suites so that they can be run in parallel
Key: LUCENE-6516
URL: https://issues.apache.org/jira/browse/LUCENE-6516
Project: Lucene - Core
Issue Type: Task
Reporter: Steve Rowe
Priority: Trivial
The two monster tests in {{Test2BSortedDocValues}} each take a long time to run, e.g. from [http://jenkins.sarowe.net/job/Lucene-core-nightly-monster-trunk/23/consoleText]:
{noformat}
[junit4] HEARTBEAT J0 PID(29118@localhost): 2015-05-31T07:41:18, stalled for 5231s at: Test2BSortedDocValues.test2BOrds
[...]
[junit4] HEARTBEAT J0 PID(29118@localhost): 2015-05-31T08:04:18, stalled for 1329s at: Test2BSortedDocValues.testFixedSorted
{noformat}
If each of these tests were in its own suite, then when run with multiple JVMs, they could be run in parallel rather than serially.
When I do this locally using 4 JVMs, the Lucene core nightly+monster tests complete about 20-25 minutes faster (~95 minutes vs. ~120 minutes).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org