Index of every page on this site: llms.txt
All skills
vllm-project avatar

/ci-fails-buildkite

@f8b29fa
by vLLMvllm-project/vllm97k stars
25,082
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/vllm-project/vllm/ci-fails-buildkite

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈51 tokens for metadata: the name and description. ≈291 when used: this file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈205 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Diagnosing vLLM Buildkite CI Failures

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.

Fetching logs

# 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

Reference

See docs/contributing/ci/failures.md for the full guide: filing CI failure issues, investigating/bisecting, reproducing flaky tests, and daily triage.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    This skill facilitates fetching and cleaning CI failure logs from Buildkite using internal project scripts. It is intended for project maintenance and debugging within the vLLM project ecosystem.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: MEDIUM · 1 issue

Signed by skilld at f8b29fa. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 1 hour ago.

Activeupdated 5 months ago

README badge

README badge for vllm-project/vllm/ci-fails-buildkite