[BUG] Existing ext4 VM scenarios exceed their original QEMU deadlines #73

Open
opened 2026-09-22 04:08:51 +02:00 by erikinkinen · 0 comments
Owner

Summary

Existing ext4 positive VM scenarios reach their original 120-second QEMU deadline in two completed Integration CI runs. Both complete catalog runs fail, while the Rust and Markdown jobs pass. The failing scenario sets differ; this report records the observed failures without attributing them to filesystem semantics or host load.

Reproduction

The original push and pull-request CI executions at Integration fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa run the maintained workflow and all 489 VM scenarios. Run 1705 reports seven failures and run 1706 reports four. These are two original executions, with no rerun, timeout increase or changed success oracle. An isolated clean-image reproduction has not yet been performed.

Expected and actual behavior

Every positive scenario must reach its existing required witnesses inside its declared limit. Run 1705 reports passed=482 failed=7 total=489; run 1706 reports passed=485 failed=4 total=489. Each listed failure has actual qemu timed out after 120s output and scenario status 1; the workflow ends with failed VM workers.

Ext4 scenario suffix Run 1705 Run 1706
geometry-positive timeout passes
mmp-positive timeout passes
orphan-file-positive timeout passes
orphan-list-positive timeout timeout
fast-commit-htree-positive timeout passes
quota-positive timeout timeout
fast-commit-linear-positive timeout timeout
links-positive passes timeout

All suffixes belong to tests/scenarios/subsystem-e2fs-fat-ext4-<suffix>.toml. Retained timeout transcripts end their EriX markers at ERIX_KERNEL:ROOTD_SMOKE:LOGD_REPLY_WAKE_OK=0000000000000001. That last printed marker does not identify the instruction executing at the deadline or prove a Logd defect.

Environment and identity

  • Integration revision: fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa; original source graph and artifact construction are recorded in each linked run.
  • Workflow: ci.yml, original push run 1705 and pull-request run 1706, with 489 maintained VM scenarios and the original 120-second QEMU ceiling.
  • Architecture: x86_64 with the workflow-selected QEMU, firmware and image inputs; no replacement image is used for this classification.
  • Input and authority: original scenario-selected boot image and test disk. The observer only reads completed CI status/logs; it grants no guest capability or additional runtime control.
  • The complete original six job logs are retained with verified lengths and SHA-256 digests. Individual image digests have not yet been independently recovered from CI artifacts.
  • Last known passing exact graph and a common root cause are not established.

Evidence and prior checks

Complete original CI review — 28 September 2026:

These are additional original observations. No unchanged job was rerun, and an identical underlying cause to earlier observations is not assumed.

  • CI1812, 447f642e4aaf4638a0997d0efc49e41dcd3fc79a: The ext4 quota VM reaches its original 120-second deadline; every other catalog scenario passes. Three complete logs contain 13,946,086 bytes and zero warning candidates. Rust and Markdown pass.

Original push run 1705 and original pull-request run 1706 retain the observed failures. Their Rust jobs each pass 320 and 321 tests, and Markdown passes. All six complete logs have no warning candidates. Expected negative-helper error output is distinct from the final VM failures. Do not treat successful reruns as a correction or widen the original limits.

Exact original-contract comparison: ten timeout serial dumps lack their required ERIX_ROOTD:READY:VFS_IO marker; the links case also lacks ERIX_ROOTD:READY:VFS_EXT_LINKS. The geometry dump already contains its declared required substrings, but still reaches the deadline instead of the required exit. Marker presence cannot replace the exit and timeout checks. None of the eleven dumps contains its scenario's forbidden Kernel fault markers. This narrows the observed stage without proving which operation stalls or why.

Tracking

Original CI1788 follow-up — 25 September 2026: run1788 at fa857c0964774def6777142afeb7a3c16440abee records120-second QEMU timeouts for ext4 links (worker4), mmp (worker7) and metadata (worker6). Quota and rename are also affected and remain linked to their existing reports. The complete catalog passes483/491. Original Rust/Markdown pass and verified complete logs contain no warnings. These observations do not establish a common filesystem or host-load cause.

Track under Phase 6 completion and the coordinated implementation review. The separate startup timing report and FAT32 timing report remain open; shared causation has not been established. Preserve original evidence, identify the failing stage with bounded diagnostics and validate any correction against these unchanged scenario oracles and the complete maintained suite.

