Skip to content

Conversation

clee2000
Copy link
Contributor

@clee2000 clee2000 commented Aug 9, 2023

follow up to #105096
It seems fine, anecdotally I have seen some issues closed and they haven't been reopened

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Aug 9, 2023
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 9, 2023

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ No Failures

As of commit 80126f7:
💚 Looks good so far! There are no failures yet. 💚

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

@clee2000 clee2000 marked this pull request as ready for review August 9, 2023 23:39
@clee2000 clee2000 requested a review from a team as a code owner August 9, 2023 23:39
@clee2000
Copy link
Contributor Author

@pytorchbot merge -f "this is a weekly script unrelated to actual pytorch code, trunk is not needed"

@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

@github-actions github-actions bot deleted the csl/closeissues branch February 9, 2025 02:07
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