[LUCENE-6516] Split monster tests in Test2BSortedDocValues out into their own suites so that they can be run in parallel

• Type: Task
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 5.3, 6.0
• Lucene Fields: New, Patch Available
• Assignee: Steven Rowe
• Reporter: Steven Rowe
• Created: 01/Jun/15 21:13
• Updated: 28/Aug/22 14:33
• Resolved: 02/Jun/15 15:34

Description

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:

   [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

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).