Skip to content

diagnostics: distinguish join-helper setup failures from pthread_join failures #2

Description

@Dmdv

Summary

Non-blocking S3 residual from final re-review at 71395f6 (ACCEPT).

When the deadline-join helper cannot be set up (e.g. pthread_attr_setdetachstate or pthread_create fails), the shutdown/join path may surface a generic pthread_join failed style diagnostic rather than a setup-specific reason.

Where

  • src/worker.cawp_pthread_join_deadline / join_exited_deadline error paths

Expected

Log or return path should distinguish:

  1. helper attr / create failure
  2. target pthread_join failure after helper ran
  3. deadline timeout (already distinct: return 1 / quarantine)

Severity

S3 / diagnostics — behavior remains fail-closed (no joinable helper leak after 71395f6).

Origin

Final re-review residual after S3 close of setdetachstate error handling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions