Patchwork [4,of,8,"STABLE] tests: increase timeout for slow test

login
register
mail settings
Submitter Pierre-Yves David
Date Feb. 24, 2019, 7:42 p.m.
Message ID <e1e189e4b1780a87c28f.1551037363@nodosa.octopoid.net>
Download mbox | patch
Permalink /patch/38911/
State Accepted
Headers show

Comments

Pierre-Yves David - Feb. 24, 2019, 7:42 p.m.
# HG changeset patch
# User Pierre-Yves David <pierre-yves.david@octobus.net>
# Date 1551034600 -3600
#      Sun Feb 24 19:56:40 2019 +0100
# Branch stable
# Node ID e1e189e4b1780a87c28fd712d598ab6ee6ad3811
# Parent  2479767a0f4167d9dbd37e63eaacc5912a7ccfc3
# EXP-Topic test-sparse-revlog
# Available At https://bitbucket.org/octobus/mercurial-devel/
#              hg pull https://bitbucket.org/octobus/mercurial-devel/ -r e1e189e4b178
tests: increase timeout for slow test

Test case `test-sparse-revlog.t` need some artifact (a bundle) build before it
can run. The artifact is expensive to build, but can be reused from one run to
the other. We are about to update that test to make the artifact building
automatic if `--allow-slow-tests` is passed. However, we need a bump the
timeout a bit to make sure the artifact building as time to finish.

We could maybe teach run-tests.py how to directly handle such artifacts.
However since there is only one of them for now, this seems premature.

There are also some room to speed up the bundle creation for
test-sparse-revlog.t

Patch

diff --git a/tests/run-tests.py b/tests/run-tests.py
--- a/tests/run-tests.py
+++ b/tests/run-tests.py
@@ -290,7 +290,7 @@  if 'java' in sys.platform:
 defaults = {
     'jobs': ('HGTEST_JOBS', multiprocessing.cpu_count()),
     'timeout': ('HGTEST_TIMEOUT', 180),
-    'slowtimeout': ('HGTEST_SLOWTIMEOUT', 500),
+    'slowtimeout': ('HGTEST_SLOWTIMEOUT', 1500),
     'port': ('HGTEST_PORT', 20059),
     'shell': ('HGTEST_SHELL', 'sh'),
 }