The cook step for iOS tests are outputting logs like this:
[info] [Cook BootIOS IOS] File '.uet/tmp/Project12104250227703450680/Plugins/P/Binaries/Mac/UnrealEditor-Matchmaking.dylib' was produced by Assemble Project BootIOS/ProjectPackage_12104250227703450680_Project and Build Editor BootIOS Mac/ProjectPackage_12104250227703450680_EditorBinaries
[info] [Cook BootIOS IOS] File '.uet/tmp/Project12104250227703450680/Plugins/P/Binaries/Mac/UnrealEditor-MatchmakingMatchmaker.dylib' was produced by Assemble Project BootIOS/ProjectPackage_12104250227703450680_Project and Build Editor BootIOS Mac/ProjectPackage_12104250227703450680_EditorBinaries
[info] [Cook BootIOS IOS] File '.uet/tmp/Project12104250227703450680/Plugins/P/Binaries/Mac/UnrealEditor-MatchmakingTests.dylib' was produced by Assemble Project BootIOS/ProjectPackage_12104250227703450680_Project and Build Editor BootIOS Mac/ProjectPackage_12104250227703450680_EditorBinaries
The issue is that the plugin gets built and packaged for a boot test, and assembled into the test project (which is both the test project + plugin including binaries).
Then, when "Build Editor BootIOS Mac" runs, it's rebuilding the plugin binaries and including them in the tagged output:
This results in both the "Assemble Project BootIOS" and "Build Editor BootIOS Mac" producing plugin binaries.
This doesn't seem to cause a build failure, but we should figure out a way to resolve this ambiguity (perhaps by marking the plugin as "precompiled" for the purposes of boot tests so that it is never rebuilt?)
The cook step for iOS tests are outputting logs like this:
The issue is that the plugin gets built and packaged for a boot test, and assembled into the test project (which is both the test project + plugin including binaries).
Then, when "Build Editor BootIOS Mac" runs, it's rebuilding the plugin binaries and including them in the tagged output:
This results in both the "Assemble Project BootIOS" and "Build Editor BootIOS Mac" producing plugin binaries.
This doesn't seem to cause a build failure, but we should figure out a way to resolve this ambiguity (perhaps by marking the plugin as "precompiled" for the purposes of boot tests so that it is never rebuilt?)