search

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.
https://aka.ms/vscode-remote
Other
3.6k stars 273 forks source link

Spontaneous Stop / build failure of extension without error #10074

Closed flipphillips closed 1 month ago

flipphillips commented 1 month ago

Steps to Reproduce:

  1. Build / rebuild (w/ or w/o cache) a Dockerfile that contains a RUN with complex build (basically, large number of files) SuiteSparse
  2. Build with -j $(nproc) or with single process
  3. Build via make library to build monolithicly or via individual builds (e.g., cd AMD && make && make install for each submodule, for simplicity)
  4. Monitor build log (would be neat to not have to manually click every time, FR)
  5. At some point during the build, the extension will just 'give up' and report Stop. The Stop is never at the same location, seems to be pseudo-non-deterministic. For example - 
1.041 SuiteSparse/CSparse/Source/cs_schol.c
[2024-07-17T16:00:11.895Z] 1.041 SuiteSparse/CSparse/Source/cs_spsolve.c
1.041 SuiteSparse/CSparse/Source/cs_sqr.c
1.041 SuiteSparse/CSparse/Source/cs_symperm.c
1.041 SuiteSparse/CSparse/Source/cs_tdfs.c
[2024-07-17T16:00:11.912Z] Stop (17176 ms): Run: /usr/share/code/code /home/flip/.vscode/extensions/ms-vscode-remote.remote-containers-0.377.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/flip/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-69b100a2-a02b-4c2b-a53b-eaefccaee2111721231994402 --workspace-folder /home/flip/GitHub/Surround360 --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/flip/GitHub/Surround360 --id-label devcontainer.config_file=/home/flip/GitHub/Surround360/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/flip/GitHub/Surround360/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root --include-configuration --include-merged-configuration
[2024-07-17T16:00:11.912Z] Exit code 1
[2024-07-17T16:00:11.915Z] Command failed: /usr/share/code/code /home/flip/.vscode/extensions/ms-vscode-remote.remote-containers-0.377.0/dist/spec-node/devContainersSpecCLI.js up --user-data-folder /home/flip/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/data --container-session-data-folder /tmp/devcontainers-69b100a2-a02b-4c2b-a53b-eaefccaee2111721231994402 --workspace-folder /home/flip/GitHub/Surround360 --workspace-mount-consistency cached --id-label devcontainer.local_folder=/home/flip/GitHub/Surround360 --id-label devcontainer.config_file=/home/flip/GitHub/Surround360/.devcontainer/devcontainer.json --log-level debug --log-format json --config /home/flip/GitHub/Surround360/.devcontainer/devcontainer.json --default-user-env-probe loginInteractiveShell --remove-existing-container --mount type=volume,source=vscode,target=/vscode,external=true --skip-post-create --update-remote-user-uid-default on --mount-workspace-git-root --include-configuration --include-merged-configuration
[2024-07-17T16:00:11.915Z] Exit code 1

No compile error, no other indication of failure.

Does this issue occur when you try this locally?: No Does this issue occur when you try this locally and all extensions are disabled?: NA

I tried with both the prerelease and release version.

remoteContainers-2024-07-17T15-59-54.657Z.log

flipphillips commented 1 month ago

This might be pilot error - There is a CUDA build failure somewhere that seems to cascade and cause this error, but it isn't picked up until much later.

chrmarti commented 1 month ago

Thanks for the update. I guess docker build tries to run things in parallel as much as possible, maybe that results in some logs continuing to arrive while the build has already failed elsewhere. Can this issue be closed?

flipphillips commented 1 month ago

Parallel log information confused me :)