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
Activity
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.
Fix race condition in report generation app and safeguarding SparkRunnerClassLoader.getResourceAsStream method
Another fix attempt
Seems like this Java bug could be the root cause (or highly related)
Build still fail
Seems like it is a known issue that requires workaround
https://github.com/ronmamo/reflections/issues/81
