Re: Improving tracking/processing of buildfarm test failures

Hello hackers,

Please take a look at the July report on buildfarm failures:
# SELECT br, COUNT(*) FROM failures WHERE dt >= '2026-07-01' AND
 dt < '2026-08-01' GROUP BY br;
REL_14_STABLE: 15
REL_15_STABLE: 10
REL_16_STABLE: 19
REL_17_STABLE: 14
REL_18_STABLE: 20
REL_19_STABLE: 76
master: 157
-- Total: 311
(Counting test failures only, excluding indent-check, Configure, Build
errors, also excluding failures from fruitcrow.)

# SELECT COUNT(*) FROM (SELECT DISTINCT issue_link FROM failures WHERE
 dt >= '2026-07-01' AND dt < '2026-08-01');
26

# SELECT issue_link, COUNT(*) FROM failures WHERE dt >= '2026-07-01' AND
 dt < '2026-08-01' GROUP BY issue_link ORDER BY 2 DESC LIMIT 5;

https://www.postgresql.org/message-id/f071e691-5930-4738-9dbd-43ed2da367fe%40gmail.com : 39
-- plpython tests fail against python 3.14 under Valgrind

https://www.postgresql.org/message-id/667f7dcf-404b-4898-a426-57ca6e0617f6%40gmail.com : 36
-- aio tests failing on newer Linux kernels

https://www.postgresql.org/message-id/3614163.1784163070%40sss.pgh.pa.us : 28
-- 036_sequences.pl fails against slow builds due to REFRESH SEQUENCES conflict with worker (after f38afa4ab)
-- Fixed

https://www.postgresql.org/message-id/CAD21AoCZY1fKYgfkvHGWGiXpatUKd23FSLnDCL4m9bWFjdXNZw@mail.gmail.com : 25
-- 051_effective_wal_level.pl fails due to write to already-closed pipe (after 6a80179f6)
-- Fixed

https://www.postgresql.org/message-id/d92b18e8-00aa-4c32-95ff-7d807a427481%40vondra.me : 10
-- occasional ECPG failures on dikkop (FreeBSD) due to non-thread-safe snprintf

# SELECT COUNT(*) FROM failures WHERE dt >= '2026-07-01' AND
 dt < '2026-08-01' AND issue_link IS NULL; -- Unsorted/unhelpful failures
123

Short-lived failures: 68

Best regards,
Alexander