Closed
Description
Describe the bug
We’ve run Blast python tests on each test mode 10 times and the results show that running tests in parallel modes (EditorSharedTest
and EditorParallelTest
) results in random tests failing.
Executions | EditorSharedTest | EditorParallelTest | EditorBatchedTest | EditorSingleTest |
---|---|---|---|---|
1 | ok | ok | ok | ok |
2 | ok | Failed .F...FF. | ok | ok |
3 | Failed ......F. | ok | ok | ok |
4 | ok | ok | ok | ok |
5 | Failed ....F... | Failed ...F.... | ok | ok |
6 | ok | ok | ok | ok |
7 | ok | Failed ..F..... | ok | ok |
8 | Failed .F...... | ok | ok | ok |
9 | Failed ....F... | Failed .......F | ok | ok |
10 | ok | Failed ....F... | ok | ok |
They all report the same error, which is an immediate editor crash before it gets to execute the test, and it leaves no log available.
E Test CRASHED, return code 0xc000041d
E ---------------
E | Stacktrace |
E ---------------
E -- No crash log available --
Steps to reproduce
Steps to reproduce the behavior:
- Build ALL targets of O3DE using
AutomatedTesting
project - Run Asset Processor, wait until all assets are processed and close Asset Processor.
- Edit
o3de\AutomatedTesting\Gem\PythonTests\Blast\TestSuite_Main.py
and set all tests to one test mode: EditorSharedTest, EditorParallelTest, EditorBatchedTest, EditorSingleTest. - Open a terminal, go to AutomatedTesting folder and run the following command to run python tests:
o3de\AutomatedTesting>..\python\python.cmd -m pytest .\Gem\PythonTests\Blast\TestSuite_Main.py --build-directory=build\windows\bin\profile\
- Run the command 10 times and check results.
- Go to step 3 and run the tests in another test mode.
Expected behavior
All tests pass in all tests modes.
Actual behavior
Random failures happen when running tests in parallel modes: EditorSharedTest and EditorParallelTest
Desktop/Device (please complete the following information):
- Device: PC
- OS: Windows
- Version 10
Metadata
Metadata
Assignees
Labels
Categorizes issue or PR as related to a bug.Major priority. Work that should be handled after all blocking and critical work is done.Categorizes an issue or PR as relevant to SIG Content.Categorizes an issue or PR as relevant to SIG SimulationCategorizes an issue or PR as relevant to SIG Testing.Discussion involving the Technical Steering Committee
Activity