skills.rest
sgl-project
sgl-projectOFFICIAL
Explore all skills by this author →
GitHub

SGLang Bisect CI Regression

Bisect CI run history to identify commits introducing test regressions.

31.6k|7.8k|Updated Jan 8, 2024
Search Tags:#debugging#troubleshooting#github actions#regression#git bisect#ci
One-click install
npx skills add https://github.com/sgl-project/sglang --skill sglang-bisect-ci-regression-sgl-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SGLang Bisect CI Regression
Source: https://github.com/sgl-project/sglang/tree/main/.claude/skills/sglang-bisect-ci-regression
Command: npx skills add https://github.com/sgl-project/sglang --skill sglang-bisect-ci-regression-sgl-project

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying the root cause of consistently failing CI tests, whether it's a code regression, a hardware issue, or an environment change.

Core Features & Use Cases

  • Automated Bisection: Pinpoints the exact commit that introduced a regression by analyzing CI run history.
  • Failure Signature Extraction: Gathers detailed error messages and test context from CI logs.
  • Hardware/Runner Analysis: Differentiates between code bugs and environment-specific issues.
  • Optional Remote Reproduction: Can reproduce failures on a specified remote GPU server.
  • Use Case: A critical test in your CI pipeline starts failing intermittently. Use this Skill to automatically trace back through the commit history and CI logs to find the exact PR that caused the failure, saving hours of manual debugging.

Quick Start

Use the sglang-bisect-ci-regression skill to investigate the failing test 'test_lora_tp.py' in the CI.

Frequently Asked Questions about SGLang Bisect CI Regression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the commit that introduced a regression in GitHub Actions CI?▼

To find a CI regression commit, use automated temporal bisection on scheduled CI runs to analyze run history and pinpoint the exact commit that introduced the failure.

How do I extract failure signatures from failing CI tests?▼

You can extract failure signatures from failing CI tests by gathering detailed error messages and test context directly from CI logs, which helps identify whether the issue is a code regression or hardware-specific.

Does this automated bisection differentiate between code bugs and hardware issues?▼

Yes, the automated bisection performs hardware and runner analysis to differentiate between code regressions and environment-specific issues, ensuring you target the actual root cause of the CI failure.

Can I reproduce CI test failures on a remote GPU server?▼

You can reproduce CI test failures on a remote GPU server by using optional remote reproduction capabilities via SSH and Docker to validate environment-specific issues outside the CI pipeline.

When should I use temporal bisection for troubleshooting CI regressions?▼

You should use temporal bisection for troubleshooting CI regressions when a consistently failing test appears in scheduled runs and you need to automatically trace back through commit history to find the root cause.

Related Skills

Explore More Software Engineering Skills→
ESO-ToolkitESO-Toolkit
2

github-actions-logs

Parse GitHub Actions workflow logs to diagnose CI/CD failures.

Official
Intermediate
moirai-internalmoirai-internal

SGLang Bisect CI Regression

Bisect SGLang CI logs to identify regression-introducing commits.

Official
Advanced
robit-manrobit-man

regression-bisect

Automate git bisect to identify the commit that introduced a regression.

Community
Advanced
starwardsstarwards
42

starwards-ci-debugging

Diagnose Starwards GitHub Actions CI failures from downloaded logs.

Official
Intermediate