Op 20-09-10 19:27, Noe Misael Nieto Arroyo schreef:
> Hi all,
> I hope this is the right place to ask this question.
>
> I was running test over Products.CMFPlone and I got this two errors:
>
> $ bin/test -cs Products.CMFPlone
> Running Testing.ZopeTestCase.layer.ZopeLite tests:
>    Set up Testing.ZopeTestCase.layer.ZopeLite in 1.257 seconds.
>    Ran 123 tests with 0 failures and 0 errors in 1.466 seconds.
> .......
>
> Failure in test testProcessLatin1
> (Products.CMFPlone.tests.testUnicodeSplitter.TestSplitter)
> Traceback (most recent call last):
>    File "/usr/lib/python2.6/unittest.py", line 279, in run
>      testMethod()
>    File
> "/home/tzicatl/Aplicaciones/Buildout/egss/Plone-4.0-py2.6.egg/Products/CMFPlone/tests/testUnicodeSplitter.py",
> line 91, in testProcessLatin1
>      self.assertEqual(self.process(input), output)
>    File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
>      (msg or '%r != %r' % (first, second))
> AssertionError: ['ffin', 'foo'] != ['\xc4ffin', 'foo']
>
>
>
> Failure in test testNormalizeLatin1
> (Products.CMFPlone.tests.testUnicodeSplitter.TestCaseNormalizer)
> Traceback (most recent call last):
>    File "/usr/lib/python2.6/unittest.py", line 279, in run
>      testMethod()
>    File
> "/home/tzicatl/Aplicaciones/Buildout/egss/Plone-4.0-py2.6.egg/Products/CMFPlone/tests/testUnicodeSplitter.py",
> line 124, in testNormalizeLatin1
>      self.assertEqual(self.process(input), output)
>    File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual
>      (msg or '%r != %r' % (first, second))
> AssertionError: ['\xc4ffin'] != ['\xe4ffin']
>
>    Ran 943 tests with 2 failures and 0 errors in 54 minutes 57.398 seconds.
>
> ....
>
>
> What are these errors about? Is there a way to "Fix" it?


I used to see exactly those two errors too.  I think I don't see them 
now because I am using a Mac.  On Ubuntu Linux it somehow depends on the 
locale setting of your system.  I tried figuring it out a year or two 
ago, installing some extra locales as well I think, but failed.  As far 
as I know it is safe to ignore.

It is mentioned briefly in this ticket as well:
http://dev.plone.org/plone/ticket/9309#comment:42

-- 
Maurits van Rees
Programmer, Zest Software

_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to