-
-
Notifications
You must be signed in to change notification settings - Fork 29.5k
New issue
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
dask pyperformance benchmark hangs on win32 #118715
Comments
Do you mean that it uses all the CPU, or that the process hangs and do nothing? Can you check which lines are executed when it "hangs"? |
I reproduced the issue. The problem comes from
|
I reported the issue to the dask/distributed project and I proposed a fix: |
@mdboom: I suggest to close this issue since it's not a bug in Python, and it's now tracked in dask/distributed. |
I want to bring a discussion elsewhere back here. @vstinner: I definitely have no experience with these Windows APIs, however, it seems that the change in 1d95451 introduced some stateful interaction between At a minimum, I think we should improve the "What's new" entry about this so people are aware of the interaction. |
It's documented at: https://docs.python.org/dev/whatsnew/3.13.html#time |
Sorry, I see you answered my question elsewhere. |
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:Cc @vstinner
To reproduce:
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.
Link to earlier discussion
CPython versions tested on:
CPython main branch
Operating systems tested on:
Windows
The text was updated successfully, but these errors were encountered: