Conversation
- Add a versioned module manifest with validation, deterministic listing, and GitHub Actions matrix generation. - Introduce a project bootstrap for module selection, profile loading, named collateral feedback, and isolated report and work paths. - Provide bounded parallel all-module execution with aggregate failure propagation and legacy consumer compatibility. - Support per-module Verible formatting policy without repository-owned wrapper executables. - Qualify native and containerized behavior with a two-module fixture covering invalid manifests, fallback resolution, cleanup isolation, and concurrent results. - Document project migration, configuration, CI gitlink verification, and the reusable multi-module contract.
…ation [Add] Support multi-module repository orchestration
- Add a versioned module-owned parameter-profile manifest with strict validation, deterministic listing, and collision-resistant CI matrix generation. - Apply exact parameter and top overrides across elaboration, lint, synthesis, formal equivalence, simulation, PyUVM, and supported commercial adapters. - Isolate report, work, netlist, and generated formal artifacts by module and profile while rejecting conflicting flow policy. - Provide bounded parallel all-profile execution with machine-readable evidence and aggregate failure, blocked, skipped, and missing status handling. - Qualify boundary widths, feature toggles, elaboration-only policy, artifact isolation, failure propagation, and native and containerized orchestration through a reusable fixture. - Document profile declaration, backend mapping, evidence layout, CI integration, and migration guidance, and advance the methodology version to 0.3.0.
…qualification [Add] Qualify parameter profiles across shared flows
- Add a versioned JSON release-evidence schema with methodology-owned generation, validation, and reviewer-oriented summary output. - Enforce required PASS and approved SKIP policy across every cannoical flow while failing closed on missing, failed, blocked or stale evidence. - Record module and methodology revisions, selected profiles, technology context, exact portable tool versions, repository-relative input hashes, and separate HDL and PyUVM coverage evidence. - Support module-owned supplemental gates, additional tools, inputs, evidence, metadata, native and container contexts, and explicit dirty-state attestations for immutable packaged sources. - Qualify deterministic comparison, malformed revisions, dirty trees, disabled flows, missing reports, supplemental gates, and packaged methodology behavior through native and containerized fixtures. - Document consumer and CI migration, align multi-module inputs with mosaic-common, and advance the methodology version to 0.4.0.
…ence_manifest [Add] Standardize release qualification evidence
- Validate the complete portable fixture manifest against every canonical flow decision, expected tool identity, representative hashed input, and native and PyUVM coverage evidence. - Extend focused fixtures with summary and status checks, explicit approved skips, unauthorized enabled-flow skips, failed supplemental gates, and missing additional evidence. - Run the complete evidence-content audit in GitHub Actions and document its role in methodology qualification.
…ence_manifest [Update] Complete release manifest acceptance coverage
- Add a versioned module-owned coverage policy with independent line, branch, toggle, and user thresholds, named coverpoint hit requirements, source scoping, and attributable exclusions. - Normalize type Verilator and LCOV evidence, reject malformed or stale policy entries, and emit precise PASS, FAIL, or SKIP qualification summaries. - Reuse normal simulation or PyUVM HDL coverage, support dedicated Verilator reruns, and keep Python functional coverage separate from structural metrics. - Integrate optional SymbiYosys cover reachability, canonical flow orchestration, open-source quality gating, and release-manifest evidence indexing. - Qualify positive, deficient, excluded, malformed, and unreachable-formal cases in native and containerized CI, document simulator limitations and usage, and advance the methodology version to 0.5.0
…d_rtl_coverage_qualification [Add] Qualify assertion and RTL coverage
- Add versioned module-owned campaign declarations and shared orchestration for negative tests and pinned Icarus four-state qualification. - Require positive and disabled-monitor controls, expected nonzero results, diagnostic signatures, and precise assertion, elaboration, equivalence, escaped-fault, and infrastructure classifications. - Isolate aggregate and per-case command, status, summary, compile, and run evidence by module, profile, simulator, and case. - Exercise real EQY equivalent and inequivalent candidates plus Icarus X/Z detection while retaining mutations and control stimulus as module-owned verification collateral. - Integrate independent campaign policy, input hashing, tool identities, summaries, parameter-profile selection, open-source quality gating, and release-manifest validation. - Qualify detected and escaped faults, broken monitors, missing inputs, approved skips, and independent release policy in native and containerized CI, document migration guidance, and advance the methodology version to 0.6.0.
- Include negative and four-state qualification in the complete parameter-profile fixture status set. - Preserve explicit SKIP evidence for profiles that do not select the optional qualification campaigns. - Restore the PR fixture integration check while retaining native, multi-module, release-manifest, and open-source validation coverage.
…ate_qualification_gates [Add] Qualify negative tests and four-state controls
- Add a non-executing Tcl command-capture model and versioned module-owned expectations for sequential, combinational, clock-gating, reset-synchronizer, and cross-profile SDC policy. - Validate portable UPF design tops, domains, supplies, connections, port and power states, attributes, isolation, level-shifting, retention, and required or forbidden strategies without claiming technology signoff. - Report actionable missing, duplicate, conflicting, broad, incomplete, forbidden, and unsupported intent finding in separate SDC and UPF evidence plus an aggregate result. - Integrate the optional static-intent target with parameter profiles, multi-module orchestration, the open-source quality gate, input hashing, and release-manifest evidence. - Qualify positive and negative fixtures natively and in the pinned container, document the supported subset and STA or VC LP boundary, and advance the methodology version to 0.7.0
…for_sdc_and_upf [Add] Validate portable SDC and UPF intent
- Add selectable local and containerized ORFS execution with an inmutable image digest, invoking-user ownership, configurable platform and variant, and isolated module or profile work directories. - Add a versioned module-owned physical-evidence policy that validates nonempty DEF, GDS, ODB, SDC, and netlist deliverables plus configurable timing, electrical, and routing thresholds. - Record container identity and hashes for physical artifacts, design configuration, constraints, reports, and policy inputs while preserving PASS, FAIL, and SKIP through the canonical flow contract. - Integrate OpenROAD evidence with the release manifests and add a cached Nangate45 GitHub Actions fixture with image, artifacts, metric, and ownership assertions. - Qualify concurrent execution, cache restoration, missing or empty artifacts, image configuration, unavailable runtimes, and nonzero violations, document the non-signoff boundary, and advance the methodology version to 0.8.0.
[Add] Containerize reproducible OpenROAD execution
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
1 participant
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.
Uh oh!
There was an error while loading. Please reload this page.