-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Gap 4.13 released, some doctest failures #37616
Comments
why is gap3 involved here? is it compared with gap4.13? |
|
It's a bug in the tests there; obviously it should be using gap3 (as it otherwise does not test the implementation in this function!), not gap (i.e. gap4). So we should apply --- a/src/sage/interfaces/gap3.py
+++ b/src/sage/interfaces/gap3.py
@@ -752,7 +752,8 @@ class GAP3Element(GapElement_generic):
r"""
EXAMPLES::
- sage: s = gap("[[1,2], [3/4, 5/6]]")
+ sage: # optional - gap3
+ sage: s = gap3("[[1,2], [3/4, 5/6]]")
sage: s._latex_()
'\\left(\\begin{array}{rr} 1&2\\\\ 3/4&\\frac{5}{6}\\\\ \\end{array}\\right)'
sage: latex(s) Otherwise we merely testing what gap4 can do (and what you see is that gap4.13 is broken at this place). Unfortunately the diff above, with gap3 installed, gives
OTOH gap3 is an experimental package, so this is tolerable (without gap3 installed, there won't be a doctest failure here, after this patch is applied. |
I've opened #37624 to fix this little thing - it's quite orthogonal to gap 4.13, so it deserves a separate PR. Please review/approve it. |
There's one more failure with
|
|
we can use https://gap-packages.github.io/typeset/ I presume |
this fixes a long-standing bug in testing gap3 code, pointed out in sagemath#37616 URL: sagemath#37624 Reported by: Dima Pasechnik Reviewer(s): Gonzalo Tornaría
There's one more failure that only manifests itself if bliss is installed
But it seems to be an upstream issue |
<!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> - Based on sagemath#37884 by @tornaria - Fixes sagemath#37616 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [ ] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> - Depends on sagemath#38144 (merged here for testing) URL: sagemath#38169 Reported by: Matthias Köppe Reviewer(s):
Mostly seem to be due to changes in order of generators.
The text was updated successfully, but these errors were encountered: