[
https://issues.apache.org/jira/browse/LUCENE-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe resolved LUCENE-6516.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.3
Trunk
Assignee: Steve Rowe
> 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
> Assignee: Steve Rowe
> Priority: Trivial
> Fix For: Trunk, 5.3
>
> Attachments: LUCENE-6516.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
