Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
With asserts enabled, TestTaskTrackerMemoryManager sometimes fails. From what I've inspected, it's because some tasks are marked as FAILED/TIPFAILED while others are marked SUCCEEDED.
This can be reproduced by applying MAPREDUCE-1092 and then running ant clean test -Dtestcase=TestTaskTrackerMemoryManager
Attachments
Attachments
Issue Links
- relates to
-
MAPREDUCE-1093 Java assertion failures triggered by tests
- Resolved
-
MAPREDUCE-1092 Enable asserts for tests by default
- Closed