[BUG] Python test entry points lack required fixtures and tools #149

Open
opened 2026-10-17 02:27:24 +02:00 by erikinkinen · 5 comments
Owner

Summary

The maintained Python regression entry points fail before some tests can exercise their intended behavior. Bootstrap tests import a fixture whose Git methods were removed, newer Cargo tests lack their selected tool environment, and a shell entry point still names a deleted test class.

Reproduction

At Integration 4ebc6af150d8648470ad1041993b4c2ebc30146c, run:

python3 -m unittest discover -s tests -p bootstrap_repos_test.py -v
./tests/clone-components-branch-selection.sh

The maintained CI fresh-interpreter step also emits an environment without the CARGO and RUSTC keys consumed by the new Cargo controls.

Expected and actual behavior

Existing bootstrap and source-selection checks must keep working after obsolete resolver tests are retired. Every native test must receive the explicitly selected tools required by its caller.

The completed bootstrap module reports 11 setup errors: BootstrapRepositoriesTests has no repository attribute. Cargo controls report missing CARGO or RUSTC. The shell entry point selects the absent ImmutableCloneTests class.

Environment and identity

  • Integration: 4ebc6af150d8648470ad1041993b4c2ebc30146c.
  • Host: Python 3.14 on Linux; fresh interpreters with an explicit environment.
  • Bootstrap fixture setup fails before its Git commands. No guest is involved.
  • Last known complete source cohort: the earlier commit-based dependency workflow.

Evidence and prior checks

The full-suite run retains the completed bootstrap module's original status and streams while continuing the remaining modules. Direct source inspection confirms the missing shared methods, omitted CI environment keys and obsolete shell selector. An older LibCstd selection in the local validation setup is a separate input error and must be corrected without weakening original-source verification.

Tracking

  • Give bootstrap tests their own local Git fixture and preserve all 11 existing regressions.
  • Pass the selected Cargo and rustc paths through the maintained CI environment; cover the actual writer and child handoff.
  • Remove the obsolete shell entry point while retaining its meaningful coverage in the complete Python suite.
  • Pass the corrected complete suite and current-source Integration CI.

Related: dependency migration.

## Summary The maintained Python regression entry points fail before some tests can exercise their intended behavior. Bootstrap tests import a fixture whose Git methods were removed, newer Cargo tests lack their selected tool environment, and a shell entry point still names a deleted test class. ## Reproduction At Integration `4ebc6af150d8648470ad1041993b4c2ebc30146c`, run: ```sh python3 -m unittest discover -s tests -p bootstrap_repos_test.py -v ./tests/clone-components-branch-selection.sh ``` The maintained CI fresh-interpreter step also emits an environment without the `CARGO` and `RUSTC` keys consumed by the new Cargo controls. ## Expected and actual behavior Existing bootstrap and source-selection checks must keep working after obsolete resolver tests are retired. Every native test must receive the explicitly selected tools required by its caller. The completed bootstrap module reports 11 setup errors: `BootstrapRepositoriesTests` has no `repository` attribute. Cargo controls report missing `CARGO` or `RUSTC`. The shell entry point selects the absent `ImmutableCloneTests` class. ## Environment and identity - Integration: `4ebc6af150d8648470ad1041993b4c2ebc30146c`. - Host: Python 3.14 on Linux; fresh interpreters with an explicit environment. - Bootstrap fixture setup fails before its Git commands. No guest is involved. - Last known complete source cohort: the earlier commit-based dependency workflow. ## Evidence and prior checks The full-suite run retains the completed bootstrap module's original status and streams while continuing the remaining modules. Direct source inspection confirms the missing shared methods, omitted CI environment keys and obsolete shell selector. An older LibCstd selection in the local validation setup is a separate input error and must be corrected without weakening original-source verification. ## Tracking - [x] Give bootstrap tests their own local Git fixture and preserve all 11 existing regressions. - [x] Pass the selected Cargo and rustc paths through the maintained CI environment; cover the actual writer and child handoff. - [x] Remove the obsolete shell entry point while retaining its meaningful coverage in the complete Python suite. - [ ] Pass the corrected complete suite and current-source Integration CI. Related: [dependency migration](https://git.erikinkinen.fi/erix/integration/issues/142).
Author
Owner

8004dfda gives bootstrap tests their own local Git fixture, passes both selected Rust tools into fresh CI interpreters, and removes the obsolete shell selector. The 11 bootstrap tests and all nine runner tests pass.

The complete-suite attempt remains failed: it reached the original 600-second limit after 150 of 172 modules. Its failures are retained; full-suite and current CI acceptance remain open.

[8004dfda](https://git.erikinkinen.fi/erix/integration/commit/8004dfdada6bfd4a57ed9e6635cc30d804bc5c85) gives bootstrap tests their own local Git fixture, passes both selected Rust tools into fresh CI interpreters, and removes the obsolete shell selector. The 11 bootstrap tests and all nine runner tests pass. The complete-suite attempt remains failed: it reached the original 600-second limit after 150 of 172 modules. Its failures are retained; full-suite and current CI acceptance remain open.
Author
Owner

The complete suite now has a 1,200-second allowance and an explicit 600-second module ceiling in eb9bc0ff. All ten runner tests pass, including a real hanging child retired at its smaller module deadline. The corrected 172-module run is active; its original failures remain recorded.

The complete suite now has a 1,200-second allowance and an explicit 600-second module ceiling in [eb9bc0ff](https://git.erikinkinen.fi/erix/integration/commit/eb9bc0fff1e417bd16c155050c6ba23ee14e3d90). All ten runner tests pass, including a real hanging child retired at its smaller module deadline. The corrected 172-module run is active; its original failures remain recorded.
Author
Owner

The corrected complete Python suite passes all 1,905 tests across 172 modules, with no warnings and successful cleanup. It took about 930 seconds within the 1,200-second total budget; each module remains limited to 600 seconds. Current-source Integration CI is still required before closing this issue.

The corrected complete Python suite passes all 1,905 tests across 172 modules, with no warnings and successful cleanup. It took about 930 seconds within the 1,200-second total budget; each module remains limited to 600 seconds. Current-source Integration CI is still required before closing this issue.
Author
Owner

Published 7375261a also repairs the negative Git-tool fixture that stopped CI2768: it returned 127 where the test expected 19. The fixture now invokes the selected Python interpreter instead of embedding a versioned interpreter path. All 13 owning tests pass; the original failed run remains recorded. The complete current suite and CI are still open.

Published `7375261a` also repairs the negative Git-tool fixture that stopped [CI2768](https://git.erikinkinen.fi/erix/integration/actions/runs/2768): it returned 127 where the test expected 19. The fixture now invokes the selected Python interpreter instead of embedding a versioned interpreter path. All 13 owning tests pass; the original failed run remains recorded. The complete current suite and CI are still open.
Author
Owner

The complete suite at 7375261a passes all 1,912 tests across 173 modules. The current CI Rust job also passes; the separate Markdown failure is repaired in 38c204aa. Guest scenarios and the new full CI result remain pending.

The complete suite at 7375261a passes all 1,912 tests across 173 modules. The current CI Rust job also passes; the separate Markdown failure is repaired in 38c204aa. Guest scenarios and the new full CI result remain pending.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:18 +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#149
No description provided.