Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Format all headers under ATen/cpu/vec, not just top-level #152364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: gh/swolchok/755/base
Choose a base branch
from

Conversation

swolchok
Copy link
Contributor

@swolchok swolchok commented Apr 28, 2025

Stack from ghstack (oldest at bottom):

not formatting these seems like an oversight. Had to add a few clang-format suppressions to keep includes in the same order to avoid breaking builds.

This PR was generated using lintrunner --paths-cmd "rg --files -g '*.h' aten/src/ATen/cpu/vec/" format

Differential Revision: D73802128

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @jerryzh168 @albanD

not formatting these seems like an oversight. Had to add a few clang-format suppressions to keep includes in the same order to avoid breaking builds.

Differential Revision: [D73802128](https://our.internmc.facebook.com/intern/diff/D73802128/)

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Apr 28, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 New Failure, 12 Unrelated Failures

As of commit 75fb26c with merge base fa6f9eb (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@pytorch-bot pytorch-bot bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Apr 28, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D73802128

@swolchok
Copy link
Contributor Author

@albanD / @seemethere I'm getting yelled at by pr-sanity-checks, which says this PR is too long and I should contact you

Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

Assuming it's a change generated by the tool, LGTM

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Apr 28, 2025
@swolchok
Copy link
Contributor Author

Assuming it's a change generated by the tool, LGTM

it's generated except for the two small uses of clang-format off/on

@albanD
Copy link
Collaborator

albanD commented Apr 29, 2025

Please share the command used to generate the diff so we can skip the pr-sanity-check !

@swolchok
Copy link
Contributor Author

swolchok commented Apr 29, 2025

Please share the command used to generate the diff so we can skip the pr-sanity-check !

lintrunner --paths-cmd "rg --files -g '*.h' aten/src/ATen/cpu/vec/" format

not formatting these seems like an oversight. Had to add a few clang-format suppressions to keep includes in the same order to avoid breaking builds.

Differential Revision: [D73802128](https://our.internmc.facebook.com/intern/diff/D73802128/)

cc jgong5 mingfeima XiaobingSuper sanchitintel ashokei jingxu10 jerryzh168

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D73802128

not formatting these seems like an oversight. Had to add a few clang-format suppressions to keep includes in the same order to avoid breaking builds.

Differential Revision: [D73802128](https://our.internmc.facebook.com/intern/diff/D73802128/)

cc jgong5 mingfeima XiaobingSuper sanchitintel ashokei jingxu10 jerryzh168

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D73802128

@swolchok
Copy link
Contributor Author

swolchok commented May 5, 2025

@albanD can you please advise on the process for bypassing pr-sanity-checks for this PR? (I understand I will need to rebase, but I don't know how we expect to proceed after that)

@albanD
Copy link
Collaborator

albanD commented May 6, 2025

Added the repro command to the PR description and appropriate label. Should be all good now !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request fb-exported module: cpu CPU specific problem (e.g., perf, algorithm) skip-pr-sanity-checks topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants