Skip to content

Add runner status script#1185

Merged
bob80905 merged 7 commits into
llvm:mainfrom
bob80905:add_runnerstatus_script
May 28, 2026
Merged

Add runner status script#1185
bob80905 merged 7 commits into
llvm:mainfrom
bob80905:add_runnerstatus_script

Conversation

@bob80905

@bob80905 bob80905 commented May 13, 2026 •
edited by alsepkow
Loading

Copy link
Copy Markdown
Contributor

This script is handy for looking at the workload of the machines for the offload test suite.
It might be especially helpful in the near future, when the split build/test feature is commonplace.
Presently, it displays which jobs are being allocated (Donev, Active, Queued) to which machine SKUs.
It should, in the future, display "build job" and "test job" allocations, for greater clarity.
It accepts one optional argument, to scope the output to a specific SKU, but leave it empty to get status on all SKUs.

For example, here's the output of this command:
image

Fixes #1227
Assisted by Github Copilot

damyanp
damyanp reviewed May 13, 2026
View reviewed changes
Comment thread tools/runner_status.py Outdated
@damyanp

damyanp commented May 13, 2026

Copy link
Copy Markdown
Contributor

The PR description needs to be updated to match the new usage.

@damyanp

damyanp commented May 13, 2026

Copy link
Copy Markdown
Contributor

While this LGTM, a couple of questions:

  • I'm not sure of the right bar for helper scripts like this
  • Is "tools" the right location for it? Would somewhere under .github be better?

@bob80905

bob80905 commented May 13, 2026

Copy link
Copy Markdown
Contributor Author

While this LGTM, a couple of questions:

  • I'm not sure of the right bar for helper scripts like this
  • Is "tools" the right location for it? Would somewhere under .github be better?

Sure, I think .github would be better.
Not sure what the bar is either, but I've had this script laying around for a while and have used it pretty frequently myself.
I imagine it'd be useful for folks to know how loaded a machine is, to estimate when their PR's workflows will be done, or to know if the machine that is still pending is being bogged down by scheduled workflows.
Might also somewhat inform us of which machines are slower / could use an additional SKU.
But in my opinion, the best use case for me is to see which machine takes the "build job" for a specific PR, it might be useful data to make sure build jobs are being well distributed.

alsepkow
alsepkow approved these changes May 28, 2026
View reviewed changes

@alsepkow alsepkow left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTUS @inbelic @Icohedron

Image

@bob80905 bob80905 merged commit a2e657a into llvm:main May 28, 2026
26 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@damyanp damyanp damyanp left review comments
@alsepkow alsepkow alsepkow approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Quality of Life] Make an easier way to track runner status

4 participants

@bob80905 @damyanp @alsepkow @bogner