Later original CI comparison — 22 September 2026: original Integration 1707 and 1708, at 9c62af2d2484b1ab0cadba768adc025dfd017485, both pass all 489 VM scenarios, Rust 320/321 tests and Markdown. All six complete job logs are retained and hash-verified, totaling 26,966,330 bytes with zero warning candidates. Both runs explicitly select Kernel a9bdf6163813d378e0b4a164bceb839e24fbb6b7. These are later original runs on a different source graph, not retries of 1705/1706. Their success does not identify the cause or demonstrate a correction for the eleven previously retained ext4 timeouts; this report remains open.

Further original ext4 CI evidence — 23 September 2026: Integration 1741 and 1742, at 3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe, complete the 489-scenario catalog with 478/11 and 481/8 pass/fail outcomes. All nineteen failures are ext4 scenarios reaching their original 120-second QEMU deadline, tracked under the existing ext4 deadline report. Rust 320/321-test configurations and Markdown pass. Both corrected managed-frame-occupancy and allocator-domain scenarios pass. The later canonical development/release image and physical-input gates are not reached.

Six complete original Integration logs total 34,342,962 bytes and have verified lengths/hashes with zero warning candidates. With the earlier successful Kernel 660/661 and Docs 1025/1026 logs, fourteen complete logs total 35,963,864 bytes and have zero final warnings. All nineteen timeout transcripts lack VFS_IO readiness and contain no scenario-forbidden fault markers. Eighteen end their complete EriX markers at LOGD_REPLY_WAKE_OK; one metadata transcript ends its complete markers at LOGD_REPLY_WRITE_OK followed by a partial next marker. Printed markers do not identify the executing instruction at the deadline or establish a Logd defect, filesystem cause or host-load explanation.

These are original executions on a later source graph, without retries, wider deadlines or changed success oracles. The ext4 report remains open. Complete corrected CI acceptance for Kernel #33 and Kernel #34 also remains open; passing selected allocator cases does not stand in for unreached workflow gates. This terminal run pair is fully retained and classified. Newer private mapping population checks and their CI remain separate, and full external-toolchain/runtime and EriX guest rebuilding are still required.

Ext4 scenario suffix Run 1741 Run 1742
fast-commit-linear-positive timeout timeout
fast-commit-mixed-positive timeout passes
geometry-positive timeout timeout
links-positive timeout timeout
metadata-positive timeout timeout
orphan-file-positive timeout timeout
orphan-list-positive timeout passes
quota-positive timeout timeout
rename-positive timeout timeout
stable-resize-positive timeout timeout
xattr-positive timeout passes

Original-image ext4 counter diagnostic — 23 September 2026: The isolated geometry scenario at Integration 3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe, selecting Kernel 03f3412076a9dde92ad4e89902d5ec8497a08476, passes locally under its original 120-second deadline with no warnings. Original pre-execution firmware, writable disks, ESP and exact command are retained. A separate TCG execution uses those same guest bytes and the original 120/45-second hard/silence bounds; guest exit, all scenario markers and the maintained filesystem postconditions pass without warnings.

The complete counter capture contains 78,599 translations, 1,611,237 code bytes and zero missed executions. Sixty complete ELF byte strings are verified inside the exact selected boot image; unembedded artifacts are excluded. Top 100 code groups cover 86.72% of the instruction upper bound. Unique Kernel mapping-batch and VSpace permission-switch code candidates contribute 29.60% and 7.02%; SHA2 candidates contribute 4.24%, other unique matches 5.46%, ambiguous matches 8.45% and unmatched code 31.95%. These are executed-code candidates, not process identity, CPU time or a speedup. They support continuing the owned-address-space work while preserving backing custody, W^X, validation and invalidation.

The first instrumented attempt exited before guest startup because the minimal host emulator lacked QCOW1 for the original writable FAT-directory drive. That failure is retained. A separate original-upstream host build adds only that backend and passes all five actual profiler ABI controls before the successful capture. External configuration retains its known unavailable-static-glib warning; compilation, controls and EriX guest execution have no warnings. The operator guidance and diagnostic record are signed and pushed through Integration PR 12. Markdown, formatting and diff checks pass; every executable, test, workflow and dependency byte remains identical to the preceding validated tree.

Integration #73 remains open: isolated success and TCG instruction counts do not explain the nineteen original CI deadlines. No failing CI job was rerun, no limit was widened and no success oracle changed. Current source caches are restored after retaining the diagnostics. External toolchain/runtime rebuilding and both complete EriX guest-build generations remain mandatory and unproven. No phase acceptance checklist item is closed by this diagnostic.

