[OOZIE-3713] Check if org.apache.oozie.util.TestBufferDrainer.testDrainBuffersFast could be more resilient to slow environment

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.2.1
• Assignee: Unassigned
• Reporter: Dénes Bodó
• Created: 12/Jan/23 17:02
• Updated: 12/Jan/23 17:03

Description

When tested OOZIE-3693 we found that some test cases ran too slowly caused timeouts. Fortunately a re-run solved the issue and with jmakai we checked if this timeout is a real issue or not. It is not.

12:20:02 [ERROR] org.apache.oozie.util.TestBufferDrainer.testDrainBuffersFast(org.apache.oozie.util.TestBufferDrainer)
12:20:02 [ERROR]   Run 1: TestBufferDrainer.testDrainBuffersFast:153->DrainerTestCase.checkSampleStringWithDifferentMaxLength:66->access$300:43->checkDrainBufferFast:166->drainProcessAndCheckTimeout:197 drainBuffer test timed out after 1109 ms
12:20:02 [ERROR]   Run 2: TestBufferDrainer.testDrainBuffersFast:153->DrainerTestCase.checkSampleStringWithDifferentMaxLength:66->access$300:43->checkDrainBufferFast:166->drainProcessAndCheckTimeout:197 drainBuffer test timed out after 4668 ms 

 

The task is to investigate if we could make this test case independent to the environment's performance.

Issue Links

• Discovered while testing: OOZIE-3693 [examples] Fix current SpotBugs discovered issues in Oozie's examples module