zhangyiss/the-littlest-jupyterhub
1
0
Fork 0
mirror of https://github.com/jupyterhub/the-littlest-jupyterhub.git synced 2025-12-18 21:54:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

[test] Provide 1.0G rather than 1G for integration tests

Browse Source 
I couldn't figure out why JupyterLab fails to build
with 1G on initial commit, but succeeds if you do a bunch
of other commits after. Previously, I binary searched
down from 2G. Here, I just add a new, no-op commit
to see if that helps
This commit is contained in:
YuviPanda
2020-05-04 12:42:32 +05:30
parent 1c7e89ab1e
commit ed9430e6b9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.circleci/integration-test.py
View File

@@ -32,7 +32,7 @@ def run_systemd_image(image_name, container_name, bootstrap_pip_spec):
# This is the minimum VM size we support. JupyterLab extensions seem # This is the minimum VM size we support. JupyterLab extensions seem
# to need at least this much RAM to build. Boo? # to need at least this much RAM to build. Boo?
# If we change this, need to change all other references to this number. # If we change this, need to change all other references to this number.
'--memory', '1G', '--memory', '1.0G',
] ]
if bootstrap_pip_spec: if bootstrap_pip_spec: