-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
Test failures with Fedora 12 on intel i7 860 processor #7773
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
Finally someone with test failures that relate to mine on Fedora 12 x86_64! Jaap |
Attachment: test.log |
comment:3
Doctest error log added. |
comment:4
I get a similar failure with linear_codes.py on a Core 2 Duo under Fedora 12 (sage 4.3.1):
All files reported by Gokhan Sever fail. In particular modsym says:
|
comment:5
I encounter a similar error with Fedora 12 on Intel Pentium M: my cpuinfo:
my gcc -v:
my lsb_release:
last lines of test.log:
detailed failure results:
|
comment:6
This problem is still present with 4.3.3. I have put on http://www.loria.fr/~zimmerma/sage-t.log.4.3.3 the log of |
comment:7
With sage-4.3.3 I've isolated the problem in
(Note the problem does not happen during the Sage session, but only when we quit Sage and it Note: I could not try
It seems the directory |
comment:8
I don't have these two lines failing on v4.3.3 comparing to my 4.3.2.alpha0 tests: Using ./sage -testall
|
comment:9
thanks to Robert Bradshaw, I was able to isolate the following test case:
where the Segfault does not occur without the last instruction |
comment:10
Note: I'm ready to do more investigation if someone tells me what to do... |
comment:11
I don't have time to look at this this weekend, but only note that GF(32) and GF(1024) are |
comment:12
David,
are you sure? I get:
Is there a way to force GF() to use Givaro or Ntl? |
comment:13
Ah, you're right. You should be able to use the I don't know what's going on if it's givaro. |
comment:14
I wasn't able to find how to use the
No SegFault occurs with NTL, which shows the problem is linked with Givaro. |
comment:15
I tried again the 22 tests which did produce a Segfault, by changing zech_log_bound from 216 to
I'm not sure we can doctest the result of the |
comment:16
With sage 4.3.5, this problem is still there:
|
comment:17
All this doctest failures went away for me with the release of sage-4.4.1.alpha3!!!! Jaap |
comment:18
Jaap,
great! Did you still have those failures with 4.4? This shows that the culprit is Sage and not Paul |
comment:19
Replying to @zimmermann6:
The failures were still there in sage-4.4.1.alpha0. I'll try alpha1. sage-4.4.1.alpha2 failed to build. Jaap
|
comment:20
Paul, sage-4.4.1.alpha1 was a mess on Fedora 12. In sage-4.4.1.rc0 all test passed. Jaap |
comment:21
Jaap,
thus the problem disappeared between both. Can you guess from the Changelog which package might Paul |
comment:22
should we close this ticket? Paul |
Reviewer: Paul Zimmermann |
On this machine I got memory errors, some of wich are reported by glibc-2.11 as double free:
*** glibc detected *** python: double free or corruption (fasttop):
Valgrind to the rescue! I made a new optional spkg:
#7766
Rebuild sage-4.3 with SAGE_VALGRIND="yes", installed valgrind-3.6.0.svn with the help of
http://wiki.sagemath.org/ValgrindingSage
./sage -t -valgrind devel/sage/sage/matrix/matrix_sparse.pyx
Some results:
The complete report can be found on my homepage on sage.math
(i'll put a link here as soon sage.math is up again) valgrind_memcheck_test_matrix_sparse.bz2
It's here: http://sage.math.washington.edu/home/jsp/valgrind_memcheck_test_matrix_sparse.bz2
Jaap
CC: @robertwb @malb @roed314 @williamstein
Component: build
Reviewer: Paul Zimmermann
Issue created by migration from https://trac.sagemath.org/ticket/7773
The text was updated successfully, but these errors were encountered: