Skip to content

Conversation

izaitsevfb
Copy link
Contributor

  1. adds a filter to hide non-viable strict jobs:
    image

  2. in grouped view makes the border more obvious / adds tooltip info:
    image
    image

  3. syncs the viable-strict logic with the source (per the comment in the original implementation)
    Note: we really need to centralize the config for viable/strict, but that's out of the scope of this PR.

@izaitsevfb izaitsevfb requested a review from clee2000 October 14, 2025 23:56
@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 14, 2025
Copy link

vercel bot commented Oct 14, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
torchci Ready Ready Preview Oct 14, 2025 11:56pm

Copy link
Member

@seemethere seemethere left a comment

Choose a reason for hiding this comment

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

LGTM, we should definitely do a follow-up where we can make this something that isn't hardcoded and we can make configurable per repo.


// Source of truth for these jobs is in https://github.com/pytorch/pytorch/blob/main/.github/workflows/update-viablestrict.yml#L26
export const VIABLE_STRICT_BLOCKING_JOBS: RepoViableStrictBlockingJobsMap = {
"pytorch/pytorch": [/pull/i, /trunk/i, /lint/i, /linux-aarch64/i],
Copy link
Member

Choose a reason for hiding this comment

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

This might be hard to maintain.

I'm curious if we can have this be populated somewhere in clickhouse and we can just pull it from there.

It's fine for a first pass but we should make a TODO / issue about revising it to do the right thing

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I totally agree, but it was hardcoded this way before this PR, I just moved it to the different file.

@izaitsevfb izaitsevfb merged commit 543c82c into main Oct 15, 2025
5 checks passed
@izaitsevfb izaitsevfb deleted the hud-add-viable-strict-filter branch October 15, 2025 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants