aw-was-here commented on PR #289: URL: https://github.com/apache/yetus/pull/289#issuecomment-1263813381
> I'll need to dig into why Yetus didn't pull the file out of the change list. Inside start-dev-env.sh, a few observations: * Running `dev-support/bin/test-patch --plugins=hadolint,maven --empty-patch` in the branch does not trigger any hadolint warnings. * Running `dev-support/bin/test-patch --plugins=hadolint,maven,github GH:4936` fails. * Removing the .yetus/excludes.txt and then running `dev-support/bin/test-patch --plugins=hadolint,maven --empty-patch --dirty-workspace` also fails. So looks like the bug with excluding a file in the same PR is still present. But it might just be for hadolint since it keeps a separate file list rather than using the master one (which is probably a bug in and of itself). Also of interesting, throwing: ``` /home/aw/hadoop/patchprocess/apache-yetus-0.14.0/lib/precommit/plugins.d/maven.sh: line 687: /tmp/yetus-24645.26567/maven-branch-dirlist-.txt: No such file or directory ``` error. Probably not related but interesting nonetheless. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: gitbox-unsubscr...@yetus.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
