You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2005/03/02 04:28:11 UTC

utf8_tests.py failing (just me?)

This using a very recent update/build.  Need I a clean build?  Is
anyone else seeing this?

   % ./utf8_tests.py 
   Failed to schedule i18n filename for addition
   EXPECTED STDERR:
   ACTUAL STDERR:
   subversion/libsvn_subr/utf.c:542: (apr_err=22)
   svn: Valid UTF-8 data
   (hex: 6e 67 5f 63 6f 70 69 65 73 2f 75 74 66 38 5f 74 65 73 74 73 2d 31 2f 62)
   followed by invalid UTF-8 sequence
   (hex: d4 e7 c5)
   EXCEPTION: SVNLineUnequal
   FAIL:  utf8_tests.py 1: conversion of paths and logs to/from utf8

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: utf8_tests.py failing (just me?)

Posted by Philip Martin <ph...@codematters.co.uk>.
John Szakmeister <jo...@szakmeister.net> writes:

> If I 'export LC_ALL=en_US.ISO8859-1', then the UTF-8 tests pass.  I'm not 
> sure what's happening, but it appears as though the locale really isn't 
> changed when the command line client is launched (it appears that 
> utf8_tests.py attempts to set the locale to "en_US.ISO8859-1" before 
> executing the tests).  I created a small test script and found that the 
> environment doesn't appear to be propagated.

I think that's standard on Unix, calling setlocale() changes the
locale of the current process but doesn't change the environment, so
the setlocale() doesn't affect any subsequent subprocesses.

My guess is that the people seeing failures are those who a) are using
a non-8859-1 locale, and b) have an 8859-1 en_US locale available.
Previously the failing tests were skipped as the locale names didn't
match (different case), now the test is run and the non-propogation
causes the failure.  The test script should probably do a setenv() on
LC_CTYPE as well as the setlocale().

-- 
Philip Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn trunk r13231: FAIL (x86_64-unknown-linux-gnu static ra_local bdb) (was: Re: utf8_tests.py failing (just me?))

Posted by Jani Averbach <ja...@jaa.iki.fi>.
On 2005-03-02 09:24-0600, kfogel@collab.net wrote:
> John Szakmeister <jo...@szakmeister.net> writes:
> > On Tuesday 01 March 2005 23:28, C. Michael Pilato wrote:
> > > This using a very recent update/build.  Need I a clean build?  Is
> > > anyone else seeing this?
> > >
> > >    [...]
> > 
> > I'm getting this as well.  My default SuSE environment is setup to be 
> > en_US.UTF-8, i.e.:
> 
> It's also failing for svntest@jaa.iki.fi, according to the breakage
> list, though it's not clear that it's failing for the same reasons.
> Here's the relevant bit from tests.log:

Here is my (svntest) locale information:

   export | egrep 'LC|LANG'
   declare -x LANG="en_US"
   declare -x LC_CTYPE="fi_FI@euro"

and system wide locale -av list will follow.

BR, Jani

locale: en_US           directory: /usr/lib/locale/en_US
-------------------------------------------------------------------------------
    title | English locale for the USA
   source | Free Software Foundation, Inc.
  address | 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
    email | bug-glibc-locales@gnu.org
 language | English
territory | USA
 revision | 1.0
     date | 2000-06-24
  codeset | ISO-8859-1

locale: en_US.utf8      directory: /usr/lib/locale/en_US.utf8
-------------------------------------------------------------------------------
    title | English locale for the USA
   source | Free Software Foundation, Inc.
  address | 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
    email | bug-glibc-locales@gnu.org
 language | English
territory | USA
 revision | 1.0
     date | 2000-06-24
  codeset | UTF-8

locale: fi_FI           directory: /usr/lib/locale/fi_FI
-------------------------------------------------------------------------------
    title | Finnish locale for Finland
   source | RAP
  address | Sankt Jørgens Alle 8, DK-1615 København V, Danmark
    email | bug-glibc-locales@gnu.org
 language | Finnish
territory | Finland
 revision | 1.0
     date | 2000-06-29
  codeset | ISO-8859-1

locale: fi_FI@euro      directory: /usr/lib/locale/fi_FI@euro
-------------------------------------------------------------------------------
    title | Finnish locale for Finland with Euro
   source | Free Software Foundation, Inc.
  address | 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
    email | bug-glibc-locales@gnu.org
 language | Finnish
territory | Finland
 revision | 1.0
     date | 2000-08-20
  codeset | ISO-8859-15

locale: fi_FI.utf8      directory: /usr/lib/locale/fi_FI.utf8
-------------------------------------------------------------------------------
    title | Finnish locale for Finland
   source | RAP
  address | Sankt JÞrgens Alle 8, DK-1615 KÞbenhavn V, Danmark
    email | bug-glibc-locales@gnu.org
 language | Finnish
