On 09/ 1/10 02:19 AM, Alex Ghitza wrote:
On Wed, 01 Sep 2010 00:07:43 +0100, "Dr. David Kirkby"<david.kir...@onetel.net>
wrote:
It's nice to know that running the tests 100 times and reporting the failures
managed to unearth a bug.
I'm not sure I would call this a bug, but it is definitely something
that's very easy to overlook, and hard to detect without running the
tests a large number of times.
Best,
Alex
Oh well, I'm disappointed then!
But in a way, the fact this test did call Maxima by mistake, means it generated
two failures, which gives us more chance of finding the underlying cause for the
busted maxima interface.
http://trac.sagemath.org/sage_trac/ticket/8772
From what it said on the trac ticket, it appears only to happen on parallel
testing.
Though I don't know if anyone has run enough serial tests to be sure of this. I
see the bug in 4% of cases in parallel parallel testing 100 times.
I did start testing 100 serial cases, in different directories, but I messed up
and run out of swap space. I'll give that another go later.
Dave
--
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
