TODOs

[shuaiwang516]

• Ctest4j runner tracking results in different parameter lists for "some" ctests when the runner executes the test method alone and executes the test with other methods in the same class together. One example test is org.apache.hadoop.yarn.util.TestFSDownload#testDownload. I think this may because of some bugs in the test name identification part, fix needed.
• If we map test names to threads that started the test, we still have the issue of threads that later get spwaned by the threads that started the test; it's very hard to tell which thread corresponds to which test;
• The current AspectJ implementation hurts the performance too much, it scans too many methods - need a better logic.