Skip to content

[Utils] Add ci_results script#1303

Merged
bogner merged 5 commits into
llvm:mainfrom
bogner:2026-06-10-ci-results
Jun 15, 2026
Merged

[Utils] Add ci_results script#1303
bogner merged 5 commits into
llvm:mainfrom
bogner:2026-06-10-ci-results

Conversation

@bogner

@bogner bogner commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Adds a script that can help inspecting and root cause CI results. We provide two commands, current-status and failure-range. The first summarizes the results from the most recent run on all CI bots, and the second helps bisect where a particular test started failing.

This all works by using the gh tool to look at the logs from github workflow runs, with some smarts that have to do with how our runs are set up.

Fixes #1300

@bogner bogner requested a review from bob80905 June 11, 2026 01:57
@bogner

bogner commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Some example output for current-status

$ py utils/ci_status.py current-status windows-nvidia-clang-d3d12.yaml windows-amd-dxc-warp-d3d12.yaml
## windows-nvidia-clang-d3d12.yaml (success)
 - Name: Windows D3D12 NVIDIA Clang
 - Timestamp: 2026-06-11T00:37:07Z
 - llvm/llvm-project: 3c7cea8273bd06fdd9f84197293fb3d7f4b94435
 - llvm/offload-test-suite: 0d3cc83a8c3570c11026aac1440c50726a671e5a

## windows-amd-dxc-warp-d3d12.yaml (failure)
 - Name: Windows D3D12 Warp DXC
 - Timestamp: 2026-06-11T01:04:45Z
 - Microsoft/DirectXShaderCompiler: c207c7b793957f2d288cb7448516c62808624f71
 - Microsoft/DirectXShaderCompiler range: d6e0ca4a0c25..c207c7b79395
 - llvm/offload-test-suite: 0d3cc83a8c3570c11026aac1440c50726a671e5a
 - llvm/offload-test-suite range: 8c4720026b98..0d3cc83a8c35

FAIL: Feature/CBuffer/vectors-16bit.test
FAIL: Feature/HLSLLib/firstbithigh.64.test
FAIL: Feature/HLSLLib/mad.fp64.test
FAIL: Feature/CBuffer/scalars-16bit.test
FAIL: Feature/CBuffer/arrays-16bit.test
FAIL: Feature/StructuredBuffer/inc_counter_array.test
FAIL: Feature/HLSLLib/mul.int16.test
FAIL: WaveOps/WaveActiveMax.test
FAIL: Feature/HLSLLib/transpose.int16.test
FAIL: Feature/HLSLLib/mul.fp16.test
FAIL: Feature/HLSLLib/transpose.fp16.test

Similarly, for failure-range:

$ py ./utils/ci_results.py failure-range windows-amd-clang-warp-d3d12.yaml  WaveOps/WaveActiveSum.fp32.test
0 - Run 27349293055 (llvm/llvm-project: 6ff34e926827, test-suite: f788760c7f74): FAIL
1 - Run 27331413794 (llvm/llvm-project: 63e33c6aeed2, test-suite: f788760c7f74): FAIL
3 - Run 27298544113 (llvm/llvm-project: 8d2510ecde24, test-suite: 0d3cc83a8c35): FAIL
7 - Run 27227869184 (llvm/llvm-project: 2b9a8e2d76e1, test-suite: 10ae425589a5): FAIL
15 - Run 27092602665 (llvm/llvm-project: 7df3d9277973, test-suite: bc20b5c4b5ca): PASS
11 - Run 27140683630 (llvm/llvm-project: 5b6236c37658, test-suite: 93b8925e2e89): PASS
9 - Run 27175942016 (llvm/llvm-project: dd87edd1f48b, test-suite: 9bc0142643ef): FAIL
10 - Run 27159468306 (llvm/llvm-project: 3136d62938e8, test-suite: 8c4720026b98): PASS

llvm/llvm-project range: 3136d62938e8..dd87edd1f48b
test suite range: 8c4720026b98..9bc0142643ef

edit: Updated output 2026-06-11 11:18 AM PDT

@bob80905

Copy link
Copy Markdown
Contributor

Looks nice.
I would think for failure_range, we would only need to print the range for 1 of the 2 compilers, since we must specify a specific workflow right?

@bob80905

Copy link
Copy Markdown
Contributor

Consider adding issue #1300 to the description.

bogner added 2 commits June 11, 2026 10:33
Adds a script that can help inspecting and root cause CI results. We
provide two commands, `current-status` and `failure-range`. The first
summarizes the results from the most recent run on all CI bots, and the
second helps bisect where a particular test started failing.

This all works by using the `gh` tool to look at the logs from github
workflow runs, with some smarts that have to do with how our runs are
set up.
@bogner bogner force-pushed the 2026-06-10-ci-results branch from 4d228a5 to b71a6ba Compare June 11, 2026 18:18
@bogner

bogner commented Jun 11, 2026

Copy link
Copy Markdown
Contributor Author

Looks nice. I would think for failure_range, we would only need to print the range for 1 of the 2 compilers, since we must specify a specific workflow right?

Good point. I've updated accordingly

bogner added 3 commits June 15, 2026 11:53
It seems the code formatter we have in pre-commit CI can't handle
f-strings properly...
@bogner bogner merged commit 37f3e30 into llvm:main Jun 15, 2026
9 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Track XFails across the repo effectively

3 participants