[SUREFIRE-1287] Improve logging to understand why test run failed and report the right failed category

**[Samarth Jain](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=samarthjain)** opened **[SUREFIRE-1287](https://issues.apache.org/jira/browse/SUREFIRE-1287?redirect=false)** and commented

As part of our automated jenkins builds that run after every checkin, we have been seeing a lot of these failures:

Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (ParallelStatsEnabledTest) on project phoenix-core: There was a timeout or other error in the fork

Sample run:
https://builds.apache.org/job/Phoenix-master/1420/console

Unfortunately that bit of error information doesn't really help. It would be good to know why exactly the fork timed out or failed. What we do know is that some of the tests in the Junit category ParallelStatsDisabledTest failed to complete. However, failsafe incorrectly reports the failed category as the first category that ran. In this case it happened to be ParallelStatsEnabledTest. Also to note is the fact that failsafe kicks off next category run even before all the tests in the current category have finished. I am not sure if that is by design or a bug.

FYI, [James R. Taylor](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jamestaylor).

---

**Affects:** 2.19.1

0 votes, 7 watchers

Start by reviewing the linked Jenkins console run and the reported Failsafe 2.19.1 failure, then trace how Failsafe handles the ParallelStatsEnabledTest and ParallelStatsDisabledTest category runs. Done means the failure output explains why the fork timed out or failed and identifies the category that actually failed.

Written by the indexing model from the issue text.