Packages listed for igwn conda environment are the same as for igwn-staging
Summary
The documentation pages for the conda environments provide links to download yaml files with the list of packages in the corresponding conda environment.
For example, for the igwn
(python 3.10) environment the documentation page is https://computing.docs.ligo.org/conda/environments/igwn/ and the 4 links to the yaml files are:
- https://computing.docs.ligo.org/conda/environments/linux-64/igwn-py310.yaml
- https://computing.docs.ligo.org/conda/environments/osx-64/igwn-py310.yaml
- https://computing.docs.ligo.org/conda/environments/osx-arm64/igwn-py310.yaml
- https://computing.docs.ligo.org/conda/environments/win-64/igwn-py310.yaml
For the igwn-staging
(python 3.10) environment the documentation page is https://computing.docs.ligo.org/conda/environments/igwn-staging/ and the 4 links to the yaml files are:
- https://computing.docs.ligo.org/conda/environments/linux-64/igwn-py310-staging.yaml
- https://computing.docs.ligo.org/conda/environments/osx-64/igwn-py310-staging.yaml
- https://computing.docs.ligo.org/conda/environments/osx-arm64/igwn-py310-staging.yaml
- https://computing.docs.ligo.org/conda/environments/win-64/igwn-py310-staging.yaml
I downloaded the files for the igwn
(python 3.10) and for the igwn-staging
(python 3.10) environments and noticed that the list of packages (including versions and build strings) in the files is the same when comparing same system-arch.
Being the igwn
environment a (link to a) tagged (i.e. stable) environment, I would expect the corresponding yaml files to only change when a new tagged environment is released. On the other hand, being the igwn-staging
environment a (link to a) non-stable environment, I expect it to change nearly day by day.
Steps to reproduce
Execute
wget https://computing.docs.ligo.org/conda/environments/linux-64/igwn-py310.yaml
wget https://computing.docs.ligo.org/conda/environments/linux-64/igwn-py310-staging.yaml
diff -w igwn-py310.yaml igwn-py310-staging.yaml
and notice there are no differences in the list of packages.
Same is true for the other system-arch: osx-64
, osx-arm64
and win-64
.
What is the current bug behavior?
There are no differences in the list of packages for the igwn
and igwn-staging
environments.
What is the expected correct behavior?
At this point in time, when the last tagged environments were released almost 3 months ago (on July 11th), there should be differences in the list of packages for the igwn
and igwn-staging
environments, because the igwn-staging
environment woule evolve, while the igwn
environment would stay fixed (until the next new tag release).