On 04/ 1/11 11:02 PM, jonha...@gmail.com wrote:
Dear Dave,
That's weird. Now the test seems to pass. I had tried it several
times before I wrote, but now it consistently passes. I'm now a
little worried about the stability of my system... Any ideas about
what can cause these problems (and tests I can run to detect them)?
Thanks,
-Jon
=)
P.S. /proc/version tells me:
Linux version 2.6.18-164.6.1.el5 (mockbuild@ls20-
bc2-14.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat
4.1.2-46)) #1 SMP Tue Oct 27 11:28:30 EDT 2009
Could you check your system logs and see if there were any error messages.
Running out of swap space, memory errors etc.
I know if one tests Sage in parallel, with
$ make ptestlong
or
$ make ptest
then there can sometimes be failures which are not reproducible due to the fact
one test could write over files created by another test. But "make check" does
not do parallel testing, so that's not the issue here. You could create a shell
script like this:
#!/bin/sh
while [ 1 ] ;
do
./sage -t devel/sage/sage/misc/preparser.py >> preparser-tests.log
done
and put that in the top-level sage directory. It will run the test for as many
times as you feel you want to dedicate CPU time to. Then grep the file
preparser-tests.log and see if there are failures. The test is taking 6.0
seconds on my machine, so it should be possible to get 1000 tests done in
reasonably manageable time.
Some time ago I did test Sage 100 or more times for a few days, and did get some
odd failures, though I think most could be explained by the fact that the
testing framework for Sage was quite poor. But I think that's been improved
somewhat since then.
Do you have an account on trac? If not, it would be worth creating a ticket. Put
as much information about your machine as possible
Make and model.
RAM
CPU
Operating system and version
Whether it's 32-bit or 64-bit operating system.
Version of Sage
Version of gcc used
The original failure, the fact it failed several times, then it passes several
times.
Whether you have a record of the system logs at the time the tests were run,
which show no problems (out of swap space, memory errors etc).
How many failures you got with my little test program etc.
I assume since that machine is a Sun, it will have error corrected RAM anyway.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
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
