[BUG] Runtime-source fixture still expects removed Cargo path patches #21

New issue

Open

opened 2026-09-12 13:58:03 +02:00 by erikinkinen · 0 comments

erikinkinen commented

2026-09-12 13:58:03 +02:00

Owner

Summary

The runtime/tool source separation regression test still requires a Cargo path patch after preparation was changed to preserve original Git package identities. Integration CI stops in host tests before reaching the full VM catalog.

Reproduction

At Integration e2b1cf5995bcf6334839cda9a013e90fa97787d5, run:

python3 -W error tests/integration_tool_source_test.py

The fixture creates separate original runtime and orchestration Git repositories and prepares a local dependency graph. One observed complete CI run fails the assertion that reads config["patch"].

Expected and actual behavior

The test should establish that actual Cargo metadata retains the original runtime URL and full selected commit, and that the resolved package comes from that runtime source rather than the newer orchestration checkout. Original Git transport configuration must not introduce cross-repository path packages.

Instead, test_monorepo_cargo_uses_runtime_clone_not_tool_head raises KeyError: 'patch' at line 50. The four-test group ends with one error and runner exit status 1. The Rust and Markdown jobs pass; the later VM catalog and image gates are not executed.

Environment and identity

Repository/head: Integration e2b1cf5995bcf6334839cda9a013e90fa97787d5.
Failing run: CI 1565, API run 9007, integration job 19370, attempt 1.
Configuration: existing container CI; host Python/Git/Cargo fixture with temporary local repositories. No guest image is involved in this failure.
Authority: fixture-local source repositories and explicitly generated Cargo transport; no additional runtime capability.
Last passing revision for this exact fixture has not been independently established. The source change that removed path configuration and the unchanged assertion are observable; this does not identify a guest regression.

Evidence and prior checks

Complete CI 1565 reports the four-test group failure at 2026-09-12 11:52 UTC. The complete job log has been retained. Expected negative-test diagnostics earlier in the log are distinct from this final exception. No rerun, deadline relaxation or production rollback was used to classify the failure.

Tracking

Related source-identity correction: Integration #17; implementation: WIP PR #12; audit: Integration #11. Replace the stale implementation-shaped assertion with actual original-source metadata and content checks, preserve runtime/tool separation coverage, and run the related host fixture families before monitoring new full CI. A passing fixture does not establish guest-build acceptance.

## Summary The runtime/tool source separation regression test still requires a Cargo path patch after preparation was changed to preserve original Git package identities. Integration CI stops in host tests before reaching the full VM catalog. ## Reproduction At Integration `e2b1cf5995bcf6334839cda9a013e90fa97787d5`, run: ```sh python3 -W error tests/integration_tool_source_test.py ``` The fixture creates separate original runtime and orchestration Git repositories and prepares a local dependency graph. One observed complete CI run fails the assertion that reads `config["patch"]`. ## Expected and actual behavior The test should establish that actual Cargo metadata retains the original runtime URL and full selected commit, and that the resolved package comes from that runtime source rather than the newer orchestration checkout. Original Git transport configuration must not introduce cross-repository path packages. Instead, `test_monorepo_cargo_uses_runtime_clone_not_tool_head` raises `KeyError: 'patch'` at line 50. The four-test group ends with one error and runner exit status 1. The Rust and Markdown jobs pass; the later VM catalog and image gates are not executed. ## Environment and identity - Repository/head: Integration `e2b1cf5995bcf6334839cda9a013e90fa97787d5`. - Failing run: CI 1565, API run 9007, integration job 19370, attempt 1. - Configuration: existing container CI; host Python/Git/Cargo fixture with temporary local repositories. No guest image is involved in this failure. - Authority: fixture-local source repositories and explicitly generated Cargo transport; no additional runtime capability. - Last passing revision for this exact fixture has not been independently established. The source change that removed path configuration and the unchanged assertion are observable; this does not identify a guest regression. ## Evidence and prior checks [Complete CI 1565](https://git.erikinkinen.fi/erix/integration/actions/runs/1565) reports the four-test group failure at 2026-09-12 11:52 UTC. The complete job log has been retained. Expected negative-test diagnostics earlier in the log are distinct from this final exception. No rerun, deadline relaxation or production rollback was used to classify the failure. ## Tracking Related source-identity correction: [Integration #17](https://git.erikinkinen.fi/erix/integration/issues/17); implementation: [WIP PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12); audit: [Integration #11](https://git.erikinkinen.fi/erix/integration/issues/11). Replace the stale implementation-shaped assertion with actual original-source metadata and content checks, preserve runtime/tool separation coverage, and run the related host fixture families before monitoring new full CI. A passing fixture does not establish guest-build acceptance.

erikinkinen added the

bug

phase-6

labels

2026-09-12 13:58:03 +02:00

~~erikinkinen referenced this issue 2026-09-12 14:15:15 +02:00~~

WIP: Coordinate native authority, shell workspace and source transport #12

erikinkinen referenced this issue from a commit

2026-09-21 18:19:25 +02:00

test: Select verified acknowledged terminal accounting