Closed as not planned
Description
When debugging or profiling highly threaded tests, leaving the JUnit timeout threads as "Thread-#" is not very useful.
The obvious name for threads would probably be the full name for the test. This could be passed in from both BlockJUnit4ClassRunner#withPotentialTimeout, which has access to the Method object, and Timeout#apply, which has access to the Description object.
The fix for #657 names these threads "Time-limited test," which somewhat more useful, but still ambiguous when a large number of tests are run.