You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "jun aoki (JIRA)" <ji...@apache.org> on 2014/09/10 03:06:28 UTC

[jira] [Resolved] (AMBARI-7205) Ambari build fails on H4 slave due to RAT failure.

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

jun aoki resolved AMBARI-7205.
------------------------------
    Resolution: Fixed

[~u39kun] cleared the garbage and the job started working on H4.
http://mail-archives.apache.org/mod_mbox/ambari-dev/201409.mbox/browser

> Ambari build fails on H4 slave due to RAT failure.
> --------------------------------------------------
>
>                 Key: AMBARI-7205
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7205
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: jun aoki
>            Assignee: Yusaku Sako
>
> https://builds.apache.org/job/Ambari-trunk-Commit/
> has been failing and passing. The failure occurs on H4 slave and H11 seems not have this issue.
> I don't have access to the job configuration but it seems some files present on H4 and RAT fails.
> Could any of commiters please 
> 1. look into H4, the job workspace,
> 2. clean the garbage  (possibly you can tear down the entire git clone) 
> ?
> {code}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 24:46 min
> [INFO] Finished at: 2014-09-08T16:29:27+00:00
> [INFO] Final Memory: 48M/330M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.10:check (default) on project ambari-server: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/rat.txt -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}



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