Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vllm-project/ci-fails-buildkite
Fetch and diagnose vLLM Buildkite CI failure logs.
Passed 19 of 21 test cases with the skill, and 5 of 21 without it.
and 14 more in the full report
16 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
If I am in the root directory of the vLLM repository and need to clean an already-downloaded raw log file called raw_ci.log, what script path should I execute?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies executing .buildkite/scripts/ci-clean-log.sh on the target log file. | Missed | Passed |
The instructions your model reads when the skill loads.
Buildkite logs are public; no login needed.
.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.
# All failed jobs in a PR's latest build (current branch's PR if omitted):
.buildkite/scripts/ci-fetch-log.sh --pr <PR>
# All failed jobs in a build (--soft also includes soft-failed jobs;
# --all fetches every finished job):
.buildkite/scripts/ci-fetch-log.sh "https://buildkite.com/vllm/ci/builds/<N>"
# One job — `gh pr checks` URLs (#<job_uuid>) and web UI URLs (?sid=) both
# work; pass "-" as a second argument to stream to stdout:
.buildkite/scripts/ci-fetch-log.sh "https://buildkite.com/vllm/ci/builds/<N>#<job_uuid>"
To clean an already-downloaded log with .buildkite/scripts/ci-clean-log.sh:
./ci-clean-log.sh ci.log
See docs/contributing/ci/failures.md for the full guide: filing CI failure issues, investigating/bisecting, reproducing flaky tests, and daily triage.
test cases passed, vs 5 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.