Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust designs that fail with "YOSYS_FLAGS=--hash-seed=1234" #2773

Open
oharboe opened this issue Feb 4, 2025 · 0 comments
Open

Adjust designs that fail with "YOSYS_FLAGS=--hash-seed=1234" #2773

oharboe opened this issue Feb 4, 2025 · 0 comments

Comments

@oharboe
Copy link
Collaborator

oharboe commented Feb 4, 2025

Description

In #2770, I wanted to find out which designs that are brittle w.r.t. testing against the baseline: https://jenkins.openroad.tools/job/OpenROAD-flow-scripts-Public/job/PR-2770-head/1/pipeline-console/?selected-node=55

It is also possible to add a seed on the command line to reproduce locally more easily. The PR was just to use the server build resources.

make "YOSYS_FLAGS=-v 3 --hash-seed=1234"

Failures and some initial observations:

  • asap7/ethmac_lvt: grt fails. The problem here I would say is well understood, too tight PLACE_DENSITY designs/asap7/ethmac_lvt/config.mk has too tight placement density leading to grt DRC errors on yosys hash seed change #2772
  • nangate45/swerv_wrapper. Not studied, but a grt failure too.
  • sky130hd/gcd. A small data sample(design here) is susceptible to larger standard variations, is my guess. [ERROR] finish__timing__drv__setup_violation_count fail test: 73.0 <= 66.0
  • sky130hd/ibex. This is a larger design, again a grt failure. I find the log confusing here, looks like it failed in grt, but that it ran detailed routing and ended with 0 DRC errors??

Suggested Solution

Make CI tests less brittle so that seed changes in yosys doesn't make CI fall over.

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant