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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
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).