You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2017/11/20 14:33:12 UTC

[GitHub] marcoabreu opened a new issue #8726: CI: Remove building from Unit Test-Jobs

marcoabreu opened a new issue #8726: CI: Remove building from Unit Test-Jobs
URL: https://github.com/apache/incubator-mxnet/issues/8726
 
 
   At the moment the compile-stages are kept pretty generic while language-specific builds are being executed during the Unit Test-Stage. In order to improve future scalability these two steps should be two separate jobs. This can be done in two ways:
   
   1. Add an second build-stage which executes language-specific actions. Disadvantage: This increases the total duration as all jobs have to finish until the next stage can be started.
   2. Nested jobs: If a Unit Test requires previous actions, split it into two jobs which are getting executed in sequence. This will allow in future to execute CPU-heavy tasks on a CPU-instance and GPU-tests on a GPU-instance.
   
   Execution in separate jobs allows reusing the created artifacts if multiple jobs exist for the same language.
   For examples consider looking in the Jenkinsfile at R: CPU/GPU, Scala: CPU and Perl: CPU/GPU (perl-package.test.sh).

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services