Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors restoring runtime pack #32038

Closed
lewing opened this issue Apr 25, 2023 · 16 comments
Closed

Errors restoring runtime pack #32038

lewing opened this issue Apr 25, 2023 · 16 comments
Labels

Comments

@lewing
Copy link
Member

lewing commented Apr 25, 2023

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=251447
Build error leg or test failing: Microsoft.NET.Pack.Tests.dll.1.WorkItemExecution
Pull request: #32029

Error Message

Fill the error message using known issues guidance.

{
  "ErrorMessage": "The runtime pack for Microsoft.NETCore.App.Runtime.Mono.browser-wasm was not downloaded.",
  "BuildRetry": false,
  "ErrorPattern": "",
  "ExcludeConsoleLog": false
}

Report

Build Definition Test Pull Request
259234 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32163
259233 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32162
259152 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #29880
257924 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32138
257825 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32138
257319 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32137
257438 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32140
257253 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32138
256957 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32125
256853 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32128
256745 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32125
256180 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution
255837 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32104
255964 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32116
255301 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32108
255196 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32102
255158 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #30038
254960 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32103
254657 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32065
254612 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32098
254538 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32095
254545 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32096
254528 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32094
254496 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32093
254171 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #32065
253959 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution
253719 dotnet/sdk Microsoft.NET.Sdk.BlazorWebAssembly.Tests.dll.2.WorkItemExecution #29131

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
1 27 27
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Apr 25, 2023
@lewing
Copy link
Member Author

lewing commented Apr 25, 2023

@marcpopMSFT is sdk onboarded to known issues?

@marcpopMSFT
Copy link
Member

Don't think we are. Do you have a pointer to how to get onboarded?

@marcpopMSFT
Copy link
Member

