-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
hang on doctest of giac.groebner_basis but NOT on interactive sage #33161
Comments
comment:1
This is a duplicate of #33050, but with more information. |
comment:2
Replying to @orlitzky:
It certainly looks the same, I'm sorry I missed that. However, what really confuses me is why running via doctests should be different than running interactively. Do you have any clue about that? I did the small file with only one test because I thought maybe some giac setting was changed by a previous test, but that doesn't change anything. Is there perhaps a weird interaction between the way doctests are run and the way giac is run? Maybe some diagnostic information printed by giac only in particular cases. |
comment:3
It's very weird and I can reproduce it now. We hit a similar issue in #33092; see the discussion starting around comment 45. Does using |
comment:4
Using |
comment:5
Replying to @antonio-rojas:
lol so I'm not the only one that happened to? I thought I was losing my mind. I wasn't even going to comment about it. |
comment:6
I can't reproduce the problem with
|
comment:7
Not sure if useful, but here is a backtrace
|
comment:8
bump to 9.6 |
comment:11
Another instance with another random seed, timing out with sage 9.7.rc1:
|
Using 9.5.rc0 and system giac 1.7.0-45:
gets stuck forever here, only for this random seed.
I reduced the doctest down to this file
test.py
:Now:
gets stuck forever and doesn't depend on the random seed.
However, running the same example interactively works:
Similar results in a different box with 9.5.beta9 and giac 1.7.0-39.
CC: @antonio-rojas @collares
Component: doctest framework
Issue created by migration from https://trac.sagemath.org/ticket/33161
The text was updated successfully, but these errors were encountered: