| From: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | 002_pg_upgrade is broken for custom install |
| Date: | 2025-04-04 11:27:30 |
| Message-ID: | CAExHW5s4_hccuXNojUvLqnRC_UfNnqB+MODO=9r+hBTF0jRd1w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi All,
When oldinstall and olddump environment variables are set,
002_pg_upgrade.pl test does not finish and fails.
# initializing database system by running initdb
ok 1 - check locales in original cluster
ok 2 - loaded old dump file
# initializing database system by running initdb
ok 3 # skip source node not using default install
ok 4 - dump before running pg_upgrade
# test failed
stderr:
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 29 just after 4.
Doesn't look like it's expected.
Even if I rollback the history as far as
f52345995d3691de7b0a888903b6cfed1497c672, the failure still appears.
IIRC, the test was working fine till October 2024. But I might be
wrong. Don't have energy to try git blame right now, but might do once
I get some time.
--
Best Wishes,
Ashutosh Bapat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-04-04 11:31:59 | Re: 002_pg_upgrade is broken for custom install |
| Previous Message | Ashutosh Bapat | 2025-04-04 11:17:13 | Re: Test to dump and restore objects left behind by regression |