Open Jozkee opened 2 weeks ago
Could you attach more logs from the failure? We've seen failures in our node projects on CodeSpaces before, which were fixed by increasing the number of cores used in the default devcontainer: https://github.com/dotnet/aspnetcore/issues/55272, https://github.com/dotnet/aspnetcore/pull/55479
CC @javiercn @captainsafia
Or, I wonder if this is due to dotnet/dotnet
not initializing the node-externals
submodule?
Logs from /workspaces/dotnet/artifacts/log/Release: vstest.log xdt.log arcade.log aspire.log aspnetcore.log cecil.log command-line-api.log deployment-tools.log diagnostics.log efcore.log emsdk.log fsharp.log msbuild.log nuget-client.log razor.log roslyn.log roslyn-analyzers.log runtime.log scenario-tests.log sourcelink.log symreader.log templating.log test-templates.log
fixed by increasing the number of cores used in the default devcontainer
The devcontainer loaded with 16-core • 64GB RAM • 128GB.
@Jozkee since the VMR work has been de-prioritized, we probably won't be able to investigate this for a while. In the meantime the one thing I'd suggest is turning off the npm build in the VMR context by passing --no-build-nodejs
to aspnetcore's build.sh
using Default devcontainer https://github.com/dotnet/dotnet/blob/main/.devcontainer/devcontainer.json and executing
./build.sh
, I consistently hit the following error once build starts for aspnetcore.cc @ViktorHofer @wtgodbe @mthalman @MichaelSimons @javiercn