[Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Darren Dale 
Hello,

I just performed an svn update, deleted my old build/ and
site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit
linux machine:

==
FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
--
Traceback (most recent call last):
  File /usr/lib64/python2.6/site-packages/nose/case.py, line 182, in
runTest
self.test(*self.arg)
  File /usr/lib64/python2.6/site-packages/numpy/testing/decorators.py,
line 169, in knownfailer
return f(*args, **kwargs)
  File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
line 557, in test_loss_of_precision_longcomplex
self.check_loss_of_precision(np.longcomplex)
  File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
line 510, in check_loss_of_precision
check(x_series, 2*eps)
  File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
line 497, in check
'arctanh')
AssertionError: (135, 3.4039637354191726288e-09, 3.9031278209478159624e-18,
'arctanh')
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Charles R Harris 
2009/3/24 Darren Dale dsdal...@gmail.com

 Hello,

 I just performed an svn update, deleted my old build/ and
 site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit
 linux machine:

 ==
 FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
 --
 Traceback (most recent call last):
   File /usr/lib64/python2.6/site-packages/nose/case.py, line 182, in
 runTest
 self.test(*self.arg)
   File /usr/lib64/python2.6/site-packages/numpy/testing/decorators.py,
 line 169, in knownfailer
 return f(*args, **kwargs)
   File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 557, in test_loss_of_precision_longcomplex
 self.check_loss_of_precision(np.longcomplex)
   File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 510, in check_loss_of_precision
 check(x_series, 2*eps)
   File /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 497, in check
 'arctanh')
 AssertionError: (135, 3.4039637354191726288e-09, 3.9031278209478159624e-18,
 'arctanh')


What machine is it?

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Nils Wagner 
On Tue, 24 Mar 2009 11:20:53 -0600
  Charles R Harris charlesr.har...@gmail.com wrote:
 2009/3/24 Darren Dale dsdal...@gmail.com
 
 Hello,

 I just performed an svn update, deleted my old build/ 
and
 site-packages/numpy*, reinstalled, and I see a new test 
failure on a 64 bit
 linux machine:

 ==
 FAIL: 
test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
 --
 Traceback (most recent call last):
   File 
/usr/lib64/python2.6/site-packages/nose/case.py, line 
182, in
 runTest
 self.test(*self.arg)
   File 
/usr/lib64/python2.6/site-packages/numpy/testing/decorators.py,
 line 169, in knownfailer
 return f(*args, **kwargs)
   File 
/usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 557, in test_loss_of_precision_longcomplex
 self.check_loss_of_precision(np.longcomplex)
   File 
/usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 510, in check_loss_of_precision
 check(x_series, 2*eps)
   File 
/usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 497, in check
 'arctanh')
 AssertionError: (135, 3.4039637354191726288e-09, 
3.9031278209478159624e-18,
 'arctanh')

 
 What machine is it?
 
 Chuck

I can reproduce the failure.
Linux linux-mogv 2.6.27.19-3.2-default #1 SMP 2009-02-25 
15:40:44 +0100 x86_64 x86_64 x86_64 GNU/Linux

cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Pentium(R) Dual  CPU  T3200  @ 
2.00GHz
stepping: 13
cpu MHz : 1000.000
cache size  : 1024 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr 
sse sse2 ss ht tm pbe syscall nx lm constant_tsc 
arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl est 
tm2 ssse3 cx16 xtpr lahf_lm
bogomips: 3996.80
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Intel(R) Pentium(R) Dual  CPU  T3200  @ 
2.00GHz
stepping: 13
cpu MHz : 1000.000
cache size  : 1024 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic 
sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr 
sse sse2 ss ht tm pbe syscall nx lm constant_tsc 
arch_perfmon pebs bts rep_good nopl pni monitor ds_cpl est 
tm2 ssse3 cx16 xtprlahf_lm
bogomips: 3996.82
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

==
FAIL: 
test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
--
Traceback (most recent call last):
   File 
/home/nwagner/local/lib64/python2.6/site-packages/nose-0.10.4-py2.6.egg/nose/case.py,
 
line 182, in runTest
 self.test(*self.arg)
   File 
/home/nwagner/local/lib64/python2.6/site-packages/numpy/testing/decorators.py,
 
line 169, in knownfailer
 return f(*args, **kwargs)
   File 
