Search Issue Tracker
Fixed
Fixed in 1.1.33
Votes
0
Found in [Package]
1.1.31
Issue ID
DSTR-442
Regression
No
[UTF] LogAssert.Expect fails when called multiple times with asynchronous logs
Reproduction steps:
1. Open user-submitted project
2. Open Test Runner window. Window > General > Test runner
3. Select Play Mode
4. Run all tests
Expected result: both tests should succeed
Actual result: both tests fail
Reproducible with: 1.1.30, 1.1.31 (2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5)
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
- Crash on ScriptableBatchRenderer::GenerateBuiltInCBuffer when opening a project after adding HDRP Samples to a specific project
- ArgumentException is thrown and reference is missing when deserializing and using MultiColumnListView
- “You may not pass in objects that are already persistent” error is thrown when entering the Play Mode and the "Active Input Handling" system was changed in a custom Build Profile
- [Linux] Assertion failed on expression 'success && actual == size' error is thrown when building project to another partition with a different file system
- Import Activity window shows "(None)" in the Asset field when changing the path of the asset
Resolution Note (fix version 1.1.33):
* Fixed issue where using Assert.Expect with the same string multiple times can lead to incorrect errors in some cases (DSTR-442).
* Improved the logging when using multiple Assert.Expect and the logs appears in another order than expected (DSTR-442).