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
Fix numerical noise after #16858 #17063
Comments
Author: Jeroen Demeyer |
Branch: u/jdemeyer/ticket/17063 |
comment:3
Well, this looks good to me. But maybe there is something subtle to check ? on different architectures, etc ? The buildbot is almost happy, but protests for some other reasons.. New commits:
|
Commit: |
comment:4
Replying to @fchapoton:
Meaning positive_review?
Of course there is. There are lots of different architectures. However, this ticket does not have to fix all doctests on all possible architectures.
The buildbot is broken, you can ignore those failures. |
Reviewer: Frédéric Chapoton |
comment:5
I think this is good to go, because this only let the precision be slightly lower than before. So it can not introduce any new failing doctest, in principle. Am I correct to say that this is in particular needed to cure some of the buildbot failures ? Let me give a positive review, even if the blocker status is rather worrying to me. I hope I did not miss the point. |
comment:6
Replying to @fchapoton:
Not buildbot failures, but reports from other people on the
The "blocker" priority shouldn't matter for reviewing the ticket. "blocker" means that Sage 6.4 must not be released before this issue is fixed, it doesn't imply that the issue is particularly deep or difficult. |
Changed branch from u/jdemeyer/ticket/17063 to |
Component: doctest coverage
Author: Jeroen Demeyer
Branch/Commit:
23c88bc
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/17063
The text was updated successfully, but these errors were encountered: