Description
Description
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=...)
Additional Context
No response
Description
Description
Our CI currently builds and tests OpenROAD-flow-scripts using Docker or
build_openroad.sh --local, but we never exercise thesetup.shdependency-installation path. This leaves the local-install workflow untested and allowssetup.shbreakages 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:
sudo ./setup.sh./build_openroad.sh --local(or sourcessetup_env.shand verifies binaries)make DESIGN_CONFIG=...)Additional Context
No response