From patchwork Sun Feb 24 19:42:43 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [4,of,8,"STABLE] tests: increase timeout for slow test From: Pierre-Yves David X-Patchwork-Id: 38911 Message-Id: To: mercurial-devel@mercurial-scm.org Date: Sun, 24 Feb 2019 20:42:43 +0100 # HG changeset patch # User Pierre-Yves David # 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 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'), }