Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.4.6
1.5.1
Issue ID
DSTR-1149
Regression
No
Test results are logged in the wrong Editor's Console when two Editor instances are running simultaneously
How to reproduce:
1. Open any project
2. Open the attached “ReproProject” to have two projects running simultaneously
3. In the “ReproProject” project, open the Test Runner window
4. Select the Player tab
5. Click the Run All button
6. Observe the Console of both projects.
Expected result: Tests are completed with a status of “failed,” and errors are displayed in the Console of the “ReproProject” project
Actual result: Tests do not finish, and no errors are logged in the Console of the “ReproProject” project, errors are logged in the other project instead
Reproducible with: 1.4.1 (2022.3.62f1), 1.4.6 (2022.3.62f1), 1.5.1(6000.0.49, 6000.1.3f1, 6000.2.0b1)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
All player communication is routed back into only one active editor instances - this means, that all messages, including test communications will arrive to one editor, no matter which one launched the player. We recommend only running tests in the Player with one editor instance open.