Thomas Graves

The only other way I can think of is to have recovery enabled when a test config is set (spark.testing.XXXX). If that looks like a hassle then I would say...

It was reported the error happened with jdk8 revision 275, after upgrading it went away. It would be good for us to confirm this.

it looks like we are getting json parse exceptions on 2 files, on is: `exception com.fasterxml.jackson.core.JsonParseException: Unexpected character (',' (code 44)): was expecting a colon to separate field name and...

Since this is Databricks, its very possible they changed the events and parsing so we need to investigate if we need to use their version to parse it properly.

The latest build passed on this so perhaps something got corrupt here. I'll reopen if we see it again.

Heppened again.

I'd rather not have us ignore this as depending on the event it could be critical. I would rather wait to see if it becomes an issues with real event...

the only case here is if it keeps failing in our testing that is pretty annoying. We might want to make sure our testing isn't doing something weird... like with...

I would rather not disable parallelism, we were just using these files out of convenience, we should come up with different way to test the tools that is more reliable

its documented that the tool is an estimate. If there is nothing actionable here then we should close it and reopen when you have logs that we can look at...