Skip to content

Workaround for e4m2 dtype#156461

Closed
drisspg wants to merge 1 commit into
gh/drisspg/160/basefrom
gh/drisspg/160/head
Closed

Workaround for e4m2 dtype#156461
drisspg wants to merge 1 commit into
gh/drisspg/160/basefrom
gh/drisspg/160/head

Conversation

@drisspg

@drisspg drisspg commented Jun 20, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

@drisspg
Update
5352a0d 
[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Jun 20, 2025 •
edited
Loading

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Pending, 1 Unrelated Failure

As of commit 5352a0d with merge base 36f7a02 (image):

NEW FAILURE - The following job has 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.

drisspg added a commit that referenced this pull request Jun 20, 2025
@drisspg
Workaround for e4m2 dtype
3f2c849 
ghstack-source-id: b264466
Pull-Request: #156461
@drisspg drisspg requested a review from eellison June 20, 2025 02:40
@drisspg drisspg added the topic: not user facing topic category label Jun 20, 2025
@drisspg drisspg requested a review from vkuzo June 20, 2025 18:37
@drisspg

drisspg commented Jun 20, 2025

Copy link
Copy Markdown
Contributor Author

@pytorchbot merge -i

@pytorch-bot pytorch-bot Bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 20, 2025
@pytorchmergebot

pytorchmergebot commented Jun 20, 2025

Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: pull / cuda12.8-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu), inductor / unit-test / cuda12.8-py3.13-gcc9-sm86 / test (inductor, 1, 2, linux.g5.4xlarge.nvidia.gpu)

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

@pytorchmergebot

pytorchmergebot commented Jun 20, 2025

Copy link
Copy Markdown
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build

Details for Dev Infra team Raised by workflow job

@drisspg

drisspg commented Jun 20, 2025

Copy link
Copy Markdown
Contributor Author

@pytorchbot merge -i

@pytorchmergebot

pytorchmergebot commented Jun 20, 2025

Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged while ignoring the following 3 checks: pull / cuda12.8-py3.10-gcc9-sm75 / test (pr_time_benchmarks, 1, 1, linux.g4dn.metal.nvidia.gpu), inductor / unit-test / cuda12.8-py3.13-gcc9-sm86 / test (inductor, 1, 2, linux.g5.4xlarge.nvidia.gpu), linux-binary-manywheel / manywheel-py3_9-cuda12_6-build / build

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

@pytorchmergebot

pytorchmergebot commented Jun 21, 2025

Copy link
Copy Markdown
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@drisspg

drisspg commented Jun 21, 2025

Copy link
Copy Markdown
Contributor Author

@pytorchbot merge -f "the jobs timed out"

@pytorchmergebot

pytorchmergebot commented Jun 21, 2025

Copy link
Copy Markdown
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 gh/drisspg/160/head branch July 23, 2025 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@vkuzo vkuzo vkuzo approved these changes

@eellison eellison Awaiting requested review from eellison

Assignees

No one assigned

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged module: inductor topic: not user facing topic category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@drisspg @pytorchmergebot @vkuzo