Re: Improving tracking/processing of buildfarm test failures

Hello hackers,

Please take a look at the October report on buildfarm failures:

# SELECT br, COUNT(*) FROM failures WHERE dt >= '2026-10-01' AND
 dt < '2026-11-01' GROUP BY br;
REL_14_STABLE: 22
REL_15_STABLE: 14
REL_16_STABLE: 10
REL_17_STABLE: 11
REL_18_STABLE: 16
REL_19_STABLE: 34
master: 81
-- Total: 188
(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-10-01' AND dt < '2026-11-01');
30

# SELECT issue_link, COUNT(*) FROM failures WHERE dt >= '2026-10-01' AND
 dt < '2026-11-01' GROUP BY issue_link ORDER BY 2 DESC LIMIT 5;
https://www.postgresql.org/message-id/E1xJIeX-000000004Kn-0X4G%40gemulon.postgresql.org : 32
-- XversionUpgrade fails due to lack of AS in old dump (after 0497318e4)
-- Fixed

https://www.postgresql.org/message-id/E1xHNun-00000001klk-3Rjg%40gemulon.postgresql.org : 19
-- xml.sql fails due to non-ASCII characters in tag attributes hexified (after 30d4a6daa)
-- Fixed

https://www.postgresql.org/message-id/CAH2-Wzk-oO3HjLaByo8Vpse6Tpha1mqAW8DFShh-kS-Wo59ugA@mail.gmail.com : 17
-- XversionUpgrade-REL_13_STABLE-xxx fails due to amcheck complain about bpchar (after a32b8dc98)
-- Fixed

https://www.postgresql.org/message-id/4ccf62c4-48ed-47cb-badc-9ae436d91b39%40app.fastmail.com#6434c9ffe3c955bfbefb5a3748bc7d2f
: 15
-- 001_pgbench_with_server.pl fails on greenfly due to lwlock corruption

https://www.postgresql.org/message-id/CAHGQGwFWXASACRnhHJgEdk8nWyLw4bLLDhiEiKSqBqd+tzJ2Pg@mail.gmail.com
051_effective_wal_level.pl fails due to slot not dropped (after 1f2245371) : 13
-- Fixed

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

Short-lived failures: 114

I've also counted successful runs: 50396

Best regards,
Alexander