[Update] Consume MF20260910V1 project qualification flows - #25
Merged
Merged
Conversation
Migrate mosaic-common to the shared project orchestration and begin module-owned parameter-profile qualification. - Pin mosaic-flow to MF20260910V1 and replace legacy root orchestration with the shared project API. - Move the module registry to the validated config/modules.json schema and generate the CI matrix through module-profile-matrix. - Isolate native and container CI caches, images, reports, work products, artifacts, and release evidence by module and parameter profile. - Update repository guidance for profile-aware portable qualification and validated release manifests. - Add passing DFF profile harnesses for scalar synchronous, vector asynchronous, and vector no-enable implementations. - Add passing profile manifests for lane mask, priority encoder, level shifter, and isolation cell using their reusable checker collateral. - Add a DFF static-intent policy that validates synchronous and asynchronous SDC contracts plus the always-on UPF baseline. - Add focused isolation-cell formal profile proof collateral and document the narrow DFF no-enable lint waiver. - Verify the DFF profile aggregate with bounded parallelism and validate the local diagnostic release manifest.
Repair the native and container qualification paths introduced by the MF20260910V1 migration. - Restore the repository-wide Verible adapter so modules with four-space source policy retain their established formatting contract. - Format the DFF parameter-profile harnesses with their default two-space policy so shared formatting checks are reproducible. - Install python3-venv in the portable image, which is required by the PyUVM environment provisioned by mosaic-flow. - Declare the immutable packaged methodology state and container execution context when generating release evidence in Docker. - Verify the previously failing counter, clock gate, reset synchronizer, and retention-register native flows plus a containerized DFF profile flow and release-manifest validation.
Restore the clock-gate OpenROAD qualification path that the shared MF202610V1 workflow migration omitted. - Add a declarative OpenROAD evidence policy for final layout artifacts and zero-violation timing and routing metrics. - Run the pinned physical flow only in the native clock-gate CI job before generating release evidence. - Disable OpenROAD inside the portable module container, where nested Docker execution is intentionally unavailable. - Upload module-rooted report and work trees so default and profiled modules retain all generated evidence. - Verify the native ORFS physical run, the clock-gate container flow, and both release-manifest contexts.
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.
Migrate mosaic-common to the shared project orchestration and begin module-owned parameter-profile qualification.