Updates reference to _runner-determinator.yml workflow, from current version to main version.

[jeanschmidt]

Updates all references to runner determinator workflow (_runner-determinator.yml) from current cloned version to main version.

This enables the team to push updates to this workflow, like fixing bugs or pushing improvements, and have it immediately be reflected on all open PRs. So avoiding potentially breaking situations, empowering moving fast and fast and simple recover in case of bugs.

From:

jobs:
  get-label-type:
    uses: ./.github/workflows/_runner-determinator.yml

To:

jobs:
  get-label-type:
    uses: pytorch/pytorch/.github/workflows/_runner-determinator.yml@main

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137791

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❌ 7 New Failures

As of commit 0e19f23 with merge base b82000c ():

NEW FAILURES - The following jobs have failed:

• Build Official Docker Images / validate / cuda11.8-cudnn9-devel / cuda11.8-cudnn9-devel (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cuda11.8-cudnn9-runtime / cuda11.8-cudnn9-runtime (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cuda12.1-cudnn9-devel / cuda12.1-cudnn9-devel (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cuda12.1-cudnn9-runtime / cuda12.1-cudnn9-runtime (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cuda12.4-cudnn9-devel / cuda12.4-cudnn9-devel (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cuda12.4-cudnn9-runtime / cuda12.4-cudnn9-runtime (gh)
  Error response from daemon: manifest unknown
• Build Official Docker Images / validate / cudacpu-cudnn-runtime / cudacpu-cudnn-runtime (gh)
  Error response from daemon: manifest unknown

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[malfet]

Wouldn't it prevent people from being able to test any changes to this workflow on the pull request?

[huydhn]

LGTM! I wonder why we don't move this to test-infra, but this probably makes more sense as this is a PyTorch-only thing. If we need some tests here, we need to write a test workflow like https://github.com/pytorch/test-infra/blob/main/.github/workflows/test-setup-nvidia.yml that calls the GHA from PR head.

[zxiiro]

Wouldn't it prevent people from being able to test any changes to this workflow on the pull request?

Yes. The workaround would be they update their PR to use the local version for testing but then runs the risk of folks needing to remember to remove that from their workflow before approving and merging.

[zxiiro]

Seems reasonable to me.

[jeanschmidt]

@pytorchbot merge -i

[pytorchmergebot]

Merge failed

Reason: 1 mandatory check(s) are pending/not yet run. The first few are:

• EasyCLA

Dig deeper by viewing the pending checks on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[jeanschmidt]

@pytorchbot merge -f "easycla job does not exist"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[pytorchmergebot]

Merge failed

Reason: 1 mandatory check(s) are pending/not yet run. The first few are:

• EasyCLA

Dig deeper by viewing the pending checks on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[jeanschmidt]

@pytorchbot rebase

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[pytorchmergebot]

Successfully rebased jeanschmidt/runner_determinator_from_main onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout jeanschmidt/runner_determinator_from_main && git pull --rebase)

[huydhn]

@pytorchbot merge -f 'CI only changes, runner determinator and lint jobs have passed'

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[zxiiro]

"easycla job does not exist"

EasyCLA job does exist and I've seen it pass in other PRs. Its a job managed by the LF for all open source projects. I wonder why its missing here but we shouldn't ignore it.