Skip to content

Make test_create_graph_and_full_backward_hook_cycle more robust to unrelated warnings #153407

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.

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

Open
wants to merge 10 commits into
base: gh/soulitzer/362/base
Choose a base branch
from

Conversation

soulitzer
Copy link
Contributor

@soulitzer soulitzer commented May 12, 2025

Copy link

pytorch-bot bot commented May 12, 2025

🔗 Helpful Links

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

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

❌ 14 New Failures, 1 Unrelated Failure

As of commit f4b1427 with merge base e2c7ae5 (image):

NEW FAILURES - The following jobs have failed:

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.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label May 12, 2025
@soulitzer soulitzer changed the title Make test_create_graph_and_full_backward_hook_cycle more robust to random warnings Make test_create_graph_and_full_backward_hook_cycle more robust to unrelated warnings May 12, 2025
soulitzer added 2 commits May 12, 2025 16:40
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

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

Ok

@soulitzer
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 12, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@soulitzer soulitzer closed this May 12, 2025
@soulitzer
Copy link
Contributor Author

@soulitzer soulitzer reopened this May 12, 2025
…obust to unrelated warnings"

[ghstack-poisoned]
soulitzer added 6 commits May 13, 2025 16:42
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
…obust to unrelated warnings"

[ghstack-poisoned]
Copy link
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the Stale label Jul 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Stale topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants