Skip to content

Revert "[Dynamo][autograd.Function] Trace fwd graph under no_grad mode (#134872)"#137891

Closed
zou3519 wants to merge 2 commits intogh/zou3519/1079/basefrom
gh/zou3519/1079/head
Closed

Revert "[Dynamo][autograd.Function] Trace fwd graph under no_grad mode (#134872)"#137891
zou3519 wants to merge 2 commits intogh/zou3519/1079/basefrom
gh/zou3519/1079/head

Conversation

@zou3519
Copy link
Contributor

@zou3519 zou3519 commented Oct 14, 2024

Stack from ghstack (oldest at bottom):

This reverts commit e688b78.

We're reverting this because:

  1. The original PR ([Dynamo][autograd.Function] Trace fwd graph under no_grad mode #134872) fixed a bug but caused another one. The
    assessment is that the bug it caused is worse than the bug it fixed.
  2. it was reverted on the release 2.5 branch, so we want to prevent
    divergence
  3. The original author is out-of-office for a while so we don't want the
    divergence to wait until they're back

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames @rec

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 14, 2024

🔗 Helpful Links

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

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

❌ 1 New Failure, 2 Unrelated Failures

As of commit 33ba0d3 with merge base 41977a0 (image):

NEW FAILURE - The following job has failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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

…no_grad mode (#134872)""

This reverts commit e688b78.

We're reverting this because:
1) The original PR (#134872) fixed a bug but caused another one. The
   assessment is that the bug it caused is worse than the bug it fixed.
2) it was reverted on the release 2.5 branch, so we want to prevent
   divergence
3) The original author is out-of-office for a while so we don't want the
   divergence to wait until they're back

[ghstack-poisoned]
zou3519 added a commit that referenced this pull request Oct 14, 2024
#134872)"

This reverts commit e688b78.

We're reverting this because:
1) The original PR (#134872) fixed a bug but caused another one. The
   assessment is that the bug it caused is worse than the bug it fixed.
2) it was reverted on the release 2.5 branch, so we want to prevent
   divergence
3) The original author is out-of-office for a while so we don't want the
   divergence to wait until they're back

ghstack-source-id: 39ed09a
Pull Request resolved: #137891
@zou3519
Copy link
Contributor Author

zou3519 commented Oct 14, 2024

@pytorchbot merge -f "unrelated failure"

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants