KEMBAR78
Add pad and narrow to torch/csrc/stable/ops.h by mikaylagawarecki · Pull Request #159328 · pytorch/pytorch · GitHub
Skip to content

Conversation

@mikaylagawarecki
Copy link
Contributor

@mikaylagawarecki mikaylagawarecki commented Jul 29, 2025

@pytorch-bot
Copy link

pytorch-bot bot commented Jul 29, 2025

🔗 Helpful Links

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

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

⏳ No Failures, 1 Pending

As of commit 4894a25 with merge base f33ce40 (image):
💚 Looks good so far! There are no failures yet. 💚

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

mikaylagawarecki added a commit that referenced this pull request Jul 29, 2025
ghstack-source-id: cdf805c
Pull Request resolved: #159328
mikaylagawarecki added a commit that referenced this pull request Jul 29, 2025
ghstack-source-id: ef932ee
Pull Request resolved: #159328
@github-actions
Copy link
Contributor

Attention! PyTorch one of the C-stable API file was changed

You MUST NOT change existing function declarations in this, as this header defines a stable C ABI. If you need to change the signature for a function, introduce a new v2 version of the function and modify code generation to target the new version of the function.


Caused by:

mikaylagawarecki added a commit that referenced this pull request Aug 4, 2025
ghstack-source-id: b6940ad
Pull Request resolved: #159328
@mikaylagawarecki mikaylagawarecki marked this pull request as ready for review August 4, 2025 21:18
// (2) SymInt is not yet header-only
inline Tensor pad(
const Tensor& self,
std::vector<int64_t> pad,
Copy link
Contributor Author

@mikaylagawarecki mikaylagawarecki Aug 4, 2025

Choose a reason for hiding this comment

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

Do we want to wait for IntArrayRef before merging this?

Copy link
Contributor

Choose a reason for hiding this comment

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

naw i'm happy with this. We can overload this anyway in the future.

mikaylagawarecki added a commit that referenced this pull request Aug 8, 2025
ghstack-source-id: e1a4b92
Pull Request resolved: #159328
mikaylagawarecki added a commit that referenced this pull request Aug 11, 2025
ghstack-source-id: 1155d44
Pull Request resolved: #159328
mikaylagawarecki added a commit that referenced this pull request Aug 11, 2025
ghstack-source-id: b6b6c42
Pull Request resolved: #159328
@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge

@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge -r

@pytorchmergebot
Copy link
Collaborator

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

[ghstack-poisoned]
pytorchmergebot pushed a commit that referenced this pull request Aug 12, 2025
ghstack-source-id: 32511ee
Pull Request resolved: #159328
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/mikaylagawarecki/329/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/159328)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 0 checks:

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
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@mikaylagawarecki
Copy link
Contributor Author

test_jit failure is flaky link, no idea why it can't be ignored by merge -i so gonna merge -f

@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge -f

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 12, 2025

❌ 🤖 pytorchbot command failed:

@pytorchbot merge: error: argument -f/--force: expected one argument

usage: @pytorchbot merge [-f MESSAGE | -i] [-ic] [-r [{viable/strict,main}]]

Try @pytorchbot --help for more info.

@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge -f "test_jit failure is flaky link, no idea why it can't be ignored by merge -i"

@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

chuanhaozhuge pushed a commit that referenced this pull request Aug 14, 2025
chuanhaozhuge pushed a commit that referenced this pull request Aug 18, 2025
can-gaa-hou pushed a commit to can-gaa-hou/pytorch that referenced this pull request Aug 22, 2025
@github-actions github-actions bot deleted the gh/mikaylagawarecki/329/head branch September 12, 2025 02:08
markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants