marcoabreu commented on a change in pull request #20138:
URL: https://github.com/apache/incubator-mxnet/pull/20138#discussion_r610025602



##########
File path: ci/docker/runtime_functions.sh
##########
@@ -783,11 +783,11 @@ unittest_ubuntu_python3_cpu_onednn() {
     export MXNET_SUBGRAPH_VERBOSE=0
     export MXNET_ENABLE_CYTHON=0
     export DMLC_LOG_STACK_TRACE_DEPTH=100
-    OMP_NUM_THREADS=$(expr $(nproc) / 4) pytest -m 'not serial' -k 'not 
test_operator' -n 4 --durations=50 --cov-report xml:tests_unittest.xml 
--verbose tests/python/unittest
+    OMP_NUM_THREADS=$(expr $(nproc) / 4) pytest -m 'not serial' -k 'not 
test_operator' -n 4 --durations=50 --cov=./contrib --cov=./python/mxnet 
--cov-report xml:tests_unittest.xml --verbose tests/python/unittest
     MXNET_ENGINE_TYPE=NaiveEngine \
-                     OMP_NUM_THREADS=$(expr $(nproc) / 4) pytest -m 'not 
serial' -k 'test_operator' -n 4 --durations=50 --cov-report 
xml:tests_unittest.xml --cov-append --verbose tests/python/unittest
-    pytest -m 'serial' --durations=50 --cov-report xml:tests_unittest.xml 
--cov-append --verbose tests/python/unittest
-    pytest --durations=50 --cov-report xml:tests_mkl.xml --verbose 
tests/python/mkl
+                     OMP_NUM_THREADS=$(expr $(nproc) / 4) pytest -m 'not 
serial' -k 'test_operator' -n 4 --durations=50 --cov=./contrib 
--cov=./python/mxnet --cov-report xml:tests_unittest.xml --cov-append --verbose 
tests/python/unittest
+    pytest -m 'serial' --durations=50 --cov=./contrib --cov=./python/mxnet 
--cov-report xml:tests_unittest.xml --cov-append --verbose tests/python/unittest
+    pytest --durations=50 --cov=./contrib --cov=./python/mxnet --cov-report 
xml:tests_mkl.xml --verbose tests/python/mkl

Review comment:
       Can't we have this in some configuration file instead of inlining it 
everywhere?




-- 
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:
[email protected]


Reply via email to