You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/07/26 14:43:00 UTC
[jira] [Resolved] (BEAM-4629) RAT failures are hard to debug
[ https://issues.apache.org/jira/browse/BEAM-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik resolved BEAM-4629.
-----------------------------
Resolution: Fixed
Fix Version/s: Not applicable
> RAT failures are hard to debug
> ------------------------------
>
> Key: BEAM-4629
> URL: https://issues.apache.org/jira/browse/BEAM-4629
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Ahmet Altay
> Assignee: Luke Cwik
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> RAT failures produces an error with a reference to log file that is not accessible.
> For example:
> > Task :rat
> Build cache key for task ':rat' is 7a8f8655183c948a3f7a087e2f7c412b
> Caching disabled for task ':rat': Caching has not been enabled for the task
> Task ':rat' is not up-to-date because:
> No history is available.
> Rat TXT report: file:/home/jenkins/jenkins-slave/workspace/beam_PreCommit_Python_GradleBuild@2/src/build/reports/rat/rat-report.txt
> This is not useful unless, the person has access to the jenkins VM. Tests should include a copy of the failed rat-report.txt.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)