WIP: Validate production logging configurations #4
No reviewers
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/logd!4
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/posix-compat"
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 and rationale
Make Logd's declared production output configurations pass strict validation. Retry and delivery tests now use explicitly output-eligible warnings; separate release tests prove requested kernel routing and queued serial/framebuffer replay cannot bypass INFO filtering. A serial-only idle test verifies delivery without duplication. Consolidate direct-transport inclusion for the sinks that use it and correct configuration-dependent test helpers/imports.
Tracking and scope
Tracks #1, #2 and #3. Includes existing dependency-pin alignment, a shared bounded CI validation driver, current component documentation and formatting of touched include fragments. This review remains WIP pending coherent product runtime-image adoption.
Architecture, authority and failure behavior
Production output filtering, retained-record ownership, capability validation and sink-call semantics are preserved. Direct transport is included only with serial/framebuffer output. Test-only synthetic delivery records explicitly use warnings; independent negative tests retain the original INFO payload while refusing external output. No warning lint is relaxed and no existing test is skipped. CI selects and hashes its Cargo executable and pinned Integration helpers, allowlists child environment inputs, retains owned command status/output and enforces hard, inactivity and output budgets without automatic retries.
Validation evidence
Original coherent realm source CI acceptance — 18 September 2026: Signed
a3cc7a06beefdb604d1b372ec7fdeb9def0356ecpasses CI 236 and CI 235. All four terminal logs are complete (631,831 bytes), with zero final warnings. This closes the original CI observation recorded above. Coherent catalog publication, actual consumer VMs and full guest-build acceptance remain separate open requirements.Original coherent realm runtime prerequisites — 18 September 2026: Signed
a3cc7a06beefdb604d1b372ec7fdeb9def0356ecselects original shared dependency revisions. All 20 host/native output-policy configurations pass 43/45/59/62/133/138 tests per configuration and 20 native builds, including separate release logging, serial and framebuffer combinations. Formatting, strict host/native Clippy, private rustdoc and Markdown pass with zero warnings. Direct Rust implementation bytes are unchanged. Original CI is under observation. Matching catalogs, source-bound consumer VMs, complete realm operation and both full guest builds remain required.Signed
bc15238f25f818a28fe51b249e2db33f667c4599passes the complete warning-denied host/native matrix: default and runtime/logging configurations each pass 43 tests, serial-only 59, framebuffer/all-feature 133, release-only/release+logging 45, release+serial 62, and release+framebuffer 138, in both development and release profiles. All twenty native builds, strict host/native Clippy, formatting, private host/native rustdoc and documentation checks pass. Earlier failures are retained. Push/review CI 233/234 passes with complete classified logs and no final warnings. Product catalog and runtime-image adoption remain separate.The emitted Rust changes were also reviewed against separately formatted original files, distinguishing feature/test corrections from include-fragment formatting. All authored code files remain below 1,000 lines (largest 940); missing_docs remains enforced. No new VM claim is made by these test/configuration fixes.
Review checklist
Coherent dependency checkpoint — 20 September 2026: signed/pushed commit e54d56ee3de36ea9d4490fd93558abfdf4c1f4de aligns original shared dependency pins with the explicit installer-rights contract. Only the manifest and roadmap change; local implementation, APIs and authority policy are unchanged. Four strict 43/133-unit configurations, four native builds with the maintained linker layout, host/native Clippy, formatting, private rustdoc and dependency checks pass without warnings. Original CI 237/238 passes with four complete hashed logs (631,829 bytes), zero warning candidates.
Full catalog equality and actual consumer-image validation remain required under Integration regression 68. The broader work remains tracked by phase completion, including native external Rust/LLVM/runtime rebuilding and both complete EriX-in-EriX generations. This dependency checkpoint does not close full lifecycle, frame or self-hosting acceptance.
Original CI observation — 21 September 2026: run 239 passes. Run 240 has now failed at original source
651024dd6956012697af1d1cafaf28950dacfa82; Forgejo returns HTTP 500 for both terminal test and Markdown job logs. The original failure and unavailable responses are retained. Cause, complete logs and warning classification remain unresolved; no restart or passing-regression claim is made.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.