Closed as not planned
Description
Bug report
Bug description:
The dask benchmark in pyperformance hangs indefinitely, only on 32-bit Windows (not any other Tier 1 platform, as far as I can tell).
git bisect has narrowed it down to this commit 1d95451:
1d95451be1f3080904c00cc4c4a6cc519efdf321 is the first bad commit Author: Victor Stinner <vstinner@python.org>
Date: Mon Mar 18 17:13:01 2024 +0100
gh-63207: Use GetSystemTimePreciseAsFileTime() in time.time() (#116822)
Doc/whatsnew/3.13.rst | 6 ++++
.../2024-03-14-17-21-25.gh-issue-63207.LV16SL.rst | 4 +++
Python/pytime.c | 38 +++++++++++++---------
3 files changed, 32 insertions(+), 16 deletions(-)
create mode 100644 Misc/NEWS.d/next/Library/2024-03-14-17-21-25.gh-issue-63207.LV16SL.rst
Cc @vstinner
To reproduce:
# Make a venv to install dependencies in
cpython\PCBuild\win32\python.exe -m venv venv
copy cpython\PCBuild\win32\python313.lib cpython
venv\Scripts\activate
python -m pip install pyperformance
python -m pyperformance run -b dask
I'm working on finding a more self contained reproducer, but may not have time for that immediately, so I thought I would report this in the meantime. I suspect it is an integer sizing mismatch bug in that commit, given that it doesn't happen on 64-bit Windows.
CPython versions tested on:
CPython main branch
Operating systems tested on:
Windows