Mike Balfour 0ae123eae6 Fix AssetContainer behavior with immediate load errors ...

The AssetContainer was getting "stuck" in the case that it tried to load a missing asset that was already registered with the AssetManager as missing. This fixes the bug, as well as adding a unit test for the specific condition.

2021-05-13 16:08:47 -05:00

..

AssetCommon.cpp

Disable weak references and unit tests for them.

2021-04-22 15:02:41 -05:00

AssetDataStreamTests.cpp

Initial commit

2021-03-08 14:30:57 -08:00

AssetManagerLoadingTests.cpp

disable AssetJobsFloodTest.ContainerCoreTest_BasicDependencyManagement_Success test (#703)

2021-05-11 15:23:43 -07:00

AssetManagerStreamingTests.cpp

Fix AssetContainer behavior with immediate load errors

2021-05-13 14:10:45 -05:00

BaseAssetManagerTest.cpp

Initial commit

2021-03-08 14:30:57 -08:00

BaseAssetManagerTest.h

Initial commit

2021-03-08 14:30:57 -08:00

MockLoadAssetCatalogAndHandler.h

Initial commit

2021-03-08 14:30:57 -08:00

TestAssetTypes.h

[LYN-3464] Vegetation unit tests intermittently failed due to an AssetManager bug. Inside the AssetContainer, if the root asset finished loading during the container initialization, the CheckReady() call at the end of initialization would detect the loaded asset, but would skip sending out notifications because the initialized flag wasn't set yet. This would lead to an extra asset reference remaining in the AssetManager itself, would would then cause errors when the asset handler for that asset got removed.

2021-05-04 09:04:18 -05:00