Skip to content

making TORCH_CHECK_{COND} non-fatal#167004

Closed
dolpm wants to merge 1 commit intopytorch:mainfrom
dolpm:export-D86168955
Closed

making TORCH_CHECK_{COND} non-fatal#167004
dolpm wants to merge 1 commit intopytorch:mainfrom
dolpm:export-D86168955

Conversation

@dolpm
Copy link
Contributor

@dolpm dolpm commented Nov 4, 2025

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Differential Revision: D86168955

@pytorch-bot
Copy link

pytorch-bot bot commented Nov 4, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit cbec338 with merge base 694592a (image):
💚 Looks good so far! There are no failures yet. 💚

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

@meta-codesync
Copy link

meta-codesync bot commented Nov 4, 2025

@dolpm has exported this pull request. If you are a Meta employee, you can view the originating Diff in D86168955.

@dolpm dolpm added the topic: not user facing topic category label Nov 4, 2025
@dolpm dolpm changed the title tmp TORCH_CHECK_.* macros shouldn't exit Nov 4, 2025
@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Nov 4, 2025
@dolpm dolpm changed the title TORCH_CHECK_.* macros shouldn't exit making TORCH_CHECK_{COND} non-fatal Nov 5, 2025
pytorch-bot bot pushed a commit that referenced this pull request Nov 5, 2025
Summary: Pull Request resolved: #167004

Test Plan: ci

Differential Revision: D86168955
Copy link
Contributor

@malfet malfet left a comment

Choose a reason for hiding this comment

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

LGTM, provided CI is green (please check bazel failures, Windows one feels false positive)

@malfet malfet added release notes: cpp release notes category topic: improvements topic category and removed topic: not user facing topic category labels Nov 5, 2025
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 5, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 5, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 5, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 5, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 6, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 6, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
@dolpm dolpm force-pushed the export-D86168955 branch 2 times, most recently from 6f3550c to 1a66314 Compare November 6, 2025 17:12
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 6, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 6, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 6, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
pytorch-bot bot pushed a commit that referenced this pull request Nov 7, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 7, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 7, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
dolpm added a commit to dolpm/pytorch that referenced this pull request Nov 7, 2025
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
Summary:

TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Test Plan: ci

Reviewed By: malfet, ivy-zhou

Differential Revision: D86168955
@facebook-github-bot
Copy link
Contributor

@pytorchbot merge

(Initiating merge automatically since Phabricator Diff has merged)

@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

Silv3S pushed a commit to Silv3S/pytorch that referenced this pull request Nov 18, 2025
TORCH_CHECK is non-fatal by design, but TORCH_CHECK_{COND} macros are fatal. this is confusing, and we should limit fatality to the set of debug macros.

Differential Revision: D86168955

Pull Request resolved: pytorch#167004
Approved by: https://github.com/malfet
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 fb-exported Merged meta-exported release notes: cpp release notes category topic: improvements topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants