From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
---|---|
To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: Improving tracking/processing of buildfarm test failures |
Date: | 2025-02-06 21:00:30 |
Message-ID: | d6f3a7a9-ec0c-461d-a703-21ddfcdf511b@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Kuroda-san,
06.02.2025 10:55, Hayato Kuroda (Fujitsu) wrote:
> Dear hackers,
>
> I hope I'm on the correct thread. If not, please let me know.
> I found a BF failure, which may be a long-standing test issue. If so, I want you to
> update the Wiki page.
Thank you for attention to the failure! I've added it to the list.
Maybe you could also start a separate discussion dedicated to this
concrete issue, but I think we can continue here as well.
> I found the failure at [1]. It contains two ERRORs, and I'm saying for
> test_decoding/isolation/slot_creation_error.
>
> Failed test
> =======
> Failed test has two sessions, and they work:
>
> 1. Open a session, s1, and start a transaction.
> 2. Open another session, s2, and try to create a slot. It waits...
> 3. On s1, execute a pg_terminate_backend($s2).
> 4. On s1, confirm the slot creation fails.
>
> The actual difference is shown [2]. ' s2_init' is a step for slot creation.
> We can see that the isolation tester detects a process termination and exit.
Couldn't you suggest where to put, say, sleep(), to reproduce this failure
reliably?
Best regards,
Alexander Lakhin
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-02-06 21:05:02 | Re: Using Expanded Objects other than Arrays from plpgsql |
Previous Message | Masahiko Sawada | 2025-02-06 20:47:52 | Re: Conflict detection for update_deleted in logical replication |