Search Issue Tracker
Fixed in 1.1.11
Votes
0
Found in [Package]
preview 0.0.4 - 1.1.3
Issue ID
1186702
Regression
No
Cancel button doesn't work as expected in Test Runner when clicked after starting the tests
How to reproduce:
1. Open attached project
2. Open Test Runner window
3. Click "Run All"
4. Immediately click the "Cancel" button from the progress dialog that shows up
5. Note that it cancels only the second test (TestTwo), but it waits until the first test (TestOne) is finished
Reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Actual results: pressing "Cancel" only takes action after the first test completes
Expected results: pressing" Cancel" cancels the test right away
Reproducible with all Test Runner versions
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment