dotnet / dnceng

.NET Engineering Services
MIT License
24 stars 19 forks source link

The "RestoreTask" task returned false but did not log an error #3100

Open jeffschwMSFT opened 5 months ago

jeffschwMSFT commented 5 months ago

Build

https://dev.azure.com/dnceng/internal/_build/results?buildId=2474913

     2>/__w/1/s/.dotnet/sdk/9.0.100-preview.5.24307.3/NuGet.targets(170,5): error MSB4181: The "RestoreTask" task returned false but did not log an error. [/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24311.10/tools/Tools.proj]
##[error].dotnet/sdk/9.0.100-preview.5.24307.3/NuGet.targets(170,5): error MSB4181: (NETCORE_ENGINEERING_TELEMETRY=Restore) The "RestoreTask" task returned false but did not log an error.
     2>Done Building Project "/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24311.10/tools/Tools.proj" (Restore target(s)) -- FAILED.
     1>Done Building Project "/__w/1/s/.packages/microsoft.dotnet.arcade.sdk/9.0.0-beta.24311.10/tools/Build.proj" (default targets) -- FAILED.

Build leg reported

No response

Pull Request

No response

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "The \"RestoreTask\" task returned false but did not log an error",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

Additional information about the issue reported

No response

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng/internal/_build/results?buildId=2474913 Error message validated: [The "RestoreTask" task returned false but did not log an error] Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 6/17/2024 3:39:02 PM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
ericstj commented 5 months ago

Should we make this "BuildRetry": true,?

lewing commented 5 months ago

I opened https://github.com/dotnet/dnceng/issues/3139 in dnceng to track the other version of this problem

ViktorHofer commented 4 months ago

Thanks to @akoeplinger's fix in NuGet, we could resolve this by promoting a newer SDK (>= 9.0.100-preview.7.24357.2) via Arcade. @mmitche opinions? Might make sense to discuss this in Tactics tomorrow.