On 2/11/10 12:10 PM, Nick Schurch wrote:
> The high level unit tests fail for me with rpy2 v2.1.0alpha3, python
> 2.6.4 and R 2.9.2:
>
> Python 2.6.4 (r264:75706, Feb 10 2010, 14:06:31)
> [GCC 4.1.2 20080704 (Red Hat 4.1.2-44)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import rpy2.robjects.tests
> During startup - Warning messages:
> 1: package 'methods' was built under R version 2.9.2
> 2: package 'datasets' was built under R version 2.9.2
> 3: package 'utils' was built under R version 2.9.2
> 4: package 'grDevices' was built under R version 2.9.2
> 5: package 'graphics' was built under R version 2.9.2
> 6: package 'stats' was built under R version 2.9.2
>>>> import unittest
>>>> tr = unittest.TextTestRunner(verbosity = 1)
>>>> suite = rpy2.robjects.tests.suite()
>>>> tr.run(suite)
> ....................................Error in .Primitive("[")(0:10,
> list("a", "b", "c")) :
>    invalid subscript type 'list'
> ..................................................................F....
> ======================================================================
> FAIL: testVectorUnicodeCharacter
> (rpy2.robjects.tests.testNumpyConversions.NumpyConversionsTestCase)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File "rpy2/robjects/tests/testNumpyConversions.py", line 53, in
> testVectorUnicodeCharacter
>      self.assertTrue(False) # arrays of unicode characters causing segfault
> AssertionError
>
> ----------------------------------------------------------------------
> Ran 107 tests in 0.732s
>
> FAILED (failures=1)
> <unittest._TextTestResult run=107 errors=0 failures=1>


The one failed tests is a forced failure, and a visual inspection is 
hopefully informative enough.

self.assertTrue(False) # arrays of unicode characters causing segfault

self.assertTrue(False): "assert that False is True"; this is the 
signature of forced failed test. This is followed by a comment about why 
this test is failing, as this is an alternative to a segfault that would 
prevent going any further with the tests.

> Anyone have any ideas, before I ditch rpy2 and revert to good-old rpy?
>

That's an idea. Since you are with R-2.9, at least this should not 
translate into an other email like:
"I cannot seem to use rpy with R-2.10. Anyone have any ideas, before I 
ditch rpy and go for the brand-new rpy2 ?"


;-)


L.

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to