| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | pgpool-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgpool: Test: stabilize 006.memqcache regression test. |
| Date: | 2026-10-08 23:16:25 |
| Message-ID: | E1xExLd-00000004TEF-2Pu6@gothos.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-committers |
Test: stabilize 006.memqcache regression test.
This commit attempts to stabilize the test, which occasionally fails.
Inspecting the buildfarm log showed that test2 failed.
test failed in test case 2
In the test2 pgproto is used to drive the test. The test data
includes erroneous query "SELECT setseed(10)" to see if pgpool correctly
handles an error response. In the PostgreSQL log, the error response
definitely returned to pgpool.
19025 2026-10-04 10:36:06.988 UTC ERROR: setseed parameter 10 is out of allowed range [-1,1]
However, pgppol log said that shutdown sequence started before the error.
2026-10-04 10:36:06.450: main pid 18965: LOG: exit handler called (signal: 2)
I suspect pgproto was terminated by timeout command before processing
the error response, because 10:36:06.450 is 1 second past from pgproto
started (10:36:05.488) and pgproto was started by timeout command to
give the runtime limit up to 1 second.
So, let's make the timeout from 1 to 5 second.
Backpatch-through: v4.3
Branch
------
V4_4_STABLE
Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=fbd8951c9137792e0be1f6fc5ce8a4c5aeeaaa07
Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2026-10-08 23:16:30 | pgpool: Test: stabilize 006.memqcache regression test. |
| Previous Message | Tatsuo Ishii | 2026-10-08 23:16:20 | pgpool: Test: stabilize 006.memqcache regression test. |