[BUG] Existing exFAT VM scenarios exceed their original deadlines #88

Open
opened 2026-09-24 20:35:35 +02:00 by erikinkinen · 0 comments
Owner

Summary

Three existing positive exFAT scenarios fail in original Integration CI 1778, preventing complete catalog acceptance. The percent-in-use case reaches the original serial-progress deadline; the contiguous and corpus cases reach the original QEMU hard deadline. The observation does not establish a filesystem defect or host-load cause.

Reproduction

The original pull-request workflow at Integration 4149f332dce6567f8f2db0f503154d8980a52e48 runs the complete catalog using its selected source graph and 12 VM workers. Its failed scenarios are:

  • tests/scenarios/subsystem-e2fs-fat-exfat-percent-positive.toml (worker 8).
  • tests/scenarios/subsystem-e2fs-fat-exfat-contiguous-positive.toml (worker 3).
  • tests/scenarios/subsystem-e2fs-fat-exfat-corpus-positive.toml (worker 4).

The maintained entry point for each is bash scripts/run-scenario.sh <scenario-path> components.toml. This report records original CI execution; no additional reproduction or unchanged retry was performed. Failure frequency and a smaller deterministic trigger are unestablished.

Expected and actual behavior

Each positive case must reach all required storage/VFS readiness markers and expected guest exit 0x10, with its post-VM checks passing under the existing limits.

Actual: worker 8 reports qemu stalled with no serial progress for 45s; workers 3 and 4 report qemu timed out after 120s. The twelve authoritative worker summaries total 487 passed and 3 failed out of 490 scenarios. Rust and Markdown jobs pass; the Integration job fails.

The percent case's final Rootd progress marker is ERIX_ROOTD:PROGRESS:VFS:HTREE_CREATED_DONE. The contiguous and corpus cases reach ERIX_ROOTD:PROGRESS:VFS:ESP_IO_DONE. Each is followed by Kernel Logd reply progress, but final VFS I/O and Rootd readiness are not established. CI timestamps on replayed serial dumps do not measure guest operation durations.

Environment and identity

  • Integration 4149f332dce6567f8f2db0f503154d8980a52e48; original pull-request run 1778/API10450, Integration job 22449, attempt 1, using the workflow-selected complete dependency catalog.
  • Release full-system x86-64 scenarios, one guest CPU each, 12 maintained CI workers; the runner reports KVM available. Runtime configuration is tests/runtime-configs/runtime.dev.storage-writable-exfat.toml, with writable fs-exfat-percent, fs-exfat-contiguous and fs-exfat-corpus media respectively.
  • Unchanged 120-second hard limit and 45-second serial-progress limit. No scenario assertion, authority grant or deadline has been relaxed.
  • Exact original image/firmware digests and an equivalent last-known-working environment are not established by this log review.

Evidence and prior checks

All three complete original job logs are retained and hash-verified, totaling 14,634,187 bytes with zero warning candidates. The Integration log is 14,525,837 bytes, SHA-256 829b950502987d75c350d070f0e8314d8e6b18a7b472b95b4c52966fb737bb56. Scenario, runtime-configuration and workflow Git blobs are bound to the original source revision. Expected failures from negative host controls are distinct from the three catalog failures.

The three deadlines identify incomplete executions; they do not identify a stalled instruction, a causative commit or a common cause. No unchanged input was rerun, cancelled or retried to obtain acceptance.

Tracking

Related existing reports cover FAT32 mirrored/Unicode deadlines, FAT32 directory metadata and ext4 deadlines. These are different selected workloads; no shared cause is asserted. Track diagnosis through Integration profiling, WIP PR 12 and Phase 6 completion.

  • Retain the complete original failure logs and exact selected scenario identities.
  • Attribute the missing progress using bounded, source-bound diagnostics under the original limits.
  • Correct the identified cause and validate all three scenarios without removing workload, assertions or authority constraints.
  • Review complete original CI after the correction before closing acceptance.
