Skip to content

[cuDNN][cuDNN V8 API] (re-re-re-open) cuDNN V8 API on by default #91117

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
Closed
eqy wants to merge 2 commits into from
Closed

[cuDNN][cuDNN V8 API] (re-re-re-open) cuDNN V8 API on by default #91117

eqy wants to merge 2 commits into from

Conversation

@eqy
Copy link
Collaborator

@eqy eqy commented Dec 19, 2022

Re-opening following #91025

CC @ptrblck @ngimel

@pytorch-bot
Copy link

pytorch-bot bot commented Dec 19, 2022 •
edited
Loading

🔗 Helpful Links

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

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

❌ 2 Failures

As of commit 1fb5639:

NEW FAILURES - The following jobs have failed:

FLAKY - The following jobs failed but were likely due to flakiness present on master:

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

@eqy eqy added ciflow/trunk Trigger trunk jobs on your pull request ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR labels Dec 19, 2022
ngimel
ngimel approved these changes Dec 19, 2022
View reviewed changes
Copy link
Collaborator

@ngimel ngimel left a comment

Choose a reason for hiding this comment

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

Hopefully it sticks this time

@eqy
Copy link
Collaborator Author

eqy commented Dec 20, 2022

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 20, 2022

@pytorchbot successfully started a rebase job. Check the current status here

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 20, 2022

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

@eqy
Copy link
Collaborator Author

eqy commented Dec 20, 2022

@pytorchmergebot merge -f "failures are unrelated"

@pytorchmergebot
Copy link
Collaborator

pytorchmergebot commented Dec 20, 2022

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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

@eqy eqy mentioned this pull request Mar 22, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ngimel ngimel ngimel approved these changes

@jerryzh168 jerryzh168 Awaiting requested review from jerryzh168

@z-a-f z-a-f Awaiting requested review from z-a-f

@HDCharles HDCharles Awaiting requested review from HDCharles

Assignees

No one assigned

Labels

ciflow/periodic Trigger jobs ran periodically on master (periodic.yml) on the PR ciflow/trunk Trigger trunk jobs on your pull request Merged open source release notes: AO frontend

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@eqy @pytorchmergebot @ngimel @pytorchbot