'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Windows / Build and test (x64, tail-call)

Process completed with exit code 1.

Windows / Build and test (x64, tail-call): Python/traceback.c#L1171

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Windows (free-threading) / Build and test (x64, tail-call)

Process completed with exit code 1.

Windows (free-threading) / Build and test (x64, tail-call): Python/traceback.c#L1171

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Windows (free-threading) / Build and test (x64, switch-case)

Process completed with exit code 1.

Windows (free-threading) / Build and test (x64, switch-case): Python/traceback.c#L1171

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [D:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Windows / Build and test (Win32, switch-case)

Process completed with exit code 1.

WASI / build and test

Process completed with exit code 1.

Ubuntu SSL tests (ubuntu-26.04, openssl, 1.1.1w)

Process completed with exit code 2.

Ubuntu SSL tests (ubuntu-26.04, openssl, 4.0.1)

Process completed with exit code 2.

Ubuntu SSL tests (ubuntu-26.04, openssl, 3.4.6)

Process completed with exit code 2.

Ubuntu SSL tests (ubuntu-26.04, openssl, 3.5.7)

Process completed with exit code 2.

Ubuntu SSL tests (ubuntu-26.04, aws-lc, 5.0.0)

Process completed with exit code 2.

Emscripten / build and test

Process completed with exit code 1.

Ubuntu SSL tests (ubuntu-26.04, openssl, 3.0.21)

Process completed with exit code 2.

Ubuntu SSL tests (ubuntu-26.04, openssl, 3.6.3)

Process completed with exit code 2.

Hypothesis tests on Ubuntu

Process completed with exit code 2.

Hypothesis tests on Ubuntu: Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Android (x86_64)

Process completed with exit code 1.

Ubuntu / build and test (ubuntu-26.04-arm)

Process completed with exit code 2.

Ubuntu / build and test (ubuntu-26.04-arm): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

iOS

Process completed with exit code 1.

Check if generated files are up to date

Process completed with exit code 2.

Windows / Build and test (arm64, switch-case)

Process completed with exit code 1.

Windows / Build and test (arm64, switch-case): Python/traceback.c#L1171

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Ubuntu (free-threading) / build and test (ubuntu-26.04)

Process completed with exit code 2.

Ubuntu (free-threading) / build and test (ubuntu-26.04): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

macOS (free-threading) / build and test (macos-26)

Process completed with exit code 2.

Ubuntu (bolt) / build and test (ubuntu-26.04)

Process completed with exit code 2.

Ubuntu (bolt) / build and test (ubuntu-26.04): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Cross build Linux

Process completed with exit code 2.

Cross build Linux: Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Ubuntu / build and test (ubuntu-26.04)

Process completed with exit code 2.

Ubuntu / build and test (ubuntu-26.04): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Ubuntu (free-threading) / build and test (ubuntu-26.04-arm)

Process completed with exit code 2.

Ubuntu (free-threading) / build and test (ubuntu-26.04-arm): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Windows (free-threading) / Build and test (arm64, switch-case)

Process completed with exit code 1.

Windows (free-threading) / Build and test (arm64, switch-case): Python/traceback.c#L1171

'PyUnstable_DumpTraceback': 'void (int,PyThreadState *)' differs in levels of indirection from 'const char *(int,PyThreadState *)' [C:\a\cpython\cpython\PCbuild\_freeze_module.vcxproj]

Address sanitizer (ubuntu-26.04)

Process completed with exit code 2.

Address sanitizer (ubuntu-26.04): Python/traceback.c#L1171

conflicting types for ‘PyUnstable_DumpTraceback’; have ‘void(int, PyThreadState *)’ {aka ‘void(int, struct _ts *)’}

Android (aarch64)

Process completed with exit code 1.

Sanitizers / TSan

Process completed with exit code 2.

macOS / build and test (macos-26)

Process completed with exit code 2.

Sanitizers / TSan (free-threading)

Process completed with exit code 2.

macOS / build and test (macos-26-intel)

Process completed with exit code 2.

Sanitizers / UBSan

Process completed with exit code 2.

All required checks pass

Process completed with exit code 1.

Hypothesis tests on Ubuntu

No files were found with the provided path: /home/runner/work/cpython/cpython-builddir/.hypothesis/examples/. No artifacts will be uploaded.

macOS (free-threading) / build and test (macos-26)

`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!

macOS (free-threading) / build and test (macos-26)

The following taps are not trusted: aws/tap Homebrew is currently ignoring formulae, casks and commands from these taps because tap trust is required. Untap them with: brew untap aws/tap Trust specific formulae, casks and commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> Whole-tap trust is broader and includes all current and future formulae, casks and commands from the listed taps. Trust whole taps with: brew trust aws/tap To disable trust checks: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release. For more information, see: https://docs.brew.sh/Tap-Trust

macOS / build and test (macos-26)

`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!

macOS / build and test (macos-26)