Description
A neat little trick that sir ndimiduk found yesterday from JUnit.
By using the Timeout building (instead of just specifying the Timeout rule as we do now), we could enable a new feature in JUnit to print out a dump of the threads when a test hits the timeout limit. This could be useful in offline analysis of test failures in the future.
It looks like we'd have to bump from 4.11 to 4.12 to enable this. I figured such a shake-down is good for master and if we have success, we can consider pulling it back to 1.6 and 1.7.