Repository navigation
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## codex/expand-ecosystem-corpus-20260913 #4 +/- ##
=========================================================================
Coverage ? 89.93%
=========================================================================
Files ? 661
Lines ? 75174
Branches ? 0
=========================================================================
Hits ? 67611
Misses ? 7558
Partials ? 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
cpunion
merged commit Oct 11, 2026
46fa4bc
into
codex/expand-ecosystem-corpus-20260913
1 of 7 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fork-only Draft staging for xgo-dev/plan9asm#40, targeting its existing contribution branch. The upstream-connected head remains unchanged. This is not completed ecosystem coverage or a runtime certificate.
Current repair batch
Head
46fa4bcacontains 20 batched commits after0c61d468. The previous run 38096927749 finished naturally before publication. Fresh current-head CI and exact-version replay are required; local component passes do not promote external versions.These repair already recognized instruction families and their formats/effects; no new-mnemonic total is claimed. Native entry/frame/backing, generated-header and unregistered effect permissions remain separate. LLVM 22 only; development Go 1.27.1, compatibility checks Go 1.20.14. No local Module Index scan or external-library compilation batch was launched.
4856910cComponent evidence cannot be credited to a different frozen full run. Rosetta/portable execution does not certify native Linux or AVX512 execution. Required cross-runtime owners remain required; earlier failures/timeouts are retained.
Completed previous CI
Policy preflight passed. All six priority shards failed; 36/42 hit the unchanged 330-minute deadline and uploaded partial reports.
The reports retain 2,559 ordinary translations; 5,539 versions remain unreported. The three skips are two invalid-source and one superseded-version outcome. These are old-source diagnostic outcomes, not new-head ledger credit or necessarily distinct module counts.
The strict aggregate audited reports in 1,116s, compared with 4,778s in the preceding run; the partial subsets differ, so this is an observed timing, not a controlled speedup. It correctly rejected six reports instead of 64 complete shards. Downstream module/cross completion failed for missing owner artifacts after priority failure prevented their jobs from running, not newly observed unit failures. No completeness guard or deadline was relaxed.
Remaining categories include native ABI/entry/TLS, SP/backing/alignment, raw continuation/CFG joins, FP padding and result availability. The fixes above must be replayed against their original exact versions; moving the first error is not candidate closure. Native-layout exclusions remain provisional and require review.
Discovery funnel
The 215 contiguous ranges cover
2025-10-01T00:00:00Zthrough2026-09-22T22:43:08Z, not the complete historical index or today's head. No reliable global unique-module denominator is available. Keep the newest version per(module path, Go-semver major); v0/v1 lines and separate major paths may coexist. Deduplication never rewinds already covered ranges.Independent, not-imported inventory: 21,257,856 index records, 1,051,454 module paths and 6,700 assembly versions. These are discoveries, not additional tested passes. cgo inventory remains outside this repository.
The ledger remains
complete=false, verified=false, with zero complete shards. Scan records prove inspection; assembly evidence proves its exact producer's translation/object tests. No manual promotion, mixed-revision report, N/A or skip replaces a pass. Only the automatic writer may publish fully matched evidence.Official classification and remaining gates
The unchanged official gate has zero unsupported forms/parse errors. This is not complete encoder-combination, ABI or runtime coverage; context-dependent wasm forms do not mean an unsupported architecture.
The strict SDK benchmark at
9f9c1225remains failed: 163/184 files passed and 21 failed, zero N/A/unattempted. Per-target passes are 386 29/33, amd64 48/55, arm 27/30, arm64 40/47 and wasm 19/19. Its 59 target-seconds plus three build-seconds met unchanged time budgets, but functionality did not pass. Native entry/ABIInternal/TLS, dynamic frames, native result tails and backing/alignment remain blockers.CI retains policy preflight, all six priority shards, then other entry jobs only after priority success. All 64 shards and strict aggregates remain required, without an explicit matrix concurrency cap. Let the new run finish before another batch push.
Keep fork PR4 and upstream PR40 Draft until current-head CI, review, coverage and automatically verified ledger pass. Only then integrate into PR40's existing fork head. No upstream push, merge, approval or closure is authorized. Fork PRs 1–3 are already closed; the separate llgo integration PR259 remains necessary.