You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2015/08/16 16:17:45 UTC
[jira] [Updated] (HADOOP-12233) if CHANGED_FILES is corrupt,
find_changed_modules never returns
[ https://issues.apache.org/jira/browse/HADOOP-12233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kengo Seki updated HADOOP-12233:
--------------------------------
Attachment: HADOOP-12233.HADOOP-12111.00.patch
-00:
* put a limit on the loops in find_buildfile_dir and module_skipdir in the same way as find_changed_modules
I confirmed that both of them stop against some artificial patch (without going into detail so that a malicious patch starving jenkins is not submitted easily) with the following message:
{code}
ERROR: pom.xml is not found. Make sure the target is a maven-based project.
{code}
> if CHANGED_FILES is corrupt, find_changed_modules never returns
> ---------------------------------------------------------------
>
> Key: HADOOP-12233
> URL: https://issues.apache.org/jira/browse/HADOOP-12233
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: yetus
> Affects Versions: HADOOP-12111
> Reporter: Allen Wittenauer
> Attachments: HADOOP-12233.HADOOP-12111.00.patch
>
>
> In building some unit tests, did a negative tests and hit this condition. We should put a limit on how many times we loop in the find_x_dirs code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)