main
md 35 lines 1.36 KB
Rendered Raw
1 ---
2 name: ci-fails-buildkite
3 description: Fetch and diagnose vLLM Buildkite CI failure logs. Use when investigating failing CI jobs on a PR or build, when the user pastes a buildkite.com URL, or asks to fetch/diagnose CI logs.
4 ---
5
6 # Diagnosing vLLM Buildkite CI Failures
7
8 Buildkite logs are public; no login needed.
9
10 `.buildkite/scripts/ci-fetch-log.sh` saves each log as `ci-<build>-<job-name>.log`, stripped of timestamps and ANSI codes. Existing files are kept; set `CI_FETCH_LOG_FORCE=1` to refetch.
11
12 ## Fetching logs
13
14 ```bash
15 # All failed jobs in a PR's latest build (current branch's PR if omitted):
16 .buildkite/scripts/ci-fetch-log.sh --pr <PR>
17
18 # All failed jobs in a build (--soft also includes soft-failed jobs;
19 # --all fetches every finished job):
20 .buildkite/scripts/ci-fetch-log.sh "https://buildkite.com/vllm/ci/builds/<N>"
21
22 # One job — `gh pr checks` URLs (#<job_uuid>) and web UI URLs (?sid=) both
23 # work; pass "-" as a second argument to stream to stdout:
24 .buildkite/scripts/ci-fetch-log.sh "https://buildkite.com/vllm/ci/builds/<N>#<job_uuid>"
25 ```
26
27 To clean an already-downloaded log with `.buildkite/scripts/ci-clean-log.sh`:
28
29 ```bash
30 ./ci-clean-log.sh ci.log
31 ```
32
33 ## Reference
34
35 See [docs/contributing/ci/failures.md](../../../docs/contributing/ci/failures.md) for the full guide: filing CI failure issues, investigating/bisecting, reproducing flaky tests, and daily triage.