Skip to content

Conversation

hackty
Copy link
Contributor

@hackty hackty commented Mar 12, 2025

nn.Dropout appeared at line 81

Copy link

pytorch-bot bot commented Mar 12, 2025

🔗 Helpful Links

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

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

⏳ No Failures, 42 Pending

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

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

Copy link

linux-foundation-easycla bot commented Mar 12, 2025

CLA Signed


The committers listed above are authorized under a signed CLA.

Copy link
Contributor

@jingsh jingsh left a comment

Choose a reason for hiding this comment

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

lgtm

@hackty
Copy link
Contributor Author

hackty commented Mar 13, 2025

@pytorchmergebot merge

Copy link

pytorch-bot bot commented Mar 13, 2025

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

Copy link

pytorch-bot bot commented Mar 13, 2025

You are not authorized to force merges to this repository. Please use the regular @pytorchmergebot merge command instead

@hackty hackty requested a review from jingsh March 13, 2025 03:22
@cyyever
Copy link
Collaborator

cyyever commented Mar 13, 2025

@pytorchmergebot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 13, 2025
@cyyever
Copy link
Collaborator

cyyever commented Mar 13, 2025

@pytorchmergebot merge -f "Safe fix"

@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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants