Read about our upcoming Code of Conduct on this issue

Commit 98e44975 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

Heptapod CI: reducing additional wait time.

The problem seemed to be related to just initialized instances. Let's
hope our prebootstrapped ones don't suffer for it. In any case they
create motivation to remove unnecessary latency, since they start much
faster.

Ideally, we should just have a better detection of the condition with
retry provided by the Heptapod and Project classes. We'll see.
parent 306720477f5b
......@@ -27,7 +27,7 @@ if [ "$HEPTAPOD_HG_NATIVE" = "yes" ]; then
COMMON_FLAGS="${COMMON_FLAGS} --heptapod-hg-native"
fi
if tox -- $COMMON_FLAGS --heptapod-wait-after-first-response 180; then
if tox -- $COMMON_FLAGS --heptapod-wait-after-first-response 30; then
echo "First pass succeeded"
exit 0
fi
......
......@@ -25,7 +25,7 @@ chown -R git:git .
GIT_HOME=`ls -d ~git` # for explicit guaranteed forwarding
chown git:git $GIT_HOME
TOX="sudo -u git HOME=$GIT_HOME /opt/gitlab/embedded/bin/tox -e omnibus"
INITIAL_WAIT=180
INITIAL_WAIT=30
for MARKER in fs_access services; do
echo "Running functional tests marked with $MARKER"
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment