KEMBAR78
fix test_lazy_module_kwargs by avikchaudhuri · Pull Request #137705 · pytorch/pytorch · GitHub
Skip to content

Conversation

@avikchaudhuri
Copy link
Contributor

Test Plan: fixed

Differential Revision: D64185644

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 10, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (3 Unrelated Failures)

As of commit 80ac69e with merge base 93bbc8a (image):

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

BROKEN TRUNK - The following job 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.

@facebook-github-bot
Copy link
Contributor

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

@facebook-github-bot
Copy link
Contributor

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Are they previously special handled in dynamo?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This only applies to non-strict, since this bug was in detecting arribute assigments (in general Dynamo errors so we don't run this detection there).

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 10, 2024
@facebook-github-bot
Copy link
Contributor

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

avikchaudhuri added a commit to avikchaudhuri/pytorch that referenced this pull request Oct 10, 2024
Summary: Pull Request resolved: pytorch#137705

Test Plan: fixed

Differential Revision: D64185644
avikchaudhuri added a commit to avikchaudhuri/pytorch that referenced this pull request Oct 10, 2024
Summary: Pull Request resolved: pytorch#137705

Test Plan: fixed

Reviewed By: tugsbayasgalan

Differential Revision: D64185644
@facebook-github-bot
Copy link
Contributor

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

Summary: Pull Request resolved: pytorch#137705

Test Plan: fixed

Reviewed By: tugsbayasgalan

Differential Revision: D64185644
@facebook-github-bot
Copy link
Contributor

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

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

@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.

4 participants