Details
-
Test
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Running locally w/ upped forkcount and maven threading > 1, the set of tests that are derived from AbstractTestAsyncTableRegionReplicasRead fail near each time often the only ones failed (Get and Scan tests). They don't give clues why died. The xml has no info in it and no -output.txt is dropped. The .txt just says failed startup.
I've tried giving the forked jvms more RAM, messed w/ file counts.... Removing all of the custom setup seems to be a breakthrough. Let me put up a patch.
Attachments
Issue Links
- links to