pg.ddx.io  pgpool-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pgpool: Test: stabilize 006.memqcache regression test.
6+ messages / 1 participants
[nested] [flat]

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-06 06:04  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-06 06:04 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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.

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=106613a0be94d137488728ddba608c17ab707...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-08 23:16  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-08 23:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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_3_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=4bccb818299bd2476105e060c41c45a01039f...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-08 23:16  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-08 23:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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=fbd8951c9137792e0be1f6fc5ce8a4c5aeeaa...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-08 23:16  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-08 23:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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_5_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=b368b10a7eea75ced6bb7c151dbe7093c841f...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-08 23:16  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-08 23:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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_6_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=d73298e0f9e073780b2ef624dbec43f4543af...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* pgpool: Test: stabilize 006.memqcache regression test.
@ 2026-10-08 23:16  Tatsuo Ishii <ishii@postgresql.org>
  0 siblings, 0 replies; 6+ messages in thread

From: Tatsuo Ishii @ 2026-10-08 23:16 UTC (permalink / raw)
  To: pgpool-committers@lists.postgresql.org

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_7_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=525a5982de11d1d208b97a2242464d1c6b040...

Modified Files
--------------
src/test/regression/tests/006.memqcache/test.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2026-10-08 23:16 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-10-06 06:04 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>
2026-10-08 23:16 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>
2026-10-08 23:16 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>
2026-10-08 23:16 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>
2026-10-08 23:16 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>
2026-10-08 23:16 pgpool: Test: stabilize 006.memqcache regression test. Tatsuo Ishii <ishii@postgresql.org>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox