hutiefang76 opened a new pull request, #13456: URL: https://github.com/apache/gravitino/pull/13456
### What changes were proposed in this pull request? Allow the first stored status read in `TestJobManagerMultiNode.testCancelJobFromAnotherNode` to be either `CANCELLING` or `CANCELLED`. The later assertions still require the job to reach `CANCELLED` and have `finishedAt > 0`. ### Why are the changes needed? When the cancelled process exits before the owner node reads its status, one pull can already persist `CANCELLED`. The test's strict intermediate `CANCELLING` assertion then fails even though cancellation succeeded. Fix: #13420 ### Does this PR introduce _any_ user-facing change? No. This only corrects a timing assumption in a test. ### How was this patch tested? - Ran `./gradlew :core:test --tests 'org.apache.gravitino.job.TestJobManagerMultiNode' -PskipITs` successfully with JDK 17. - Repeated `./gradlew :core:cleanTest :core:test --tests 'org.apache.gravitino.job.TestJobManagerMultiNode.testCancelJobFromAnotherNode' -PskipITs` three times successfully with JDK 17. - `./gradlew :core:spotlessCheck -PskipITs` passed. The local backend exercised here is H2; PostgreSQL and MySQL CI coverage will validate the same assertion under those backends. -- 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]
