Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/324#issuecomment-221917899
The issue is not with before, but with _after_, since it effectively acts
as a _finally_ block. The way it was before if a test failed for whatever
reason, then the FC.shutdown was not executed, and due to that you had this
file lock exception.
As for multiple-threading test, it is not black and white, but rather
allows the system to validate if there are concurrency issues of some type. I
am also not sure what you mean by scheduling issues as the test controls the
thread pool. So may be you can clarify.
---
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.
---
