[
https://issues.apache.org/jira/browse/HADOOP-9583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated HADOOP-9583:
-------------------------------
Status: Patch Available (was: Open)
bq. Ok, TestUberAM terminated and the build failed, but it still posted overall
+1. It seems the patch no longer works after HADOOP-9186.
I believe we're being bitten by HADOOP-8875, as test-patch currently doesn't
have a way to test itself. So the output above is from the original test-patch
before the change.
I manually ran the updated test-patch, and it correctly identified the test
timeouts and reported an overall -1 result.
> 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
> 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
