davidzollo opened a new pull request, #11097:
URL: https://github.com/apache/seatunnel/pull/11097

   ## Summary
   - move the dedicated long-running connector suites into shared workflow 
configuration so shards 1..7 and part-8 stay aligned
   - replace fixed sleeps in ClusterFailureNoRestoreIT with job-metrics-based 
progress checks
   - reuse shared timeout constants and schema-assert timeout settings in the 
affected E2E and engine tests
   
   ## Validation
   - ./mvnw spotless:apply -nsu -Dmaven.gitcommitid.skip=true -T 3C
   - ./mvnw help:evaluate -Dexpression=project.modules -q -DforceStdout -pl 
:seatunnel-connector-v2-e2e -nsu -Dmaven.gitcommitid.skip=true, then python3 
tools/update_modules_check/update_modules_check.py sub_it_module ... to verify 
shards 1..7 exclude connector-iceberg-e2e and connector-hbase-e2e while part-8 
keeps only those two suites
   - ./mvnw -pl 
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-ddl
 -DskipTests -DfailIfNoTests=false test-compile -nsu 
-Dmaven.gitcommitid.skip=true -T 3C
   
   ## Validation Notes
   - local script validation used python3 because this workstation's default 
python is Python 2, while the GitHub Actions runners use Python 3 for the same 
helper invocation
   - ./mvnw -pl seatunnel-e2e/seatunnel-engine-e2e/connector-seatunnel-e2e-base 
-DskipTests -DfailIfNoTests=false test-compile -nsu 
-Dmaven.gitcommitid.skip=true -T 3C is still blocked by a pre-existing compile 
failure in LocalModeIT (SeaTunnelClient#getHealthMetrics(String) missing)
   - ./mvnw -pl seatunnel-engine/seatunnel-engine-server 
-Dtest=CheckpointErrorRestoreEndTest,JobStateEventTest -DfailIfNoTests=false 
test -nsu -Dmaven.gitcommitid.skip=true -T 3C is still blocked by pre-existing 
compile failures in unrelated seatunnel-engine-server sources on this branch
   


-- 
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