ci-failure-retrieval

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.

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.

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.

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.

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.

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.