Where did you get the failure details? From the raw helix logs, looks like a space issue: �[m�[37m /private/tmp/helix/working/BF5C09E5/p/d/sdk/8.0.100-ci/NuGet.targets(156,5): error : No space left on device [/private/tmp/helix/working/BF5C09E5/w/9828087B/e/testExecutionDirectory/PackMultiTargetedLibrary/PackMultiTargetedLibrary/PackMultiTargetedLibrary.csproj]

@lewing
Copy link
Member Author

lewing commented Apr 25, 2023

I saw it on several builds but it could definitely be a space issue, my attention has been split

@lewing
Copy link
Member Author

lewing commented Apr 26, 2023

@marcpopMSFT https://dev.azure.com/dnceng-public/public/_build/results?buildId=252412&view=logs&j=fa59fe4e-195c-56fa-189b-58fd241f10dd&t=71146b80-38e1-5fea-9b74-ba1045aac3e1&l=329

    Microsoft.NET.Sdk.BlazorWebAssembly.Tests.VanillaWasmTests.Build_Works [FAIL]
      Expected command to pass but it did not.
      File Name: C:\h\w\A64108EF\p\d\dotnet.exe
      Arguments: msbuild /t:Build C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj /restore
      Exit Code: 1
      StdOut:
      MSBuild version 17.7.0-preview-23225-01+6300d22b2 for .NET
        Determining projects to restore...
        Restored C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj (in 5.21 sec).
      C:\h\w\A64108EF\p\d\sdk\8.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(287,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj]
      C:\h\w\A64108EF\p\d\sdk\8.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(478,5): error NETSDK1112: The runtime pack for Microsoft.NETCore.App.Runtime.Mono.browser-wasm was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'browser-wasm'. [C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj]
      StdErr:
      
      
      Stack Trace:
           at FluentAssertions.Execution.XUnit2TestFramework.Throw(String message)
           at FluentAssertions.Execution.TestFrameworkProvider.Throw(String message)
           at FluentAssertions.Execution.DefaultAssertionStrategy.HandleFailure(String message)
           at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
           at FluentAssertions.Execution.AssertionScope.FailWith(Func`1 failReasonFunc)
           at FluentAssertions.Execution.AssertionScope.FailWith(String message)
        /_/src/Tests/Microsoft.NET.TestFramework/Assertions/CommandResultAssertions.cs(33,0): at Microsoft.NET.TestFramework.Assertions.CommandResultAssertions.Pass()
        /_/src/Tests/Microsoft.NET.Sdk.BlazorWebAssembly.Tests/VanillaWasmTests.cs(30,0): at Microsoft.NET.Sdk.BlazorWebAssembly.Tests.VanillaWasmTests.Build_Works()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
      Output:
        > C:\h\w\A64108EF\p\d\dotnet.exe msbuild /t:Build C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj /restore
        MSBuild version 17.7.0-preview-23225-01+6300d22b2 for .NET
          Determining projects to restore...
          Restored C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj (in 5.21 sec).
        C:\h\w\A64108EF\p\d\sdk\8.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(287,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy [C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj]
        C:\h\w\A64108EF\p\d\sdk\8.0.100-ci\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.FrameworkReferenceResolution.targets(478,5): error NETSDK1112: The runtime pack for Microsoft.NETCore.App.Runtime.Mono.browser-wasm was not downloaded. Try running a NuGet restore with the RuntimeIdentifier 'browser-wasm'. [C:\h\w\A64108EF\t\dotnetSdkTests\ys0g00bx.jwf\Build_Works_A---CED90528\VanillaWasm.csproj]

@lewing
Copy link
Member Author

lewing commented Apr 26, 2023

on #32048

@lewing
Copy link
Member Author

lewing commented Apr 27, 2023

Advertising manifest not updated. Manifest package for microsoft.net.sdk.testworkload doesn't exist.
Installing workload manifest microsoft.net.sdk.android version 34.0.0-preview.4.225…
Installing workload manifest microsoft.net.sdk.maui version 8.0.0-preview.3.8159…
Installing workload manifest microsoft.net.workload.mono.toolchain.current version 8.0.0-preview.4.23227.6…
Installing workload manifest microsoft.net.workload.emscripten.current version 8.0.0-preview.4.23226.1…
Installing workload manifest microsoft.net.workload.emscripten.net6 version 8.0.0-preview.4.23226.1…
Installing workload manifest microsoft.net.workload.emscripten.net7 version 8.0.0-preview.4.23226.1…
Installing workload manifest microsoft.net.workload.mono.toolchain.net6 version 8.0.0-preview.4.23227.6…
Installing workload manifest microsoft.net.workload.mono.toolchain.net7 version 8.0.0-preview.4.23227.6…
Installing pack Microsoft.NET.Runtime.WebAssembly.Sdk version 8.0.0-preview.4.23227.6...
Writing workload pack installation record for Microsoft.NET.Runtime.WebAssembly.Sdk version 8.0.0-preview.4.23227.6...
Installing pack Microsoft.NETCore.App.Runtime.Mono.browser-wasm version 8.0.0-preview.4.23227.6...
Workload installation failed. Rolling back installed packs...
Rolling back pack Microsoft.NETCore.App.Runtime.Mono.browser-wasm installation...
Rolling back pack Microsoft.NET.Runtime.WebAssembly.Sdk installation...
Uninstalling workload pack Microsoft.NET.Runtime.WebAssembly.Sdk version 8.0.0-preview.4.23227.6…
Workload installation failed: microsoft.netcore.app.runtime.mono.browser-wasm::8.0.0-preview.4.23227.6 is not found in NuGet feeds [https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/azure-public/vside/_packaging/vs-impl/nuget/v3/index.json;https://pkgs.dev.azure.com/azure-public/vside/_packaging/vs-buildservices/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-DotNet-msbuild-Trusted-8ffc3fe3/nuget/v3/index.json".](https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet7-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-libraries-transport/nuget/v3/index.json;https://pkgs.dev.azure.com/azure-public/vside/_packaging/vs-impl/nuget/v3/index.json;https://pkgs.dev.azure.com/azure-public/vside/_packaging/vs-buildservices/nuget/v3/index.json;https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-DotNet-msbuild-Trusted-8ffc3fe3/nuget/v3/index.json%22.)
##[error]Cmd.exe exited with code '1'.

Different version of the same problem, it looks like the runtime pack sometimes isn't in the feed when the build starts. This is probably happening because there is no ordering in the post build publishing and these tests are still using the most recent advertising manifest rather than the runtime version in the pr. @marcpopMSFT @dsplaisted we need to resolve the test issue.

@lewing
Copy link
Member Author

lewing commented Apr 27, 2023

It is basically #23820 but for every sdk build

@marcpopMSFT
Copy link
Member

This is because the workload install isn't using a rollback so picks up the latest one AND because the runtimepack version is tied to the workload version?

BTW, to onboard to known issues, I just needed to create the Known Build Error label. That has now been created.

@marcpopMSFT
Copy link
Member

@lewing I'm more confused now. I was expecting to only see this error in tests in the AOT legs as those legs are the ones installing wasm-tools. But I have a PR where I see this fail in the Windows NT leg. Shouldn't it be using the workloads from stage0 to resolve the runtime pack version or is something else happening here?

@lewing
Copy link
Member Author

lewing commented Apr 28, 2023

Yeah, I think the Known Issue here may be slightly different than the one I described in with the workload install comment; which is also a real issue.

@dsplaisted
Copy link
Member

@lewing I investigated this and it looks like the problem is that the microsoft.net.sdk.webassembly.pack NuGet package is setting SelfContained to true. This is not something that you can safely do in a NuGet package, because setting SelfContained to true may mean that the runtime pack needs to be downloaded, and you can't modify things in a NuGet package that would affect restore.

Can this logic be moved to the SDK or a workload or something?

@lewing
Copy link
Member Author

lewing commented May 2, 2023

yeah i think we can move it pretty easily.

cc @maraf @radical

@maraf
Copy link
Member

maraf commented May 3, 2023

Can I close the issue or is there any other problem?

@dsplaisted
Copy link
Member

We should be able to close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants