Skip to content

Inductor test segfault on macos (and arm64) when C++ stacktraces are enabled #119905

@albanD

Description

@albanD

🐛 Describe the bug

This was discovered while working on #119408 that tries to automatically enable TORCH_SHOW_CPP_STACKTRACES for the re-runs of failing jobs.

On macos, this consistently leads to test files in test/inductor/ to segfault.

An example is https://github.com/pytorch/pytorch/actions/runs/7823402867/job/21344456540 and you can find other in the CI of the PR.
Sending a PR that removes the special case for inductor should trigger this again as well.

Versions

Main

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler

Metadata

Metadata

Assignees

No one assigned

    Labels

    module: inductoroncall: pt2triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions