You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our CI currently builds and tests OpenROAD-flow-scripts using Docker or build_openroad.sh --local, but we never exercise the setup.sh dependency-installation path. This leaves the local-install workflow untested and allows setup.sh breakages to go undetected.
Expected behavior
CI should include a job that runs sudo ./setup.sh (on a supported OS, e.g., Ubuntu 22.04) and verifies that the environment can subsequently build/run the flow.
Suggested Solution
Add a CI workflow/job that:
Checks out the repo
Runs sudo ./setup.sh
Runs ./build_openroad.sh --local (or sources setup_env.sh and verifies binaries)
Optionally runs a minimal flow test (make DESIGN_CONFIG=...)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 21 days if no further activity occurs. Remove the Stale label or comment to keep it open.
Activity
github-actions commentedon Oct 20, 2026
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 21 days if no further activity occurs. Remove the
Stalelabel or comment to keep it open.