runtime build failure: "GenerateFileVersionProps" task could not be loaded because installer.tasks.dll not found

[trylek]

Initial cost estimate: 2 days
Initial contacts: @trylek, @ViktorHofer, @safern

OS: Windows
Architecture: x86
Configuration: Release
Repro steps (non-deterministic): build clr+libs+libs.tests -a x86 -c Release

  System -> D:\git\runtime\artifacts\bin\manual.System\net6.0-Release\System.dll
  System.Data -> D:\git\runtime\artifacts\bin\manual.System.Data\net6.0-Release\System.Data.dll
  System.Xml -> D:\git\runtime\artifacts\bin\manual.System.Xml\net6.0-Release\System.Xml.dll
  ApiCompat ->
  Trimming shared framework assemblies with ILLinker...
  externals ->
D:\git\runtime\src\libraries\pretest.proj(55,5): error MSB4062: The "GenerateFileVersionProps" task could not be loaded from the assembly D:\git\runtime\artifacts\bin\installer.tasks\Debug\netstandard2.0\installer.tasks.dll. Could not load file or assembly 'D:\git\runtime\artifacts\bin\installer.tasks\Debug\netstandard2.0\installer.tasks.dll'. The system cannot find the file specified. Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

[ViktorHofer]

@trylek who reported the issue? This sounds very similar to restore issues where the build doesn't fail even though restore isn't entirely successful which is something that Nuget controls and we can't fix.

[ViktorHofer]

If it was you who encountered the issue, do you still have the full build log available to verify my assumption?

[trylek]

@ViktorHofer - yes, I hit the issue locally, happens to me quite often. I reran the build yesterday after hitting this so I'm afraid I don't have the logs readily available but I'll collect them the next time this reproes - what particular logs are you interested in? I must admit I'm not aware of any "single global log", according to my knowledge for instance CoreCLR build emits a series of smaller logs covering the various build steps (individual msbuild executions).

[ViktorHofer]

AFAIK the global build log should be in artifacts\log\$(Configuration)\. I never hit that issue so it might be related to different developer workflows. Logs should help to better understand the issue.