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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment