On Jan 27, 7:15 pm, Jaap Spies <j.sp...@hccnet.nl> wrote:
> Gokhan Sever wrote:
> > Hello,
>
> > uname -a
> > Linux ccn 2.6.31.9-174.fc12.i686.PAE #1 SMP Mon Dec 21 06:04:56 UTC
> > 2009 i686 i686 i386 GNU/Linux
>
> > Getting many errors after ./sage -testall
>
> > ----------------------------------------------------------------------
> > The following tests failed:
>
> > sage -t "devel/sage/sage/modules/free_module.py" # Segfault
> > sage -t "devel/sage/sage/coding/code_constructions.py" # Segfault
> > sage -t "devel/sage/sage/coding/linear_code.py" # Segfault
> > sage -t "devel/sage/sage/groups/generic.py" # Segfault
> > sage -t "devel/sage/sage/modular/ssmod/ssmod.py" # Segfault
> > sage -t "devel/sage/sage/modular/modform/ambient.py" # Segfault
> > sage -t "devel/sage/sage/modular/modsym/space.py" # Segfault
> > sage -t "devel/sage/sage/modular/modsym/modsym.py" # Segfault
> > sage -t "devel/sage/sage/matrix/matrix_sparse.pyx" # Segfault
> > sage -t "devel/sage/sage/matrix/matrix2.pyx" # Segfault
> > sage -t "devel/sage/sage/matrix/matrix_space.py" # Segfault
>
> Finally some one with test failures that relate to mine on Fedora 12!
>
> See ticket:http://sagetrac.org/sage_trac/ticket/7773
>
> Jaap
Could someone register me at the Trac? I am getting a bizarre error
there:
Trac detected an internal error:
KeyError: 'recaptcha_challenge_field'
There was an internal error in Trac. It is recommended that you inform
your local Trac administrator and give him all the information he
needs to reproduce the issue.
The action that triggered the error was:
POST: /register
TracGuide — The Trac User and Administration Guide
There is this message at register page:
"This reCAPTCHA key isn't authorized for the given domain. More
info.."
Anyways, I will post my error logs there once I logged in.
Do you think we should report these issues at Bugzilla as well?
Also what is the difference between running the test suite (from
$SAGE_ROOT/README.TXT) and testing the installation with ./sage -
testall
If you want to run the test suite for each individual spkg as it is
installed, type
export SAGE_CHECK="yes"
before starting the Sage build. This will run each test suite and
will raise an error if any failures occur.
Once there is an error built is stopped with this. As I described in
this message:
http://groups.google.com/group/sage-devel/browse_thread/thread/4bef86f4eabac321#
To me, this shouldn't stop the build process instead should be
reported at the end of the action.
One more, can we test both test_suite and doctests seperated for each
package instead of one-run run-all approach?
Thanks.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
