[
https://issues.apache.org/jira/browse/YETUS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087723#comment-15087723
]
Sean Busbey commented on YETUS-272:
-----------------------------------
Is the preference for a "-1" vote against or a "0" advisory to go with the "I
can't do anything about this you should test manually"?
The closest I can find to a similar piece of feedback is the whitespace
detector. It uses a "-1" to say "the committer should use this particular way
of applying to fix this issue."
> 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
> Priority: Minor
>
> 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)
