[BUG] Compiler process fixtures assume a Python executable below 1 MiB #16

Closed
opened 2026-10-12 18:48:05 +02:00 by erikinkinen · 1 comment
Owner

Summary

The compiler evidence process tests assume the selected Python fixture executable fits a fixed 1 MiB capture allowance. A larger distro interpreter causes the suite to refuse before child creation, masking the intended process ownership and cancellation controls.

Reproduction

Run the Exsh Python descriptor cleanup tests from a clean checkout of 6d1df9216920a6c86013f3c4cda93a01c096c3d6 with a Python executable larger than 1 MiB: python3 -B -Werror -m unittest discover -s tests -p 'descriptor_cleanup_*_test.py'. The executable is copied into the explicitly selected fixture directory by OwnedTests.setUp.

Expected and actual behavior

The test should allocate a selected-tool capture allowance based on that original fixture's actual executable extent and actual link payloads. Data/output allowances, production capture refusals, stall timing and total deadlines should remain independently constrained. CI instead reports eleven errors and one failed automatic-reaping refusal control; each stops at the oversized fixture capture. Production correctly rejects the insufficient allowance.

Environment and identity

  • Component repository/revision: Exsh 6d1df9216920a6c86013f3c4cda93a01c096c3d6.
  • Image profile and configuration: host Python tests; no VM/image failure is implicated.
  • Architecture and runtime: Linux x86-64; the selected CI Python executable exceeds 1 MiB. The local selected interpreter is 11,544 bytes and passes the same suite.
  • Input/session route and authority: an explicitly copied native fixture interpreter in the test's original source window; no deployment compiler approval is granted by this fixture.
  • Last known working revision: the size assumption also exists in the preceding dc24005e352fa94f730446a3b48303f0188972d7 head.

Evidence and prior checks

Exact-head failing CI run. The original complete log has been retained before repair. All twelve affected controls fail before spawning their intended child; the production aggregate input check is functioning. The same checkout passes 425 controls with the smaller local interpreter. This is a fixture portability defect, not evidence of a production admission failure.

Tracking

Related work: compiler evidence and cleanup frame design. Keep the meaningful over-budget capture control and all original output/stall/total limits when correcting the fixture.

## Summary The compiler evidence process tests assume the selected Python fixture executable fits a fixed 1 MiB capture allowance. A larger distro interpreter causes the suite to refuse before child creation, masking the intended process ownership and cancellation controls. ## Reproduction Run the Exsh Python descriptor cleanup tests from a clean checkout of `6d1df9216920a6c86013f3c4cda93a01c096c3d6` with a Python executable larger than 1 MiB: `python3 -B -Werror -m unittest discover -s tests -p 'descriptor_cleanup_*_test.py'`. The executable is copied into the explicitly selected fixture directory by `OwnedTests.setUp`. ## Expected and actual behavior The test should allocate a selected-tool capture allowance based on that original fixture's actual executable extent and actual link payloads. Data/output allowances, production capture refusals, stall timing and total deadlines should remain independently constrained. CI instead reports eleven errors and one failed automatic-reaping refusal control; each stops at the oversized fixture capture. Production correctly rejects the insufficient allowance. ## Environment and identity - Component repository/revision: Exsh `6d1df9216920a6c86013f3c4cda93a01c096c3d6`. - Image profile and configuration: host Python tests; no VM/image failure is implicated. - Architecture and runtime: Linux x86-64; the selected CI Python executable exceeds 1 MiB. The local selected interpreter is 11,544 bytes and passes the same suite. - Input/session route and authority: an explicitly copied native fixture interpreter in the test's original source window; no deployment compiler approval is granted by this fixture. - Last known working revision: the size assumption also exists in the preceding `dc24005e352fa94f730446a3b48303f0188972d7` head. ## Evidence and prior checks [Exact-head failing CI run](https://git.erikinkinen.fi/erix/exsh/actions/runs/467). The original complete log has been retained before repair. All twelve affected controls fail before spawning their intended child; the production aggregate input check is functioning. The same checkout passes 425 controls with the smaller local interpreter. This is a fixture portability defect, not evidence of a production admission failure. ## Tracking Related work: [compiler evidence and cleanup frame design](https://git.erikinkinen.fi/erix/exsh/issues/4). Keep the meaningful over-budget capture control and all original output/stall/total limits when correcting the fixture.
Author
Owner

The fixture fix budgets the original selected interpreter extent and actual alias bytes. A real executable larger than one MiB now exercises the same native owner; a one-byte-short allowance still refuses before sealing or spawning. Data, output and timing limits are unchanged.

The [fixture fix](https://git.erikinkinen.fi/erix/exsh/commit/0386416978b862fe20dc0c8b7504ad11cbc1a6e3) budgets the original selected interpreter extent and actual alias bytes. A real executable larger than one MiB now exercises the same native owner; a one-byte-short allowance still refuses before sealing or spawning. Data, output and timing limits are unchanged.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:49 +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/exsh#16
No description provided.