Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

CaoE
Copy link
Collaborator

@CaoE CaoE commented Mar 11, 2024

Copy link

pytorch-bot bot commented Mar 11, 2024

🔗 Helpful Links

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

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 c4552c4 with merge base 7a4e451 (image):

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

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

@github-actions github-actions bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Mar 11, 2024
@CaoE CaoE added module: windows Windows support for PyTorch module: performance Issues related to performance, either of kernel code or framework glue ciflow/trunk Trigger trunk jobs on your pull request labels Mar 11, 2024
@CaoE CaoE requested review from jgong5, mingfeima and xuhancn March 11, 2024 05:24
@CaoE CaoE changed the title Fix lower precision check for MKLDNN on windows Fix lower precision check for MKLDNN on Windows Mar 11, 2024
@xuhancn xuhancn added intel priority matters to intel architecture from performance wise intel This tag is for PR from Intel labels Mar 11, 2024
@CaoE CaoE marked this pull request as ready for review March 11, 2024 06:18
@xuhancn xuhancn requested a review from malfet March 11, 2024 06:26
@seemethere
Copy link
Member

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

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

Details for Dev Infra team Raised by workflow job

@seemethere
Copy link
Member

@pytorchbot merge

@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

@atalman
Copy link
Contributor

atalman commented Mar 25, 2024

@pytorchbot cherry-pick --onto release/2.2 -c regression --fixes #120788

@pytorchbot
Copy link
Collaborator

Cherry picking #121618

The cherry pick PR is at #122645 and it is linked with issue #120788

Details for Dev Infra team Raised by workflow job

atalman pushed a commit that referenced this pull request Mar 25, 2024
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 intel priority matters to intel architecture from performance wise intel This tag is for PR from Intel Merged module: cpu CPU specific problem (e.g., perf, algorithm) module: performance Issues related to performance, either of kernel code or framework glue module: windows Windows support for PyTorch open source topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Operator performance plummets on PyTorch 2.2.1 Windows platform

8 participants