Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-870

"Error occurred in starting fork" shouldn't be reported for all forks with non-zero exit codes

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.12
    • Fix Version/s: 2.12.1
    • Component/s: None
    • Labels:
      None

      Description

      If a forked test has a non-zero exit code for any reason, it's reported by Surefire as "Error occurred in starting fork". It's distinctly possible for a forked test to have a non-zero exit code for reasons other than problems starting the fork - i.e., a bad test that as a System.exit(1) in it, etc. The error should either be more general, or more specific tracing of the problem should be done.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                krosenvold Kristian Rosenvold
                Reporter:
                abayer Andrew Bayer
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: