You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2015/06/29 04:36:04 UTC

[jira] [Created] (AMBARI-12196) Ambari-server component build fails with 'maven-surefire-plugin' failing with more than 500 tests

Srimanth Gunturi created AMBARI-12196:
-----------------------------------------

             Summary: Ambari-server component build fails with 'maven-surefire-plugin' failing with more than 500 tests
                 Key: AMBARI-12196
                 URL: https://issues.apache.org/jira/browse/AMBARI-12196
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Srimanth Gunturi
            Assignee: Srimanth Gunturi
            Priority: Critical
             Fix For: 2.1.0


Ambari-server component fails to build in [https://builds.apache.org/job/Ambari-trunk-Commit/3028/consoleFull]. The message given during build is:
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on project ambari-server: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12:test failed: Task java.util.concurrent.FutureTask@dc688d rejected from java.util.concurrent.ThreadPoolExecutor@542e8e[Running, pool size = 1, active threads = 1, queued tasks = 500, completed tasks = 0] -> [Help 1]
{noformat}

It turns out that _maven-surefire-plugin_ version 2.12 has an issue with having more than 500 tests and having {{forkMode=always}}. The issue is [https://issues.apache.org/jira/browse/SUREFIRE-913].

Updating _maven-surefire-plugin_ version to 2.13 should fix this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)