ReportGenerationAppTest is flaky

Description

The test case {{testGenerateReport}} fails with: 

Digging into bamboo logs, I can see that this is due to the fact the report does not exist:

That, in turn, appears to be caused by a failure in the report generation spark earlier:

So, there appear to be multiple issues here:

  • TMS contains an ill-formed message (which appears to be the root cause)

  • The report generation fails, but that failure is not detected

  • The reports handler returns an internal error if a report does not exist 

 

Release Notes

None

Activity

Show:
Terence Yim
September 5, 2018, 4:40 PM

Resolving this bug for now as I believe all the known flakiness has been addressed. We can reopen this bug if we observe flakiness again in the future.

Terence Yim
September 5, 2018, 12:23 AM

Fix race condition in report generation app and safeguarding SparkRunnerClassLoader.getResourceAsStream method

https://github.com/caskdata/cdap/pull/10629

Terence Yim
August 31, 2018, 5:21 PM
Terence Yim
August 31, 2018, 8:27 AM

Seems like this Java bug could be the root cause (or highly related)

https://bugs.openjdk.java.net/browse/JDK-6947916

Fixed

Assignee

Terence Yim

Reporter

Andreas Neumann

Labels

Docs Impact

None

UX Impact

None

Components

Fix versions

Affects versions

Priority

Blocker