ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srimanth Gunturi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12196) Ambari-server component build fails with 'maven-surefire-plugin' failing with more than 500 tests
Date Mon, 29 Jun 2015 02:45:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-12196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Srimanth Gunturi updated AMBARI-12196:
--------------------------------------
    Description: 
Ambari-server component fails to build in [https://builds.apache.org/job/Ambari-trunk-Commit/3028/consoleFull].
The message given during build is:
{code}
[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]
{code}

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.

  was:
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.


> 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
>
>         Attachments: AMBARI-12196.patch
>
>
> Ambari-server component fails to build in [https://builds.apache.org/job/Ambari-trunk-Commit/3028/consoleFull].
The message given during build is:
> {code}
> [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]
> {code}
> 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)

Mime
View raw message