From a0844c4b56fc8451313e37194aac8be2fd647914 Mon Sep 17 00:00:00 2001
From: Tobias Henkel <tobias.henkel@bmw.de>
Date: Mon, 6 Apr 2020 20:07:24 +0200
Subject: [PATCH] Retry nodeenv creation

We saw some failures while creating the nodeenv so add a retry there.

Change-Id: I97d65a31a4d1170e3aa2dae730e6e52e47780c82
---
 tools/pip.sh | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/tools/pip.sh b/tools/pip.sh
index 47b5027f7f..8dda202d72 100755
--- a/tools/pip.sh
+++ b/tools/pip.sh
@@ -23,7 +23,15 @@ then
     pip install nodeenv
     # Initialize nodeenv and tell it to re-use the currently active virtualenv
     # TODO(jeblair): remove node version pin.  upath 1.0.4 objects to node >9.
-    nodeenv --python-virtualenv -n 10.16.0
+    attempts=0
+    until nodeenv --python-virtualenv -n 10.16.0; do
+        ((attempts++))
+        if [[ $attempts > 2 ]]
+        then
+            echo "Failed creating nodeenv"
+            exit 1
+        fi
+    done
     # Use -g because inside of the virtualenv '-g' means 'install into the'
     # virtualenv - as opposed to installing into the local node_modules.
     # Avoid writing a package-lock.json file since we don't use it.