[
https://issues.apache.org/jira/browse/HADOOP-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738086#comment-13738086
]
Hudson commented on HADOOP-9583:
--------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #300 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/300/])
HADOOP-9583. test-patch gives +1 despite build failure when running tests.
Contributed by Jason Lowe. (kihwal:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1513200)
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> test-patch gives +1 despite build failure when running tests
> ------------------------------------------------------------
>
> Key: HADOOP-9583
> URL: https://issues.apache.org/jira/browse/HADOOP-9583
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HADOOP-9583.another_dummy.patch,
> HADOOP-9583-dummy.patch, HADOOP-9583-dummy.patch,
> HADOOP-9583-dummy-without-changes.patch, HADOOP-9583.patch
>
>
> I've seen a couple of checkins recently where tests have timed out resulting
> in a Maven build failure yet test-patch reports an overall +1 on the patch.
> This is encouraging commits of patches that subsequently break builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
