Skip to content

buckification #14391

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

buckification #14391

wants to merge 1 commit into from

Conversation

ezrilow
Copy link

@ezrilow ezrilow commented Sep 17, 2025

Summary:

Buckification Summary

Buckified ruamel-yaml==0.18.15. This diff is part of the stack to import ruamel-yaml==0.18.15.

Signals should be green prior to landing.
If anything looks wrong, please look into the BUCK file and fix.
If failed, please refer to the Manual Buckification Wiki page to fix the BUCK file.

Differential Revision: D82025749

@ezrilow @facebook-github-bot
buckification
7ee123e 
Summary:
# Buckification Summary

Buckified `ruamel-yaml==0.18.15`. This diff is part of the stack to import `ruamel-yaml==0.18.15`.

Signals should be green prior to landing.
If anything looks wrong, please look into the BUCK file and fix.
If failed, please refer to the [Manual Buckification Wiki page](https://www.internalfb.com/wiki/Third-Party_%40_Meta/third-party/Using_mgt_to_Import_Third-Party_Code/Python_%28PyPI%29/Manual_Buckification_of_Packages/) to fix the BUCK file.

Differential Revision: D82025749
@pytorch-bot PyTorch Bot
Copy link

pytorch-bot bot commented Sep 17, 2025 •
edited
Loading

🔗 Helpful Links

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

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 7ee123e with merge base e1ea74f (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 17, 2025
@facebook-github-bot
Copy link
Contributor

@ezrilow has exported this pull request. If you are a Meta employee, you can view the originating diff in D82025749.

@github-actions GitHub Actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

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

@JacobSzwejbka JacobSzwejbka JacobSzwejbka approved these changes

@larryliu0820 larryliu0820 Awaiting requested review from larryliu0820 larryliu0820 is a code owner

Assignees
No one assigned
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@ezrilow @facebook-github-bot @JacobSzwejbka