Complete owned-traversal CI review — 23 September 2026: original Integration 1743 and 1744, at 4fce71efe6277332b7dcad110c9c87eb57040e58 selecting Kernel b90a80c94721f99d2a829117dd29123b3aaebc7c, both pass all 489 catalog VM scenarios. Native lifetime, managed-frame occupancy, allocator-domain, canonical development/release images, physical input and remaining workflow gates pass. Rust 320/321-test configurations, profiler validation and Markdown also pass. Six complete Integration logs total 26,973,962 bytes with zero warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,603,130 bytes with zero final warnings.

This graph retains the exact corrected reserved-heap and temporary-CSpace cleanup code, and its Kernel descends from their signed correction. Complete corrected CI now closes Kernel #33 and Kernel #34. Their original native/host failures and later nineteen ext4 CI deadlines remain retained. No failing job was rerun and no limit or success oracle changed. Both new full runs pass the ext4 scenarios; the original timeout cause is still unproven, so Integration #73 remains open for attribution and timing review.

Later leaf/population/ancestor cohorts retain their own CI acceptance. Complete semantic authority review, root activation, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.

Complete private-leaf construction CI review — 23 September 2026: original Integration 1745 and 1746, at 4bc569bef76af4d4ce619dbe97ebc79a54cfdb6f selecting Kernel 4e58b1463749f761ab8a76ebd2cf39c583b5e62b, both pass all 489 catalog VM scenarios and the subsequent canonical development/release, physical-input and release-policy gates. Native lifetime, managed occupancy and allocator-domain checks pass. Rust 320/321-test configurations, profiler validation and Markdown pass. Six complete Integration logs total 26,972,820 bytes without warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,611,312 bytes with zero final warnings.

No job was rerun and no deadline or success oracle changed. Both complete runs pass the ext4 scenarios, while the original timeout cause remains unproven in Integration #73. This closes CI review for this exact private-leaf construction graph; subsequent mapping/range implementations retain their own CI acceptance. No active-root isolation or runtime speedup is inferred.

Registered image/stack population, readiness, actual root residency, invalidation, complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.

Complete ordinary private mapping CI review — 23 September 2026: original Integration 1747 and 1748, at 7855069f7c137f6eb76f3d05d7d20eadf7e2929e selecting Kernel f782ee68035fefb7bd30f5ac69373ecfc1eeac2d, both pass all 489 catalog VM scenarios and the subsequent canonical development/release, physical-input and release-policy gates. Native lifetime, managed occupancy and allocator-domain checks pass. Rust 320/321-test configurations, profiler validation and Markdown pass. Six complete Integration logs total 26,973,516 bytes without warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,616,149 bytes with zero final warnings.

No job was rerun and no deadline or success oracle changed. Both complete runs pass the ext4 scenarios, while the original timeout cause remains unproven in Integration #73. This closes CI review for this exact ordinary private mapping graph; subsequent mapping/range implementations retain their own CI acceptance. No active-root isolation or runtime speedup is inferred.

The latest registered data/image checkpoint has separate selected native acceptance and pending CI. Coherent baseline/all-root retirement, readiness, actual root residency, invalidation and complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%.

Original quota-scenario deadline evidence — 23 September 2026: Integration PR run 1750, at 092f67ae5a528d7c41f34c72dcc087bc0132b3ce, completes the maintained 489-scenario catalog with 488 passes and one failure. The original subsystem-e2fs-fat-ext4-quota-positive reaches its unchanged 120-second QEMU deadline, lacks required VFS_IO readiness and contains none of its forbidden fault markers. Its last complete EriX marker is LOGD_REPLY_WAKE_OK; this does not identify the executing instruction or establish a cause. Rust 320/321-test configurations and Markdown pass, as do the managed-frame-occupancy and allocator-domain VM scenarios. Later canonical development/release image and physical-input gates are not reached.

All three complete original job logs are retained with verified lengths and hashes, totaling 13,867,495 bytes with zero warning candidates. Paired push run 1749 is still running in this observation. No input was rerun, deadline widened or success oracle changed. The existing ext4 regression report remains open; this source graph supplies additional failure evidence rather than correction acceptance. Current prepared supervisor-window work and its pending native validation are separate.

Completed paired ext4 CI review — 23 September 2026: The original push run 1749 at 092f67ae5a528d7c41f34c72dcc087bc0132b3ce now passes all 489 maintained VM scenarios, canonical development/release images and the subsequent physical-input gates. Its Rust 320/321-test configurations and Markdown also pass. This is the original paired execution, not a rerun.

