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
Make sage -t --debug trigger on an incorrect doctest in addition to an unexpected error #13610
Comments
Attachment: 13610.patch.gz |
comment:3
Alright, this works for me on OS X. Needs review. |
Reviewer: Jeroen Demeyer |
comment:7
Review patch looks good to me. |
Changed work issues from keyboard interrupt, doctesting after exiting the debugger not working correctly to none |
comment:9
Doctest failure in |
comment:10
Attachment: 13610_review.patch.gz |
comment:11
Looks good. |
Merged: sage-5.9.beta4 |
This was referenced Sep 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#12415 introduces the ability to drop into a Python debugger when an unexpected error is encountered. I was attempting to have a similar behavior happen when an incorrect result was obtained so that it's easier to figure out what has gone wrong in the doctest. But problems with interrupt handling were delaying the completion of #12415 (already a patchbomb), so I've stripped out that functionality and put it here.
Depends on #14289
Depends on #14290
Depends on #14331
Depends on #13278
Depends on #14370
Component: doctest framework
Author: David Roe
Reviewer: Jeroen Demeyer
Merged: sage-5.9.beta4
Issue created by migration from https://trac.sagemath.org/ticket/13610
The text was updated successfully, but these errors were encountered: