One test failed on standard rc1+clisp...p15, running 32 bit Arch linux
with GCC 4.3, /proc/cpuinfo below and doctest below it.
cheers,
Andrzej.
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2600+
stepping : 0
cpu MHz : 2091.115
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips : 4186.88
clflush size : 32
and only test that failed:
sage -t devel/sage-main/sage/rings/complex_double.pyx
**********************************************************************
File "/opt/sage-3.0.rc1/tmp/complex_double.py", line 1659:
sage: z^2 - z + 1
Expected:
2.22044604925e-16 + ...e-16*I
Got:
2.22044604925e-16
**********************************************************************
1 items had failures:
1 of 7 in __main__.example_93
***Test Failed*** 1 failures.
For whitespace errors, see the file /opt/sage-3.0.rc1/
tmp/.doctest_complex_double.py
[4.1 s]
exit code: 1024
----------------------------------------------------------------------
The following tests failed:
sage -t devel/sage-main/sage/rings/complex_double.pyx
Total time for all tests: 4.1 seconds
On 21 Kwi, 23:56, "John Cremona" <[EMAIL PROTECTED]> wrote:
> On my 32-bit kubuntu machine all is well with rc1:
>
> All tests passed!
> Total time for all tests: 3933.1 seconds
>
> John
>
> 2008/4/21 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> > On Apr 21, 11:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> > > 2008/4/21 William Stein <[EMAIL PROTECTED]>:
> > <SNIP>
>
> > > > Both of the failures you guys report -- in twist.py and testdoc.py
> > > > involve
> > > > opening a network port, doing some tests that things are working,
> > > > then closing it. I think closing just takes a while with ports,
> > perhaps,
> > > > and that might be relevant. I think if we make the ports in the
> > tests
> > > > more spread out that could help.
>
> > Hi John,
>
> > > That makes sense. Would it be better not to report such test failures
> > > which pass on a second try?
>
> > with any doctest failure you should mention if it is reproducible or
> > not. In this case it seems that twisted or whoever closes the port
> > might do so in an unclean way, i.e. the kernel considers the port
> > still open and will only release it after some timeout. Knowing
> > nothing about the internals of twisted I wouldn't know how to fix it,
> > so somebody else should dig ;)
>
> > > John
>
> > Cheers,
>
> > Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
