Skip to content

Conversation

@albanD
Copy link
Collaborator

@albanD albanD commented Oct 16, 2022

Stack from ghstack (oldest at bottom):

Waiting for test run to see if this backward is actually exercised.
If not, I will add test before merging.

Test updated. Ready to go now.

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 16, 2022

🔗 Helpful Links

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

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

✅ No Failures, 6 Pending

As of commit 922cbc1:
💚 Looks good so far! There are no failures yet. 💚

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

Copy link
Contributor

@ezyang ezyang left a comment

Choose a reason for hiding this comment

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

Lf xfail removal

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 16, 2022
@albanD albanD changed the title conv backward impl [WI] conv backward impl Oct 16, 2022
@albanD albanD changed the title [WI] conv backward impl [WIP] conv backward impl Oct 16, 2022
~~Waiting for test run to see if this backward is actually exercised.
If not, I will add test before merging.~~
Test updated. Ready to go now.

[ghstack-poisoned]
@albanD albanD changed the title [WIP] conv backward impl conv backward impl Oct 16, 2022
~~Waiting for test run to see if this backward is actually exercised.
If not, I will add test before merging.~~
Test updated. Ready to go now.

[ghstack-poisoned]
@albanD
Copy link
Collaborator Author

albanD commented Oct 17, 2022

@pytorchbot merge -g

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (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

@github-actions
Copy link
Contributor

Hey @albanD.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

Rick0317 pushed a commit to Rick0317/pytorch that referenced this pull request Oct 18, 2022
ghstack-source-id: 1239ce6
Pull Request resolved: pytorch/pytorch#87047
@facebook-github-bot facebook-github-bot deleted the gh/albanD/108/head branch June 8, 2023 15:08
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 Merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants