Hi David,

I am using an Opteron system:

CPU: 8 x Quad-Core AMD Opteron(tm) Processor 8384 (up to 32 cores)
RAM 320 Gigabyte (SWAP deactivated)
Harddrive: 600 Gigabyte (/scratch/)
OS: Debian 5.0.3 (AMD 64)

apart from the RAM difference, this system uses Debian, not Ubuntu,
but don't know if that makes a big difference. Tests pass on my
machine:

jlopez@theia:~/sage$ ./sage -t -long -force_lib "devel/sage/sage/
interfaces/rubik.py"

sage -t -long -force_lib "devel/sage/sage/interfaces/rubik.py"
         [37.1 s]

----------------------------------------------------------------------
All tests passed!
Total time for all tests: 37.2 seconds

jlopez@theia:~/sage$ sage -t -long -force_lib "devel/sage/sage/groups/
perm_gps/cubegroup.py"
sage -t -long -force_lib "devel/sage/sage/groups/perm_gps/
cubegroup.py"
         [25.8 s]

----------------------------------------------------------------------
All tests passed!
Total time for all tests: 25.8 seconds

Cheers
Javier

On 16 abr, 21:26, "Dr. David Kirkby" <david.kir...@onetel.net> wrote:
> Is there anyone here with an AMD Opteron? I've got a couple of doctests 
> failures
> on a 2.2 GHz Opteron machine with 1 GB RAM and 3 GB swap. The failures are:
>
> http://trac.sagemath.org/sage_trac/ticket/11206http://trac.sagemath.org/sage_trac/ticket/11207
>
> This is running Ubuntu 10.10After looking carefully at memory usage, I'm
> convinced the errors are unrelated to the modest memory on this machine.
>
> I just wonder if it's an Opteron specific bug, so I wonder if anyone with an
> Opteron can run the failed tests.
>
> --
> 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?
>
> 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

Reply via email to