Improve error reporting in 027_stream_regress test
Nazir Bilal Yavuz <byavuz81@gmail.com>
From: Nazir Bilal Yavuz <byavuz81@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Date: 2025-06-30T13:01:04Z
Lists: pgsql-hackers
Attachments
- v1-0001-Improve-error-reporting-in-027_stream_regress-tes.patch (text/x-patch) patch v1-0001
Hi, This patch aims to improve 027_stream_regress test's regression test error reporting per Andres' suggestion [1]. It basically dumps 50 lines from head and tail of the regression.diff file to the failure message if both primary and standby is alive and the regression test is failed. I used the diag() function to dump regression.diff to the failure message. I am not sure if that is the best function to use, open to suggestions. One disadvantage of this patch is that regress_log_027_stream_regress has both complete and head+tail of the regression.diff file. [1] https://www.postgresql.org/message-id/k46gdpibwaevxgb3cefgkl4weykcggal6evlbg5pcei4aswtli%40wrs732j5co3p -- Regards, Nazir Bilal Yavuz Microsoft
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Improve error reporting of recovery test 027_stream_regress
- 47da198934e9 19 (unreleased) landed
-
Add PostgreSQL::Test::Cluster::read_head_tail() helper to PostgreSQL/Utils.pm
- b93f4e2f98b3 19 (unreleased) landed
-
Handle timeout in PostgreSQL::Test::Cluster::is_alive()
- cb833c1b6d19 19 (unreleased) landed
-
Check status of nodes after regression test run in 027_stream_regress
- 1e9b5140c44b 19 (unreleased) landed
-
Add PostgreSQL::Test::Cluster::is_alive()
- d4c9195eff41 19 (unreleased) landed