Affects Version/s: 3.0.0-M5
Fix Version/s: None
Component/s: Maven Surefire Plugin
Surefire-api clears the interrupted flag sometimes but not consistently in any code which writes to the console.
It is not expected that writing to the console would result in clearing the interrupted flag nor is it easy to trace this is the cause when it does.
The line of code causing this has a warning that it's result is ignored and probably shouldn't be.
The stack trace
The last line of code calls System.out.println(abc);
Instead of discarding the interrupted flag, I suggest setting it again in a finally block when exiting the sensitive code or it's not cleared unexpectedly.
If this is expected behaviour, I suggest producing a warning that it was cleared so you work out why certain tests to detect the behaviour of an interrupted thread, fail when run in surefire.