zachgk commented on issue #15548: MXNet GPU build on CPU machine fails
URL: 
https://github.com/apache/incubator-mxnet/issues/15548#issuecomment-521490427
 
 
   @DickJC123 Can you take a look at another case of this? We run a nightly 
maven snapshot pipeline in the CI that builds for GPU on a CPU machine as well. 
However, it now seems to be failing some Scala unit tests that are run (still 
on the CPU machine while building for GPU). It fails either when trying to 
create a KVStore or use a DataIterator (MXDataIterNext).
   
   The error message it fails with is (from 
http://jenkins.mxnet-ci.amazon-ml.com/job/restricted-publish-artifacts/job/master/208/):
   ```
   org.apache.mxnet.MXNetError: [20:13:12] 
/work/mxnet/3rdparty/dmlc-core/include/dmlc/threadediter.h:472: [20:13:12] 
include/mxnet/base.h:459: Check failed: e == cudaSuccess (30 vs. 0) :  CUDA: 
unknown error
   Stack trace:
     [bt] (0) /work/mxnet/scala-package/native/target/libmxnet.so(+0x54430b) 
[0x7f95a73f130b]
     [bt] (1) /work/mxnet/scala-package/native/target/libmxnet.so(+0x2a8d4a5) 
[0x7f95a993a4a5]
     [bt] (2) /work/mxnet/scala-package/native/target/libmxnet.so(+0x346eee5) 
[0x7f95aa31bee5]
     [bt] (3) /work/mxnet/scala-package/native/target/libmxnet.so(+0x9395bd) 
[0x7f95a77e65bd]
     [bt] (4) /work/mxnet/scala-package/native/target/libmxnet.so(+0x2c63b3f) 
[0x7f95a9b10b3f]
     [bt] (5) /work/mxnet/scala-package/native/target/libmxnet.so(+0x2c0a564) 
[0x7f95a9ab7564]
     [bt] (6) /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x91c10) 
[0x7f979d4e7c10]
     [bt] (7) /lib/x86_64-linux-gnu/libpthread.so.0(+0x8184) [0x7f979e671184]
     [bt] (8) /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f979eda203d]
   ```
   
   It builds MXNet using the script at 
https://github.com/apache/incubator-mxnet/blob/master/tools/staticbuild/build.sh
 and sets up cuda for building using 
https://github.com/apache/incubator-mxnet/blob/master/tools/setup_gpu_build_tools.sh.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to