Skip to content

chore(db): purge run 34512984806 — GB300 DSv4.1 Flash vLLM server got 1 CPU core / 清除 run 34512984806：GB300 vLLM server 仅分配 1 个 CPU 核心 #1121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
functionstackx merged 1 commit into from
Sep 11, 2026
Merged

chore(db): purge run 34512984806 — GB300 DSv4.1 Flash vLLM server got 1 CPU core / 清除 run 34512984806：GB300 vLLM server 仅分配 1 个 CPU 核心 #1121

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions packages/db/src/etl/run-overrides.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,7 @@ export const PURGED_RUNS: ReadonlySet<number> = new Set([
30405836523, // 2026-07-28 | Reason: No non-DSpark — kimik3-fp4-b300-vllm-agentic AgentX points run without speculative decoding, and Kimi-K3 agentic coding is published DSpark-only (source run of the PR #2397 sweep-reuse ingest)
32695861783, // 2026-08-24 | Reason: dev image — the dsv4-fp4-b300-sglang-agentic-hicache-mtp AgentX sweep ran on lmsysorg/sglang-staging:dev-cu13-pr-35880, built from the unmerged SGLang draft PR sgl-project/sglang#35880 (source run of the PR #2701 sweep-reuse ingest)
32863999669, // 2026-08-25 | Reason: incomplete failing run — Run Sweep on main for #2687 ([Power] Require GB multinode telemetry) failed 30 of 125 jobs (GB200/GB300 multi-node dyn-sgl arms), leaving partial data
34512984806, // 2026-09-10 | Reason: wrong results — the dsv41flash-fp4-gb300-vllm-agentic-dspark AgentX sweep for PR #2961 launched the vLLM server via srun without --cpus-per-task, and the GB300 Slurm cluster default allocated only 1 CPU core to the entire vLLM server, crippling throughput; infra launch bug on our side, not a vLLM or NVIDIA recipe issue. Fixed by #3017 (--cpus-per-task=144); results to be re-run
]);

export const PURGED_RUN_ATTEMPTS: ReadonlyMap<number, ReadonlySet<number>> = new Map([
Expand Down
Loading