szha opened a new issue #18723:
URL: https://github.com/apache/incubator-mxnet/issues/18723


   ## Description
   
   Currently the instructions for interactive shell with the test environment 
on CI for reproducing and debugging tests is not documented on cwiki or the 
website. The process involves:
   
   
   1. observe the failed pipeline and examine the log to find the test
   
![image](https://user-images.githubusercontent.com/2626883/87608515-fb416000-c6b4-11ea-8d43-b94eaaf84adc.png)
   
   1. find the Jenkins file that corresponds to the failed pipeline in 
[ci/jenkins](https://github.com/apache/incubator-mxnet/tree/master/ci/jenkins). 
In this case it's 
[Jenkins_centos_gpu](https://github.com/apache/incubator-mxnet/blob/master/ci/jenkins/Jenkinsfile_centos_gpu)
   
   1. find the failed test step in the Jenkins file, and the build step that 
produces the binary it uses. in this case the test step is 
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkinsfile_centos_gpu#L45
    and its corresponding build step is
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkinsfile_centos_gpu#L39
   
   1. go to 
[ci/jenkins/Jenkins_steps.groovy](https://github.com/apache/incubator-mxnet/blob/master/ci/jenkins/Jenkins_steps.groovy)
 to find the corresponding build step 
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkins_steps.groovy#L733-L745
   note down the docker and runtime function to invoke. in this case it's
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkins_steps.groovy#L739
   
   1. in the same file, find the test step
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkins_steps.groovy#L1027-L1038
   note down the docker and runtime function. in this case it's
   
https://github.com/apache/incubator-mxnet/blob/e2366e9102e6862416bf998af52baaa5e9c0a31b/ci/jenkins/Jenkins_steps.groovy#L1033
   
   1. run the command to trigger the build of the tested binary with the above 
docker name and runtime function. in this case the command should be:
   `ci/build.py --platform centos7_gpu_cu102 /work/runtime_functions.sh 
build_static_libmxnet cu102`
   
   1. wait for the build to complete. afterwards, to run the complete test 
suite, run the test step command
   `ci/build.py --platform centos7_gpu_cu102 /work/runtime_functions.sh 
ci_package_pypi cu102`
   
   1. to launch the interactive shell, we need to first locate the docker id 
from the docker files in 
[ci/docker](https://github.com/apache/incubator-mxnet/tree/master/ci/docker). 
in this case it's
   
   1. with the docker id, run
   ```
   docker run -it --rm -v  $(PWD):/work/mxnet mxnetci/build.centos7_cpu:latest 
/bin/bash
   ```


----------------------------------------------------------------
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


Reply via email to