[BUG] Cancellation fixture fails in deep temporary directories #174

Closed
opened 2026-10-21 00:39:14 +02:00 by erikinkinen · 2 comments
Owner

Summary

The real boot-tool cancellation test fails when its owned temporary directory has
a long absolute path. It binds an absolute AF_UNIX address even though the child
already has an explicit working directory.

Reproduction

At Integration 160525b785c9620eeddbf2ff9b11c2ffd7fe9c03, set TMPDIR to a long
owned directory and run the maintained module with its usual Cargo environment:

python3 -m unittest discover -s tests -p boot_tool_owned_producer_test.py -v

The cancellation case fails at server.bind(str(path)) before starting the
producer. The complete host run reproduced this failure once.

Expected and actual behavior

The test should reach its original cancellation, socket EOF and inner/outer
native-custody assertions. Instead, it raises OSError: AF_UNIX path too long.
The other twelve tests in the module passed.

Environment and identity

Integration 160525b785c9620eeddbf2ff9b11c2ffd7fe9c03, Linux x86_64 and Python
3.14. This is a host fixture failure; the producer had not started when the
address was refused.

Evidence and prior checks

The original module returned 1 after thirteen tests, with one setup error and
positive retirement of its original module owner. The correction uses a short
relative address inside the same owned directory and restores the parent's
working directory before spawning. The existing lifetime control deliberately
selects a directory whose absolute socket address is refused. Separate bind,
listen and pipe refusals must preserve the first error and admit no child.

Tracking

Keep the original failed whole-suite outcome. Complete coverage can combine the
unchanged modules' actual results with the corrected module's new result after
checking their source and fixture correspondence.

Related work: PR 12.

  • Reproduce the failure in a long owned temporary directory.
  • Bind the short socket name inside that same directory.
  • Keep the real cancellation, EOF and both original custody assertions.
  • Cover setup refusal and pass the changed module and affected CI.
## Summary The real boot-tool cancellation test fails when its owned temporary directory has a long absolute path. It binds an absolute AF_UNIX address even though the child already has an explicit working directory. ## Reproduction At Integration `160525b785c9620eeddbf2ff9b11c2ffd7fe9c03`, set `TMPDIR` to a long owned directory and run the maintained module with its usual Cargo environment: ```sh python3 -m unittest discover -s tests -p boot_tool_owned_producer_test.py -v ``` The cancellation case fails at `server.bind(str(path))` before starting the producer. The complete host run reproduced this failure once. ## Expected and actual behavior The test should reach its original cancellation, socket EOF and inner/outer native-custody assertions. Instead, it raises `OSError: AF_UNIX path too long`. The other twelve tests in the module passed. ## Environment and identity Integration `160525b785c9620eeddbf2ff9b11c2ffd7fe9c03`, Linux x86_64 and Python 3.14. This is a host fixture failure; the producer had not started when the address was refused. ## Evidence and prior checks The original module returned 1 after thirteen tests, with one setup error and positive retirement of its original module owner. The correction uses a short relative address inside the same owned directory and restores the parent's working directory before spawning. The existing lifetime control deliberately selects a directory whose absolute socket address is refused. Separate bind, listen and pipe refusals must preserve the first error and admit no child. ## Tracking Keep the original failed whole-suite outcome. Complete coverage can combine the unchanged modules' actual results with the corrected module's new result after checking their source and fixture correspondence. Related work: [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Reproduce the failure in a long owned temporary directory. - [x] Bind the short socket name inside that same directory. - [x] Keep the real cancellation, EOF and both original custody assertions. - [x] Cover setup refusal and pass the changed module and affected CI.
Author
Owner

Fixed in a27acd3a6c. The listener uses a relative name in the same owned directory, and restores the original working directory and signal mask before spawning. All 14 module tests pass, including real cancellation and bind/listen/pipe refusal controls.

The original failed whole run remains recorded. Its 198 unchanged passing modules plus the corrected module cover all 2,198 current cases locally; CI remains a separate open criterion.

Fixed in a27acd3a6cb4db13e821bb5cca28cb2ec0fda453. The listener uses a relative name in the same owned directory, and restores the original working directory and signal mask before spawning. All 14 module tests pass, including real cancellation and bind/listen/pipe refusal controls. The original failed whole run remains recorded. Its 198 unchanged passing modules plus the corrected module cover all 2,198 current cases locally; CI remains a separate open criterion.
Author
Owner

The host step in CI 2945 at a27acd3a6c completed all 199 modules and 2,198 cases successfully, including all 14 socket-module tests. It then advanced to the Timed and helper checks. The affected host step is complete, so this regression is closed.

The original failed run remains retained. The separate deadline failure in CI 2942 is tracked in #175; the rest of CI 2945 is still running.

The host step in CI 2945 at a27acd3a6cb4db13e821bb5cca28cb2ec0fda453 completed all 199 modules and 2,198 cases successfully, including all 14 socket-module tests. It then advanced to the Timed and helper checks. The affected host step is complete, so this regression is closed. The original failed run remains retained. The separate deadline failure in CI 2942 is tracked in [#175](https://git.erikinkinen.fi/erix/integration/issues/175); the rest of CI 2945 is still running.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:20 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#174
No description provided.