I think the difference is that the pytest and astropy tweaks to the end were entirely standalone and didn't impact other packages (you can do `conda install pytest=x` without having to change numpy). My new conda env changes numpy/astropy/scipy in ways that mean that you can't downgrade without changing everything and since there are packages in the new env that aren't in the old one (they split numpy and matplotlib into two) I think trying to install an old env on top causes real problems trying to resolve exactly which numpy is being used etc. You can't downgrade numpy, for example, without forcing every package to downgrade and clearly the conda solver couldn't handle it.

I have implemented the first bullet and the LSST_CONDA_ENV_NAME fix in https://github.com/lsst-sqre/ci-scripts/pull/65

I will discuss DM-23098 with Leanne later this afternoon.

@mlong executed:  
cd /project/jenkins/prod
rm -rf agent-ldfc-ws-0/ws/stack-os-matrix/centos-7.devtoolset-8.py3 agent-ldfc-ws-2/ws/stack-os-matrix/centos-7.devtoolset-8.py3 agent-ldfc-ws-4/ws/stack-os-matrix/centos-6.devtoolset-8.py3

on direction from KTL

The PR https://github.com/lsst-sqre/ci-scripts/pull/65 seems OK to me.

rm completed.

Let me know if anything else needs done from our side.