[BUG] SHA workflow guard fixture fails before recording calls #188

Open
opened 2026-10-24 08:47:39 +02:00 by erikinkinen · 0 comments
Owner

Summary

The native SHA workflow guard controls fail before their fake provider records a call. Reading the missing trace then hides the original subprocess result.

Reproduction

Run the maintained native_sha2_workflow_test module from Integration f3d5b32b92. CI3026 host_zero records multiple missing trace.jsonl errors. The fixture prepends a sha2-tool shell function and executes it with /usr/bin/sh.

Expected and actual behavior

The selected fake executable should record exact argv/stdin and let the guard control reach its intended assertion. Instead the fixture reads a nonexistent trace. The function name contains a hyphen and is not portable POSIX shell syntax; this is a source-supported cause, while the original stderr is unavailable because trace parsing masked it.

Environment and identity

Integration revision f3d5b32b92, maintained Docker host shard. Current source retains the same fixture. This is a host fixture failure; no native guest failure is established.

Evidence and prior checks

The complete original shard log is retained, with its failed-module footer and source postcheck. No rerun or replacement stderr is used as evidence. The other source/native observations remain separate.

Tracking

Related review: Integration PR12.

  • Use a private selected executable provider that works with the maintained shell and records exact original arguments/stdin.
  • Preserve and report the original subprocess failure before attempting trace diagnostics.
  • Pass the complete guard controls, including unchanged empty/large/denied cases, without relaxing their assertions.
## Summary The native SHA workflow guard controls fail before their fake provider records a call. Reading the missing trace then hides the original subprocess result. ## Reproduction Run the maintained native_sha2_workflow_test module from Integration f3d5b32b92ab8e5b33a6b76dc9f474ca2f1b8d04. [CI3026 host_zero](https://git.erikinkinen.fi/erix/integration/actions/runs/3026/jobs/1) records multiple missing trace.jsonl errors. The fixture prepends a sha2-tool shell function and executes it with /usr/bin/sh. ## Expected and actual behavior The selected fake executable should record exact argv/stdin and let the guard control reach its intended assertion. Instead the fixture reads a nonexistent trace. The function name contains a hyphen and is not portable POSIX shell syntax; this is a source-supported cause, while the original stderr is unavailable because trace parsing masked it. ## Environment and identity Integration revision f3d5b32b92ab8e5b33a6b76dc9f474ca2f1b8d04, maintained Docker host shard. Current source retains the same fixture. This is a host fixture failure; no native guest failure is established. ## Evidence and prior checks The complete original shard log is retained, with its failed-module footer and source postcheck. No rerun or replacement stderr is used as evidence. The other source/native observations remain separate. ## Tracking Related review: [Integration PR12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [ ] Use a private selected executable provider that works with the maintained shell and records exact original arguments/stdin. - [ ] Preserve and report the original subprocess failure before attempting trace diagnostics. - [ ] Pass the complete guard controls, including unchanged empty/large/denied cases, without relaxing their assertions.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:21 +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#188
No description provided.