[BUG] Nested output fixture hides progress from the enclosing runner #169

Open
opened 2026-10-18 15:46:20 +02:00 by erikinkinen · 2 comments
Owner

Summary

The long-running native output fixture captures genuine progress inside its nested command owners but does not forward it to the enclosing Python test runner. A suite with the selected 60-second stall limit therefore treats a productive 62-second child as quiet and terminates before the fixture can finish.

Reproduction

Use Integration e38c9571f3ee77100297c9f54b298a283359c7d9 and run the maintained scripts/run-python-tests.py with explicit installed tools and environment, 900-second total limit, 180-second module limit, 60-second stall limit and 16 MiB output budget. The failure occurs in NativeLiveOutputTests.test_two_real_owners_receive_progress_beyond_original_sixty_seconds in tests/command_live_output_test.py.

This local diagnostic selects 900/180/60-second limits; the maintained CI selects 1200/600/90 seconds.

The fixture writes 620 real bytes over 62 seconds. Its inner owner forwards those bytes, while the next owner omits stream_receivers and retains them only in its files.

Expected and actual behavior

Real producer bytes must reach every enclosing owner while both original capture files and complete-result assertions remain intact. All existing hard and stall limits must remain unchanged.

The original full run terminates with a deadline failure: process exit -15, owner failure 124, after 326.47 seconds overall. The last test line identifies the 62-second fixture. Thirty earlier modules completed; no complete-suite acceptance is claimed. Cleanup is confirmed and the owner is not quarantined.

Environment and identity

  • Affected published Integration source: e38c9571f3ee77100297c9f54b298a283359c7d9.
  • Host: Linux x86-64, Python 3.14, original fresh-interpreter runner.
  • Complete selected tool environment and original 900/180/60-second limits.
  • No guest, VM image or runtime capability change is involved.

Evidence and prior checks

The retained local reproductions use test/decoder bytes identical to this published source.

The original outer status and both complete streams are retained, along with all completed module receipts. Source inspection identifies the missing outer forwarding route. The repair forwards only the original child bytes and compares both retained stdout captures with the complete 620-byte result. It adds no heartbeat and changes no deadline.

Tracking

  • Forward genuine output through both fixture owners and preserve both capture assertions.
  • Pass the exact native module with its original 62-second producer.
  • Pass the complete fresh-module runner with all prepared inputs.
  • Pass current-source Integration CI.

The closed capture report concerns an earlier display interpretation and established no defect; it is a different case. The Python entry-point issue tracks separate tool and fixture wiring.

Implementation: PR #12. Phase scope: #65.

## Summary The long-running native output fixture captures genuine progress inside its nested command owners but does not forward it to the enclosing Python test runner. A suite with the selected 60-second stall limit therefore treats a productive 62-second child as quiet and terminates before the fixture can finish. ## Reproduction Use Integration `e38c9571f3ee77100297c9f54b298a283359c7d9` and run the maintained `scripts/run-python-tests.py` with explicit installed tools and environment, 900-second total limit, 180-second module limit, 60-second stall limit and 16 MiB output budget. The failure occurs in `NativeLiveOutputTests.test_two_real_owners_receive_progress_beyond_original_sixty_seconds` in `tests/command_live_output_test.py`. This local diagnostic selects 900/180/60-second limits; the maintained CI selects 1200/600/90 seconds. The fixture writes 620 real bytes over 62 seconds. Its inner owner forwards those bytes, while the next owner omits `stream_receivers` and retains them only in its files. ## Expected and actual behavior Real producer bytes must reach every enclosing owner while both original capture files and complete-result assertions remain intact. All existing hard and stall limits must remain unchanged. The original full run terminates with a deadline failure: process exit `-15`, owner failure `124`, after 326.47 seconds overall. The last test line identifies the 62-second fixture. Thirty earlier modules completed; no complete-suite acceptance is claimed. Cleanup is confirmed and the owner is not quarantined. ## Environment and identity - Affected published Integration source: `e38c9571f3ee77100297c9f54b298a283359c7d9`. - Host: Linux x86-64, Python 3.14, original fresh-interpreter runner. - Complete selected tool environment and original 900/180/60-second limits. - No guest, VM image or runtime capability change is involved. ## Evidence and prior checks The retained local reproductions use test/decoder bytes identical to this published source. The original outer status and both complete streams are retained, along with all completed module receipts. Source inspection identifies the missing outer forwarding route. The repair forwards only the original child bytes and compares both retained stdout captures with the complete 620-byte result. It adds no heartbeat and changes no deadline. ## Tracking - [x] Forward genuine output through both fixture owners and preserve both capture assertions. - [x] Pass the exact native module with its original 62-second producer. - [x] Pass the complete fresh-module runner with all prepared inputs. - [ ] Pass current-source Integration CI. The closed [capture report](https://git.erikinkinen.fi/erix/integration/issues/95) concerns an earlier display interpretation and established no defect; it is a different case. The [Python entry-point issue](https://git.erikinkinen.fi/erix/integration/issues/149) tracks separate tool and fixture wiring. Implementation: [PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12). Phase scope: [#65](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

Fixed in 7d3e7b3f. Nested command fixtures now forward their actual child output to the enclosing observer while retaining both captures. The productive 62-second fixture passes with the existing watchdog limits. The complete prepared-suite and current-source CI criteria remain open.

Fixed in [7d3e7b3f](https://git.erikinkinen.fi/erix/integration/commit/7d3e7b3f845d1fea372a4f682126ccb3c3b9496b). Nested command fixtures now forward their actual child output to the enclosing observer while retaining both captures. The productive 62-second fixture passes with the existing watchdog limits. The complete prepared-suite and current-source CI criteria remain open.
Author
Owner

The complete maintained runner now passes all 185 modules and 2,064 tests on 7d3e7b3f, including the productive 62-second fixture. It uses the required native inputs and unchanged 1200/600/90-second limits. The prepared-suite criterion is checked; current-source CI remains open.

The complete maintained runner now passes all 185 modules and 2,064 tests on [7d3e7b3f](https://git.erikinkinen.fi/erix/integration/commit/7d3e7b3f845d1fea372a4f682126ccb3c3b9496b), including the productive 62-second fixture. It uses the required native inputs and unchanged 1200/600/90-second limits. The prepared-suite criterion is checked; current-source CI remains open.
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#169
No description provided.