Re: coredump and traceback on the CI

чт, 20 окт. 2022 г. в 23:09, William Lallemand : > On Thu, Oct 20, 2022 at 10:51:23PM +0500, Илья Шипицин wrote: > > I would suggest to display vtest result failure only if vtest failed, > > haproxy/vtest.yml at master · haproxy/haproxy (github.com) > > < >

Re: coredump and traceback on the CI

On Thu, Oct 20, 2022 at 10:51:23PM +0500, Илья Шипицин wrote: > I would suggest to display vtest result failure only if vtest failed, > haproxy/vtest.yml at master · haproxy/haproxy (github.com) > > > I doubt if

Re: coredump and traceback on the CI

I would suggest to display vtest result failure only if vtest failed, haproxy/vtest.yml at master · haproxy/haproxy (github.com) I doubt if there could be coredump together with successful vtest just curious,

coredump and traceback on the CI

Hello List, I had some difficulties today to reproduce a bug which was only visible on the alpine container CI. So I found some way to investigate directly from the CI. The attached patch enables the coredumps and does a "gdb -ex 'thread apply all bt full'" for the alpine/musl job. I think this