Open samcook opened 4 years ago
@NikolayPianikov any thoughts on this?
@rprouse I missed it. @samcook Sorry for delay, I will try to reproduce
Edit: After spending a couple of hours, I found out that my case is not directly related to I/O or streams. Somehow TeamCity ignores CultureInfo instances I set on the fly. That is way more interesting. Sorry to bother. https://stackoverflow.com/questions/4732805/wrong-currentculture-when-running-an-nunit-test-in-teamcity/65161987#65161987
Hi, I'm having the same error on non-latin chars with the following configuration:
- nunit-console 3.10.0 | 3.11.0 | 3.11.1 (all three versions yield the same error in my case)
- additional cmd line parameter on "nunit--encoding=utf-8"
- Agent with the parameter "teamcity.runner.commandline.stdstreams.encoding=UTF-8"
- NUnit.Extension.TeamCityEventListener Version 1.0.7 (%teamcity.tool.NuGet.CommandLine.DEFAULT%\tools\nuget.exe install NUnit.Extension.TeamCityEventListener -Version 1.0.7 -o packages) initial step.
Any update on this? Thanks.
Hi,
I'm running a set of nunit tests on Teamcity 2020.1 (build 78475).
Everything was working fine using nunit-console 3.10.0, but I've updated to nunit-console 3.11.1 and now I'm getting the following error while running a test case with some non-ASCII characters (
Øçtanüŵ
) in the test data.The TC server logs contain the following details:
Maybe related to #71?
I've tried adding
--encoding=utf-8
to the nunit console parameters, and also settingteamcity.runner.commandline.stdstreams.encoding
toUTF-8
in the build step configuration parameters as suggested in #36, but I'm still getting the error.