Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/17402
Yes, I'll post an updated change once I wrap up a couple of other things...
> Seems like the scope of the bug was a little larger than you thought.
@vanzin The scope of the bug (specifically the text "after each suite") was
vague so this was a purposefully small proof-of-concept change. I tried to be
clear about this in JIRA comments and in the PR description.
That being said: yes, the direction I'll go is reviewing more existing
tests and seeing where it would make sense to put a check for leaked memory.
Ideally I'd put this in an after() or afterAll() block but I need to do some
more digging to figure out exactly where.
---
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]
