Closed consideRatio closed 1 year ago
It seems that jupyterhub 1.3.0, also up to 1.5.1 (latest 1.5.1) has spawn failures now. But I'm very confused why they would have been introduced out of the blue.
This compares pinning jupyerhub 1.5.1 vs 2.3.1, only they change in a recently run job and that makes the difference.
Looking back and rerunning the last successful 1.3.0 tests, we got the following dependencies installed that differs, and a failure!
-alembic==1.10.3
+alembic==1.10.4
-attrs==22.2.0
+attrs==23.1.0
-coverage==7.2.3
-cryptography==40.0.1
+coverage==7.2.4
+cryptography==40.0.2
-google-auth==2.17.2
+google-auth==2.17.3
-importlib-metadata==6.3.0
+importlib-metadata==6.6.0
-packaging==23.0
+packaging==23.1
-pyasn1==0.4.8
-pyasn1-modules==0.2.8
+pyasn1==0.5.0
+pyasn1-modules==0.3.0
-pytest==7.3.0
+pytest==7.3.1
-requests==2.28.2
+requests==2.29.0
-SQLAlchemy==2.0.9
+SQLAlchemy==2.0.11
-yarl==1.8.2
+yarl==1.9.2
I don't get why yet, but we have test failures in the main branch.
Maybe related