/home/nwagner/local/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 
line 557, in test_loss_of_precision_longcomplex
 self.check_loss_of_precision(np.longcomplex)
   File 
/home/nwagner/local/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 
line 510, in check_loss_of_precision
 check(x_series, 2*eps)
   File 
/home/nwagner/local/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 
line 497, in check
 'arctanh')
AssertionError: (135, 3.4039637354191726288e-09, 
3.9031278209478159624e-18, 'arctanh')

--
Ran 2031 tests in 15.923s

FAILED (KNOWNFAIL=1, failures=1)
nose.result.TextTestResult run=2031 errors=0 failures=1
  
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Darren Dale 
2009/3/24 Charles R Harris charlesr.har...@gmail.com



 2009/3/24 Darren Dale dsdal...@gmail.com

 Hello,

 I just performed an svn update, deleted my old build/ and
 site-packages/numpy*, reinstalled, and I see a new test failure on a 64 bit
 linux machine:

 ==
 FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
 --
 Traceback (most recent call last):
   File /usr/lib64/python2.6/site-packages/nose/case.py, line 182, in
 runTest
 self.test(*self.arg)
   File /usr/lib64/python2.6/site-packages/numpy/testing/decorators.py,
 line 169, in knownfailer
 return f(*args, **kwargs)
   File
 /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py, line
 557, in test_loss_of_precision_longcomplex
 self.check_loss_of_precision(np.longcomplex)
   File
 /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py, line
 510, in check_loss_of_precision
 check(x_series, 2*eps)
   File
 /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py, line
 497, in check
 'arctanh')
 AssertionError: (135, 3.4039637354191726288e-09,
 3.9031278209478159624e-18, 'arctanh')


 What machine is it?


64-bit gentoo linux, gcc-4.3.3, python-2.6.1
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Pauli Virtanen 
Tue, 24 Mar 2009 13:15:21 -0400, Darren Dale wrote:
 I just performed an svn update, deleted my old build/ and
 site-packages/numpy*, reinstalled, and I see a new test failure on a 64
 bit linux machine:
 
 ==
 FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
 --
[clip]
   /usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
 line 497, in check
 'arctanh')
 AssertionError: (135, 3.4039637354191726288e-09,
 3.9031278209478159624e-18, 'arctanh')

I can reproduce this (on another 64-bit machine). This time around, it's 
the real function that is faulty:

 x = np.longdouble(3e-9)
 np.arctanh(x+0j).real - x
9.0876776281460559983e-27
 np.arctanh(x).real - x
0.0
 np.finfo(np.longdouble).eps * x
3.2526065174565132804e-28

So, the system atanhl is ~ 30 relative eps away from the correct answer:

 from sympy import mpmath
 mpmath.mp.dps=60
 p = mpmath.mpf('3e-9')
 print (mpmath.atanh(p) - p)*1e27
9.0001681879956480095820042512435586643130912

I'll relax the test tolerance to allow for this...

-- 
Pauli Virtanen

___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] test failure in numpy trunk

2009-03-24 Thread Charles R Harris 
On Tue, Mar 24, 2009 at 1:12 PM, Pauli Virtanen p...@iki.fi wrote:

 Tue, 24 Mar 2009 13:15:21 -0400, Darren Dale wrote:
  I just performed an svn update, deleted my old build/ and
  site-packages/numpy*, reinstalled, and I see a new test failure on a 64
  bit linux machine:
 
  ==
  FAIL: test_umath.TestComplexFunctions.test_loss_of_precision_longcomplex
  --
 [clip]
/usr/lib64/python2.6/site-packages/numpy/core/tests/test_umath.py,
  line 497, in check
  'arctanh')
  AssertionError: (135, 3.4039637354191726288e-09,
  3.9031278209478159624e-18, 'arctanh')

 I can reproduce this (on another 64-bit machine). This time around, it's
 the real function that is faulty:

  x = np.longdouble(3e-9)
  np.arctanh(x+0j).real - x
 9.0876776281460559983e-27
  np.arctanh(x).real - x
 0.0
  np.finfo(np.longdouble).eps * x
 3.2526065174565132804e-28

 So, the system atanhl is ~ 30 relative eps away from the correct answer:


I see this also. The compiler is gcc version 4.3.0 20080428 (Red Hat
4.3.0-8) (GCC). Maybe we should ping the compiler folks? I could also open a
Fedora bug for this.

Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion