Minor Description
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
Attachments
Attachments
Issue Links
- duplicates
-
YETUS-175 add a way to warn where patches have not had any test coverage
-
- Resolved
-