You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@apache.org> on 2018/04/03 01:16:00 UTC

[jira] [Created] (SUREFIRE-1510) Jenkins CI fails due to performance of Windows break concurrency of forked JVMs

Tibor Digana created SUREFIRE-1510:
--------------------------------------

             Summary: Jenkins CI fails due to performance of Windows break concurrency of forked JVMs
                 Key: SUREFIRE-1510
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1510
             Project: Maven Surefire
          Issue Type: Task
          Components: Maven Failsafe Plugin, Maven Surefire Plugin, process forking
         Environment: Windows
ASF Jenkins CI
            Reporter: Tibor Digana
            Assignee: Tibor Digana


We have a problem with this build
https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/6
There are two Build Failures:
# testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT): number of different pids is not as expected expected:<2> but was:<1>
# test[junit4-twoForks-ff1](org.apache.maven.surefire.its.FailFastJUnitIT): wrong number of errors expected:<2> but was:<1>

The {{ForkModeIT}} missed delays in JUnit test methods, but the {{FailFastJUnitIT}} code is ok and the only problem is virtual CPU scheduler. We expect that two JVMs start up within 1.5 second and most probably this did not happen.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)