Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8fti-000liN-2N for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2026 14:53:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w8fth-00C7Oq-1N for pgsql-hackers@arkaria.postgresql.org; Fri, 03 Apr 2026 14:53:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w8fth-00C7Oi-0N for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2026 14:53:21 +0000 Received: from mail-wm1-x329.google.com ([2a00:1450:4864:20::329]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1w8fte-00000000OBt-3nrq for pgsql-hackers@lists.postgresql.org; Fri, 03 Apr 2026 14:53:21 +0000 Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-48334ee0aeaso18650675e9.1 for ; Fri, 03 Apr 2026 07:53:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1775227998; x=1775832798; darn=lists.postgresql.org; h=content-disposition:mime-version:message-id:subject:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=j5NUW6MK72nPrgtBdsiWz0WGnYD9tAvE9emscHG3buQ=; b=lGYNKJaz/3c6dqbax6AYERpjVwdTogHhtHvAZotGylPrNzFQEZdIgGv/2rBh5jzZsN IM+QW3ofSpvQGDsqHGPOrWjYoCbimP7clX1hDCvuVyG9mPwqIUJXgdlIvpAxLngnpIdo 6SM6Ustv42ip3pcuiuC5djsgom/KKcbEJ+tYzAYMuBw1BiVsTrW1RQL4ZHJQeSAijWnq kmA9rcWzVtvZOuAd+5gF61K+EwsIcj35r6vHQFzVtwO0o9LnqvXSPbOr0C1AtbMquG4b Q3skHP3WS0369mKY9UlFBhXrDaha6x0mWI9ENTSObrIoS+2PCZegr64DTAnhKp23+buY YUAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1775227998; x=1775832798; h=content-disposition:mime-version:message-id:subject:to:from:date :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=j5NUW6MK72nPrgtBdsiWz0WGnYD9tAvE9emscHG3buQ=; b=pVemBT6CIRpzW1eFDwxp3K/hEfo6FUjpBMmLaD2qpWU9jBAi90+2iEAxLcN0n84Yke 9OmTMRHzAVNImw+gOBjrgfIb2Mp0TIpR3FJhfUQOQwO2Kn4JpmvmO1RCneL83IHojAAx tXhN9FMmCaiLHBcfRwfGdLhofv7890aJ0sGBO1dRBheQwATknTT89iMTaOEWtVGw9vcX ernW1hiLnTMrciiVTcP54qNmpU6mvfxQLvgygMsRCIpNRMc8NqaebnB7z3K+rSgE1QF/ z6wkkR2xcukOyUK0dC6AtwR8Q/NbxhCbh5LMmfboOTH/ZN74gsYqTNJ97SvNgJCtKh8L nzEg== X-Gm-Message-State: AOJu0Yx/EFFWgnKN5Ue8RrXXg6au+neDggRm1uIUiuppxbVcnh1oC+Q0 Idnxj3U6G2w3DS1pJsaUVyN+6lCehtUl+aIf+J/1JS1YfqX2G9XkO5fcD16i0w== X-Gm-Gg: ATEYQzy8MV/hAjBDWohuEdTTx/TOwr0twp8otRC/zwlucU/xFo15DkPGZwHtinqLNdD knUiftzLgAqqsE4d3AvBC+XPUJXSl9Rc6SMChSFu5HJ420c5JWNze4oTdI/dGnzylLg86AMKO/v lP86TuRihE9X0ux8SJmL/PqxrFm0XLYXX/z03+cxHtez2sP86MQlprXLxp588hx+CTxoY1m2eit hwvUT78RLpi5OZ/qPsvgc7MKZ0gF/4+jmNpvOVpu/xhZIpprRxwYSmg3ERU2KCYpLVL8MnELUO2 vk/W4mL/kjhG2FGtE3aevNO/ZsqrU5KwA9/Oij8ExcTfY57r18Fd9IF7LLgMC5QY5yiha4oDHXp 6RaCKXILEd5fKirsRXcLNmAjjWZGfRAKk9o2daZOXvTHITjBCiOOYsjZgY8kqATTHUwc1C0I/uB shTKAOf7uI6ZJU18cSqBATkdPr8tY3+lzpu8+2QjbVPxDzYv0bZ2DIqyiPWeXHBCAiVu4kAm9dA 2uZgInECTyBkFo++XiBUPzqB4o1d2chcFkemTq31S1clJ27mbwMS2GtpA== X-Received: by 2002:a05:600c:4688:b0:486:de04:5906 with SMTP id 5b1f17b1804b1-4889978bf4amr49735535e9.19.1775227997751; Fri, 03 Apr 2026 07:53:17 -0700 (PDT) Received: from ip-10-97-1-34.eu-west-3.compute.internal (ec2-15-237-197-144.eu-west-3.compute.amazonaws.com. [15.237.197.144]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4888a7162cesm200863325e9.13.2026.04.03.07.53.16 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 03 Apr 2026 07:53:16 -0700 (PDT) Date: Fri, 3 Apr 2026 14:53:15 +0000 From: Bertrand Drouvot To: pgsql-hackers@lists.postgresql.org Subject: meson: Adjust test timeout for Valgrind builds Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="9mXTMSOWn9DVpXyR" Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --9mXTMSOWn9DVpXyR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi hackers, When building with -DUSE_VALGRIND, tests run significantly slower due to Valgrind's instrumentation overhead, causing the default 1000s test's timeout to be exceeded. Example when running the regress test suite: " $ meson test -C build -q --print-errorlogs --setup running --suite regress-running regress-running - postgresql:regress-running/regress time out (After 1000 seconds) Summary of Failures: 1/1 regress-running - postgresql:regress-running/regress TIMEOUT 1000.01s Ok: 0 Fail: 0 Timeout: 1 " PFA a patch that detects Valgrind builds using a compiler check, which correctly handles USE_VALGRIND being passed via -Dc_args, CPPFLAGS or CFLAGS and increases the test timeout to 10000s in that case. I don't have a strong opinion on the new value. In practice, the regress suite runs in about 30 seconds without Valgrind and in about 46 minutes with Valgrind on my setup. Note that the timeout is per test, not for the entire suite so that 10000s looks large enough (I tested to run the entire suite with the patch and it did not produce any timeout). Another option could be to disable the timeout on a Valgrind build (set timeout to 0) but then a test could block forever. Note that there are no changes needed for autoconf as it does not set a timeout for the tests. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com --9mXTMSOWn9DVpXyR Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v1-0001-meson-adjust-test-timeout-for-Valgrind-builds.patch"