[PROD-429] Handle event logs with no application end events

[rmoneys]

https://synccomputing.atlassian.net/browse/PROD-429

In the case described in the ticket there are no stage, SQL or application end events in the log. There are only these events:

% jq -r .Event issues/prod-429/eventlog
DBCEventLoggingListenerMetadata
SparkListenerResourceProfileAdded
SparkListenerBlockManagerAdded
SparkListenerEnvironmentUpdate
SparkListenerApplicationStart
SparkListenerExecutorAdded
SparkListenerBlockManagerAdded

In this scenario the finish_time on the application is not set leading to the exception described in the ticket. The solution here builds on the validation that mandates end events for jobs and stages to also mandate events required to set the finish time.

Formatting removed the carriage returns so the file looks completely changed, but really only lines [26,29] were added.

A test for the solution is provided in https://github.com/synccomputingcode/sync_backend/pull/184

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[gorskysd]

Nice job identifying this as a lazy event! Looks good to me.

Only thing is if you want to increment the version, but I'll PR another log_parser change soon and can do it there.

[rmoneys]

Thanks @gorskysd, I'll let you increment the version.

The companion PR, https://github.com/synccomputingcode/sync_backend/pull/184, has a test to validate the new code. You had mentioned there being little expectation for tests under the internal_tools directory - is there a better place for the test?