`build -s libs.pretest` fails on Linux

[jkotas]

Repro:

Run ./build.sh -s libs.pretest on Linux

Result:

  Determining projects to restore...
/home/jkotas/runtime/.dotnet/sdk/5.0.100-rc.2.20479.15/NuGet.RestoreEx.targets(19,5): error : The result "" of evaluating the value "$(DotNetBuildTasksSharedFrameworkTaskFile)" of the "AssemblyFile" attribute in element <UsingTask> is not valid.  /home/jkotas/runtime/src/libraries/pretest.proj [/home/jkotas/runtime/Build.proj]
/home/jkotas/runtime/.dotnet/sdk/5.0.100-rc.2.20479.15/NuGet.RestoreEx.targets(19,5): error :    at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args) [/home/jkotas/runtime/Build.proj]

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[jkotas]

@jkoritzinsky Could you please route this?

Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Description:	Repro: Run ./build.sh -s libs.pretest on Linux Result: Determining projects to restore... /home/jkotas/runtime/.dotnet/sdk/5.0.100-rc.2.20479.15/NuGet.RestoreEx.targets(19,5): error : The result "" of evaluating the value "$(DotNetBuildTasksSharedFrameworkTaskFile)" of the "AssemblyFile" attribute in element <UsingTask> is not valid. /home/jkotas/runtime/src/libraries/pretest.proj [/home/jkotas/runtime/Build.proj] /home/jkotas/runtime/.dotnet/sdk/5.0.100-rc.2.20479.15/NuGet.RestoreEx.targets(19,5): error : at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args) [/home/jkotas/runtime/Build.proj]
Author:	jkotas
Assignees:	-
Labels:	area-Infrastructure, untriaged
Milestone:	-

[ViktorHofer]

@jkotas can you please share a binlog? I'm unsure how this could ever happen and I'm inclined to believe that this actually has to do with restore failing (because of an outage right now). A binlog should tell.

[jkotas]

You are probably right. I am not able to reproduce this anymore.

If it is the case, it seems like our scripts or something in msbuild or nuget is silently ignoring errors instead of propagating them up.

[ViktorHofer]

Likely nuget but hardly actionable without logs or repro steps.