generated from erix/meta
[BUG] Completed ordinary startup exceeds the maintained readiness and command limits #72
Labels
No labels
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/integration#72
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
A fresh ordinary development image now passes the original-source/feature contract and completes the full startup observation, but exceeds all four maintained performance limits. The largest completed-service interval is RTC-provider readiness to TTYD readiness. These host arrival windows include scheduling, IPC, buffering and observer uncertainty; they do not yet identify a loader-only cause.
Reproduction
Use signed Integration
fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa, its complete original catalog, selected Rust 1.97.1 tools and the explicit repository test signing fixtures. Build the ordinary development package and disk, then run:This is one retained actual attempt. No local compiler, manual build or other VM was active. Guest hard/silence/command-collection bounds remain 120/15/10 seconds. No unchanged retry or bound relaxation is requested.
Expected and actual behavior
Expected: all thirty required service barriers and the native command transcript complete, with root launch to final readiness at most 5 seconds, each completed-service gap at most 1 second, final readiness to the full-caret prompt at most 1 second, and all four commands at most 2 seconds.
Actual conservative interval metrics:
The unchanged oracle exits 1 at its first exceeded limit. The observer completes with zero dropped records and no missing required stages; the VM/native transcript passes and QEMU stderr is empty. Cleanup succeeds. The separately computed remaining metrics use the same conservative event-window arithmetic and the actual command log, without changing the oracle.
Environment and identity
fd8a5cf0dbcf9a9cd3ddb6038370295e6ec2c8fa; Kernela9bdf6163813d378e0b4a164bceb839e24fbb6b7; Rootd64c97b13c450003d9c2b6bd9ed2a627088684b46.72be8589c6575de76cd91102d20b24f9c4514800714ad1016361e3335fa2daf1.bcead1bc063cc4b71ac322855b48105e4af28d74546025b944b5f3760ac3df13; command-log SHA-2561b7a469c7020eb8b4c7f17a7234bb33834a10d346b33e0b573824532f92bda4c.Evidence and prior checks
The maintained profiler ranks RTC-provider to TTYD at 3.094329035–3.098663889 seconds, TTYD to Powerboxd at 1.030008239–1.034295155 seconds, and Powerboxd to Launchd at 1.036671511–1.040957920 seconds. Final readiness to the prompt spans 1.258176422–1.262470092 seconds. The image builds without warnings and actual preflight admits the Kernel-bound contract. All 171 host helper commands have successful warning-free final evidence. Original failed admission and helper resource warnings remain separately preserved.
Tracking
Related: profiling implementation 3, corrected admission 69, WIP PR 12, and Phase 6 completion.
Discriminate authenticated artifact reading/verification, relocation/materialization, process start and service handshake before attributing these intervals. Preserve fresh source and digest checks, authority ceilings and disposal. Optimize an evidenced cause, then validate changed inputs with the same complete workload and thresholds. Full source/effect/frame/Pagerd proof, native external Rust/LLVM/runtime rebuilding and both complete EriX guest builds remain mandatory.
Executed-code profiling checkpoint — 22 September 2026: signed Integration 4fa27f942bc2, tracked in Integration PR 12, adds bounded host TCG execution counters, explicit fresh-output ownership and exact packaged-ELF code candidates without adding guest authority. All 172 maintained helper commands pass without warnings. The profiler passes five Rust tests in both profiles, strict Clippy, private rustdoc, eleven Python controls and five actual selected-emulator controls. Unchanged orchestration inputs retain their preceding four strict matrices. The operator guide distinguishes complete counters from VM acceptance.
One original-image diagnostic retains 92,896 translated blocks, 1,994,216 code bytes and zero missed execution counts. Its top 100 code groups cover 85.65% of the translated instruction upper bound; 33.30% has Kernel mapping-batch candidates and 7.70% has VSpace permission-switch candidates among the selected ELF inputs. Unknown and ambiguous work remains visible. These are code matches, not process ownership or elapsed-time attribution. Both the instrumented attempt and its same-emulator uninstrumented control fail waiting for the final native-command marker under unchanged 120/15/10 collection bounds. Neither proves startup acceptance, whole-transcript instrumentation overhead or a speedup. Profiler acceptance and startup performance remain open. The next optimization must preserve complete validation, live backing checks, page permissions, invalidation ordering and cleanup on errors.
The signed manual update, tracked in Docs PR 4, passes 45 tests, all 2,431 pages, 450,367 word bounds and both changed-page visual reviews with zero final warnings or overflow. Original Docs CI 1005/1006 passes from four complete logs (774,674 bytes); initial reference-convergence warnings resolve on the final passes. Integration 1711/1712 is queued, while original 1701/1702 still runs. Existing queued jobs remain untouched. All 3,174 authored code files remain below 1,000 lines. No whole acceptance leaf closes: 15/460, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain inside EriX and completing the required full guest-build generations remain mandatory and unproven.
Owned address-space preparation — 22 September 2026: Kernel issue 22 records the private hardware-root construction, exact authority, activation, invalidation, failure custody and retirement contract before implementation. Signed Kernel 5e818e8b6d1d, in Kernel PR 3, adds the design contract and an independent mapping-bit provenance regression. The current shared hierarchy and production permission encoder remain unchanged. An isolated rewrite produced the same 17 instructions and 63 bytes, so it was rejected as an optimization.
Four strict Kernel matrices pass 737 default / 761 all-feature tests in development and release, retaining the same three existing ignored cases. Formatting, host/native Clippy, all 13 native builds, private rustdoc and Markdown pass without warnings. Original CI 628/629 is running. No hardware-owned root, concurrent user execution, elapsed-time speedup or native isolation closure is claimed. The profiler and unchanged startup timing gates remain open in Integration 3 and Integration 72. The phase checklist stays at 15/460 accepted leaves, weighted 3.48%; external Rust/LLVM rebuilding inside EriX and both full guest-build generations remain mandatory and unproven.
Native table-custody checkpoint — 22 September 2026: signed Kernel 2e744897de7c, in Kernel PR 3, gives unpublished table allocations one cleanup owner through translation and initialization. Empty-table installation and huge splits transfer custody at parent publication. The raw allocation-return helper and duplicate huge-split initialization are removed. Parent/leaf invalidation, interrupt masking, permission templates and current shared-hierarchy lifetime remain intact. Five host controls cover allocation/translation failure, invalid geometry, abandoned preparation and publication. Four strict configurations pass 742 default / 766 all-feature tests, retaining three existing ignored cases; formatting, host/native Clippy, private rustdoc and thirteen native builds pass without warnings. Original Kernel CI 630/631 passes from four complete logs, 771,607 bytes and zero warnings.
Signed Integration fe63adde8ff9, in Integration PR 12, selects that exact Kernel in all three catalogs. Every other selection and Kernel dependency manifest is unchanged. All 172 maintained helper commands pass without warnings; unchanged Rust inputs retain their preceding strict matrices. Three original-source native executions pass lifetime revocation, owned invocation and mapping checks with unchanged 60-second guest limits, warning-free builds and empty QEMU stderr. Mapping isolation and sparse mappings have identical runtime settings; both maintained marker contracts pass on the retained mapping capture. All fifteen selected component signatures verify, and each packaged Kernel image equals its retained artifact after normal stripping. These results cover the current shared hierarchy, not independent hardware roots.
The Kernel evidence update and Integration evidence update change documentation only, with executable inputs proven unchanged. Their original Kernel CI 632/633 is running and Integration 1715/1716 is queued. Older full Integration CI 1701/1702 at
b06dfad002passes from six complete logs, 26,962,712 bytes and zero warnings, including both runs' ext4 quota, ext4 links and FAT32 directory-metadata cases. Their earlier timing failures remain retained with unestablished causes; 18, 20 and 70 have exact follow-up observations. No workflow was rerun or cancelled.All 3,176 authored code files remain below 1,000 lines. The next work in Kernel 22 must resolve the supervisor baseline, bootstrap/saved-frame overlays and inactive-space population before adding root ownership, residency and retirement. Startup timing acceptance, complete authority cleanup and the profiler's measured speedup remain open. The phase checklist stays at 15/460 accepted leaves, weighted 3.48%. Rebuilding the external Rust/LLVM toolchain and runtime inside EriX, then completing both full EriX guest-build generations, remains mandatory and unproven.