ci-failure-retrieval

Retrieve and diagnose CI test failures for TensorRT-LLM pull requests.

2.8k|332|Updated Feb 25, 2026

Search Tags:#automation #debugging #jenkins #ci #pull-request #github-api #test-report

Ready to run

npx skills add https://github.com/NVIDIA/skills --skill ci-failure-retrieval

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-failure-retrieval
Source: https://github.com/NVIDIA/skills/tree/main/skills/TensorRT-LLM/ci-failure-retrieval
Command: npx skills add https://github.com/NVIDIA/skills --skill ci-failure-retrieval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve and diagnose CI test failures from TensorRT-LLM pull requests using the GitHub API and Jenkins testReport API. Use when the user asks about CI failures on a PR, wants to see failed test details, or needs stdout/stderr from a CI run.

Core Features & Use Cases

Retrieve the Jenkins build number by scanning PR comments produced by the CI bot.
Query the Jenkins testReport API to summarize failures (pass/fail/skip) and identify failing test cases.
Retrieve detailed error messages and, if needed, full stdout/stderr for specific failures for deeper debugging.
Provide a consolidated failure overview to accelerate triage and remediation.

Quick Start

Provide a PR number to fetch a failure summary and logs from the Jenkins test reports.

Frequently Asked Questions about ci-failure-retrieval

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

FAQPage Schema

How do I retrieve CI test failures for a TensorRT-LLM pull request?▼

To retrieve CI test failures, provide the PR number to fetch a failure summary and logs from Jenkins test reports. The tool scans PR comments for the Jenkins build number and queries the testReport API to summarize pass, fail, and skip counts.

What is the best way to debug Jenkins CI failures using GitHub API data?▼

Debugging Jenkins CI failures involves scanning GitHub PR comments produced by the CI bot to retrieve the Jenkins build number, then querying the Jenkins testReport API to identify failing test cases and extract detailed error messages.

Can I get stdout and stderr logs from a failing Jenkins CI run?▼

Yes, you can get stdout and stderr logs from a failing Jenkins CI run. The tool queries the Jenkins testReport API to retrieve detailed error messages and, if needed, the full stdout and stderr output for specific failing test cases.

Do I need corporate network access to diagnose TensorRT-LLM CI failures?▼

Yes, you need corporate network access to diagnose TensorRT-LLM CI failures. The tool requires access to the GitHub API and Jenkins testReport API, and specifically requires corporate network access to resolve the internal Jenkins base URL.

How does a CI failure retrieval tool summarize pull request test results?▼

A CI failure retrieval tool summarizes pull request test results by querying the Jenkins testReport API to aggregate pass, fail, and skip metrics. It identifies failing test cases and provides a consolidated failure overview to accelerate triage.

Why are my Jenkins test reports not resolving when diagnosing PR failures?▼

Jenkins test reports may not resolve when diagnosing PR failures because the tool requires corporate network access to resolve the internal Jenkins base URL. Without this access, the Jenkins testReport API cannot be queried for failure data.