test pipeline, why not returning 1 on python test error??????

[3dprintscanner]

This change captures the exit code from the python unit tests. This now results in a failed build as the tests cannot find the python -> c++ bindings. This appears to be a conda / pyenv issue and seems like the build python module isn't getting loading into the environment when traversing into the test directory.

# save the package at given folder, then we can upload using singa-*.tar.bz2 suffix=$TRAVIS_JOB_NUMBER #TZ=Asia/Singapore date +%Y-%m-%d-%H-%M-%S` export CONDA_BLD_PATH=~/conda-bld-$suffix mkdir $CONDA_BLD_PATH

conda build tool/conda/singa --python 3.6 conda install --use-local singa cd test/python $HOME/miniconda/bin/python run.py echo $? `

This causes a module import error and the tests fail.

Would like to debug, however need access to the build agent to further investigate the best way of setting this up

[3dprintscanner]

Further to this, it appears that on Ubuntu 18.04, the conda config for building the library pulls the 3.x.x version of libprotobuf, changing the build to go against the 2.x.x protobuf version causes this to break from a broken linked dependency in _singa_wrap.so

[moazreyad]

This PR is required for enabling the python test with continuous integration. Without this PR, the user must check the error messages of the python test manually by looking at the log and the python test errors are not shown as check errors in Travis CI or Github Actions.

Here is the Gihub action with python errors without this PR (the check passes even if there are errors) and here is the Github action with this PR (the check fails correctly due to errors in python test).