Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKw8F-00022h-IK for pgsql-hackers@arkaria.postgresql.org; Fri, 18 Feb 2022 05:48:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nKw8D-0003UV-Sw for pgsql-hackers@arkaria.postgresql.org; Fri, 18 Feb 2022 05:48:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKw8B-0003UM-Qm for pgsql-hackers@lists.postgresql.org; Fri, 18 Feb 2022 05:48:37 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKw84-0000xH-98 for pgsql-hackers@postgresql.org; Fri, 18 Feb 2022 05:48:34 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 858F35C0248; Fri, 18 Feb 2022 00:48:26 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 18 Feb 2022 00:48:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; bh=Wauv6XLZ9L9u18HQ8tOVXgGKg0X3wy/mIti3+V bKdWo=; b=mtv8nXTBbUe0d+lQRrrEZ5yKrf/K7Ei4gyqdO46WMK28OepjQXdfFs eQbHxfepdYW/oeSc5DdasD9fjib194SaFioIatZ3UpijtzmQM5D9q96zuU2yF1Uh NuACxdlPMn3I0eOxHaeRXNzx9gUGkU02+Rkx7JtFY6nRY0+pZmuCXgv9Nzm93qyU KFLJBCDhj3xCFCklslcAIbGDY6uTV2C7urq/JIPNx84BCxeNprctHoLRSmzdGbkb p4ZBbAz2/sYa7/7SvPNxfsnG8RW0yqGPjop20p8QbWOUmYFqSU/Czc3ljn3O4Bt9 RXrlYKO1atfAN+RRf4YsVWIZpOLifuew== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Wauv6XLZ9L9u18HQ8 tOVXgGKg0X3wy/mIti3+VbKdWo=; b=VS8GmVU2RKnmbKCyeEdEDbnGAbgF2810p 5GzKLbKwbvvS5aFBzqTpR5yndmvSj6mh771r8WBydLgGQfagyO7XB97ynfKIrbCC liO1LcllZJWxWvgI6SomW6PHwusYEljkhGTMLi63+0j7T3ngOEzXICkO2Z3lFtZ+ mxPQgnrai/J5AbvNYyNzKcfF3fCBvGDA2Oz7sK7gCXGN+ii9Axmwnsfl5GS6Ts3w /BDGtjmGQsvNZPlljHynUy/KDFoDzEaacZqccQMNvPgJT1dPEGnJhpu76thX9uzs o0EoVnzMOGZkNuv5n9F4G1qxdzL1aym2gkPuS9v6Zo21+LK+DKe4A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeelgdekjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomheptehnughrvghs ucfhrhgvuhhnugcuoegrnhgurhgvshesrghnrghrrgiivghlrdguvgeqnecuggftrfgrth htvghrnhepudekhfekleeugeevteehleffffejgeelueduleeffeeutdelffeujeffhfeu ffdunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprg hnughrvghssegrnhgrrhgriigvlhdruggv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 18 Feb 2022 00:48:26 -0500 (EST) Date: Thu, 17 Feb 2022 21:48:25 -0800 From: Andres Freund To: Noah Misch Cc: pgsql-hackers@postgresql.org Subject: Re: Timeout control within tests Message-ID: <20220218054825.vhoiv2f7vgwdsnnb@alap3.anarazel.de> References: <20220218052842.GA3627003@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220218052842.GA3627003@rfd.leadboat.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2022-02-17 21:28:42 -0800, Noah Misch wrote: > I propose to have environment variable PG_TEST_TIMEOUT_DEFAULT control the > timeout used in the places that currently hard-code 180s. Meson's test runner has the concept of a "timeout multiplier" for ways of running tests. Meson's stuff is about entire tests (i.e. one tap test), so doesn't apply here, but I wonder if we shouldn't do something similar? That way we could adjust different timeouts with one setting, instead of many different fobs to adjust? Greetings, Andres Freund