Debug CI failures (#4588)

* Debug CI failures

* Debugging

* Debugging

* Debugging

* Debugging

* Debugging

* Debugging

* Debugging

* Debugging

* Removed build that was failing

* Fixed URL that had changed

.github/workflows/CI.yml

@@ -470,10 +470,10 @@ jobs:
             python-version: "3.11"
             compilers: compilers
 
-          - name: PowerPC CPU Python 3.11 devtoolset-7 compilers
-            docker-image: quay.io/condaforge/linux-anvil-ppc64le
-            python-version: "3.11"
-            compilers: devtoolset-7
+          #- name: PowerPC CPU Python 3.11 devtoolset-7 compilers
+          #  docker-image: quay.io/condaforge/linux-anvil-ppc64le
+          #  python-version: "3.11"
+          #  compilers: devtoolset-7
 
           - name: ARM CPU Python 3.11 with condaforge compilers
             docker-image: quay.io/condaforge/linux-anvil-aarch64

devtools/ci/gh-actions/conda-envs/build-macos-latest.yml

@@ -16,4 +16,3 @@ dependencies:
 - pytest
 - pytest-xdist
 - pytest-timeout
-- gromacs

docs-source/usersguide/application/02_running_sims.rst

@@ -515,7 +515,7 @@ carbohydrates, include that file as well:
     forcefield = ForceField('amber14-all.xml', 'amber14/tip3pfb.xml', 'amber14/GLYCAM_06j-1.xml')
 
 Be aware that GLYCAM works somewhat differently from most force fields.  It uses
-its own nonstandard `naming convention <http://glycam.org/docs/forcefield/glycam-naming-2>`_
+its own nonstandard `naming convention <https://glycam.org/docs/forcefield/glycam-naming-2/index.html>`_
 for carbohydrates, and requires your input file to follow it.  If any residues have
 names different from what it expects, GLYCAM will be unable to assign parameters
 to them.