Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3651#issuecomment-68114368
> The only issue with using append = true is that multiple test invocations
will just keep appending to the file, potentially making debugging a little
more confusing. Not a big deal, I think. Maybe adding a task in the root pom
that runs before surefire/scalatest and just deletes that file?
I suppose we still have this issue, right? It might not be a big deal if
people run `mvn clean` between builds, but I could imagine it being annoying if
you're doing incremental re-builds during an iterative debugging session. Is
this hard to fix? I don't think it's the end of the world if we don't get to
this now, though.
Also, we should probably backport this change into the maintenance branches
so that we can detect whether their Java tests are broken. We should verify
that `SPARK_HOME` is obsolete in yarn/repl for those versions, too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
