[BUG] Existing ext4 quota VM scenario exceeds its QEMU deadline #18
Open
opened 2026-09-12 11:15:01 +02:00 by erikinkinen
·
0 comments
No Branch/Tag specified
main
fix/bounded-source-path-diagnostics
fix/configured-boot-tool-revision
fix/propagate-image-manifest-failures
feature/service-cargo-dependency-aliases
feature/consistent-dynlink-compiler-metadata
feature/configured-image-cargo-routing-merge-ready-5583860a
fix/trusted-frame-snapshot-identity
feature/native-startup-compiler-selections-merge-ready-0761fd75
feature/exact-kernel-runtime-exports-merge-ready-f1cdc8b6
feature/native-startup-compiler-selections-72ec5647
feature/exact-kernel-runtime-exports-merge-ready-39827352
fix/configured-image-cargo-routing
feature/shared-development-source-selection
feature/native-input-owner-cohort
feature/retained-source-range-comparison-merge-ready-012d1dc4
feature/completed-python-syntax-progress-merge-ready-45097d26
feature/retained-fixture-metadata-merge-ready-eb7dfbea
feature/retained-fixture-source-paths-merge-ready-fc961955
feature/retained-image-failed-queue-merge-ready-52c5cdb3
feature/retained-native-companion-source-merge-ready-36ba241f
feature/retained-image-metadata-python-merge-ready-2331d9b0
feature/vfsd-conditional-resize-provider
feature/vfsd-directory-access-provider
feature/retained-source-range-comparison-merge-ready-dfb8c6e7
feature/retained-fixture-metadata-merge-ready-37b4dc99
feature/retained-fixture-source-paths-merge-ready-c823d028
feature/retained-image-failed-queue-merge-ready-8c4c37ba
feature/retained-native-companion-source-merge-ready-60f7cf9e
feature/vfsd-permission-evidence-provider
feature/completed-python-syntax-progress-merge-ready-3d8d5288
feature/retained-image-metadata-python-merge-ready-38f1c74e
feature/vfs-three-region-capacity-merge-ready-bb59d3b6
feature/vfsd-directory-root-companions
feature/retained-source-range-comparison-merge-ready-bbaf8a9e
feature/retained-source-range-comparison-merge-ready-9b231c76
feature/retained-image-failed-queue-merge-ready-51d5cd03
feature/retained-native-companion-source-merge-ready-0b4be9dc
feature/retained-fixture-source-paths-merge-ready-c01cc992
feature/retained-fixture-metadata-merge-ready-e476d0d7
feature/retained-image-metadata-python-merge-ready-847d3fac
feature/completed-python-syntax-progress-merge-ready-3b81e619
feature/retained-fixture-metadata-merge-ready-f55a380e
feature/retained-image-metadata-python-merge-ready-e2524564
feature/cargo-bundle-stage-observations-merge-ready-9e5f66f9
feature/cargo-bundle-stage-observations
feature/interactive-probe-diagnostics
feature/complete-firmware-fixture-inputs-merge-ready-9022dca4
feature/portable-git-error-fixture-merge-ready-9a9424b8
feature/catalog-fixture-policy-controls
perf/generic-caller-native-owner
feature/root-runtime-main-dependencies
feature/retained-bootstrap-progress
feature/explicit-kernel-runtime-exports
fix/bootstrap-ci-companion-profile
feature/main-ci-provider-policy
feature/retained-host-executable-birth
fix/artifact-upload-stage-diagnostics
fix/image-grant-retirement-registration
feature/local-catalog-source-ownership
fix/explicit-companion-branch-policy
fix/native-diagnostic-fixture-startup-budget
fix/generated-source-retirement-proof
fix/native-c-helper-source-cohort
feature/clean-standalone-library-variants
fix/shared-service-symbol-restoration
feature/legacy-sdk-tool-custody
feature/retained-runtime-disk-formatter
fix/kernel-dynamic-dependency-order
feature/current-api-reference-scope
feature/retained-ext4-population-budget
feature/explicit-exsh-lifecycle-catalog
feature/retained-vfs-capacity-assembly
feature/native-boot-offline-sources
fix/source-descriptor-acquisition-custody
feature/retained-ext4-image-readback
feature/retained-image-library-variants
feature/retained-helper-import-edges
feature/retained-git-validation-duties
feature/native-graph-terminal-retirement
feature/retained-vm-python-selection
feature/native-c-process-contract
feature/extended-release-payload-policy
feature/retained-source-range-comparison
feature/owned-vm-command-lifetimes
feature/owned-git-acquisition-progress
feature/completed-python-syntax-progress
feature/retained-fixture-metadata
feature/owned-source-directory-persistence
feature/native-graph-held-guard-checks
feature/native-c-owner-input-cohort
feature/retained-image-metadata-python
feature/retained-signing-key-consumption
feature/retained-boot-tool-image-build
feature/retained-host-data-use
feature/retained-efi-development-link-staging
feature/retained-image-manifest-inputs
feature/native-extended-profile-inputs
fix/source-closure-entry-diagnostics
feature/owned-offline-catalog-preparation
feature/native-c-artifact-matrix
fix/raw-live-scope-freshness
feature/native-c-pure-owner-cohort
perf/source-bookend-ancestry-boundary
fix/preparation-profile-custody
perf/source-descriptor-admission
feature/native-scripted-build-cli
feature/native-scripted-root-build
feature/native-live-output-custody
fix/catalog-graph-prepared-profile
fix/root-source-bytecode-producer
fix/shared-source-diagnostic-expectations
fix/source-closure-diagnostics
fix/source-root-admission
perf/target-history-comparison
perf/catalog-helper-parent-boundary
perf/target-output-completion-boundary
perf/census-directory-borrows
refactor/native-custody-core
refactor/constructor-owned-binding
perf/constructor-dependency-source-boundary
fix/historical-output-capture-interval
perf/retained-input-hash-streams
fix/caller-controller-signal-admission
perf/recipe-runtime-binding-projection
test/efi-offline-original-inputs
test/efi-source-bundle-selection
fix/input-control-fixture-storage
perf/unit-query-binding-projection
perf/constructor-dependency-projection
fix/compiler-input-consumer-enrollment
perf/offline-context-output-batch
perf/target-cfi-source-bookends
perf/target-input-source-proof
perf/target-profile-query-boundary
perf/constructor-query-boundary
fix/input-diagnostics-ci-storage
fix/settled-recipe-lease-failure
fix/efi-fixture-source-entries
fix/catalog-helper-descriptor-lifetime
perf/source-tool-proof-projection
perf/owned-input-module-compilation
perf/recipe-unit-output-validation
perf/catalog-helper-borrow-pairs
perf/owned-input-root-imports
perf/owned-code-parse-reuse
test/original-output-capture-faults
perf/recipe-capture-completion-continuation
perf/recipe-selected-runtime-proof
perf/efi-completion-proof-projections
test/connected-efi-current-producers
perf/target-completion-output-return
fix/linked-image-runtime-registration
fix/offline-forest-negative-retirement
perf/recipe-output-capture-batch
fix/runtime-link-retirement-order
fix/cargo-free-offline-inputs
fix/vm-fixture-timeout-evidence
perf/recipe-unit-output-proofs
perf/target-prepared-producer-binding
perf/recipe-unit-input-proofs
fix/scripted-artifact-stage-diagnostics
perf/helper-chunk-descriptor-use
perf/recipe-fixed-effect-source-proofs
test/connected-recipe-efi-publication
fix/recipe-owned-dependency-bindings
perf/helper-proof-row-index
fix/shared-helper-selection-controls
perf/source-history-projection
perf/native-target-query-proofs
feature/native-scripted-root-driver
fix/native-target-control-runner
fix/compiler-tool-fixture-portability
fix/recipe-source-loan-doc-wrap
perf/catalog-helper-verification
fix/native-helper-runner-syntax
feature/recipe-efi-artifact-adoption
feature/native-recipe-target-compiler
feature/native-recipe-target-closure
feature/native-build-script-producers
feature/native-recipe-external-inputs
fix/recipe-executable-source-checks
feature/observed-unit-origins
feature/native-recipe-root-units
feature/external-source-scope-withdrawal
fix/native-profile-trim-paths
feature/owned-native-build-pipeline
feature/native-build-script-call
feature/source-input-offline-execution
feature/recipe-executable-inputs
fix/runtime-input-original-registration
feature/native-recipe-source-leases
feature/native-recipe-product-files
perf/source-consumer-selection-proofs
feature/native-build-script-environment
fix/source-input-entry-guard
fix/source-input-fixture-tool-selection
perf/catalog-source-postcheck-proofs
fix/shared-shallow-fetch-prefix
fix/compiler-input-receiver-birth
perf/passive-helper-verification
fix/cargo-shallow-fetch-prefix
perf/offline-retained-space-checks
perf/source-consumer-adjacent-proofs
perf/source-archive-member-lookup
feature/production-source-bundle-publications
perf/immutable-source-export-selection
fix/native-fixture-retirement-order
feature/complete-source-input-catalog
feature/prepared-source-production-join
fix/qualified-source-fixture-python
fix/gateway-source-failure-diagnostics
fix/source-bundle-original-custody
feature/native-release-output-publications
feature/production-cargo-publications
feature/source-input-production-join
fix/owned-region-source-baseline
feature/archive-byte-codec
feature/owned-release-file-writer
fix/diagnostic-fixture-startup-budget
fix/native-wrapper-fixture-ordering
fix/production-export-initialization
fix/shared-helper-source-closure
feature/owned-original-git-packs
perf/runtime-artifact-tls-lifetime
feature/production-source-object-inputs
feature/native-production-offline-sources
feature/native-production-contract
feature/native-link-history-selection
perf/native-signal-mask-observations
feature/native-graph-preparation-profiling
fix/native-rust-ci-contract
fix/self-contained-native-metadata
fix/native-graph-fixture-toolchain
fix/catalog-source-work-owner
feature/rust-rlib-metadata-revision
fix/rlib-long-name-diagnostics
feature/gptfdisk-runtime-inputs
fix/host-ci-fixture-contracts
fix/input-owner-bootstrap-cohort
feature/cabal-metadata-revision-selection
feature/git-portable-string-configuration
feature/locale-byte-string-producers
feature/owned-vm-input-code
feature/memory-string-family-producers
fix/retained-census-progress
feature/toolchain-cxx-runtime-inputs
fix/catalog-metadata-planning-borrow
feature/native-current-locale-scenario
feature/current-locale-multibyte
feature/source-history-depth
feature/catalog-compilation-input-lifetime
fix/retained-helper-read-directories
feature/owned-coreutils-scenario
feature/scenario-owned-directory-build
feature/build-scope-toolchain-ownership
feature/native-build-source-contract
feature/clean-native-image-closure
feature/readonly-ext4-population-selection
feature/gpt-layout-readback
feature/ext4-format-readback-contract
feature/retained-partition-readback
feature/explicit-inventory-source-revisions
feature/retained-image-driver
feature/retained-image-failed-queue
feature/retained-native-companion-source
feature/retained-fixture-source-paths
feature/retained-image-gpt-inputs
feature/retained-efi-image-build
feature/native-graph-retirement-diagnostics
feature/retained-image-artifact-inputs
feature/native-graph-input-materialization
feature/native-graph-kernel-allocation-contract
feature/retained-image-kernel
feature/native-graph-allocation-runtime
feature/native-artifact-graph-execution
feature/retained-native-runtime-links
feature/compiler-runtime-input-binding
feature/native-boot-linked-artifact-owners
feature/native-compiler-environment-identity
feature/native-graph-object-symbols
feature/native-boot-runtime-link
feature/selected-native-runtime-inputs
feature/graph-compiler-retained-accounting
feature/native-boot-compiler-stages
feature/native-boot-artifact-graph
feature/native-graph-product-integrity
feature/owned-stream-directory-image
feature/directory-stream-workload
feature/native-allocation-error-contract
feature/native-graph-allocation-marker
feature/native-boot-profile-matrix
feature/native-alloc-runtime-input
feature/native-allocation-marker
feature/native-package-version-input
feature/sha2-owned-stream-vm
feature/owned-shell-frame-inventory
feature/posix-compat
feature/exfat-final-upcase-literal
feature/realm-counted-file-resize-fixture
feature/rustdoc-ci-helper-provider
feature/counted-realm-binding-fixture
feature/realm-credential-fixtures
feature/counted-realm-authority-deployment
feature/native-realm-caller-loss-fixture
feature/native-realm-capacity-reuse-controls
feature/configured-private-byte-client-fixture
feature/guarded-private-mediator-fixtures
feature/native-realm-admission-fixture
feature/disabled-realm-startup-controls
feature/explicit-realm-startup-storage
feature/selected-exfat-large-cluster-media
feature/selected-fat-detached-recovery
feature/orchestration-rustdoc-contracts
feature/offline-toolchain-bootstrap-graph
feature/ram-entry-capacity-lifetimes
feature/imported-payload-contracts
feature/offline-payload-source-store
feature/native-gitlink-source-roles
feature/selected-exfat-catalog-growth
feature/dependency-policy-source-custody
feature/selected-fat-undo-catalog-fixtures
feature/process-local-output-observers
feature/live-ci-output-source-closure
feature/plain-ext-undo-fixtures
feature/charged-ci-input-extents
feature/exact-public-ci-source-graph
feature/ci-preparation-progress
feature/explicit-ci-output-custody
feature/python-test-failure-retention
feature/retained-cargo-ci-consumers
feature/source-bound-python-test-shards
feature/isolated-python-host-tests
feature/strict-non-cargo-source-roots
feature/explicit-offline-preparation-command
feature/original-acquisition-integrity
feature/owned-preparation-progress
feature/snapshot-persistence-profiler
feature/original-object-transport
feature/portable-cargo-graphs
feature/generated-cargo-lock-inputs
feature/inventory-bound-source-delivery
feature/original-git-object-custody
feature/original-main-source-pipeline
feature/declared-build-scope
feature/joined-scenario-catalog-lifetime
feature/complete-tracked-source-size
feature/source-preserving-syntax
feature/bounded-startup-profiler
feature/correlated-vm-failure-status
feature/original-native-c-memory-linking
feature/explicit-offline-vm-networking
feature/orchestration-module-contracts
feature/owned-host-command-lifetimes
feature/selected-compiler-cache-inputs
feature/dynamic-compiler-coordinates
feature/watchdog-fixture-writers
feature/dynamic-image-serialization
feature/dynlink-fixture-readers
feature/ci-source-acquisition
feature/cross-repository-policy-checks
feature/native-cli-media-module-controls
feature/explicit-original-ci-source-graph
feature/balanced-python-host-shards
feature/kernel-return-helper-cohort
feature/rootd-fixture-source-selection
feature/enclosing-cargo-work-budget
feature/dynamic-cache-helper-inputs
feature/realm-readiness-workload-group
feature/dynamic-symbol-export-visibility
feature/retained-native-byte-inspection
feature/explicit-shared-library-variants
feature/object-symbol-syntax-coverage
feature/object-symbol-inspection
feature/compiler-bound-shared-identities
feature/scenario-harness-policy-closure
feature/block-fixture-source-cleanliness
feature/cargo-rlib-native-objects
feature/generated-cargo-regression-fixtures
feature/compiler-observation-retirement
feature/cargo-native-compiler-observations
feature/host-tool-admission-checks
feature/ci-scenario-heap-policy-inputs
feature/retained-host-tool-artifacts
feature/retained-source-only-boot-inputs
feature/generated-cargo-lock-refresh-order
feature/retained-native-library-artifacts
feature/retained-efi-artifact
feature/native-boot-command-profiles
feature/native-profile-fixture-storage
feature/retained-service-builder-inputs
feature/native-boot-required-target-features
feature/native-boot-build-profiles
feature/retained-primary-native-artifacts
feature/native-build-fixture-prerequisites
feature/ci-component-fixture-inputs
feature/native-object-fixture-toolchain
feature/coherent-native-boot-source-graph
feature/native-build-validation-inputs
feature/workspace-feature-source-helper-cohort
feature/precheck-owned-live-output
feature/detached-syntax-fixture-storage
feature/workspace-feature-preparation
feature/native-input-progress-diagnostics
feature/native-end-copy-source-controls
feature/current-rootd-fixture-policy
feature/host-cancellation-retained-evidence
feature/clock-ci-tool-components
feature/coreutils-provider-validation-source-graph
feature/coreutils-nested-ci-environment
feature/explicit-console-font-inputs
feature/selector-validation-source-graph
feature/rustdoc-authored-input-controls
feature/readonly-storage-verifier
feature/direct-exsh-default-controls
feature/integration-native-fixture-source
feature/physical-selector-reviews
feature/runtime-root-porting-wave-coverage
feature/four-way-host-validation
feature/physical-command-echo
feature/caller-loss-readiness-controls
feature/offline-command-fixture-lifetimes
feature/cargo-catalog-membership
feature/python-test-phase-profile
feature/block-durability-workloads
feature/timed-clock-contract
feature/component-catalog-source-cleanliness
feature/selected-compiler-target-preflight
feature/shared-cargo-capture
feature/native-c-error-catalog-consumers
feature/native-conversion-consumers
feature/bounded-source-read-cleanup
feature/owned-fetch-capture
feature/readonly-configuration-clis
feature/portable-generated-symbols
feature/gpt-formatter-route-controls
feature/coherent-host-validation
feature/retained-source-blob-layout
feature/external-descriptor-diagnostic-output
feature/inert-cleanup-diagnostics
feature/native-descriptor-query-diagnostic
feature/native-signal-policy-controls
feature/native-binary-output-controls
feature/native-cleanup-diagnostic-controls
feature/complete-file-identity-layout
feature/ordinary-service-read-accounting
feature/retained-compilation-inputs
feature/retained-service-source-comparison
feature/ordinary-service-shared-libraries
feature/kernel-fixture-parser-source-closure
feature/native-descriptor-inheritance
feature/original-source-rustdoc-json
feature/standalone-vm-worker-custody
feature/input-helper-completion-custody
feature/failed-vm-metadata-retention
feature/ci-runtime-profile-contracts
feature/source-signal-disposition-query
feature/source-directory-identity-comparison
feature/native-test-runtime-source-cohort
feature/registry-fixture-source-closure
feature/owned-service-artifact-route
feature/compiled-terminal-provider-inputs
feature/service-source-scenario-cleanliness
feature/coreutils-provider-ci-context
feature/native-vm-process-custody
feature/ci-rustdoc-source-policy
feature/native-runtime-service-source-cohort
feature/ci-native-worker-completion
feature/complete-worker-source-verification
feature/rust-documentation-policy
feature/rootd-complete-policy-api
feature/native-binary-printf-workflows
feature/native-cmp-workflows
feature/runtime-fixture-policy-consistency
feature/vfs-namespace-cancellation
feature/vfs-three-region-capacity
feature/sha2-host-command-fixture
feature/native-sha2-verification-workflows
feature/coreutils-catalog-provider-selection
feature/ext-special-inode-contract
feature/borrowed-product-launch-records
feature/rootd-bootstrap-policy
feature/conventional-terminal-speed-symbols
feature/held-directory-filesystem-workload
feature/terminal-contract-markdown
feature/owned-runtime-fingerprint-inputs
feature/native-c-terminal-runtime
feature/native-runtime-counted-capacity
feature/terminal-control-storage
feature/native-c-time-runtime
feature/scoped-filesystem-source-record
feature/native-c-scoped-filesystem-client
feature/gpt-typed-formatter-oracle
feature/realm-description-policy-oracles
feature/process-root-private-symbol-checks
feature/counted-original-description-pools
feature/scenario-source-read-only
feature/native-c-termios-parameters
feature/process-root-active-dependency-closure
feature/native-c-pipe-creation-probe
feature/native-c-readiness-probe
feature/native-c-multibyte-runtime
feature/native-c-descriptor-io
feature/typed-realm-fixture-prerequisites
feature/native-cpu-local-execution-fixture
feature/caller-loss-fixture-readiness
feature/native-default-acl-inheritance
feature/native-persistent-acl-metadata
feature/catalog-service-build-lifetimes
feature/foundation-fixture-contracts
feature/acquired-catalog-provider-objects
feature/native-ext4-product-population
feature/explicit-ext4-image-initialization
feature/ordinary-c-process-startup
feature/owner-driven-manual-fixture
feature/native-input-failure-diagnostics
feature/native-process-heap-runtime
feature/owned-vm-input-helpers
feature/composed-component-manuals
feature/native-offline-manual-store
feature/pathname-and-shell-help-workflows
feature/dynamic-metadata-page-permissions
feature/native-fat32-esp-construction
feature/owned-gpt-payload-assembly
feature/owned-gpt-image-construction
feature/native-capture-stream-progress
feature/shared-compiler-coordinates
feature/catalog-terminal-waiter-fixture
feature/timed-deadline-adapter-inventory
feature/catalog-cargo-provider-graph
feature/retained-command-retirement-allowance
feature/scoped-boot-image-workflows
feature/lexical-continuation-storage
feature/native-runtime-record-contract
feature/shell-transport-target-layout
feature/recipient-stream-view-packaging
feature/native-runtime-fixture-catalog-controls
feature/counted-job-runtime-policy-storage
feature/native-boot-command-inventory
feature/native-runtime-consumer-cohorts
feature/native-runtime-source-cohorts
feature/native-c-source-owner-cohort
feature/owned-source-cache-identity
feature/native-sha-plan-controls
feature/terminal-packaging-waiter-controls
feature/retained-boot-tool-operation
feature/declared-dependency-feature-selection
feature/shared-object-builder-modules
feature/command-workspace-harness-inputs
feature/native-c-memory-producer
feature/authenticated-publication-policy
feature/command-catalog-packaging
feature/descendant-termination-grace
feature/fixture-socket-io
feature/fixture-startup-ownership
feature/packaging-catalog-layout-controls
feature/owned-boot-tool-producer
feature/native-duplex-socket-workloads
feature/wide-device-fixture-encoding
feature/exsh-packaging-catalog-fixture
feature/caller-loss-helper-source-closure
feature/persisted-filesystem-timestamps
feature/filesystem-time-contract-wording
feature/native-cli-fat-catalog
feature/truthful-filesystem-timestamps
feature/guarded-native-thread-fixture
feature/native-caller-loss-command-custody
feature/elf-original-byte-inspection
feature/native-thread-factory-intake
feature/realm-client-dynamic-registration
feature/externally-clocked-owned-commands
feature/loader-tls-storage-capacity
feature/runtime-heap-policy-coherence
feature/procd-tls-packet-capacity
feature/three-column-client-framing
feature/recipient-readiness-capacity
feature/standard-readiness-storage-policy
feature/ci-component-source-layout-controls
feature/live-realm-filesystem-lifetimes
feature/pty-readiness-capacity
feature/package-assembly-source-snapshot
feature/public-deadline-capacity
feature/counted-job-program-storage
feature/counted-ram-name-storage
feature/realm-fifo-storage-fixture
feature/kernel-fixture-harness-inputs
feature/realm-pipe-clock-policy
feature/retire-legacy-git-transport-overrides
feature/selected-component-catalog-binding
feature/filesystem-compliance-source-evidence
feature/detached-fixture-output-custody
feature/native-default-sigpipe-fixture
feature/realm-directory-relative-open-fixture
feature/realm-linked-parent-mount-fixture
feature/realm-retained-link-image-fixtures
feature/realm-acquisition-scope-fixture
feature/realm-descriptor-alias-fixture
feature/native-fixture-ci-source-graph
feature/portable-git-error-fixture
feature/complete-firmware-fixture-inputs
feature/integration-rust-source-graph
feature/native-cli
feature/phase-4-audit
feature/dynlink
feature/program-loader
feature/e2fs-fat
feature/block-devices
feature/vfs
feature/centralized-process-authority
ci-feature-interactive-probe-diagnostics
ci-feature-ci-source-acquisition
ci-feature-posix-compat
nightly
ci-feature-native-cli
ci-feature-phase-4-audit
ci-feature-dynlink
ci-feature-program-loader
ci-feature-e2fs-fat
ci-feature-block-devices
ci-feature-vfs
ci-feature-centralized-process-authority
Labels
Clear labels
alpha-1
EriX Alpha 1 release acceptance
bug
Something is not working
ci
docs
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
performance
Measured performance profiling, bottleneck analysis, and regression budgets.
phase-6
Phase 6: POSIX compatibility, full EriX self-hosting, and its required audits and validation.
question
More information is needed
refactor
Code cleanup, removal of obsolete paths, and structural improvements preserving behavior.
security
wontfix
This won't be fixed
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#18
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The existing ext4 quota VM scenario timed out in the full Integration catalog. The workflow continued to later scenarios with a recorded failure, so a completed catalog cannot be accepted as passing.
Reproduction
Observed in PR CI run 1560 at Integration
e7995dc7a2, worker 6, scenario subsystem-e2fs-fat-ext4-quota-positive. The bounded catalog's bootloader VM stage 3/3 reached the QEMU overall 120-second deadline and terminated QEMU through the timeout wrapper.The same quota scenario also timed out at 09:33:48 UTC in push run 1561, revision
5bf0fd2c84dd7cd838655cd8abc6915997868a04. Both observations are retained; an isolated deterministic reproduction and the underlying cause are not yet established. Do not retry unchanged inputs until green or increase the deadline to claim a correction.Expected and actual behavior
Expected: the existing scenario completes its required success/cleanup checks within the unchanged declared deadline.
Actual: QEMU overall timeout at 09:07:23 UTC on 2026-09-12. No serial-silence timeout was reported. Run 1560 is now a terminal failure: all twelve worker summaries total 485 passed and one failed out of 486 catalog scenarios. Later dependent integration steps did not establish acceptance. Run 1561 is also a terminal failure: all twelve worker summaries independently total 485 passed and one failed out of 486. It repeats the same quota timeout. Neither failed catalog establishes acceptance for subsequent dependent steps.
Environment and identity
e7995dc7a2.Evidence and prior checks
Complete logs identify 119 packaging refusals caused by an obsolete smoke-only Launchd policy tuple. The same producer remains defective at
4efc9d5d; the new host regression reproduces its status-1 rejection. Issue 96 tracks the correction and native regression acceptance.The other failures are three realm PREPARE refusals matching the older guarded-fixture mismatch in Exsh issue 10, plus the original 120-second ext4 quota timeout. Later targeted realm passes do not rewrite those original failures. The new smoke fix explicitly disables realm/client/plan storage in the current 16-field tuple and preserves strict input rejection; corrected host and native checks are in progress. Original CI1797/1798 is running and CI1799–1810 waits. Accepted progress stays 15.42%, 414/874 sub-items and 17/460 whole parents. Numeric CPU values, loss/exhaustion and both full EriX guest builds plus external toolchain rebuilding remain open.
Native configured-client acceptance — 25 September 2026: the exact signed Integration 7a42fa26 graph passes the configured-client, preparation and startup VMs with all original markers, deadlines and cleanup gates. The configured witness seals two isolated realms, observes six successful byte-client exits across three realm instances, checks independent retirement, rejects stale client selectors and reuses a Launchd realm record with a new generation. This proves the native configure/seal/publish/mediated-I/O criterion; full Procd managed-row/final CPU reclamation, supervisor loss and resource ceilings remain separate requirements.
Launchd 372ab70e retains only the required result-carrier GRANT and preserves RECV-only client copies plus complete setup retirement. All six strict 497-test configurations and original CI179/180 pass. Loaderd 5bcf522c retains the counted grant destination; four strict 145-test configurations and original CI107/108 pass. The original red tests, failed native runs and admitted host TCG diagnostic remain preserved. Docs 6a1a9686 passes the full 2,655-page manual and 45 tests locally and in original CI1085/1086; four complete CI logs total 824,660 bytes and final warnings are zero.
The configuration carrier defect, counted grant defect and configured-client stall are resolved by this component and native evidence. The Exsh fixture report retains its pending release compiler/frame validation despite the three native passes. Complete Integration CI1801/1802 is still queued. Whole-fleet authority/source/effect/frame acceptance, final accounting/profiler observation, rebuilding the external Rust/LLVM/runtime toolchain inside EriX and both full EriX guest-build generations remain open.
Original prerequisite Integration CI1793/1794 each passes 490/491 scenarios; Rust and Markdown pass, and six complete logs total 27,432,406 bytes with zero warnings. CI1794 retains the ext4 quota timeout. CI1793 instead exposes a distinct one-shot replay QMP connection loss, recorded using the canonical bug template and phase label. No original workflow was rerun, and no deadline or authority check was relaxed.
Only the existing native-witness sub-item gains credit: 15.42% weighted progress, 413/873 sub-items. Whole acceptance remains 3.86%, 17/460 parents.
Additional retained observation: CI 1597 at
84e876b0a025159e77e8a62f44947209f098ca3dreports worker 6 QEMU timeout after 120 seconds forsubsystem-e2fs-fat-ext4-quota-positive.toml. The final catalog is 485 passed, one failed, 486 total. Later image gates are not reached. Rust and Markdown pass. Complete original logs identify the existing scenario and deadline, without establishing the guest cause or a newly reproduced frequency.CI run 1560 retains the timeout and catalog continuation. The observed complete log-response snapshot had no warning candidates. Guest output is replayed by the failure handler; its host dump timestamps cannot establish the original guest event timing.
Complete terminal logs for run 1560 confirm the 485/1 catalog result and failure exit. The complete terminal logs for run 1561 independently confirm the same 485/1 catalog result. Both failed guest dumps end after DATA_IO_DONE and successful LOGD reply/wake markers; no subsequent nested-directory completion is shown. These host replay timestamps do not establish guest event times.
The last guest dump contains DATA_IO_DONE and LOGD reply/wake markers. These identify progress but do not prove that the waiting process resumed or that the subsequent directory operations completed.
The next scenario started after this failure. Separate run 1559 failed earlier in a host scenario-lock fixture; that is tracked independently and does not explain this guest timeout. No attribution to contention, filesystem code, the observer or a recent change is established.
Endpoint construction checkpoint — 14 September 2026: Completed older Integration 1605/1606 at
7cc0593e101b2e0ca42f24d4fa189dd96cb1455ceach reports 485 passes and one failure across all 486 scenarios. The sole failed scenario is the existing ext4 quota timeout tracked in #18. All six complete logs total 27,546,527 bytes with zero warning candidates; Rust and Markdown pass. There are no VM-worker dependency-feature compiler failures. Subsequent dependent image and terminal gates remain unestablished. The allocator cohort 1607/1608 is running; current endpoint-construction cohort 1609/1610 is waiting. Both failure-handler guest dumps end after DATA_IO_DONE and successful LOGD reply/wake markers, repeating the recorded boundary. Dump timestamps are host replay times. No new causal attribution, unchanged rerun or deadline increase is claimed.Original memory-receipt cohort observation — 16 September 2026: CI 1639 at
db80a2c1dfc669bd724762d476f5f5c0da005ff6is terminal with 407 passes and 79 failures across 486 scenarios. Exactly 78 preparation refusals report the incompatible Exsh workspace layout tracked in #57. The additional failed scenario is the existing ext4 quota timeout tracked in #18: worker 6 reports QEMU timeout after 120 seconds and the scenario records status 1. Its guest dump ends after DATA_IO_DONE and successful LOGD reply/wake markers; these host replay timestamps do not establish guest event times or a cause.All three complete terminal logs total 13,431,206 bytes with no compiler/lint warning candidates. Rust and Markdown pass. The run artifact API returns no original image/firmware bytes or inner receipts, so exact environment equivalence remains unverified. Original paired CI 1640 is still running. No unchanged rerun, relaxed deadline, guest correction or acceptance of later image gates is claimed.
Second original memory-receipt run — 16 September 2026: CI 1640, exact
db80a2c1dfc669bd724762d476f5f5c0da005ff6, is now terminal. It reports 408 passes and 78 failures across 486 scenarios, with exactly 78 incompatible Exsh layout refusals. The ext4 quota scenario explicitly passes in this original paired run. That observation does not explain or fix the 120-second timeout in original CI 1639; #18 remains open, as does the layout adoption issue #57.All three logs are complete (13,033,398 bytes) with zero compiler/lint warnings; Rust and Markdown pass. Both original runs together retain six complete logs totaling 26,464,604 bytes. The artifact API still exposes no original image/firmware or inner receipts. The cohort is fully classified without restarting it, changing deadlines or weakening mixed-layout rejection. Full source/frame/runtime prerequisites still gate coherent catalog adoption.
First matching watchdog correction run — 16 September 2026: CI 1641, exact
01daadd3d775079a77dd3278f6b07ecbaebe3e84, passes its 13 serial watchdog controls and remaining host checks. The full catalog run then records 407 passes and 79 failures across 486 scenarios: 78 known Exsh layout refusals and one 120-second ext4 quota timeout. This is another recurrence of #18, not evidence that the deterministic fixture correction changed guest timing. #57 still tracks coherent layout adoption. All three terminal logs are complete (13,436,715 bytes), with zero compiler/lint warnings; Rust and Markdown pass. The artifact API exposes no original images or inner receipts. Paired CI 1642 remains running; retain those same handles and original deadlines. No unchanged rerun or full runtime acceptance is claimed.Further original CI results — 16 September 2026: watchdog CI 1642, exact
01daadd3d775079a77dd3278f6b07ecbaebe3e84, records 408 passes and 78 known layout failures across 486 scenarios; the quota scenario passes in that run. Permission-validation CI 1643, exact89d15e4536004c087dcebd63c87216c0fd58958d, records 407 passes and 79 failures: the same 78 layout refusals plus the original 120-second quota timeout. Both runs pass their host controls, Rust and Markdown checks. All six terminal logs are complete, totaling 26,457,909 bytes with zero warning candidates. Artifact APIs expose no original images or inner receipts. This preserves the timing regression in #18 and coherent layout adoption in #57 as open obligations. Permission CI 1644 and release-input CI 1645 are running; CI 1646 waits. No run was restarted or assigned a larger deadline.Remaining original CI results — 17 September 2026: permission CI 1644, exact
89d15e4536004c087dcebd63c87216c0fd58958d, finishes with 408 passing and 78 known layout refusals. Release-input CI 1645, exactdf8147dfa437194cd091747fd7147941bd2793c4, finishes with 405 passes and 81 failures: those 78 layout refusals, the original quota timeout, and new 120-second FAT32 mirrored/Unicode timeouts. Paired CI 1646, at the same source revision, records 408 passes and only the 78 layout refusals. The separate FAT32 observations are tracked with the canonical bug template in #58; a common cause with quota is not established.All nine terminal logs are complete, totaling 40,256,559 bytes with zero warning candidates; host/Rust/Markdown checks pass. Original artifact APIs expose no images or inner receipts. Both formerly pending cohorts are fully classified, with their original failures retained. No run was restarted, no limit was increased and no complete product or guest-build acceptance is asserted.
Original Integration regression classification — 17 September 2026: Original runs 1647–1650 are fully classified. Runs 1648, 1649 and 1650 each pass 408 of 486 scenarios and fail the same 78 known shell-layout refusals in issue 57. Run 1647 passes 407 and additionally repeats the existing ext4 quota timeout in issue 18. All twelve complete terminal logs total 52,533,051 bytes and contain no warnings. Rust and Markdown jobs pass. No additional failed scenario is identified; the complete catalogs remain failed. The separate local automatic-KVM preboot observation is tracked in issue 60.
Original archive-head regression classification — 17 September 2026: CI 1653 and CI 1654, both at
77921a7d97874e3f44aae66ae9bef6e6196af2f5, each finish with 406 passing and 80 failing scenarios out of 486. All six terminal logs are complete (27,648,897 bytes), with no warning candidates; Rust and Markdown pass. Both retain the 78 layout refusals and quota timeout. The additional original failures are ext4-xattr in push CI 1653 and ext4-metadata in PR CI 1654, each at the unchanged 120-second QEMU deadline. The opposite case passes in the paired run. No serial-stall report, deterministic isolated reproduction or common cause is established. No workflow is restarted.Original linker-selection regression classification — 18 September 2026: Integration
bc0e67f927ded76dd3ff5790180a7bded0886885finishes original CI 1655 and CI 1656 failed. Each passes 407/486 VM scenarios and retains 78 known Exsh layout refusals plus the existing ext4 quota 120-second timeout. Rust and Markdown pass. All six logs are complete (26,854,856 bytes), with zero warning candidates. No unchanged workflow was retried, and no new common cause or guest-build acceptance is inferred.Compiler-metadata original CI closure — 18 September 2026: CI 1657 and CI 1658, exact
56e035d46a11dc803d654bf2151e484fab307682, each finish with 407 passes and 79 failures across 486 scenarios. Each retains 78 known Exsh capacity-layout refusals (#57) and one ext4 quota timeout at the original 120-second deadline (#18). Rust and Markdown pass. All six terminal logs are complete: 26,867,392 bytes, no compiler/lint warnings. These observations establish recurrence, without establishing a new guest timing cause. Both known bugs and full runtime acceptance remain open; no unchanged rerun or deadline change was made.Original Integration catalog completion — 18 September 2026: At exact revision
0db8a679f5d1acb50d9ff92e003cec91f145dfc8, CI 1659 finishes with 396 passes and 90 failures out of 486; CI 1660 finishes with 393 passes and 93 failures. Each retains the 78 known Exsh layout refusals. The remaining 12 and 15 failures are original 120-second QEMU storage-scenario timeouts. All six terminal logs are complete (36,570,659 bytes), with zero warning candidates. Rust/unit and Markdown jobs pass. No workflow was restarted, no deadline was enlarged and no failed scenario is accepted. A shared guest or host cause is unestablished.Original relocation catalog CI closure — 18 September 2026: CI 1663 and CI 1664, exact
8e66e54c86d93f257b6051da0381ff8cdc84fe2f, each finish with 407 passes and 79 failures across 486 scenarios. Each retains 78 known Exsh capacity-layout refusals (#57) and one ext4 quota timeout at the original 120-second deadline (#18). Rust and Markdown pass. All six terminal logs are complete: 26,859,606 bytes, no compiler/lint warnings. These observations establish recurrence, without establishing a new guest timing cause. Both known bugs and full runtime acceptance remain open; no unchanged rerun or deadline change was made.Original coherent-graph CI classification — 19 September 2026: CI 1669 records 485 passes/1 failure; CI 1670 records 484 passes/2 failures, each across all 486 scenarios at
8b1c037aed2503e1f2a4b17c8a8be0666d62a305. Both retain the original 120-second ext4 quota timeout in bug 18; the latter also fails physical input observation in the exact-selector race scenario, now bug 64. That scenario explicitly passes in the paired run. All six terminal logs are complete (27,557,577 bytes), with no warning candidates; Rust and Markdown pass. No incompatible shell-layout refusal remains. The layout issue’s full source/frame prerequisites and later native-image gates remain unproved. Neither workflow was rerun, and no deadline or admission check was relaxed.Original CI observation — 19 September 2026: CI 1671 finishes with 471 passes/16 failures and CI 1672 with 465 passes/22 failures across all 487 scenarios at
c479813423fb71c606fa30e5cf7d4dfb16f557d0. Every failed scenario is an ext3/ext4 positive filesystem case reportingerror: qemu timed out after 120s, with scenario status 1. The existing filesystem deadline report retains the expanded matrix; quota issue 18 applies to the quota failure in 1672. All six complete logs are hashed (41,592,478 bytes), with zero warning candidates. Rust, Markdown and the full helper step pass. The zero-realm startup and exact-selector race scenarios explicitly pass in both runs. No common cause, source regression boundary or performance diagnosis is inferred; all actual deadlines and failure statuses remain unchanged, and neither workflow was rerun.Further original CI observations — 19 September 2026: push run 1679, original Integration
b65183ddb93eb4396d4140a002c3727fec42ff87, passes 488 of 489 catalog scenarios and fails onlysubsystem-e2fs-fat-ext4-quota-positive. Worker 9 reports the unchanged 120-second QEMU timeout at 18:11:12 UTC; the complete catalog finishes with one recorded failure. Later native and interactive workflow gates are not reached in this run. Rust and Markdown pass. Three complete hashed logs total 13,856,284 bytes with zero warning candidates. The main log has 13,751,641 bytes, SHA2564f0a4dceee87449767330274b37c4f17392be12b550eff37ba726aaa31c9daf2; its timeout is at raw LF line 48,985. Companion run 1680 passes all 489 catalog scenarios before a separate development COM1 directory failure tracked in issue 56. Neither the sibling pass nor the later failure establishes a cause for this timeout. No unchanged rerun, cancellation or limit change occurred.Tracking
Original CI1788 follow-up — 25 September 2026: run1788 at
fa857c0964774def6777142afeb7a3c16440abeerepeats the ext4 quota overall QEMU timeout at120 seconds on worker10. The complete catalog records483 passed/eight failed/491 total. Rust and Markdown pass. The six complete original logs across1788/1789 verify29,610,471 bytes and zero warnings. No unchanged retry, relaxed limit or common cause is claimed.Original quota follow-up — 25 September 2026: CI1785 at
ffedb3630895b2bc547ab58e4900f750d84cd64band CI1787 atfa857c0964774def6777142afeb7a3c16440abeeboth repeat the ext4 quota positive scenario overall QEMU timeout at120 seconds, worker10. Each complete catalog passes489/491; the other failure is the historical realm scenario at different preparation/start steps. No common cause is inferred. Original Rust and Markdown jobs pass, complete logs contain no warnings, and no unchanged job was rerun.Related work: #2, #3, #11 and WIP PR #12. Preserve source/image/configuration identities, timeout status and remaining catalog outcomes. Obtain bounded reproduction or sufficient causal evidence, apply a reviewed correction, and require the unchanged scenario plus full current-revision regressions to pass without warnings. Keep unexecuted or incomplete checks explicit.
Original completed installer-handoff regressions — 21 September 2026:
Original Integration 1697 and 1698, at signed
648fbd5614d3d0b82223b1c3bb7f1b5a0c81ea7d, finish with 488/489 and 487/489 passing VM scenarios. Rust and Markdown jobs pass. All six complete logs are retained with verified hashes: 28,115,674 bytes and zero warning candidates.subsystem-e2fs-fat-ext4-quota-positivereaches the unchanged 120-second QEMU deadline in run(s) 1697, 1698. Each timeout is correlated with its own worker, scenario start and serial dump, stopping before that worker begins another scenario. The dumps reach VFS progress and native logging activity; this does not establish a shared cause or prove a filesystem implementation defect. These original failures remain unresolved; no unchanged run was retried or cancelled and no deadline was relaxed. The subsequent acknowledged terminal-accounting service graph still requires separate adoption and VM validation.Original full-regression observation — 21 September 2026:
Original Integration 1699/1700, source
fcd7b4a9608f629a12de78c53da5c3615d906b46, each finish at 487/489 VM passes. All six complete logs retain 28,483,276 bytes with zero warning candidates; Rust and Markdown jobs pass. The original worker boundaries identify quota's 120-second timeout in 1699 and 45-second serial stall in 1700, ext4 links' 120-second timeout in 1700, and FAT32 directory metadata's 120-second timeout in 1699. The latter has a distinct canonical bug report. Existing quota 18 and links 20 remain open. No shared root cause is inferred, and no unchanged rerun, cancellation or threshold relaxation is requested.Original full-regression follow-up — 22 September 2026: Integration run 1701 and run 1702, source b06dfad00202, both pass. Six complete original logs total 26,962,712 bytes with zero warning candidates. Each run explicitly records passing ext4 quota, ext4 links and FAT32 directory-metadata scenarios in the full catalog. These are observations of the original submitted runs; no job was restarted or cancelled and no deadline was changed for this follow-up. The prior failures remain retained, and these passes do not establish their cause or failure frequency. This report stays open while the independent timing investigation and current-source regressions continue.
Additional original full-regression observation — 22 September 2026: Integration 1703 and 1704, source
dff878dd35, both pass. Six complete logs total 26,964,178 bytes with zero warnings and explicit ext4 quota/links and FAT32 directory passes in each run. These are observations of the original submitted handles, with no retry or deadline change. They do not establish the cause or frequency of the retained earlier failures, so this report remains open.erikinkinen referenced this issue2026-09-12 11:24:43 +02:00
erikinkinen referenced this issue from erix/e2fsd2026-09-12 12:37:52 +02:00
erikinkinen referenced this issue2026-09-14 07:36:11 +02:00
erikinkinen referenced this issue2026-09-14 15:41:40 +02:00
erikinkinen referenced this issue2026-09-14 15:41:41 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-15 04:10:30 +02:00
erikinkinen referenced this issue2026-09-16 06:23:18 +02:00
erikinkinen referenced this issue2026-09-17 17:53:33 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-22 00:24:38 +02:00
erikinkinen referenced this issue from erix/kernel2026-09-22 00:24:38 +02:00
erikinkinen referenced this issue from erix/launchd2026-09-25 12:13:35 +02:00
erikinkinen referenced this issue from erix/docs2026-09-25 12:13:44 +02:00
erikinkinen referenced this issue from erix/posixd2026-09-25 12:14:58 +02:00