DanielLeens commented on PR #12311: URL: https://github.com/apache/seatunnel/pull/12311#issuecomment-6033681452
Thanks @SEZ9. The comment was not cut off on my side; the matrix is the one in `CoordinatorServiceLostMemberResolutionTest` on `f85d43600df`, spelled out here: | Job status | `CANCELING` vertex | `DEPLOYING` vertex | `RUNNING` vertex | |---|---|---|---| | `CANCELING` | `CANCELED` | `CANCELED` | `CANCELED` | | any other `JobStatus` (e.g. `RUNNING`, `FAILING`, `FAILED`; iterated over the complement of `CANCELING`) | `FAILED` | `FAILED` | `FAILED` | | missing (`null`) | `FAILED` | `FAILED` | `FAILED` | Skipped states: every vertex state other than those three (`CREATED`, `SCHEDULED`, `INITIALIZING`, `CANCELED`, `FAILED`, `FINISHED`, and so on) returns `Optional.empty()` for every `JobStatus`, and a `null` vertex state returns empty too. The tests are `cancelingVertexOfUserCancelledJobResolvesToCanceled`, `notYetCancelledVerticesOfUserCancelledJobResolveToCanceled`, `engineInitiatedCancelStillResolvesToFailed` (the negative case you asked about), `deployingAndRunningVerticesStillResolveToFailed` and `otherStatesAreLeftUntouched`. CI status, so there is no ambiguity: fork run 37337325279 on this head did not run any tests. Its `Dead links` job failed on HTTP 429 from `deepwiki.com` (README badge links), and every test job was skipped behind that gate. So there is currently no test result for this head, including `SplitClusterFaultToleranceIT`. A rerun would hit the same 429 (I checked just now, deepwiki still answers 429); the fix is #12639, which is open and waiting for review. I will re-run this head once that lands and post the result here. -- 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]
