generated from erix/meta
[BUG] Workspace producer and catalog shell layouts disagree in 78 scenarios #57
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#57
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 version-22 workspace producer is published while the catalog still selects a version-21 shell. The original CI records 408 passing and 78 failing catalog scenarios, with 78 workspace-layout refusals during image preparation.
Reproduction
The original CI workflow selects:
This report retains the original run; no unchanged rerun or failure-frequency claim is made.
Expected and actual behavior
Expected: the selected producer and target layout agree before packaging. Actual: the producer reports
unsupported exsh capacity layout version; subsequent missing manifest errors follow the failed preparation. The aggregate at 00:39:07 UTC on September 16, 2026 ispassed=408 failed=78 total=486. Later canonical native-image gates are not reached. These preparation failures are not observed guest crashes.Environment and identity
Integration CI 1637 at
38424571b76b36c1e631d99fd2c859fb32311eea, using its original pinned component graph in the Linux x86-64 CI container. Original image/firmware bytes and inner runner receipts are unavailable through the run artifact API; their exact digests remain unverified.Evidence and prior checks
All three terminal logs are complete (13,031,316 bytes), with no compiler/lint warning candidates. Rust and Markdown pass. The original catalog selects Exsh
70521817b0c8d907e765b0d8ef8ed1eaa89f67ce, whose target layout constant is 21. The producer at the recorded Integration head requires 22. The signed producer commit already states that coordinated catalog adoption and full frame/runtime validation remain outstanding; this CI establishes the regression breadth. Matching-version fixture packaging does not establish product-catalog compatibility.Paired-run classification — 16 September 2026: original CI 1638 at the same exact head is also failed. Its complete three logs total 13,033,595 bytes, with zero compiler/lint warnings. Rust and Markdown pass. The aggregate is again
passed=408 failed=78 total=486, with exactly 78 incompatible-layout refusals. Both original runs together retain six complete logs (26,064,911 bytes). This confirms the second original observation, not an unchanged rerun or guest crash. The run artifact API exposes no original image/firmware or inner runner receipts. Coherent adoption still requires complete source/frame/runtime prerequisites; mixed-layout rejection remains required.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 generation-cleanup catalog completion — 18 September 2026: At exact revision
4d4628f565d7102e6ef2987e4085fd8d97d247d3, CI 1661 and CI 1662 each finish with 408 passes and 78 failures out of 486. The exact failed set is the 78 known Exsh layout refusals. There are no storage timeout failures in these two observations; earlier timeout failures remain unresolved. All six terminal logs are complete (26,074,278 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.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.Earlier original CI recovery — 19 September 2026: CI 1667 and CI 1668, at
ad85421257b7d964845fd4b84931966ad36cc122, each retain 408 passes and the same 78 known layout refusals across 486 scenarios. All six complete logs total 26,072,734 bytes without warnings. Two initially truncated log responses remain retained; correcting a stale observer byte ceiling recovered the original terminal output. No workflow rerun or VM deadline change occurred. These historical failures are distinct from the newer coherent graph.Tracking
Complete the source/frame and runtime prerequisites, then adopt a coherent producer/target graph and run the full catalog. Keep old/mixed-layout rejection and all frame/storage checks; accepting incompatible layouts or omitting scenarios is not a correction. Both original runs are now terminal with the same layout-refusal failure class. Source audit #1 and PR #12 coordinate the work. No guest fix or full in-system build is claimed.