Together with PR run 1750, six complete original job logs total 27,356,442 bytes with verified lengths/hashes and zero warning candidates. The paired PR outcome remains 488 passes and one original 120-second quota-scenario timeout. A passing paired run does not identify or correct that failure; the ext4 report remains open. Both terminal executions are fully retained and classified; later source cohorts continue separately.

Original MMP and quota deadline evidence — 23 September 2026: Integration PR run 1752, at 7aa451477c8ac5238bb6c334b69a466b2a94996b, completes the maintained 489-scenario catalog with 487 passes and two failures. Both original subsystem-e2fs-fat-ext4-mmp-positive and subsystem-e2fs-fat-ext4-quota-positive reach their unchanged 120-second QEMU deadlines. MMP contains every required marker, including VFS_IO and Rootd READY, but still fails the required timely emulator exit. Quota lacks VFS_IO. Neither dump contains its forbidden fault markers. Both last complete EriX markers are LOGD_REPLY_WAKE_OK; those observations do not identify the executing instruction or establish a cause.

Rust 320/321-test configurations and Markdown pass, as do the managed-frame-occupancy and allocator-domain scenarios. Later canonical development/release image and physical-input gates are not reached. Three complete original job logs are retained with verified lengths and hashes, totaling 14,245,669 bytes with zero warning candidates. Paired push run 1751 is still running in this observation. No input was rerun, deadline widened or success oracle changed. The existing ext4 regression report remains open; this adds distinct post-readiness and pre-readiness timeout evidence without accepting a correction. Current shared table ownership work and its pending native validation remain separate.

Original named idle deadline evidence — 23 September 2026: Push run 1751, at 7aa451477c8ac5238bb6c334b69a466b2a94996b, completes 488/489 maintained scenarios. Named idle time resolution exceeds its original 60-second deadline and lacks the required zero process-exit status. No forbidden fault marker is present. The last complete marker is STORAGE readiness, followed by partial logging output; this does not establish the cause. The new bug report preserves the canonical report sections and bug/ci/phase-6 metadata.

Three complete original terminal job logs total 13,834,471 bytes with zero warning candidates. Rust 320/321-test matrices, Markdown and both allocator scenarios pass; later canonical images and physical-input gates are not reached. Paired PR run 1752 fails different ext4 deadlines. Neither outcome closes the ext4 report or demonstrates a correction. Original inputs were not rerun and no deadline or acceptance criterion changed.

Additional original CI classification — 24 September 2026:

  • Run 1761, 6df174bb1bda1c61273ec2f483c8420178f1db27, integration job 22322: The ext4 quota catalog scenario fails its original VM deadline; worker 9 reports 39 passed and one failed. Canonical images are not reached. Report #73. Three complete logs: 13,866,342 bytes.

Original complete logs and relevant workflow/runner Git blobs verify. Rust and Markdown pass, with zero warning candidates. These observations do not establish an identical cause to the earlier report, an attributed correction or a Kernel regression. All original failures and requirements are retained without retry; this report remains open pending correction evidence.

