Skip to content

Conversation

@izaitsevfb
Copy link
Contributor

#126601 (internally D58103182) was exported missing one class definition. This PR brings github repo in sync with fbcode.

@pytorch-bot
Copy link

pytorch-bot bot commented Jul 8, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 86296c8 with merge base c6cce97 (image):
💚 Looks good so far! There are no failures yet. 💚

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

@pytorch-bot pytorch-bot bot added the release notes: distributed (c10d) release notes category label Jul 8, 2024
@izaitsevfb izaitsevfb added the topic: not user facing topic category label Jul 8, 2024
@izaitsevfb izaitsevfb requested review from a team and d4l3k July 8, 2024 23:56
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.

Was it ninja-landed?

@facebook-github-bot
Copy link
Contributor

@izaitsevfb has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@izaitsevfb
Copy link
Contributor Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Successfully rebased fix-discrepancy-export-126601 onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout fix-discrepancy-export-126601 && git pull --rebase)

@pytorchmergebot pytorchmergebot force-pushed the fix-discrepancy-export-126601 branch from 297dc27 to 86296c8 Compare July 9, 2024 22:03
@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.

7 participants