This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GitHub Actions/ Windows / Build and test (x64, switch-case)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Windows / Build and test (x64, tail-call)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Windows (free-threading) / Build and test (x64, tail-call)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Windows (free-threading) / Build and test (x64, switch-case)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Hypothesis tests on Ubuntu
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Ubuntu / build and test (ubuntu-26.04-arm)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Windows / Build and test (arm64, switch-case)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Ubuntu (free-threading) / build and test (ubuntu-26.04)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Ubuntu (bolt) / build and test (ubuntu-26.04)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Cross build Linux
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Ubuntu / build and test (ubuntu-26.04)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Ubuntu (free-threading) / build and test (ubuntu-26.04-arm)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Windows (free-threading) / Build and test (arm64, switch-case)
'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]
Check failure
on line 1171
in Python/traceback.c
View workflow job for this annotation
GitHub Actions/ Address sanitizer (ubuntu-26.04)
conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gh-145559: Make PyUnstable_DumpTraceback return void again #154131
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
Uh oh!
There was an error while loading. Please reload this page.
gh-145559: Make PyUnstable_DumpTraceback return void again #154131
Filter by extension
Viewed files
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Check failure on line 1171 in Python/traceback.c
Uh oh!
There was an error while loading. Please reload this page.