Skip to content

Conversation

@swolchok
Copy link
Contributor

@swolchok swolchok commented Oct 30, 2024

See comment for explanation. In short, doing the fixup in float.

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10

See comment for explanation. In short, doing the fixup in float.
@pytorch-bot pytorch-bot bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Oct 30, 2024
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 30, 2024

🔗 Helpful Links

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

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

✅ No Failures

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

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

Copy link
Contributor

@huydhn huydhn left a comment

Choose a reason for hiding this comment

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

Thank you for the fix!

@swolchok
Copy link
Contributor Author

I ran the following to verify per HUD failures:

env PYTORCH_OPINFO_SAMPLE_INPUT_INDEX=9 python test/inductor/test_torchinductor_opinfo.py TestInductorOpInfoCPU.test_comprehensive_matmul_cpu_float16
env PYTORCH_OPINFO_SAMPLE_INPUT_INDEX=2 python test/inductor/test_torchinductor_opinfo.py TestInductorOpInfoCPU.test_comprehensive_nn_functional_linear_cpu_float16

@swolchok
Copy link
Contributor Author

@pytorchbot merge -f "unbreaking main"

@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

rahulsingh-intel pushed a commit to rahulsingh-intel/pytorch that referenced this pull request Nov 5, 2024
@github-actions github-actions bot deleted the unbreak-fp16-dot branch November 30, 2024 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Merged module: cpu CPU specific problem (e.g., perf, algorithm) topic: bug fixes topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants