Repository navigation
Conversation
uploadMetadata.py now reads flow-status.json, which the CI job writes next to each design's reports with the run's exit code, whether its time limit stopped it, and the elapsed and limit minutes. Each design record gains an "outcome" object: passed, error, timeout or crash, with the stage the run ended in and the first error line found in its stage logs. A crash is a failed run whose last stage log shows the tool died on a signal. A design that failed before writing metadata.json used to be skipped with a warning. When its run left a status file it is now reported with only its outcome, so a design that keeps timing out shows up instead of silently going missing. On the per-design fallback for oversized payloads, such a record names itself with the run__flow__ keys that metadata.json would have held. Designs without a status file are reported exactly as before. Signed-off-by: Miguel Dalberto Pedro <miguel.pedro@precisioninno.com>
Signed-off-by: Miguel Dalberto Pedro <miguel.pedro@precisioninno.com>
Signed-off-by: Jonas Gava <jfgava@precisioninno.com>
Contributor
There was a problem hiding this comment.
Code Review
This pull request enables CUGR for global routing across multiple designs by adding the GLOBAL_ROUTE_USE_CUGR environment variable to their respective config.mk files. The review feedback highlights missing trailing newlines at the end of the configuration files for the riscv32i and dynamic_node designs.
Signed-off-by: Jonas Gava <jfgava@precisioninno.com>
Member
🔍 QoR checkMetrics reflect the PR merge build — i.e. what will land on the target branch. Commit 62 design(s) checked — 3 with regression(s), 0 without a comparable baseline. ❌ asap7/ibex base — 2 failing metric(s)
❌ nangate45/ariane136 base — 1 failing metric(s)
❌ sky130hs/aes base — 1 failing metric(s)
|
…t-private/upload-design-outcomes Report how each design's flow run ended in the metadata upload
…ROAD-flow-scripts into secure-enable-cugr-default-1
openroad-ci
force-pushed
the
secure-enable-cugr-default-1
branch
from
November 9, 2026 20:56
931706c to
676ffa9
Compare
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.
Starting with the following designs that presented QoR improvement compared to FastRoute: