Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.5.2p2
Issue ID
892237
Regression
No
Symbols are not escaped correctly or not escaped at all when using -editorTestsVerboseLog teamcity command
According to https://confluence.jetbrains.com/display/TCD10/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-Escapedvalues , lines formatted for TeamCity should have symbols escaped with | symbol instead of the usual \ symbol.
To reproduce:
1. Open the project, attached by user via command line by using this command:
Unity.exe -batchmode -projectPath %path_to_project% -runEditorTests -editorTestsResultFile "tests.xml" -editorTestsVerboseLog teamcity
2. Open Editor.log and find lines in this format:
##teamcity[testStarted name='MethodName(argument)']
3. Observe, how some symbols are not escaped correctly
Expected: symbols in a line formatted for TeamCity are escaped using | symbol
Actual: the usual \ symbol is used to escape symbols in lines formatted for TeamCity
Reproduced in 5.3.8f1, 5.4.5p1, 5.5.2p2, 5.5.3p2
Could not reproduce in 5.6 and 2017.1, because the versions use new Editor Tests Runner and editorTestsVerboseLog teamcity argument was not reimplemented there
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Add comment