-
Notifications
You must be signed in to change notification settings - Fork 159
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
Recursion depth trap when repeatedly calling Test
#1752
Comments
I suspect the problem is we don't reset the depth of the stack when we longjmp. |
It seems to be a bit unpredictable, whether it happens or not. |
It will be (I suspect) connected to the number of tests which exit via an error. |
Yes. In our continuous integration, it was always one of the last files to be tested that was having problems. |
Ah, just checking, is this only on 4.8? I have a feeling I fixed something related to this in master (and the error doesn't seem to trigger in master for me) |
We only test with master at the moment, so I don't know anything about whether it's present in stable-4.8. |
Ah, no, I can reproduce it, it just takes a while. If I add a way of printing out GAP's |
Fix coming up. |
Awesome @ChrisJefferson, thanks |
This is (hopefully) fixed by #1753. |
Fixed by #1753 |
Observed behaviour
If the contents of the test file
bug.tst
is:and I load GAP without any packages
gap -A
, then dothen when
i
is1665
This is a minimal example of the problem, but this is causing some of the Semigroups package continuous integration test to fail, see the discussion here for more details. This bug is confirm by several others, not only me, so unlikely to be an issue with my setup.
Expected behaviour
The loop to run forever.
Copy and paste GAP banner (to tell us about your setup)
The text was updated successfully, but these errors were encountered: