Skip to content

CI smoke-test: fail on any signal-kill, not just SIGKILL (137) #89

Description

@jcfischer

Non-blocking follow-up from PR #88 review.

The macOS binary smoke-test currently fails only on exit 137 (SIGKILL — the unsigned-binary symptom #88 targeted). Other signal-kills (SIGSEGV=139, SIGABRT=134) currently pass as "ok". A future enhancement could treat any rc >= 128 (signal-terminated) at startup as a failure, catching a broader class of broken-binary regressions.

Scope note: deliberately out of scope for #88, which targeted the codesign/SIGKILL issue specifically. Low priority.

Source: sage review of #88.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions