[
https://issues.apache.org/jira/browse/YETUS-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830601#comment-16830601
]
Allen Wittenauer commented on YETUS-868:
----------------------------------------
There are a few different scenarios that should be handled:
a) in-tree excludes, absolute path
b) in-tree excludes, relative path
c) out-tree excludes, absolute path
d) out-tree excludes, relative path
then all of those same cases in docker:
a) run using apache built container (such as above)
c) run using a built-at-run-time container (most of what the ASF does)
> Patch modifying the excludes file should force a re-read
> --------------------------------------------------------
>
> Key: YETUS-868
> URL: https://issues.apache.org/jira/browse/YETUS-868
> Project: Yetus
> Issue Type: Bug
> Components: Precommit
> Affects Versions: 0.10.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Critical
> Fix For: 0.11.0
>
> Attachments: YETUS-868.00.patch
>
>
> If a patch modifies the file that holds the exclusion data, it should get
> re-read and re-processed after it has been applied. Currently, it is only
> read at launch during determine_needed_tests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
