On 2026-06-22 Mo 11:00 PM, Alexander Lakhin wrote:
Hello Andrew,
16.05.2026 14:22, Andrew Dunstan wrote:
OK, I have found and fixed the buildfarm bug. See
<https://github.com/PGBuildFarm/client-code/commit/55fdf7e0aa355600512a26cdd159b974498f802e>
It will be in the next release, but meanwhile I have deployed it on
drongo and fairywren.
Fairywren has failed 005_char_signedness.pl yesterday [1]:
Restoring global objects in the new cluster ok
Restoring database schemas in the new cluster
*failure*
Consult the last few lines of
"C:/tools/xmsys64/home/pgrunner/bf/root/REL_18_STABLE/pgsql.build/testrun/pg_upgrade/005_char_signedness/data/t_005_char_signedness_new_data/pgdata/pg_upgrade_output.d/20260622T020818.960/log/pg_upgrade_dump_1.log"
for
the probable cause of the failure.
Failure, exiting
[02:08:41.260](23.954s) not ok 13 - run of pg_upgrade
But still no pg_upgrade logs to find out what caused the failure,
unfortunately.
Could you have a look once more, please?
[1]
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2026-06-22%2002%3A03%3A10
Unfortunately it was not keeping the directories around on R18. I have
turned that on for now.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