## Summary Existing ext4 positive VM scenarios reach their original 120-second QEMU deadline in two completed Integration CI runs. Both complete catalog runs fail, while the Rust and Markdown jobs pass. The failing scenario sets differ; this report records the observed failures without attributing them to filesystem semantics or host load. ## Reproduction The original push and pull-request CI executions at Integration `fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa` run the maintained workflow and all 489 VM scenarios. Run 1705 reports seven failures and run 1706 reports four. These are two original executions, with no rerun, timeout increase or changed success oracle. An isolated clean-image reproduction has not yet been performed. ## Expected and actual behavior Every positive scenario must reach its existing required witnesses inside its declared limit. Run 1705 reports `passed=482 failed=7 total=489`; run 1706 reports `passed=485 failed=4 total=489`. Each listed failure has actual `qemu timed out after 120s` output and scenario status 1; the workflow ends with failed VM workers. | Ext4 scenario suffix | Run 1705 | Run 1706 | | --- | --- | --- | | geometry-positive | timeout | passes | | mmp-positive | timeout | passes | | orphan-file-positive | timeout | passes | | orphan-list-positive | timeout | timeout | | fast-commit-htree-positive | timeout | passes | | quota-positive | timeout | timeout | | fast-commit-linear-positive | timeout | timeout | | links-positive | passes | timeout | All suffixes belong to `tests/scenarios/subsystem-e2fs-fat-ext4-<suffix>.toml`. Retained timeout transcripts end their EriX markers at `ERIX_KERNEL:ROOTD_SMOKE:LOGD_REPLY_WAKE_OK=0000000000000001`. That last printed marker does not identify the instruction executing at the deadline or prove a Logd defect. ## Environment and identity - Integration revision: `fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa`; original source graph and artifact construction are recorded in each linked run. - Workflow: `ci.yml`, original push run 1705 and pull-request run 1706, with 489 maintained VM scenarios and the original 120-second QEMU ceiling. - Architecture: x86_64 with the workflow-selected QEMU, firmware and image inputs; no replacement image is used for this classification. - Input and authority: original scenario-selected boot image and test disk. The observer only reads completed CI status/logs; it grants no guest capability or additional runtime control. - The complete original six job logs are retained with verified lengths and SHA-256 digests. Individual image digests have not yet been independently recovered from CI artifacts. - Last known passing exact graph and a common root cause are not established. ## Evidence and prior checks Complete original CI review — 28 September 2026: These are additional original observations. No unchanged job was rerun, and an identical underlying cause to earlier observations is not assumed. - [CI1812](https://git.erikinkinen.fi/erix/integration/actions/runs/1812), `447f642e4aaf4638a0997d0efc49e41dcd3fc79a`: The ext4 quota VM reaches its original 120-second deadline; every other catalog scenario passes. Three complete logs contain 13,946,086 bytes and zero warning candidates. Rust and Markdown pass. [Original push run 1705](https://git.erikinkinen.fi/erix/integration/actions/runs/1705) and [original pull-request run 1706](https://git.erikinkinen.fi/erix/integration/actions/runs/1706) retain the observed failures. Their Rust jobs each pass 320 and 321 tests, and Markdown passes. All six complete logs have no warning candidates. Expected negative-helper error output is distinct from the final VM failures. Do not treat successful reruns as a correction or widen the original limits. Exact original-contract comparison: ten timeout serial dumps lack their required `ERIX_ROOTD:READY:VFS_IO` marker; the links case also lacks `ERIX_ROOTD:READY:VFS_EXT_LINKS`. The geometry dump already contains its declared required substrings, but still reaches the deadline instead of the required exit. Marker presence cannot replace the exit and timeout checks. None of the eleven dumps contains its scenario's forbidden Kernel fault markers. This narrows the observed stage without proving which operation stalls or why. ## Tracking Original CI1788 follow-up — 25 September 2026: [run1788](https://git.erikinkinen.fi/erix/integration/actions/runs/1788) at `fa857c0964774def6777142afeb7a3c16440abee` records120-second QEMU timeouts for ext4 links (worker4), mmp (worker7) and metadata (worker6). Quota and rename are also affected and remain linked to their existing reports. The complete catalog passes483/491. Original Rust/Markdown pass and verified complete logs contain no warnings. These observations do not establish a common filesystem or host-load cause. Track under [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65) and [the coordinated implementation review](https://git.erikinkinen.fi/erix/integration/pulls/12). The separate [startup timing report](https://git.erikinkinen.fi/erix/integration/issues/72) and [FAT32 timing report](https://git.erikinkinen.fi/erix/integration/issues/70) remain open; shared causation has not been established. Preserve original evidence, identify the failing stage with bounded diagnostics and validate any correction against these unchanged scenario oracles and the complete maintained suite. Later original CI comparison — 22 September 2026: original Integration [1707](https://git.erikinkinen.fi/erix/integration/actions/runs/1707) and [1708](https://git.erikinkinen.fi/erix/integration/actions/runs/1708), at `9c62af2d2484b1ab0cadba768adc025dfd017485`, both pass all 489 VM scenarios, Rust 320/321 tests and Markdown. All six complete job logs are retained and hash-verified, totaling 26,966,330 bytes with zero warning candidates. Both runs explicitly select Kernel `a9bdf6163813d378e0b4a164bceb839e24fbb6b7`. These are later original runs on a different source graph, not retries of 1705/1706. Their success does not identify the cause or demonstrate a correction for the eleven previously retained ext4 timeouts; this report remains open. Further original ext4 CI evidence — 23 September 2026: Integration [1741](https://git.erikinkinen.fi/erix/integration/actions/runs/1741) and [1742](https://git.erikinkinen.fi/erix/integration/actions/runs/1742), at `3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe`, complete the 489-scenario catalog with 478/11 and 481/8 pass/fail outcomes. All nineteen failures are ext4 scenarios reaching their original 120-second QEMU deadline, tracked under [the existing ext4 deadline report](https://git.erikinkinen.fi/erix/integration/issues/73). Rust 320/321-test configurations and Markdown pass. Both corrected managed-frame-occupancy and allocator-domain scenarios pass. The later canonical development/release image and physical-input gates are not reached. Six complete original Integration logs total 34,342,962 bytes and have verified lengths/hashes with zero warning candidates. With the earlier successful Kernel 660/661 and Docs 1025/1026 logs, fourteen complete logs total 35,963,864 bytes and have zero final warnings. All nineteen timeout transcripts lack VFS_IO readiness and contain no scenario-forbidden fault markers. Eighteen end their complete EriX markers at LOGD_REPLY_WAKE_OK; one metadata transcript ends its complete markers at LOGD_REPLY_WRITE_OK followed by a partial next marker. Printed markers do not identify the executing instruction at the deadline or establish a Logd defect, filesystem cause or host-load explanation. These are original executions on a later source graph, without retries, wider deadlines or changed success oracles. The ext4 report remains open. Complete corrected CI acceptance for [Kernel #33](https://git.erikinkinen.fi/erix/kernel/issues/33) and [Kernel #34](https://git.erikinkinen.fi/erix/kernel/issues/34) also remains open; passing selected allocator cases does not stand in for unreached workflow gates. This terminal run pair is fully retained and classified. Newer private mapping population checks and their CI remain separate, and full external-toolchain/runtime and EriX guest rebuilding are still required. | Ext4 scenario suffix | Run 1741 | Run 1742 | | --- | --- | --- | | fast-commit-linear-positive | timeout | timeout | | fast-commit-mixed-positive | timeout | passes | | geometry-positive | timeout | timeout | | links-positive | timeout | timeout | | metadata-positive | timeout | timeout | | orphan-file-positive | timeout | timeout | | orphan-list-positive | timeout | passes | | quota-positive | timeout | timeout | | rename-positive | timeout | timeout | | stable-resize-positive | timeout | timeout | | xattr-positive | timeout | passes | Original-image ext4 counter diagnostic — 23 September 2026: The isolated geometry scenario at Integration `3c92de7ff68b332adc5d5de41e0e06af7ed4c1fe`, selecting Kernel `03f3412076a9dde92ad4e89902d5ec8497a08476`, passes locally under its original 120-second deadline with no warnings. Original pre-execution firmware, writable disks, ESP and exact command are retained. A separate TCG execution uses those same guest bytes and the original 120/45-second hard/silence bounds; guest exit, all scenario markers and the maintained filesystem postconditions pass without warnings. The complete counter capture contains 78,599 translations, 1,611,237 code bytes and zero missed executions. Sixty complete ELF byte strings are verified inside the exact selected boot image; unembedded artifacts are excluded. Top 100 code groups cover 86.72% of the instruction upper bound. Unique Kernel mapping-batch and VSpace permission-switch code candidates contribute 29.60% and 7.02%; SHA2 candidates contribute 4.24%, other unique matches 5.46%, ambiguous matches 8.45% and unmatched code 31.95%. These are executed-code candidates, not process identity, CPU time or a speedup. They support continuing the [owned-address-space work](https://git.erikinkinen.fi/erix/kernel/issues/22) while preserving backing custody, W^X, validation and invalidation. The first instrumented attempt exited before guest startup because the minimal host emulator lacked QCOW1 for the original writable FAT-directory drive. That failure is retained. A separate original-upstream host build adds only that backend and passes all five actual profiler ABI controls before the successful capture. External configuration retains its known unavailable-static-glib warning; compilation, controls and EriX guest execution have no warnings. The [operator guidance and diagnostic record](https://git.erikinkinen.fi/erix/integration/commit/092f67ae5a528d7c41f34c72dcc087bc0132b3ce) are signed and pushed through [Integration PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12). Markdown, formatting and diff checks pass; every executable, test, workflow and dependency byte remains identical to the preceding validated tree. [Integration #73](https://git.erikinkinen.fi/erix/integration/issues/73) remains open: isolated success and TCG instruction counts do not explain the nineteen original CI deadlines. No failing CI job was rerun, no limit was widened and no success oracle changed. Current source caches are restored after retaining the diagnostics. External toolchain/runtime rebuilding and both complete EriX guest-build generations remain mandatory and unproven. No phase acceptance checklist item is closed by this diagnostic. Complete owned-traversal CI review — 23 September 2026: original Integration [1743](https://git.erikinkinen.fi/erix/integration/actions/runs/1743) and [1744](https://git.erikinkinen.fi/erix/integration/actions/runs/1744), at `4fce71efe6277332b7dcad110c9c87eb57040e58` selecting Kernel `b90a80c94721f99d2a829117dd29123b3aaebc7c`, both pass all 489 catalog VM scenarios. Native lifetime, managed-frame occupancy, allocator-domain, canonical development/release images, physical input and remaining workflow gates pass. Rust 320/321-test configurations, profiler validation and Markdown also pass. Six complete Integration logs total 26,973,962 bytes with zero warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,603,130 bytes with zero final warnings. This graph retains the exact corrected reserved-heap and temporary-CSpace cleanup code, and its Kernel descends from their signed correction. Complete corrected CI now closes [Kernel #33](https://git.erikinkinen.fi/erix/kernel/issues/33) and [Kernel #34](https://git.erikinkinen.fi/erix/kernel/issues/34). Their original native/host failures and later nineteen ext4 CI deadlines remain retained. No failing job was rerun and no limit or success oracle changed. Both new full runs pass the ext4 scenarios; the original timeout cause is still unproven, so [Integration #73](https://git.erikinkinen.fi/erix/integration/issues/73) remains open for attribution and timing review. Later leaf/population/ancestor cohorts retain their own CI acceptance. Complete semantic authority review, root activation, external Rust/LLVM/runtime rebuilding and both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Complete private-leaf construction CI review — 23 September 2026: original Integration [1745](https://git.erikinkinen.fi/erix/integration/actions/runs/1745) and [1746](https://git.erikinkinen.fi/erix/integration/actions/runs/1746), at `4bc569bef76af4d4ce619dbe97ebc79a54cfdb6f` selecting Kernel `4e58b1463749f761ab8a76ebd2cf39c583b5e62b`, both pass all 489 catalog VM scenarios and the subsequent canonical development/release, physical-input and release-policy gates. Native lifetime, managed occupancy and allocator-domain checks pass. Rust 320/321-test configurations, profiler validation and Markdown pass. Six complete Integration logs total 26,972,820 bytes without warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,611,312 bytes with zero final warnings. No job was rerun and no deadline or success oracle changed. Both complete runs pass the ext4 scenarios, while the original timeout cause remains unproven in [Integration #73](https://git.erikinkinen.fi/erix/integration/issues/73). This closes CI review for this exact private-leaf construction graph; subsequent mapping/range implementations retain their own CI acceptance. No active-root isolation or runtime speedup is inferred. Registered image/stack population, readiness, actual root residency, invalidation, complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Complete ordinary private mapping CI review — 23 September 2026: original Integration [1747](https://git.erikinkinen.fi/erix/integration/actions/runs/1747) and [1748](https://git.erikinkinen.fi/erix/integration/actions/runs/1748), at `7855069f7c137f6eb76f3d05d7d20eadf7e2929e` selecting Kernel `f782ee68035fefb7bd30f5ac69373ecfc1eeac2d`, both pass all 489 catalog VM scenarios and the subsequent canonical development/release, physical-input and release-policy gates. Native lifetime, managed occupancy and allocator-domain checks pass. Rust 320/321-test configurations, profiler validation and Markdown pass. Six complete Integration logs total 26,973,516 bytes without warning candidates; with eight previously reviewed Kernel/Docs logs, fourteen complete logs total 28,616,149 bytes with zero final warnings. No job was rerun and no deadline or success oracle changed. Both complete runs pass the ext4 scenarios, while the original timeout cause remains unproven in [Integration #73](https://git.erikinkinen.fi/erix/integration/issues/73). This closes CI review for this exact ordinary private mapping graph; subsequent mapping/range implementations retain their own CI acceptance. No active-root isolation or runtime speedup is inferred. The latest registered data/image checkpoint has separate selected native acceptance and pending CI. Coherent baseline/all-root retirement, readiness, actual root residency, invalidation and complete semantic authority review and external Rust/LLVM/runtime rebuilding plus both complete EriX guest-build generations remain required. Canonical acceptance stays 15/460 leaves, weighted 3.48%. Original quota-scenario deadline evidence — 23 September 2026: Integration [PR run 1750](https://git.erikinkinen.fi/erix/integration/actions/runs/1750), at `092f67ae5a528d7c41f34c72dcc087bc0132b3ce`, completes the maintained 489-scenario catalog with 488 passes and one failure. The original `subsystem-e2fs-fat-ext4-quota-positive` reaches its unchanged 120-second QEMU deadline, lacks required VFS_IO readiness and contains none of its forbidden fault markers. Its last complete EriX marker is LOGD_REPLY_WAKE_OK; this does not identify the executing instruction or establish a cause. Rust 320/321-test configurations and Markdown pass, as do the managed-frame-occupancy and allocator-domain VM scenarios. Later canonical development/release image and physical-input gates are not reached. All three complete original job logs are retained with verified lengths and hashes, totaling 13,867,495 bytes with zero warning candidates. Paired push run 1749 is still running in this observation. No input was rerun, deadline widened or success oracle changed. [The existing ext4 regression report](https://git.erikinkinen.fi/erix/integration/issues/73) remains open; this source graph supplies additional failure evidence rather than correction acceptance. Current prepared supervisor-window work and its pending native validation are separate. Completed paired ext4 CI review — 23 September 2026: The original [push run 1749](https://git.erikinkinen.fi/erix/integration/actions/runs/1749) at `092f67ae5a528d7c41f34c72dcc087bc0132b3ce` now passes all 489 maintained VM scenarios, canonical development/release images and the subsequent physical-input gates. Its Rust 320/321-test configurations and Markdown also pass. This is the original paired execution, not a rerun. Together with [PR run 1750](https://git.erikinkinen.fi/erix/integration/actions/runs/1750), six complete original job logs total 27,356,442 bytes with verified lengths/hashes and zero warning candidates. The paired PR outcome remains 488 passes and one original 120-second quota-scenario timeout. A passing paired run does not identify or correct that failure; [the ext4 report](https://git.erikinkinen.fi/erix/integration/issues/73) remains open. Both terminal executions are fully retained and classified; later source cohorts continue separately. Original MMP and quota deadline evidence — 23 September 2026: Integration [PR run 1752](https://git.erikinkinen.fi/erix/integration/actions/runs/1752), at `7aa451477c8ac5238bb6c334b69a466b2a94996b`, completes the maintained 489-scenario catalog with 487 passes and two failures. Both original `subsystem-e2fs-fat-ext4-mmp-positive` and `subsystem-e2fs-fat-ext4-quota-positive` reach their unchanged 120-second QEMU deadlines. MMP contains every required marker, including VFS_IO and Rootd READY, but still fails the required timely emulator exit. Quota lacks VFS_IO. Neither dump contains its forbidden fault markers. Both last complete EriX markers are LOGD_REPLY_WAKE_OK; those observations do not identify the executing instruction or establish a cause. Rust 320/321-test configurations and Markdown pass, as do the managed-frame-occupancy and allocator-domain scenarios. Later canonical development/release image and physical-input gates are not reached. Three complete original job logs are retained with verified lengths and hashes, totaling 14,245,669 bytes with zero warning candidates. Paired push run 1751 is still running in this observation. No input was rerun, deadline widened or success oracle changed. The [existing ext4 regression report](https://git.erikinkinen.fi/erix/integration/issues/73) remains open; this adds distinct post-readiness and pre-readiness timeout evidence without accepting a correction. Current shared table ownership work and its pending native validation remain separate. Original named idle deadline evidence — 23 September 2026: [Push run 1751](https://git.erikinkinen.fi/erix/integration/actions/runs/1751), at `7aa451477c8ac5238bb6c334b69a466b2a94996b`, completes 488/489 maintained scenarios. Named idle time resolution exceeds its original 60-second deadline and lacks the required zero process-exit status. No forbidden fault marker is present. The last complete marker is STORAGE readiness, followed by partial logging output; this does not establish the cause. The [new bug report](https://git.erikinkinen.fi/erix/integration/issues/75) preserves the canonical report sections and bug/ci/phase-6 metadata. Three complete original terminal job logs total 13,834,471 bytes with zero warning candidates. Rust 320/321-test matrices, Markdown and both allocator scenarios pass; later canonical images and physical-input gates are not reached. Paired PR run 1752 fails different ext4 deadlines. Neither outcome closes the [ext4 report](https://git.erikinkinen.fi/erix/integration/issues/73) or demonstrates a correction. Original inputs were not rerun and no deadline or acceptance criterion changed. Additional original CI classification — 24 September 2026: - [Run 1761](https://git.erikinkinen.fi/erix/integration/actions/runs/1761), `6df174bb1bda1c61273ec2f483c8420178f1db27`, integration job 22322: The ext4 quota catalog scenario fails its original VM deadline; worker 9 reports 39 passed and one failed. Canonical images are not reached. [Report #73](https://git.erikinkinen.fi/erix/integration/issues/73). Three complete logs: 13,866,342 bytes. Original complete logs and relevant workflow/runner Git blobs verify. Rust and Markdown pass, with zero warning candidates. These observations do not establish an identical cause to the earlier report, an attributed correction or a Kernel regression. All original failures and requirements are retained without retry; this report remains open pending correction evidence.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:23 +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#73
No description provided.