what's going on with lapwing?
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Andrew Dunstan <adunstan@postgresql.org>, pgbuildfarm@rjuju.net
Date: 2025-03-03T19:38:06Z
Lists: pgsql-hackers
lapwing has been failing sepgsql-check for over a month, but there's no log file: https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=lapwing&dt=2025-03-03%2016%3A29%3A50&stg=contrib-sepgsql-check I feel like something must be broken with logfile collection in the buildfarm client, because I keep seeing failures like this where there's no log to view. It's hard to know whether this is a configuration issue with this BF member or whether something actually needs fixing. In any case, we should try to figure out what's going on here. Apologies if this has been discussed elsewhere and I have missed it. Pointers appreciated. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
Revert workarounds for -Wmissing-braces false positives on old GCC
- 618c64ffd396 18.0 landed
-
Convert sepgsql tests to TAP
- aeb8ea361a0a 18.0 cited