Search Issue Tracker

Fixed

Fixed in 1.4.5

Votes

2

Found in [Package]

1.3.9

Issue ID

DSTR-877

Regression

No

"WaitForEndOfFrame" call never completes when running in a UnityTest from the command line using batchmode

Package: Test-Framework

-

How to reproduce:

  1. Extract the user-attached project (Tests_UnityProj.zip)
  2. Open the terminal in the project’s parent directory
  3. Run the following command: [Unity Editor executable path]/Unity -projectPath IN-15450_Tests_UnityProj -batchmode -runTests -testPlatform playmode -testResults Logs/test_results/nunit/integration_test_results.xml -logFile Logs/unity/integration_tests.log

Expected result: The test finishes
Actual result: The test never finishes and if checking the end of the generated “Logs/unity/integration_tests.log“ file it shows that the tests stopped at the “WaitForEndOfFrame“ call

Reproducible with: 1.1.33 (2021.3.30f1, 2022.3.8f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a3), 1.3.9 (2021.3.30f1, 2022.3.8f1, 2023.1.11f1, 2023.2.0b7, 2023.3.0a3)
Reproducible on: Windows 10, Ubuntu 20.04, Intel MacOS 13.5.1

Workaround: Running the tests in the Editor GUI using the built-in Test Runner window finishes the test successfully

  1. Resolution Note (fix version 1.4.5):

    An error is now thrown if running a test using batchmode and yielding WaitForEndOfFrame, which makes the run no longer to freeze.

Log in to vote on this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues