|
Size: 939
Comment:
|
Size: 1884
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| == eno: x86_64-Linux-fc8 == | == eno: x86_64-Linux-fc8 (status: 0/10) == |
| Line 14: | Line 14: |
| Using gcc-4.3.1: | Using gcc-4.3.1: I (william) can't build ntl. I'm totally stuck until getting past this. |
| Line 16: | Line 16: |
| I (william) can't build ntl. I'm totally stuck until getting past this. | == cicero: x86-Linux-fc8 (status: 9/10) == |
| Line 18: | Line 18: |
| == cicero: x86-Linux-fc8 == | Using gcc-4.1.2: built fine out of the box; all tests for rc1 pass. |
| Line 20: | Line 20: |
| Using gcc-4.1.2: build fine out of the box; all tests for rc1 pass. | Using gcc-4.3.1: Mariah gets an "illegal instruction" error when testing {{{ sage -t devel/sage/sage/functions/special.py }}} |
| Line 22: | Line 25: |
| == cleo: ia64-Linux-rhel5 == | == cleo: ia64-Linux-rhel5 (status: 7/10) == Using gcc-4.1.2: Built fine out of the box. Currently testing; many tests have timed out since this machine is so slow. Possible serious singular crash in groups/matrix_gps/matrix_group.py, though it could be a timeout. There is something massively foobar'd about this machine or its file system or something. For example: {{{ [wstein@cleo sage-3.0.4.rc0]$ time ./sage -c "print 1+1" 2 real 0m26.532s user 0m1.447s sys 0m3.224s }}} A 26 second startup time? Ick. Is there something seriously wrong with the build of Python? |
| Line 26: | Line 39: |
| == iras: ia64-Linux-suse == | == iras: ia64-Linux-suse (status: 8/10) == |
| Line 28: | Line 41: |
| There is a major bug in flint. See http://trac.sagemath.org/sage_trac/ticket/3616 | There is a major bug in flint that freezes doctesting. See http://trac.sagemath.org/sage_trac/ticket/3616 |
| Line 30: | Line 43: |
| == menas: x86_64-Linux-suse == | == menas: x86_64-Linux-suse (status: 9/10) == |
| Line 32: | Line 45: |
| With gcc-4.2.1 and reverting to the old version of clisp all tests pass for sage-4.3.1.rc0: |
With gcc-4.2.1 and reverting to the old version of clisp all tests pass for sage-4.3.1.rc0: |
| Line 40: | Line 52: |
I think reverting clisp will be ok for this architecture and for this release since the only reason for the new version was build support on more architectures. |
Getting Sage-3.0.4 to build and pass all tests on Skynet
To get from rc0 to rc1 from within a built sage do this:
sage: hg_sage.apply('http://sage.math.washington.edu/home/was/patches/a.hg')
sage: hg_sage.merge()
sage: hg_sage.ci()Then do "./sage -br" at the prompt.
eno: x86_64-Linux-fc8 (status: 0/10)
Using gcc-4.3.1: I (william) can't build ntl. I'm totally stuck until getting past this.
cicero: x86-Linux-fc8 (status: 9/10)
Using gcc-4.1.2: built fine out of the box; all tests for rc1 pass.
Using gcc-4.3.1: Mariah gets an "illegal instruction" error when testing
sage -t devel/sage/sage/functions/special.py
cleo: ia64-Linux-rhel5 (status: 7/10)
Using gcc-4.1.2: Built fine out of the box. Currently testing; many tests have timed out since this machine is so slow. Possible serious singular crash in groups/matrix_gps/matrix_group.py, though it could be a timeout. There is something massively foobar'd about this machine or its file system or something. For example:
[wstein@cleo sage-3.0.4.rc0]$ time ./sage -c "print 1+1" 2 real 0m26.532s user 0m1.447s sys 0m3.224s
A 26 second startup time? Ick. Is there something seriously wrong with the build of Python?
iras: ia64-Linux-suse (status: 8/10)
There is a major bug in flint that freezes doctesting. See http://trac.sagemath.org/sage_trac/ticket/3616
menas: x86_64-Linux-suse (status: 9/10)
With gcc-4.2.1 and reverting to the old version of clisp all tests pass for sage-4.3.1.rc0:
sage -i clisp-2.41.p14.spkg sage -f maxima-5.13.0.p2.spkg
Without reverting clisp, maxima hangs on certain integrals.
I think reverting clisp will be ok for this architecture and for this release since the only reason for the new version was build support on more architectures.