From ed9430e6b9cf2829f88f2d0023f7951a1908515c Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Mon, 4 May 2020 12:42:32 +0530 Subject: [PATCH] [test] Provide 1.0G rather than 1G for integration tests 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 --- .circleci/integration-test.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.circleci/integration-test.py b/.circleci/integration-test.py index 7afbe88..0c47235 100755 --- a/.circleci/integration-test.py +++ b/.circleci/integration-test.py @@ -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 # to need at least this much RAM to build. Boo? # If we change this, need to change all other references to this number. - '--memory', '1G', + '--memory', '1.0G', ] if bootstrap_pip_spec: