Conda env silently fails when the pip section has error

[gabrielelanaro]

I don't know if this is fixable (or if it should be fixed) in the role as it's technically a problem of conda env, but basically when there's a mistake in the pip section of miniconda_env the process returns exit status 0, despite the fact that the command failed.

For example, given this environment.yml:

dependencies:
- pip
- pip:
  - flask-restful==0.3.5
  - /var/www/recipestore/foodlab
  - jwt==0.3.2
  - pyasn1==0.1.9
  - pycrypto==2.6.1
  - requests-cache==0.4.12
  - sqlalchemy-utils==0.32.1
name: eatingproject

The file has a mistake and prints to standard error

"/opt/miniconda/bin/conda" env update -f "/tmp/eatingproject-environment.yml" > hello
Invalid requirement: '/var/www/recipestore/foodlab'
It looks like a path. Does it exist ?

However, process has exit status 0:

echo $?
0

Is it possible to trigger a failure in this case?

btw I opened an issue here:
https://github.com/conda/conda-env/issues/255

[uchida]

It seems the problem for conda-env as you say, conda-env does not reflect pip error in its error code.
On my role side, checking stderr could help this issue, I will consider about it.

[uchida]

I tried to check stderr for conda env create, but I realized recent version of conda, 4.1.x, write stderr as warning message:

No psutil available.
To proceed, please conda install psutil

There is an option to add the role variable, miniconda_env_check_stderr or so, to check whether stderr is absent or not.

[ibayer]

Thanks for the nice role!!!

I was also victim of pip silently failing. :-(