CryoThrust commented on PR #12156:
URL: https://github.com/apache/seatunnel/pull/12156#issuecomment-6136975273

   Synced with `dev` at `b3898b62d`. The conflict was only the imports in 
`StateTransitionCleanupTest`; both `JobMaster` from this PR and 
`TaskExecutionState` used by the new upstream tests are retained.
   
   JDK 11 verification after the sync:
   - `StateTransitionCleanupTest`: 13 passed, including the upstream 
late-terminal-state cases.
   - `JobStatusTest`: 2 passed.
   - Module Spotless and `-DskipTests verify`: passed. UI build was skipped for 
this backend-only check.
   
   On F1/F3: `cancelJob()` uses its captured `jobStatus` local, with 
`testCancelJobCommitsToTheJobStatusSnapshotItValidated`, the 
not-started/running decision tests, and the explicitly documented 
cleared-status regression. F4 now has the constant Javadoc and the duplicate 
call-site comments are removed.
   
   F2 is still a separate concurrency change tracked in #12342; the static 
outcome tests do not prove the interleaving safe. This sync does not claim to 
resolve that race. The reason for keeping it separate is the monitor/lock-order 
change needed in `cancelJob()` and `stopJob()`, rather than the enum 
classification this PR changes.
   
   The push triggers fresh CI; I will use its exact-head result rather than 
carrying forward the previous run's breakdown.
   


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