ThomasDelteil opened a new issue #11171: Flaky test: test_gluon.test_hybrid_static_memory_switching URL: https://github.com/apache/incubator-mxnet/issues/11171 test_gluon.test_hybrid_static_memory_switching http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-11024/6/pipeline/ ``` t_gluon.test_hybrid_static_memory_switching ... /work/runtime_functions.sh: line 382: 7 Segmentation fault (core dumped) nosetests-3.4 --verbose tests/python/unittest build.py: 2018-06-06 13:18:39,834 Running of command in container failed (139): docker run --rm -t --shm-size=500m -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu/build:/work/build -u 1001:1001 mxnetci/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_python3_cpu_mkldnn build.py: 2018-06-06 13:18:39,835 You can try to get into the container by using the following command: docker run --rm -t --shm-size=500m -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu/build:/work/build -u 1001:1001 -ti --entrypoint /bin/bash mxnetci/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_python3_cpu_mkldnn into container: False Traceback (most recent call last): File "ci/build.py", line 318, in <module> sys.exit(main()) File "ci/build.py", line 253, in main command=command, docker_registry=docker_registry) File "ci/build.py", line 155, in container_run raise subprocess.CalledProcessError(ret, cmd) subprocess.CalledProcessError: Command 'docker run --rm -t --shm-size=500m -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-python3-mkldnn-cpu/build:/work/build -u 1001:1001 mxnetci/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_python3_cpu_mkldnn' returned non-zero exit status 139 script returned exit code 1 ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