## Summary Three existing positive exFAT scenarios fail in original [Integration CI 1778](https://git.erikinkinen.fi/erix/integration/actions/runs/1778), preventing complete catalog acceptance. The percent-in-use case reaches the original serial-progress deadline; the contiguous and corpus cases reach the original QEMU hard deadline. The observation does not establish a filesystem defect or host-load cause. ## Reproduction The original pull-request workflow at Integration `4149f332dce6567f8f2db0f503154d8980a52e48` runs the complete catalog using its selected source graph and 12 VM workers. Its failed scenarios are: - `tests/scenarios/subsystem-e2fs-fat-exfat-percent-positive.toml` (worker 8). - `tests/scenarios/subsystem-e2fs-fat-exfat-contiguous-positive.toml` (worker 3). - `tests/scenarios/subsystem-e2fs-fat-exfat-corpus-positive.toml` (worker 4). The maintained entry point for each is `bash scripts/run-scenario.sh <scenario-path> components.toml`. This report records original CI execution; no additional reproduction or unchanged retry was performed. Failure frequency and a smaller deterministic trigger are unestablished. ## Expected and actual behavior Each positive case must reach all required storage/VFS readiness markers and expected guest exit `0x10`, with its post-VM checks passing under the existing limits. Actual: worker 8 reports `qemu stalled with no serial progress for 45s`; workers 3 and 4 report `qemu timed out after 120s`. The twelve authoritative worker summaries total 487 passed and 3 failed out of 490 scenarios. Rust and Markdown jobs pass; the Integration job fails. The percent case's final Rootd progress marker is `ERIX_ROOTD:PROGRESS:VFS:HTREE_CREATED_DONE`. The contiguous and corpus cases reach `ERIX_ROOTD:PROGRESS:VFS:ESP_IO_DONE`. Each is followed by Kernel Logd reply progress, but final VFS I/O and Rootd readiness are not established. CI timestamps on replayed serial dumps do not measure guest operation durations. ## Environment and identity - Integration `4149f332dce6567f8f2db0f503154d8980a52e48`; original pull-request run 1778/API10450, Integration job 22449, attempt 1, using the workflow-selected complete dependency catalog. - Release full-system x86-64 scenarios, one guest CPU each, 12 maintained CI workers; the runner reports KVM available. Runtime configuration is `tests/runtime-configs/runtime.dev.storage-writable-exfat.toml`, with writable `fs-exfat-percent`, `fs-exfat-contiguous` and `fs-exfat-corpus` media respectively. - Unchanged 120-second hard limit and 45-second serial-progress limit. No scenario assertion, authority grant or deadline has been relaxed. - Exact original image/firmware digests and an equivalent last-known-working environment are not established by this log review. ## Evidence and prior checks All three complete original job logs are retained and hash-verified, totaling 14,634,187 bytes with zero warning candidates. The Integration log is 14,525,837 bytes, SHA-256 `829b950502987d75c350d070f0e8314d8e6b18a7b472b95b4c52966fb737bb56`. Scenario, runtime-configuration and workflow Git blobs are bound to the original source revision. Expected failures from negative host controls are distinct from the three catalog failures. The three deadlines identify incomplete executions; they do not identify a stalled instruction, a causative commit or a common cause. No unchanged input was rerun, cancelled or retried to obtain acceptance. ## Tracking Related existing reports cover [FAT32 mirrored/Unicode deadlines](https://git.erikinkinen.fi/erix/integration/issues/58), [FAT32 directory metadata](https://git.erikinkinen.fi/erix/integration/issues/70) and [ext4 deadlines](https://git.erikinkinen.fi/erix/integration/issues/73). These are different selected workloads; no shared cause is asserted. Track diagnosis through [Integration profiling](https://git.erikinkinen.fi/erix/integration/issues/3), [WIP PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Retain the complete original failure logs and exact selected scenario identities. - [ ] Attribute the missing progress using bounded, source-bound diagnostics under the original limits. - [ ] Correct the identified cause and validate all three scenarios without removing workload, assertions or authority constraints. - [ ] Review complete original CI after the correction before closing acceptance.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:19 +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#88
No description provided.