fix(plan): move parent FK update actions to MULTI_UPDATE - #26442
Merged
Mergify / Mergify Merge Queue
completed
Aug 3, 2026 in 28m 42s
Dequeued — checks failed
- ✅ Entered queue —
2026-08-03 10:53 UTC· Rule:main· triggered by ruleAutomatic queue on approval for main - ❌ Checks failed · in-place
- 🚫 Left the queue —
2026-08-03 11:22 UTC· atb45ac19e6cd63a3531cfea90d0aefcc0a384490f
This pull request spent 28 minutes 41 seconds in the queue, with no time running CI.
Waiting for
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-skipped = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-success = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone CI / UT Test on Ubuntu/x86 -
check-skipped = Matrixone CI / UT Test on Ubuntu/x86 -
check-success = Matrixone CI / UT Test on Ubuntu/x86
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone CI / SCA Test on Linux/arm64 -
check-skipped = Matrixone CI / SCA Test on Linux/arm64 -
check-success = Matrixone CI / SCA Test on Linux/arm64
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Utils CI / Coverage -
check-skipped = Matrixone Utils CI / Coverage -
check-success = Matrixone Utils CI / Coverage
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
-
All conditions
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-skipped = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-success = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone CI / UT Test on Ubuntu/x86 -
check-skipped = Matrixone CI / UT Test on Ubuntu/x86 -
check-success = Matrixone CI / UT Test on Ubuntu/x86
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone CI / SCA Test on Linux/arm64 -
check-skipped = Matrixone CI / SCA Test on Linux/arm64 -
check-success = Matrixone CI / SCA Test on Linux/arm64
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Utils CI / Coverage -
check-skipped = Matrixone Utils CI / Coverage -
check-success = Matrixone Utils CI / Coverage
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
-
#review-threads-unresolved = 0[🛡 GitHub branch protection]github-review-approved[🛡 GitHub branch protection]
Reason
The merge conditions cannot be satisfied due to failing checks
Failing checks:
- 🟠 Matrixone CI / SCA Test on Linux/arm64 (job log)
- 🟠 Matrixone CI / UT Test on Ubuntu/x86 (job log)
- 🟠 Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) (job log)
- 🟠 Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) (job log)
- 🟠 Matrixone UT Coverage / UT Coverage on Ubuntu/x86 (job log)
Hint
You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.
Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).
- Requeue this pull request
Loading