Skip to content

Conversation

@clee2000
Copy link
Contributor

@clee2000 clee2000 commented Oct 10, 2025

As in title

If you change only one workflow file, lintrunner (default arg, also the one in CI since it only inputs changed files) won't look at other files in the repo, but the sync-tag might come from those other files

This makes it so that it looks at all workflow files so it will catch those failures

Also change output line so it prints which file + which job it is different from

Pros:
catches errors

Cons:
unusual behavior (getting around what lintrunner says the linter should run on)

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 10, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 10, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 9b07e85 with merge base 0977cc4 (image):

NEW FAILURE - The following job has failed:

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

@clee2000 clee2000 marked this pull request as ready for review October 10, 2025 19:08
@clee2000 clee2000 requested a review from a team October 10, 2025 19:08
@clee2000 clee2000 force-pushed the csl/workflow_consistency_linter branch from 58701be to a47fc9a Compare October 22, 2025 16:23
@clee2000
Copy link
Contributor Author

@pytorchbot merge -f "Lint passed"

@pytorchmergebot
Copy link
Collaborator

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

@clee2000
Copy link
Contributor Author

@pytorchbot revert -m "broke lint GH job link HUD commit link" -c nosignal

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchmergebot
Copy link
Collaborator

@clee2000 your PR has been successfully reverted.

@clee2000 clee2000 force-pushed the csl/workflow_consistency_linter branch from a38dbdc to 9b07e85 Compare October 23, 2025 20:35
@clee2000
Copy link
Contributor Author

@pytorchbot merge -f "Lint passed"

@pytorchmergebot
Copy link
Collaborator

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

@github-actions github-actions bot deleted the csl/workflow_consistency_linter branch November 24, 2025 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td Do not run TD on this PR Merged Reverted topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants