|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This is probably not related to the issue above! We have real error messaging being fired off by one of our tests around UTF characters. Jenkins is passing it along, but it or one of our reporting tools in between is turning a UTF error message into scrambled ascii at some point along the way. On a terminal, the same test displays the error message and the original UTF.
Original error message:
An error occurred in an after(:all) hook.
Errno::EPERM: Operation not permitted - Operation not permitted - some/灾备环/cool境应/path/用启动
occurred at org/jruby/RubyFile.java:1063:in `unlink'
Jenkins reported error:
An error occurred in an after(:all) hook.
Errno::EPERM: Operation not permitted - Operation not permitted - some/�备环/cool境应/path/用�动 occurred at org/jruby/RubyFile.java:1063:in
`unlink'}}
The build goes on to succeed, but I think Jenkins or one of our tools is mangling the UTF of the error output by the time it ends up in the job log. Cheers! C