-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[DOC] Add examples of running Python unittests to docs #19253
Conversation
Hey @r3stl355 , Thanks for submitting the PR
CI supported jobs: [miscellaneous, windows-gpu, unix-cpu, edge, unix-gpu, website, clang, sanity, centos-cpu, windows-cpu, centos-gpu] Note: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we build MXNet outside of conda and use it inside conda, there can be toolchain mismatch issues causing segfault or deadlock. For example, this is known to happen when building mxnet-horovod with mpi. The reason appears to be a conflict between statically linked libraries in the conda python binary and binaries linked by the mpi integration. See dmlc/gluon-nlp#1371 for details.
As we don't have any instructions for building mxnet with the conda toolchain, how about updating this PR to be independent of conda?
Sure, I'll remove conda |
run ci [macosx-x86_64] |
run ci [centos-cpu,centos-gpu, unix-cpu] |
@mxnet-bot run ci [macosx-x86_64,centos-cpu,centos-gpu, unix-cpu] |
Jenkins CI successfully triggered : [centos-cpu, centos-gpu, unix-cpu] |
@mxnet-bot run ci [macosx-x86_64,centos-cpu,centos-gpu, unix-cpu] |
Jenkins CI successfully triggered : [centos-gpu, unix-cpu, centos-cpu] |
@mxnet-bot run ci [centos-cpu,centos-gpu, unix-cpu] |
Jenkins CI successfully triggered : [centos-gpu, unix-cpu, centos-cpu] |
@mxnet-bot run ci [edge] |
Jenkins CI successfully triggered : [edge] |
Many thanks for the contribution, Nikolay! |
Ahh, merged - thanks. I can now starting looking at something else |
Description
Added an example of running Python tests in Conda environment
Checklist
Essentials