Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/98252
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 71a2c32: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
720f5cc to
9f65121
Compare
|
Currently trying to figure out how opinionated I should be in the container. I prefer clang and lldb, hence some scripts to do that. Ideally there would be some user defined mix-ins that can be added to customize to the users preferences, still trying to figure that. @ZainRizvi I would be curious for the devx take on this specifically around choice of base docker image, perhaps I should be using an existing CI reference? I have been running this on my local devcontainer and can build Pytorch with these settings: Also since the cluster has Docker installed, this does work pretty seamlessly there as well and can build with same settings. I am going to create a cuda build |
There was a problem hiding this comment.
Thanks for taking this on, it's a great PR to see!
I see you're following the instructions from README.md to setup this image. I do like the idea of using our existing CI base images instead for an even more consistent debugging experience though. @huydhn, would you be able to point him to a good image to use?
cc: @malfet
There was a problem hiding this comment.
Thank you for working on this.
I think base image shouldn't matter(as long as it reasonably recent), nor choice of compiler (though I guess VSCode is better at parsing clang errors than CPP ones
Please move update_laternatives to .devicontainer/scripts folder rather than keep it in top level directory.
Also, I'm curious, why not have single Dockerfile, with an extra step for CUDA (which is triggered via arg in devcontainer.json)
There was a problem hiding this comment.
And so on..
| local master=${3} | |
| local slaves=${4} | |
| local leader=${3} | |
| local follower=${4} |
There was a problem hiding this comment.
while I don't agree with the terminology, it is very present in the man pages for update-alternatives: https://man7.org/linux/man-pages/man1/update-alternatives.1.html
There was a problem hiding this comment.
Ok. But please move this script to .devcontainer folder. Or perhaps delete it altogether, if you don't plan to configure clang as default compiler.
There was a problem hiding this comment.
Let's not merge commented out code
There was a problem hiding this comment.
I have tested this workflow I can build with clang succesfully on CPU but when trying to compile with CUDA:
#$ "/usr/bin"/clang -D__CUDA_ARCH__=520 -D__CUDA_ARCH_LIST__=520 -E -x c++
-DCUDA_DOUBLE_MATH_FUNCTIONS -D__CUDACC__ -D__NVCC__
"-I/opt/conda/bin/../include" -D__CUDACC_VER_MAJOR__=11
-D__CUDACC_VER_MINOR__=8 -D__CUDACC_VER_BUILD__=89
-D__CUDA_API_VER_MAJOR__=11 -D__CUDA_API_VER_MINOR__=8
-D__NVCC_DIAG_PRAGMA_SUPPORT__=1 -include "cuda_runtime.h" -m64
"CMakeCUDACompilerId.cu" -o "tmp/CMakeCUDACompilerId.cpp1.ii"
/usr/bin/clang: /opt/conda/bin/../lib/libtinfo.so.6: no version information
available (required by /usr/lib/x86_64-linux-gnu/libLLVM-11.so.1)
/usr/bin/clang: /opt/conda/bin/../lib/libtinfo.so.6: no version information
available (required by /usr/lib/x86_64-linux-gnu/libedit.so.2)
/usr/bin/clang: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libLLVM-11.so.1: undefined symbol:
ffi_type_sint32, version LIBFFI_BASE_7.0
# --error 0x7f --
Call Stack (most recent call first):
/opt/conda/share/cmake-3.22/Modules/CMakeDetermineCompilerId.cmake:6 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
/opt/conda/share/cmake-3.22/Modules/CMakeDetermineCompilerId.cmake:48 (__determine_compiler_id_test)
/opt/conda/share/cmake-3.22/Modules/CMakeDetermineCUDACompiler.cmake:298 (CMAKE_DETERMINE_COMPILER_ID)
cmake/public/cuda.cmake:47 (enable_language)
cmake/Dependencies.cmake:43 (include)
CMakeLists.txt:710 (include)
I think this has to do with the mismatch between conda install cuda libs. I can remove this Clang stuff entirely but not sure
There was a problem hiding this comment.
What about turning this into an ARG instead, like the other sections?
|
@pytorchbot merge |
Merge failedReason: This PR needs a If not, please add the To add a label, you can comment to pytorchbot, for example For more information, see Details for Dev Infra teamRaised by workflow job |
|
❌ 🤖 pytorchbot command failed: Try |
|
@pytorchbot merge |
Merge failedReason: This PR needs a If not, please add the To add a label, you can comment to pytorchbot, for example For more information, see Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: This PR is too stale; the last push date was more than 3 days ago. Please rebase and try again. You can rebase and merge by leaving the following comment on this PR: Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
e42d96f to
71a2c32
Compare
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
Thanks very much for add this! is it possible to set up one for MacOS plus AMD GPU? |
|
@GZ82 |
# Summary <!-- copilot:summary --> ### <samp>🤖 Generated by Copilot at 293ded1</samp> This pull request adds support for using Visual Studio Code Remote - Containers extension with the pytorch project. It adds a `.devcontainer` folder with a `devcontainer.json` file, a `Dockerfile`, and a `noop.txt` file that configure and create a dev container with Anaconda and Python 3. <!-- copilot:poem --> ### <samp>🤖 Generated by Copilot at d6b9cd7</samp> > _`devcontainer.json`_ > _Configures PyTorch containers_ > _For CPU or GPU_ ## Related to: pytorch#92838 Pull Request resolved: pytorch#98252 Approved by: https://github.com/ZainRizvi
Summary
🤖 Generated by Copilot at 293ded1
This pull request adds support for using Visual Studio Code Remote - Containers extension with the pytorch project. It adds a
.devcontainerfolder with adevcontainer.jsonfile, aDockerfile, and anoop.txtfile that configure and create a dev container with Anaconda and Python 3.🤖 Generated by Copilot at d6b9cd7
Related to:
#92838
cc @ZainRizvi @kit1980 @huydhn @clee2000