You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Erik Timan <er...@timan.info> on 2012/08/01 16:22:24 UTC
Test failure (make check) in etap/190-json-stream-parse.t
Hello all!
I've built CouchDB 1.2.0 on CentOS 6.2 using the RPM spec from
https://github.com/wendall911/couchdb-rpm. While it builds fine, make
check fails for me when running etap/190-json-stream-parse.t. I get
"Failed 88/99 subtests".
After diving deeper, I found that the test failed on line 87 in
190-json-stream-parse.t:
{<<"foo", 5, "bar">>, "\"foo\\u0005bar\"", "string literal with
\\u0005"},
(for context, see
https://github.com/apache/couchdb/blob/e736fa9e314034e2603ac5861692ddeab92f1dad/test/etap/190-json-stream-parse.t#L87)
If I comment that line out, all other test cases completes ok. To me it
looks like some unicode problem. Can someone shed some light upon why
this is happening and if there is a real problem here?
Some additional info:
Arch: x86_64
CouchDB version: 1.2.0
Erlang version: R15B01
JS-devel version: 1.8.5
Tnx!
/Erik
Re: Test failure (make check) in etap/190-json-stream-parse.t
Posted by CGS <cg...@gmail.com>.
It seems like your version JSON may skip \u0005 (but I may be wrong) and
here I cannot help anymore because I have no idea how to debug that. Sorry.
Maybe someone more knowledgeable will step up and clarify the problem.
CGS
On Thu, Aug 2, 2012 at 3:30 PM, Erik Timan <er...@timan.info> wrote:
> On Wed, Aug 1, 2012, at 17:38, CGS wrote:
> > It looks to me you need to work in UTF8 environment (I might be wrong
> > though). For that, check the output of `echo $LANG'. That will tell you
> > if
> > you are working with UTF8 environment. If not, you can set it with
> > `export
> > LANG="your_language.utf8"' (replace "your_language" with your environment
> > language; for C-shell variants, use setenv).
> >
> > CGS
>
> I've tried setting both LANG and LC_ALL & friends to use UTF-8, but it
> seems to make no difference. I can see that it makes a difference for
> the Erlang shell when running io:getopts(), but the test seems
> unaffected.
>
> Erik
>
Re: Test failure (make check) in etap/190-json-stream-parse.t
Posted by Erik Timan <er...@timan.info>.
On Wed, Aug 1, 2012, at 17:38, CGS wrote:
> It looks to me you need to work in UTF8 environment (I might be wrong
> though). For that, check the output of `echo $LANG'. That will tell you
> if
> you are working with UTF8 environment. If not, you can set it with
> `export
> LANG="your_language.utf8"' (replace "your_language" with your environment
> language; for C-shell variants, use setenv).
>
> CGS
I've tried setting both LANG and LC_ALL & friends to use UTF-8, but it
seems to make no difference. I can see that it makes a difference for
the Erlang shell when running io:getopts(), but the test seems
unaffected.
Erik
Re: Test failure (make check) in etap/190-json-stream-parse.t
Posted by CGS <cg...@gmail.com>.
It looks to me you need to work in UTF8 environment (I might be wrong
though). For that, check the output of `echo $LANG'. That will tell you if
you are working with UTF8 environment. If not, you can set it with `export
LANG="your_language.utf8"' (replace "your_language" with your environment
language; for C-shell variants, use setenv).
CGS
On Wed, Aug 1, 2012 at 4:22 PM, Erik Timan <er...@timan.info> wrote:
> Hello all!
>
> I've built CouchDB 1.2.0 on CentOS 6.2 using the RPM spec from
> https://github.com/wendall911/couchdb-rpm. While it builds fine, make
> check fails for me when running etap/190-json-stream-parse.t. I get
> "Failed 88/99 subtests".
>
> After diving deeper, I found that the test failed on line 87 in
> 190-json-stream-parse.t:
>
> {<<"foo", 5, "bar">>, "\"foo\\u0005bar\"", "string literal with
> \\u0005"},
>
> (for context, see
>
> https://github.com/apache/couchdb/blob/e736fa9e314034e2603ac5861692ddeab92f1dad/test/etap/190-json-stream-parse.t#L87
> )
>
> If I comment that line out, all other test cases completes ok. To me it
> looks like some unicode problem. Can someone shed some light upon why
> this is happening and if there is a real problem here?
>
> Some additional info:
>
> Arch: x86_64
> CouchDB version: 1.2.0
> Erlang version: R15B01
> JS-devel version: 1.8.5
>
> Tnx!
> /Erik
>