[BUG] Isolated Python CI cannot find installed filesystem tools #139

Closed
opened 2026-10-16 13:47:56 +02:00 by erikinkinen · 3 comments
Owner

Summary

The complete Python CI stage cannot find installed filesystem tools on Debian-based runners. Its explicit child PATH contains the Rust toolchain, /usr/bin and /bin, but omits the system-tool directories.

Reproduction

Run the Integration workflow at 94a19951a6f2a496c10a5ac35cc9056678ab55ed on its Debian-based runner with e2fsprogs installed. The full Python stage constructs its own environment before running the test modules.

A minimal lookup on that layout reproduces the omission:

PATH=/usr/bin:/bin python3 -c 'import shutil; assert shutil.which("mkfs.ext4")'

The executable is installed in /usr/sbin; the complete environment must include the directories containing the required tools.

Expected and actual behavior

The installed image tools should be available to the filesystem fixtures. Instead, CI reports 34 failed controls across the ACL metadata, source-epoch, POSIX filesystem packaging and realm-link modules because mkfs.ext4 is unavailable. No VM scenario matrix is reached.

Environment and identity

  • Integration failure: 94a19951a6f2a496c10a5ac35cc9056678ab55ed; the same environment writer is present in b7b17f96d23597c0445fa6844c8d8a257a44ae2d.
  • CI run 2726, integration job; Debian-based runner with e2fsprogs installed.
  • The local host places these tools in /usr/bin, which explains why the original local suite passed.
  • The runner intentionally uses a complete child environment. Inherited PATH is not part of its contract.

Evidence and prior checks

The complete original CI log contains 2 ACL errors, 1 source-epoch error, 30 filesystem-packaging failures and 1 realm-link failure. The workflow installs the required package, but its environment writer omits /usr/sbin and /sbin. This is a tool-selection failure before guest execution.

Tracking

Related: isolated Python test runner.

  • Include the required system-tool directories in the explicit CI environment.
  • Cover the real environment writer and both system-tool directory layouts.
  • Confirm that the affected filesystem modules run with the corrected environment.
  • Observe the corrected full Python CI stage reaching VM scenario execution.
## Summary The complete Python CI stage cannot find installed filesystem tools on Debian-based runners. Its explicit child PATH contains the Rust toolchain, `/usr/bin` and `/bin`, but omits the system-tool directories. ## Reproduction Run the Integration workflow at `94a19951a6f2a496c10a5ac35cc9056678ab55ed` on its Debian-based runner with e2fsprogs installed. The full Python stage constructs its own environment before running the test modules. A minimal lookup on that layout reproduces the omission: ```sh PATH=/usr/bin:/bin python3 -c 'import shutil; assert shutil.which("mkfs.ext4")' ``` The executable is installed in `/usr/sbin`; the complete environment must include the directories containing the required tools. ## Expected and actual behavior The installed image tools should be available to the filesystem fixtures. Instead, CI reports 34 failed controls across the ACL metadata, source-epoch, POSIX filesystem packaging and realm-link modules because `mkfs.ext4` is unavailable. No VM scenario matrix is reached. ## Environment and identity - Integration failure: `94a19951a6f2a496c10a5ac35cc9056678ab55ed`; the same environment writer is present in `b7b17f96d23597c0445fa6844c8d8a257a44ae2d`. - CI run 2726, integration job; Debian-based runner with e2fsprogs installed. - The local host places these tools in `/usr/bin`, which explains why the original local suite passed. - The runner intentionally uses a complete child environment. Inherited PATH is not part of its contract. ## Evidence and prior checks The complete original CI log contains 2 ACL errors, 1 source-epoch error, 30 filesystem-packaging failures and 1 realm-link failure. The workflow installs the required package, but its environment writer omits `/usr/sbin` and `/sbin`. This is a tool-selection failure before guest execution. ## Tracking Related: [isolated Python test runner](https://git.erikinkinen.fi/erix/integration/issues/137). - [x] Include the required system-tool directories in the explicit CI environment. - [x] Cover the real environment writer and both system-tool directory layouts. - [x] Confirm that the affected filesystem modules run with the corrected environment. - [x] Observe the corrected full Python CI stage reaching VM scenario execution.
Author
Owner

0e93075a adds /usr/sbin and /sbin to the explicit Python CI environment. The regression executes the actual workflow writer and checks both isolated directory layouts, so local tool copies cannot hide an omission.

All eight focused tests and seven source checks pass. The full 1,670-test run is still active; a fresh CI run will determine whether the workflow reaches VM execution.

`0e93075a` adds `/usr/sbin` and `/sbin` to the explicit Python CI environment. The regression executes the actual workflow writer and checks both isolated directory layouts, so local tool copies cannot hide an omission. All eight focused tests and seven source checks pass. The full 1,670-test run is still active; a fresh CI run will determine whether the workflow reaches VM execution.
Author
Owner

All four affected filesystem modules now pass: ACL metadata (11 tests), source epochs (6), filesystem packaging (30) and realm links (2).

The original full run still returns 1 because three native-permission fixtures exceed the Unix socket-path limit under a long temporary root; that separate defect is tracked in #140. CI2732 is running at 0e93075a; the final criterion here remains open.

All four affected filesystem modules now pass: ACL metadata (11 tests), source epochs (6), filesystem packaging (30) and realm links (2). The original full run still returns 1 because three native-permission fixtures exceed the Unix socket-path limit under a long temporary root; that separate defect is tracked in [#140](https://git.erikinkinen.fi/erix/integration/issues/140). CI2732 is running at `0e93075a`; the final criterion here remains open.
Author
Owner

Fixed in 0e93075a. CI run 2732 completed all 1,670 Python tests across 147 modules and entered the VM matrix, including the four filesystem modules affected by the missing system-tool directories. All four acceptance criteria are met.

The VM matrix is still running; its observed selector-race and extop stalls are separate from this tool-selection fix.

Fixed in `0e93075a`. CI run 2732 completed all 1,670 Python tests across 147 modules and entered the VM matrix, including the four filesystem modules affected by the missing system-tool directories. All four acceptance criteria are met. The VM matrix is still running; its observed selector-race and extop stalls are separate from this tool-selection fix.
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#139
No description provided.