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

Process pending events from forked process after exited and then finish forked Thread.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.20
    • Component/s: process forking
    • Labels:
      None

      Description

      It is a fix after Jenkins build failure:

      https://builds.apache.org/job/maven-surefire/org.apache.maven.surefire$surefire-integration-tests/1673/testReport/junit/org.apache.maven.surefire.its/ConsoleOutputIT/largerSoutThanMemory/

      The events go to Queue from std/out of forked JVM. The events are processed asynchronously. Processing of them should prolong #close() method in ThreadedStreamConsumer. Max 5 minutes timeout.
      This should prevent from particular exit when heavily a lot of console logs is printed by forked Test set.

      [ERROR] Process Exit Code: 0
      [ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?

        Attachments

          Activity

            People

            • Assignee:
              tibor17 Tibor Digana
              Reporter:
              tibor17 Tibor Digana
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: