Search Issue Tracker
Fixed
Fixed in 1.4.5
Votes
5
Found in [Package]
1.4.1
Issue ID
DSTR-1002
Regression
Yes
[Linux][Test Framework] Test Runner prevents interaction with the pause button when "Debug.Break" is used in a test
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the Test Config window (Custom > Test Config)
3. Enable the “Inspect Points” option in the Test Config window
4. Open the Test Runner window (Window > General > Test Runner)
5. Enable only the “PlayMode” option at the top of the Test Runner window
6. Run the “Test” test
7. Wait until the pause button is blue to indicate the process has been paused
8. Press the “Pause” button to unpause the Editor
Expected result: The Editor unpauses
Actual result: The Editor does not let you interact with the “Pause” button
Reproducible with: 1.3.2 (2021.3.33f1, 2022.3.14f1), 1.4.0, 2.0.1-pre.18 (2021.3.33f1, 2022.3.14f1, 2023.2.2f1, 2023.3.0a16)
Not reproducible with: 1.3.1 (2021.3.33f1, 2022.3.14f1)
Reproducible on: Ubuntu 22.04
Not reproducible on: Windows 10
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
- "Shader warning in 'Hidden/HDRP/DownsampleDepth'" warnings are thrown after building a project
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
Resolution Note (fix version 1.4.5):
A progress bar was disabled for PlayMode runs in Editor and Player. It was needlessly blocking the editor while running tests on a Player or in PlayMode.