territory | Finland
 revision | 1.0
     date | 2000-06-29
  codeset | UTF-8

-- 
Jani Averbach

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn trunk r13231: FAIL (x86_64-unknown-linux-gnu static ra_local bdb) (was: Re: utf8_tests.py failing (just me?))

Posted by kf...@collab.net.
John Szakmeister <jo...@szakmeister.net> writes:
> On Tuesday 01 March 2005 23:28, C. Michael Pilato wrote:
> > This using a very recent update/build.  Need I a clean build?  Is
> > anyone else seeing this?
> >
> >    [...]
> 
> I'm getting this as well.  My default SuSE environment is setup to be 
> en_US.UTF-8, i.e.:

It's also failing for svntest@jaa.iki.fi, according to the breakage
list, though it's not clear that it's failing for the same reasons.
Here's the relevant bit from tests.log:

START: utf8_tests.py
CMD: svnadmin "create" "local_tmp/repos" "--bdb-txn-nosync" "--fs-type=bdb" <TIME = 0.029191>
CMD: svn "import" "--username" "jrandom" "--password" "rayjandom" "-m" "Log message for revision 1." "local_tmp/greekfiles" "file:///srv/svntest/svntest/obj-st/subversion/tests/clients/cmdline/local_tmp/repos" "--config-dir" "/srv/svntest/svntest/obj-st/subversion/tests/clients/cmdline/local_tmp/config" <TIME = 0.042575>
CMD: svnadmin "create" "repositories/utf8_tests-1" "--bdb-txn-nosync" "--fs-type=bdb" <TIME = 0.028609>
CMD: svnadmin dump "local_tmp/repos" | svnadmin load "repositories/utf8_tests-1" <TIME = 0.007228>
CMD: svn "co" "--username" "jrandom" "--password" "rayjandom" "file:///srv/svntest/svntest/obj-st/subversion/tests/clients/cmdline/repositories/utf8_tests-1" "working_copies/utf8_tests-1" "--config-dir" "/srv/svntest/svntest/obj-st/subversion/tests/clients/cmdline/local_tmp/config" <TIME = 0.653905>
CMD: svn "add" "working_copies/utf8_tests-1/b" "--config-dir" "/srv/svntest/svntest/obj-st/subversion/tests/clients/cmdline/local_tmp/config" <TIME = 0.023724>
Failed to schedule i18n filename for addition
EXPECTED STDERR:
ACTUAL STDERR:
svn: Can't convert string from native encoding to 'UTF-8':
svn: working_copies/utf8_tests-1/b?\212?\231?\197
EXCEPTION: SVNLineUnequal
FAIL:  utf8_tests.py 1: conversion of paths and logs to/from utf8
END: utf8_tests.py


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: utf8_tests.py failing (just me?)

Posted by John Szakmeister <jo...@szakmeister.net>.
On Tuesday 01 March 2005 23:28, C. Michael Pilato wrote:
> This using a very recent update/build.  Need I a clean build?  Is
> anyone else seeing this?
>
>    % ./utf8_tests.py
>    Failed to schedule i18n filename for addition
>    EXPECTED STDERR:
>    ACTUAL STDERR:
>    subversion/libsvn_subr/utf.c:542: (apr_err=22)
>    svn: Valid UTF-8 data
>    (hex: 6e 67 5f 63 6f 70 69 65 73 2f 75 74 66 38 5f 74 65 73 74 73 2d
> 31 2f 62) followed by invalid UTF-8 sequence
>    (hex: d4 e7 c5)
>    EXCEPTION: SVNLineUnequal
>    FAIL:  utf8_tests.py 1: conversion of paths and logs to/from utf8

I'm getting this as well.  My default SuSE environment is setup to be 
en_US.UTF-8, i.e.:
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

If I 'export LC_ALL=en_US.ISO8859-1', then the UTF-8 tests pass.  I'm not 
sure what's happening, but it appears as though the locale really isn't 
changed when the command line client is launched (it appears that 
utf8_tests.py attempts to set the locale to "en_US.ISO8859-1" before 
executing the tests).  I created a small test script and found that the 
environment doesn't appear to be propagated.

When I run this script:
--------
#!/usr/bin/python

import os, locale

locale.setlocale(locale.LC_ALL, "en_US.ISO8859-1")
print "Current locale is %s" % locale.getlocale(locale.LC_ALL)
print "However..."
os.system("locale")
--------

I get:
Current locale is ['en_US', 'iso8859-1']
However...
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

-John


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org