wombatu-kun commented on code in PR #19919:
URL: https://github.com/apache/hudi/pull/19919#discussion_r4595849349


##########
.github/workflows/bot.yml:
##########
@@ -1875,6 +1875,12 @@ jobs:
           - sparkProfile: 'spark3.5'
             flinkProfile: 'flink2.2'
             sparkArchive: 'spark-3.5.9/spark-3.5.9-bin-hadoop3.tgz'
+    env:
+      # The only modules with integration-test classes besides hudi-flink, 
whose ITs run in the
+      # flink jobs. The build below builds these and what they depend on (-am) 
and the IT step
+      # verifies just these, instead of building and re-packaging all 66 
modules. A module that
+      # adds an IT class must be listed here, or its ITs stop running in CI.
+      IT_MODULES: 
hudi-cli,hudi-integ-test,hudi-aws,hudi-azure,packaging/hudi-gcp-bundle

Review Comment:
   IT_MODULES is a hand-maintained allowlist, so a module that gains an IT 
class without being listed here silently stops running its ITs in CI - the 
comment is the only guard against that drift. Could a test like the 
BUNDLE_MODULES one in test-fork-ci-status.cjs compare this list against the 
modules that actually contain IT* test classes and fail on mismatch? follow-up, 
not a blocker.



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to