DKIM2-Signature: i=1; m=1; t=1791063162; d=kurilemu.de;
	mf=PGFsdmhlcnJlQGt1cmlsZW11LmRlPg==;
	rt=PHBnc3FsLWhhY2tlcnNAcG9zdGdyZXNxbC5vcmc+;
	s=fm3:rsa-sha256:e4qeZJEhcMxJnLYRz67zTDCReT9CCGejKbr5jiWc3G6G75c
	fAoia57POST7UpfcCaofyWWIm+Xs/+yT32nLY9BLOz2M9pGQzEvpaKiSyLykWU5L
	uRAIIdj9oaoPmDnBNuyLuZp3x7oDUJzB1jT/MX0U606oPOoDJkQhNxYbsOsiCSVd
	ZRjcd9Qk1LtgGZ0eit/iKTpKKXB1vux3GELrCUwRUqjf7iQbHpSWO22jid1kK4iI
	wfetk/qcyVw49FMAPKDLCng7MSJYjOO+/aXntGy/oZ56X4xukmM5tidz4GCVT6Ws
	EUEIvtoSwMsOs8oW4rU71ZODKnpMgJJyd6ED1hA==;
Message-Instance: m=1;
 h=sha256:Q9ZoNxCLgR2eyYXTKndRbanpBWVq9dKo+jUTZs077L0=:w50dwrOl2B0Jofmh2ZF9RP0nsnJdesd7LXf0ficsiIc=;
Feedback-ID: ie3de48e3:Fastmail
Date: Sat, 3 Oct 2026 23:32:39 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	Narek Galstyan <narek.galstyan@enterprisedb.com>,
 pgsql-hackers@postgresql.org,
	"narekg@berkeley.edu" <narekg@berkeley.edu>, ngalstyan4@gmail.com
Subject: Re: Coverage with make coverage-html is broken on latest Debian
 using lcov v2
Message-ID: <asFzNIrD0_SAD995@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <44mk7ctqddpmo5666am4nagw4ocovrubvqjdg3zpm5t3qatwaf@qx5zshy6mogj>
Archived-At: 
 <https://www.postgresql.org/message-id/asFzNIrD0_SAD995%40alvherre.pgsql>
Precedence: bulk

On 2026-Oct-03, Andres Freund wrote:

> - The intentional use of SIGQUIT shutdowns in a lot of tests leads to
>   incomplete coverage
> 
>   That doesn't trigger gcov / lcov / genhtml errors, but it leads to things
>   being assumed uncovered that aren't.
> 
>   Because we shut down a lot of tap test clusters with immediate mode, this
>   actually has pretty large impact.
> 
>   I've experimented with replacing all the _exit() uses in the backend with
>   something that triggers flushing of the coverage information in some cases
>   that can be considered kinda maybe safe.

We had these threads about this problem
https://postgr.es/m/58ce1068-0cfc-3394-df69-ee0d03aaebb5%402ndquadrant.com
https://postgr.es/m/816a4de5-3f15-4d66-1ec1-791cab2ca6df@gmail.com
but I don't think we did anything about that.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/