-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
Randomly appearing failure in schemes/elliptic_curves/padics.py #25969
Comments
comment:1
Either I'm incredibly "lucky" or #24735 really triggered this for me. Observations until now:
|
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to random_fail |
comment:3
I'm not entirely sure to what extent the failure is really random. It might be deterministic but occur only under a very precise set of conditions. |
comment:4
A possible cannon-to-shoot-a-mosquito solution might be #25971. |
comment:5
I cannot reproduce on my desktop PC, even though that is executing the exact same build script in a sandbox with the exact same dependencies. It looks like I can reproduce deterministically on my laptop. Unfortunately that takes forever to run the whole testsuite... |
comment:6
It looks like this was actually triggered by the |
comment:7
Although looking at the diff, I can't see anything that might cause this. All the changes in
|
comment:8
Replying to @timokau:
I don't think that it's any of those changes in particular. This is a kind of non-local bug that I've seen in the past. Most likely it has something to do with precise memory (de)allocations: an unrelated change in Sage triggers some garbage collection which subtly changes something which eventually leads to this bug. |
comment:9
Then what can we do about it? All I can say is that it pretty reliably (2 times in a row) happens after the upgrade and pretty reliable doesn't happen (3 times in a row) before. |
comment:10
Looks like only integer arithmetic is involved; Might be a corrupted mpir limb in the pool due to a preceeding interrupt test. Where exactly the interrupt hits depends on may external factors... |
comment:11
Probably unrelated, but when trying to reproduce this on sage-the-dist (I could not), I got another error in the same file:
|
comment:12
Replying to @vbraun:
As far as I can see, there is no such test in that file. The doctester tests every file in a separate process, so there can be no interference from interrupt tests in other files. |
This failure has been reported after applying two unrelated patches (#23719 and #24735):
Component: misc
Keywords: random_fail
Issue created by migration from https://trac.sagemath.org/ticket/25969
The text was updated successfully, but these errors were encountered: