[BUG] Compiler process fixtures assume a Python executable below 1 MiB #16
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/exsh#16
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
6d1df9216920a6c86013f3c4cda93a01c096c3d6with 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 byOwnedTests.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
6d1df9216920a6c86013f3c4cda93a01c096c3d6.dc24005e352fa94f730446a3b48303f0188972d7head.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.
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.