| From: | r314tive <tanswis42(at)gmail(dot)com> |
|---|---|
| To: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, myon(at)debian(dot)org |
| Subject: | Re: ci: Skip minfree file in the cores_backtrace.sh |
| Date: | 2026-05-28 12:44:32 |
| Message-ID: | CALCfnurEnHHZB0FVei2wdiayOOEHB4=occtTLgz3bporP+KR6g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I looked at v2, focused on the cores_backtrace.sh file selection.
The patch applies cleanly on current master at
8a86aa313a714adc56c74e4b08793e4e6102b5ca.
git diff --check reports no issues, and:
sh -n src/tools/ci/cores_backtrace.sh
reports no syntax issues.
I checked the current Cirrus core-file naming and did not find a configured
name that this pattern would miss. Linux uses /tmp/cores/%e-%s-%p.core,
FreeBSD uses /tmp/cores/%N.%P.core, NetBSD/OpenBSD move *.core files into
the common directory, and macOS uses ${HOME}/cores/core.%P.
I also checked the OpenBSD cores step in the linked Cirrus run:
https://cirrus-ci.com/build/6447813132812288
It ran cores_backtrace.sh, lldb loaded /var/crash/initdb.core, and
thread backtrace all produced a backtrace.
I have not reproduced the original failure locally or run Cirrus CI myself.
Regards,
Ilmar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-05-28 12:55:46 | Re: Set notice receiver before libpq connection startup |
| Previous Message | Robert Haas | 2026-05-28 12:40:39 | Re: injection_points: Switch wait/wakeup to use atomics rather than latches |