Re: BF assertion failure on mandrill in walsender, v13 - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: BF assertion failure on mandrill in walsender, v13
Date
Msg-id 482ba30e-d055-a14a-bae6-7987fee665a9@dunslane.net
Whole thread Raw
In response to Re: BF assertion failure on mandrill in walsender, v13  (Noah Misch <noah@leadboat.com>)
Responses Re: BF assertion failure on mandrill in walsender, v13  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 6/10/21 1:47 AM, Noah Misch wrote:
> On Thu, Jun 10, 2021 at 10:47:20AM +1200, Thomas Munro wrote:
>> Not sure if there is much chance of debugging this one-off failure in
>> without a backtrace (long shot: any chance there's still a core
>> file?)
> No; it was probably in a directory deleted for each run.  One would need to
> add dbx support to the buildfarm client, or perhaps add support for saving
> build directories when there's a core, so I can operate dbx manually.
>
>


This is what the setting "keep_error_builds" does. In the END handler it
renames the build and install directories with a timestamp. Cleanup is
left to the user.

I don't have much knowledge of dbx, but I would take a patch for support.


cheers


andrew

-- 

Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options
Next
From: Anastasia Lubennikova
Date:
Subject: Re: Testing autovacuum wraparound (including failsafe)