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.94.2) (envelope-from ) id 1sIXNv-00GJUo-Be for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Jun 2024 17:40:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sIXNs-00Fmyj-I4 for pgsql-hackers@arkaria.postgresql.org; Sat, 15 Jun 2024 17:40:13 +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.94.2) (envelope-from ) id 1sIXNs-00Fmyb-8B for pgsql-hackers@lists.postgresql.org; Sat, 15 Jun 2024 17:40:13 +0000 Received: from mail-yw1-f181.google.com ([209.85.128.181]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sIXNq-001pe3-NA for pgsql-hackers@postgresql.org; Sat, 15 Jun 2024 17:40:12 +0000 Received: by mail-yw1-f181.google.com with SMTP id 00721157ae682-6333082fb8fso11893127b3.2 for ; Sat, 15 Jun 2024 10:40:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718473208; x=1719078008; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WzF+CssTeYWuwwCgc+QDZIu+J7TDp0R6QpkKCsLzz9o=; b=lAwoiS9v0RrlCPER9ujQbFw+IOul0u1rZIcFheGcvqhIyRRPAIQ3fD0Go6myRE98o2 s4tjMWS+jsJwiLD95COWplPez1QXvw65nqdMRKU9lIQITwYAxb/8G1yGAHxUQNeoZwaj VceIxrjWQaLzZxVwgqmgHfX/RC88ErfMPS4S8moFY+uV1AuawE/FCWRcC8rsW5fnuY1I MjltG8FPjyZvSsbFtf7tTAPnH/y6JqfJm+oSUuDxyQzjfG4HXHts/xFWwNbmWtcjUhza p43zg1cRYU0QjXKMpfbU5uvjxePx3LyUWto+wgiLthtFXquH5yl7ooPGJ/V3OcbqGftw Z17w== X-Forwarded-Encrypted: i=1; AJvYcCX4RtGhfTTYRFo+UCnuANxEp6eH1Vr4UrwwWoXxCAG76BKGatJ4uicWQSLouMBuPZgORN0gqg0cdu2f2oJXTuaipKKAYFDoTxViuDy3 X-Gm-Message-State: AOJu0YxEKT/CqmIlW9oI00hS7WEYxhQfgQDzjRuvbfoGb+svwkLnrW9M pfTWTj0zBf6K4wLaL+A/zIIR6FMrb2+evdFVfj9vyi/O9s2iRBELrv1ncxI9Ka9e8Cp/SmkiGo4 xa4trE6BD/lkI9EcTjGW8Yi5OTKpX8LOr5RTfyA== X-Google-Smtp-Source: AGHT+IF8j+Juj+OgJiBTRFpdZemoTe7INzIUucFehjdlq+G9874yxpqDc43OejLJXc/iCoFuDaIJT4gwl60F0A9QC3I= X-Received: by 2002:a05:690c:6a12:b0:620:31ca:599d with SMTP id 00721157ae682-63222d4b77dmr65296647b3.29.1718473208476; Sat, 15 Jun 2024 10:40:08 -0700 (PDT) MIME-Version: 1.0 References: <20240612155040.u6cvatdb5tiwcxci@awork3.anarazel.de> <2302192.1718380169@sss.pgh.pa.us> In-Reply-To: From: Jelte Fennema-Nio Date: Sat, 15 Jun 2024 19:39:57 +0200 Message-ID: Subject: Re: RFC: adding pytest as a supported test framework To: Robert Haas Cc: Andrew Dunstan , Tom Lane , Jacob Champion , Daniel Gustafsson , Andres Freund , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, 15 Jun 2024 at 19:27, Robert Haas wrote: > This surprises me. I agree that the current state of affairs is kind > of annoying, but the contents of regress_log_whatever are usually > quite long. Printing all of that out to standard output seems like > it's just going to flood the terminal with output. I don't think I'd > be a fan of that change. I think at the very least the locations of the different logs should be listed in the output.