Re: Improving tracking/processing of buildfarm test failures

Hello hackers,

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

# SELECT br, count(*) FROM failures WHERE dt >= '2025-01-01' AND
 dt < '2025-02-01' GROUP BY br;
REL_13_STABLE: 1
REL_14_STABLE: 1
REL_15_STABLE: 4
REL_16_STABLE: 12
REL_17_STABLE: 10
master: 64
-- Total: 92
(Counting test failures only, excluding indent-check, Configure, Build
errors.)

# SELECT COUNT(*) FROM (SELECT DISTINCT issue_link FROM failures WHERE
 dt >= '2025-01-01' AND dt < '2025-02-01');
19

# SELECT issue_link, count(*) FROM failures WHERE dt >= '2025-01-01' AND
 dt < '2025-02-01' GROUP BY issue_link ORDER BY 2 DESC LIMIT 4;
https://www.postgresql.org/message-id/559462.1737760111%40sss.pgh.pa.us : 17
-- Fixed

https://www.postgresql.org/message-id/a9a97e83-9ec8-5de5-bf69-80e9560f5345@gmail.com : 11

https://www.postgresql.org/message-id/657815a2-5a89-fcc1-1c9d-d77a6986bc26@gmail.com : 9

https://www.postgresql.org/message-id/3611540.1737518430%40sss.pgh.pa.us : 7

# SELECT count(*) FROM failures WHERE dt >= '2025-01-01' AND
 dt < '2025-02-01' AND issue_link IS NULL; -- Unsorted/unhelpful failures
18

Short-lived failures:
30

I've also offloaded past year's content of the "Known Buildfarm Test Failures" page to:
https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures_-_Archive

Best regards,
Alexander Lakhin
Neon (https://neon.tech)