[
https://issues.apache.org/jira/browse/YETUS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115768#comment-15115768
]
Yetus QA commented on YETUS-272:
--------------------------------
(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at
https://builds.apache.org/job/PreCommit-YETUS-Build/250/console in case of
problems.
> add a way to flag/veto patches to code which jenkins doesn't test
> -----------------------------------------------------------------
>
> Key: YETUS-272
> URL: https://issues.apache.org/jira/browse/YETUS-272
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Steve Loughran
> Assignee: Allen Wittenauer
> Priority: Minor
> Attachments: YETUS-272.00.patch, YETUS-272.01.patch
>
>
> We have a recurrent problem in Hadoop where people submit patches related to
> s3, not realising that a yetus +1 doesn't mean that any of the s3 tests ran
> (they don't), and so there's risk/pressure that patches get committed without
> any actual tests.
> Could it be possible to provide a way to say "any patch under this path must
> be manually tested", and have patches vetoed if, say, they make any change to
> hadoop-tools/hadoop-aws
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
