-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
dozens of failures in magma optional test suite on skynet (eno) with sage-4.3 #7870
Comments
this is the output of running the test suite, showing the actual failures. |
comment:1
Attachment: magma.out.gz I tested again using the new magma V2.16-7 with sage-4.3.5.
There are now even more failures. I've attached a new test log created using the following on eno:
|
it got much worse! |
Attachment: magma-sage-4.3.5.out.gz Attachment: trac_7870.patch.gz This fixes all the doctest issues on eno with magma V2.16-7 |
comment:3
I am testing this now with magma V2.16-1 and will report back. It will not be a clean result, since I already saw
|
comment:4
Full log is at http://www.warwick.ac.uk/staff/J.E.Cremona/magma_test.log . |
comment:5
Replying to @JohnCremona:
Apologies -- it looks as if I did not apply the patch since the differences look exactly like the ones you fixed! I will try again. |
Author: William Stein |
Reviewer: John Cremona |
comment:6
OK, so after actually applying the patch (I had forgotten to do hg qpush) I get exactly one failure. This is on 64-bit ubuntu, Sage 4.3.5 and Magma V2.16-1:
and this looks like some error in parsing the expected output (are you allowed two different "..."?) since it looks fine to me. The only other things I can think of is that there may be different numbers of spaces in the expected and actual magma output! |
Changed keywords from none to Magma |
comment:7
John, I think you should give my patch a positive review anyways. The problem above is that in Magma V2.16-7, this works fine:
However, in older versions of Magma, it doesn't:
Since Magma's capabilities, etc., change a lot -- even from minor version to version -- I think the Sage optional doctests should be targeted at the latest released version of Magma. Note that the computation is multiplying a polynomial over ZZ[x] by a floating point numbers. In Sage, there is a beautiful coercion model that makes most such things "just work". In Magma, one implements the '*' function for every conceivable choice of pairs of types... and I guess somebody got around to eventually implementing this one. Just to emphasize how totally arbitrary (and sad) Magma's system still is after all these years, notice that even in Magma V2.16-7, the same computation with polynomials over ZZ and rational numbers doesn't work!
Sage had the same sort of silly anomalies until people like David Harvey, Craig Citro, David Roe, and Robert Bradshaw and others stepped in and greatly improved the situation.
Sage coercion is still of course far from perfect. But it's also far from sucking. -- William |
comment:9
I just lost my posting here (cookie problem) and don't feel like rewriting it all.... I only have C2.16-1 and the patch requires V2.16-7 or higher to pass, it seems, so I cannot verify it at present. Is it anywhere documented which version of Magma Sage relies on for positive tests? |
comment:10
With Sage 4.4 and a newly installed magma V1.16-7 I still get falures in these files:
See http://www.warwick.ac.uk/staff/J.E.Cremona/magma.out for the full log. |
comment:26
This seems right. So, if everything is ok for you, also, give it a positive review. |
comment:27
According to the I don't have Magma, but do have Mathematica, so I thought I'd try
but it seems to run every doctest, not just the Mathematica ones, which fail anyway, as noted at #8495. Dave |
comment:28
This needs to be rebased to sage-4.7.alpha1. |
Attachment: trac-7870-magma-doctest-review3.patch.gz |
This comment has been minimized.
This comment has been minimized.
comment:29
I rebased the patch to 4.7alpha1. Please only apply the last one: review3. Could anyone (John?) check this soon, so that we won't need to rebase it again? |
comment:30
Replying to @sagetrac-mraum:
Thanks.
OK, I'll try that soon. (I have just been away for the weekend or I would have done it already.) |
comment:31
With magma-V2.17-5 (which I downloaded and installed specially) and sage-4.7.alpha1 I tested everything both with and without -only-optional=magma and in both cases all tests passed. So I am giving this a positive review (again). |
comment:32
It seems that your 'review3' patch is based on an older version of the patches, I get the number_field doctest failures again. |
comment:33
Well, yes. We really need to run the test on a setup without Magma then. I add the fix for this problem (which is review2 patch rebased to current Sage). |
This comment has been minimized.
This comment has been minimized.
Attachment: trac-7870-magma-doctest-review4.patch.gz |
comment:34
With the earlier patch (patch3) and the latest magma I tested everything and got no errors, so it seems like a waste of (my) time to do it all again. I do not understand mraum's comments about doing tests on a machine with no magma. I ran complete tests with and without -only-optional=magma. |
Merged: sage-4.7.alpha2 |
comment:35
Works now without magma. |
Changed reviewer from Martin Raum, John Cremona to Martin Raum, John Cremona, Jeroen Demeyer |
I ran the magma optional test suite on skynet (eno):
And the failures are:
Apply:
Component: interfaces
Keywords: Magma
Author: William Stein, John Cremona
Reviewer: Martin Raum, John Cremona, Jeroen Demeyer
Merged: sage-4.7.alpha2
Issue created by migration from https://trac.sagemath.org/ticket/7870
The text was updated successfully, but these errors were encountered: