Parsing fails (invalid byte sequence in US-ASCII)

[choefele]

In this Travis build, the parser fails with the following error message (ruby 2.0.0p247, xcpretty 0.1.4):

/Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/lib/xcpretty/parser.rb:265:in `===': invalid byte sequence in US-ASCII (ArgumentError)
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/lib/xcpretty/parser.rb:265:in `update_test_state'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/lib/xcpretty/parser.rb:182:in `parse'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/lib/xcpretty/formatters/formatter.rb:63:in `pretty_format'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/lib/xcpretty/printer.rb:15:in `pretty_print'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/bin/xcpretty:73:in `block in <top (required)>'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/bin/xcpretty:72:in `each_line'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/bin/xcpretty:72:in `each_line'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/gems/xcpretty-0.1.4/bin/xcpretty:72:in `<top (required)>'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/bin/xcpretty:23:in `load'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/bin/xcpretty:23:in `<main>'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/bin/ruby_executable_hooks:15:in `eval'
    from /Users/travis/.rvm/gems/ruby-2.0.0-p247/bin/ruby_executable_hooks:15:in `<main>'

This seems to be related to the Travis configuration (Mac OS X 10.8, Xcode 5.0.2). I can't reproduce this error on my machine (Mac OS X 10.9, Xcode 5.1).

That's not much to go on, but do you have an idea what could be the problem?

[supermarin]

This is where my Ruby / UNIX knowledge starts lacking.
There was another report like this awhile ago; the problem is that it doesn't happen all the time (I guess).

@jasperblues is this related to #36?

[supermarin]

BTW, if you export LC_CTYPE=en_US.UTF-8 before the run, does it fix the issue?

[choefele]

Yes, this fixes the problem

[0xced]

Would be nice to add a note about it in the README.

[supermarin]

@0xced would you prefer that or a Wiki FAQ section?