[GH-ISSUE #4749] Nightly build/test failure - 2026-10-18 #1211

New issue

Open

opened 2026-10-29 21:24:00 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-29 21:24:00 +00:00

Owner

Originally created by @github-actions[bot] on GitHub (Oct 18, 2026).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/4749

Nightly Failure Report

Run: https://github.com/kvcache-ai/Mooncake/actions/runs/39048302137
Branch: refs/heads/main
Timestamp: 2026-10-18T16:11:37.462Z

Please investigate the failed jobs in the workflow run linked above.

Originally created by @github-actions[bot] on GitHub (Oct 18, 2026). Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/4749 ## Nightly Failure Report **Run**: https://github.com/kvcache-ai/Mooncake/actions/runs/39048302137 **Branch**: refs/heads/main **Timestamp**: 2026-10-18T16:11:37.462Z Please investigate the failed jobs in the workflow run linked above.

bsakaguchi added the

nightly-failure

label

2026-10-29 21:24:00 +00:00

bsakaguchi commented

2026-10-29 21:24:01 +00:00

Author

Owner

@he-yufeng commented on GitHub (Oct 18, 2026):

Triage on the four failures:

nightly-coverage / nightly-test (Build project): real compile break, already fixed on main. Both legs failed compiling mooncake-store/tests/master_service/dsl/scenario.cpp:1926, which called BatchProbeKey(keys, tenant) in the old two-argument form. The signature gained a leading const GrantLeasePolicy& in 5d77d344 (#4314, landed 10-16 16:17 +08), while the DSL call site came from 7b92ab88 (#4523, landed 10-15 15:54 +08) — a landing-order race between two PRs touching the same API, each green against the main it was tested on. 19e0ab28 (#4729, landed 10-18 02:09 +08) updated the call to BatchProbeKey({}, keys, TenantId(...)), which is the form current main has. So this leg should go green on the next nightly; no further action.

Build Docker Image: infra-level, separate. The job failed with zero failed steps (runner/provisioning level, not a build error), so it is unrelated to the compile break. Worth a rerun-watch on the next nightly rather than a code change.

Nothing to do on this issue beyond the next run confirming both legs recover; the only lasting takeaway is that #4314 and #4523 landed within 25 hours of each other in the same file family, and the second one carried a stale call site.

@he-yufeng commented on GitHub (Oct 18, 2026): Triage on the four failures: **nightly-coverage / nightly-test (Build project): real compile break, already fixed on main.** Both legs failed compiling `mooncake-store/tests/master_service/dsl/scenario.cpp:1926`, which called `BatchProbeKey(keys, tenant)` in the old two-argument form. The signature gained a leading `const GrantLeasePolicy&` in 5d77d344 (#4314, landed 10-16 16:17 +08), while the DSL call site came from 7b92ab88 (#4523, landed 10-15 15:54 +08) — a landing-order race between two PRs touching the same API, each green against the main it was tested on. 19e0ab28 (#4729, landed 10-18 02:09 +08) updated the call to `BatchProbeKey({}, keys, TenantId(...))`, which is the form current main has. So this leg should go green on the next nightly; no further action. **Build Docker Image: infra-level, separate.** The job failed with zero failed steps (runner/provisioning level, not a build error), so it is unrelated to the compile break. Worth a rerun-watch on the next nightly rather than a code change. Nothing to do on this issue beyond the next run confirming both legs recover; the only lasting takeaway is that #4314 and #4523 landed within 25 hours of each other in the same file family, and the second one carried a stale call site.

bsakaguchi referenced this issue

2026-10-29 21:32:36 +00:00

[PR #1211] [MERGED] 【docu】Remove duplicate mooncake store #2076