[issue47037] Build problems on Windows

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue47037] Build problems on Windows

Steve Dower added the comment: New changeset d0a91bd277d1122b41d59e8022b596e3b3ae24fe by Steve Dower in branch 'main': bpo-47037: Test debug builds on Windows in CI so that native assertions are noticed sooner (GH-31965) https://github.com/python/cpython/commit/d0a91bd277d1122b41d59e8022b596

[issue47037] Build problems on Windows

Eryk Sun added the comment: The main entry point for python[_d].exe should support a command-line -X option or environment variable that suppresses Windows error/assert/warn reporting, or redirects it to stderr in verbose mode. This would be useful to simplify everyone's automated testing. I

[issue47037] Build problems on Windows

Terry J. Reedy added the comment: I recompiled, retested, and all tests are ok, with no unexpected box. Thank you all. The vcruntime warnings are also gone, so I will chalk them up to a onetime glitch. -- ___ Python tracker

[issue47037] Build problems on Windows

Steve Dower added the comment: New changeset d190a9351be577a534a84fd1899f02a9f50f7276 by Christian Heimes in branch 'main': bpo-47037: Don't test for strftime('%4Y') on Windows (GH-31945) https://github.com/python/cpython/commit/d190a9351be577a534a84fd1899f02a9f50f7276 -- _

[issue47037] Build problems on Windows

Change by Steve Dower : -- pull_requests: +30054 pull_request: https://github.com/python/cpython/pull/31965 ___ Python tracker ___ _

[issue47037] Build problems on Windows

Steve Dower added the comment: I think this is also a good enough reason to switch the GitHub CI back to a debug build, rather than release, so that assert failures are caught before they get merged. This is not the first time it's happened. -- __

[issue47037] Build problems on Windows

Change by Eryk Sun : -- priority: normal -> critical ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue47037] Build problems on Windows

Eryk Sun added the comment: > Ouch, is Python crashes because of an unsupported strftime call? It's not a crash. It's a CRT error report dialog, which is enabled by default for the _CRT_ASSERT and _CRT_ERROR macros in debug builds. This dialog can be helpful when debugging interactively. It

[issue47037] Build problems on Windows

Terry J. Reedy added the comment: Re the 3.9/3.10 warnings: I have not intentionally touched my C install in years. I don't know what Windows' updates do (most recently yesterday) . I presume vcruntime140.dll is on my C: ssd, which has shown no problems. Debug runs w/o -j0 normally take ab

[issue47037] Build problems on Windows

Change by Christian Heimes : -- keywords: +patch pull_requests: +30036 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/31945 ___ Python tracker

[issue47037] Build problems on Windows

Tim Peters added the comment: Christian, yes, but only in a debug build. See Eryk Sun's message a bit above: the machinery to prevent this is already present, but isn't getting called early enough. -- ___ Python tracker

[issue47037] Build problems on Windows

Christian Heimes added the comment: Ouch, is Python crashes because of an unsupported strftime call? -- nosy: +christian.heimes ___ Python tracker ___

[issue47037] Build problems on Windows

Dennis Sweeney added the comment: indeed, bisected to 2cf7f865f099db11cc6903b334d9c376610313e8 is the first bad commit commit 2cf7f865f099db11cc6903b334d9c376610313e8 Author: Christian Heimes Date: Tue Mar 15 11:41:04 2022 +0200 bpo-46587: Skip tests if strftime does not support glibc

[issue47037] Build problems on Windows

Eryk Sun added the comment: bpo-46587 added top-level code to "Lib/test/support/__init__.py" to check whether time.strftime("%4Y") works. Since "Lib/test/libregrtest/setup.py" imports the support module, that code executes before suppress_msvcrt_asserts() is called by setup_tests(). ---

[issue47037] Build problems on Windows

Tim Peters added the comment: BTW, the frequency of this new failure mode appears to be vastly increased if running the debug tests with "-j0". For example, the box popping up is reliably the very first sign of life if I run this from the PCBuild directory: rt -q -d -j0 --

[issue47037] Build problems on Windows

Tim Peters added the comment: Actually, I see this ('Debug Assertion Failed!' in the same spot) every time I try to run the test suite with a debug build, starting yesterday. Didn't have time to track it down. It _appeared_ to an obscure consequence of this commit: """ $ git log timemodule.

[issue47037] Build problems on Windows

Steve Dower added the comment: This sounds more like recent installation changes on your machine. Have you updated Visual Studio or something like that? Perhaps the debug UCRT has gone missing. I'm not aware of any recent compilation changes that would cause this. -- __

[issue47037] Build problems on Windows

New submission from Terry J. Reedy : 3.11 apparently builds without error, and 'python' and 'python -m idlelib' appears to start normally, but there is a new problem. python -m test raises OS box with 'Debug Assertion Failed!', program python_d.exe, File minkernal\crts\ucrt\src\time\wcsftime.