Skip to content

Using acc_t for log_softmax #143896

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 7 commits into
base: gh/yanbing-j/37/base
Choose a base branch
from

Conversation

yanbing-j
Copy link
Collaborator

@yanbing-j yanbing-j commented Dec 27, 2024

This PR is to fix #140222. Using high precision as the accumulate type for log_softmax forward. Reproducer in the issue can pass now.

Stack from ghstack (oldest at bottom):

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

@pytorch-bot pytorch-bot bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Dec 27, 2024
Copy link

pytorch-bot bot commented Dec 27, 2024

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Cancelled Job, 4 Unrelated Failures

As of commit 44e69b2 with merge base 28796f7 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following job failed but was likely due to flakiness present on trunk:

BROKEN TRUNK - The following job failed but was present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

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

yanbing-j added a commit that referenced this pull request Dec 27, 2024
ghstack-source-id: abd0e7f
Pull Request resolved: #143896
@yanbing-j yanbing-j marked this pull request as draft December 27, 2024 06:30
@yanbing-j yanbing-j added the ciflow/trunk Trigger trunk jobs on your pull request label Dec 27, 2024
@yanbing-j yanbing-j added the topic: not user facing topic category label Dec 27, 2024
[ghstack-poisoned]
[ghstack-poisoned]
yanbing-j added a commit that referenced this pull request Dec 30, 2024
ghstack-source-id: 4e7474a
Pull Request resolved: #143896
@yanbing-j yanbing-j requested a review from mingfeima December 30, 2024 06:59
@yanbing-j yanbing-j marked this pull request as ready for review January 14, 2025 05:23
yanbing-j added a commit that referenced this pull request Jan 14, 2025
ghstack-source-id: 19f7cab
Pull Request resolved: #143896
[ghstack-poisoned]
@yanbing-j yanbing-j requested a review from malfet January 14, 2025 09:51
yanbing-j added a commit that referenced this pull request Jan 20, 2025
ghstack-source-id: 1480b76
Pull Request resolved: #143896
[ghstack-poisoned]
@pytorch-bot pytorch-bot bot temporarily deployed to upload-benchmark-results January 20, 2025 05:34 Inactive
@pytorch-bot pytorch-bot bot temporarily deployed to upload-benchmark-results January 20, 2025 05:34 Inactive
@pytorch-bot pytorch-bot bot temporarily deployed to upload-benchmark-results January 20, 2025 05:34 Inactive
@yanbing-j yanbing-j requested review from gchanan and ptrblck January 21, 2025 01:58
@yanbing-j
Copy link
Collaborator Author

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/yanbing-j/37/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/143896)

pytorchmergebot pushed a commit that referenced this pull request Feb 7, 2025
ghstack-source-id: dfc94f0
Pull Request resolved: #143896
@cyyever
Copy link
Collaborator

cyyever commented Apr 4, 2025

@pytorchbot rebase

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/yanbing-j/37/orig onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/143896)

pytorchmergebot pushed a commit that referenced this pull request Apr 4, 2025
ghstack-source-id: 8d4506b
Pull Request resolved: #143896
@cyyever
Copy link
Collaborator

cyyever commented Apr 4, 2025

@pytorchmergebot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: Approvers from one of the following sets are needed:

  • superuser (pytorch/metamates)
  • Core Reviewers (mruberry, lezcano, Skylion007, ngimel, peterbell10, ...)
  • Core Maintainers (soumith, gchanan, ezyang, dzhulgakov, malfet, ...)
Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@yanbing-j yanbing-j requested a review from soumith April 7, 2025 01:41
@yanbing-j
Copy link
Collaborator Author

Hi @cyyever, thanks for the approval! Do you have any suggestions of the reviewers to land this PR?

@cyyever cyyever requested a review from Copilot April 7, 2025 01:44
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

Files not reviewed (1)
  • aten/src/ATen/native/cpu/SoftMaxKernel.cpp: Language not supported
Comments suppressed due to low confidence (1)

test/test_nn.py:13260

  • [nitpick] The variable name 'input' shadows the built-in function; consider renaming it (e.g., to 'input_tensor' or 'inp') to avoid potential issues.
input = torch.randn(2, 2, 2, 2, 2, dtype=torch.bfloat16)

@cyyever
Copy link
Collaborator

cyyever commented Apr 7, 2025

@Skylion007 May help review?

@yanbing-j yanbing-j requested review from Skylion007 and removed request for soumith and gchanan April 7, 2025 01:53
Copy link
Contributor

github-actions bot commented Jun 6, 2025

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 Jun 6, 2025
@yanbing-j yanbing-j removed the Stale label Jun 6, 2025
@cyyever
Copy link
Collaborator

cyyever commented Jun 6, 2025

@pytorchbot rebase -b main

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

Successfully rebased gh/yanbing-j/37/orig onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via ghstack checkout https://github.com/pytorch/pytorch/pull/143896)

pytorchmergebot pushed a commit that referenced this pull request Jun 6, 2025
ghstack-source-id: a3e7232
Pull Request resolved: #143896
Copy link
Contributor

github-actions bot commented Aug 5, 2025

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 Aug 5, 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 module: cpu CPU specific problem (e.g., perf, algorithm) open source Stale topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants