Re: Anti-critical-section assertion failure in mcxt.c reached by walsender
От | Andrew Dunstan |
---|---|
Тема | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender |
Дата | |
Msg-id | b191b1cb-3f0e-8beb-5dfb-90291b8eaf5b@dunslane.net обсуждение исходный текст |
Ответ на | Re: Anti-critical-section assertion failure in mcxt.c reached by walsender (Andrew Dunstan <andrew@dunslane.net>) |
Список | pgsql-hackers |
On 5/7/21 11:27 AM, Andrew Dunstan wrote: > On 5/7/21 12:38 AM, Andres Freund wrote: >> Hi, >> >> On 2021-05-07 00:30:11 -0400, Tom Lane wrote: >>> Andres Freund <andres@anarazel.de> writes: >>>> On 2021-05-06 21:43:32 -0400, Tom Lane wrote: >>>>> That I'm not sure about. gdb is certainly installed, and thorntail is >>>>> visibly running the current buildfarm client and is configured with the >>>>> correct core_file_glob, and I can report that the crash did leave a 'core' >>>>> file in the data directory (so it's not a case of systemd commandeering >>>>> the core dump). Seems like core-file collection should've worked >>>>> ... unless maybe it's not covering TAP tests at all? >>>> I suspect that is it - there's not really a good way for the buildfarm >>>> client to even know where there could be data directories :(. >>> Does it need to? I'm envisioning "find tmp_check -name '$core_file_glob'" >>> or something along that line. >> Yea, it'd be doable that way. It'd be a bit harder to associate the core >> files with specific tests though. But I now checked, and it indeed >> checks for core files in a specific subset of tests, and that that test >> only globs inside the passed-in datadir. >> > working on it ... > > > cheers > > see <https://github.com/PGBuildFarm/client-code/commit/5361bb5ff01ee47e8998f5f8f44732ccc5a01183> cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: