zeroshade opened a new pull request, #1401: URL: https://github.com/apache/arrow-go/pull/1401
### Rationale for this change `Verify (ubuntu-latest)` in the RC workflow started failing on main and on every PR around 2026-10-21. GitHub moved `ubuntu-latest` from ubuntu-24.04 (image 20261012.334.1, passing) to ubuntu-26.04 (image 20261018.168.1, failing). On 26.04, `ci/scripts/test.sh` picks the image's default clang 21.1.8 for `-asan`, and LeakSanitizer crashes as test binaries exit in cgo packages: ``` Tracer caught signal 11: addr=0x795b2f7ff000 pc=0x0000005475ea sp=0x795b280cdc70 ==18479==LeakSanitizer has encountered a fatal error. ==18479==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc) FAIL github.com/apache/arrow-go/v18/arrow/memory/mallocator ``` Seen on main pushes (runs 39667307742, 39668138403, in `arrow/cdata` and `arrow/memory/mallocator`) and on #1395, #1397 and #1398. The last passing main run (39648059952) was on ubuntu-24.04 with the clang-19 runtime the workflow installs. ### What changes are included in this PR? Pin the Verify job's Linux runner to `ubuntu-24.04` (macOS is unchanged) and update the comment on the ASan runtime step, which still referred to `ubuntu-latest`. The check name changes from `Verify (ubuntu-latest)` to `Verify (ubuntu-24.04)`; no status checks are required on main, so nothing else needs updating. This restores the known-good toolchain; it does not fix the underlying LeakSanitizer crash on 26.04 / clang 21, which can be investigated separately before moving back to `ubuntu-latest`. ### Are these changes tested? By this PR's own RC workflow run: `Verify (ubuntu-24.04)` should pass. ### Are there any user-facing changes? No. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
