Repository for tests of HiGHS during development and for releases.
Run every downstream test against one HiGHS ref:
gh workflow run pre-release.yml -f highs_ref=latest
gh run watch # or open the Actions tabhighs_ref can be any branch, tag or SHA in ERGO-Code/HiGHS. The same run
happens every Monday on latest and on master. pre-release.yml only calls the workflows
below, so to run one of them alone, use gh workflow run <file> -f ....
.github/workflows/smoke.yml: release gate G1 fromtest-build. For each build variant, configure, build,ctest, then solve afiro, 25fv47, egout and flugpl with every LP solver and MIP root-LP solver, checking the objective and that the requested solver really ran (scripts/smoke_unix.sh,scripts/smoke_windows.ps1). Linux: default, hipo, debug, static, warnings (gcc-14), bazel. macOS: default, hipo, debug, fortran, x86_64 (Rosetta), bazel. Windows: default, hipo and hipo-shared (in-tree OpenBLAS by clang-cl), hipo-vcpkg-clang. Plus analpine:edge(musl) build and ctest (HiGHS#3000)..github/workflows/release-checks.yml: G0, every HiGHS CI run on the commit is green, which fails otherwise. G5 reports in the run summary, for review: the version strings and HConfig templates against the last release (scripts/version_bump_check.sh), and the options diff against the last release's highspy (scripts/dump_options.py)..github/workflows/cmake-*: HiGHSmasterandlatestconsumed through CMakefind_packageandFetchContent. HiPO is covered here only for MinGW..github/workflows/hipo-consumer.yml: builds HiGHS with HiPO for each way of providing BLAS, and checks that an application really runs HiPO through an install, a moved install, the build tree and a subproject. On Linux it also uses pkg-config, for HiPO with the system OpenBLAS (system) and for HiGHS without HiPO (none), each from a prefix outside the default search path. To run one setup locally:bash hipo-consumer/run.sh <highs-source> <work-dir> system shared.hipo-consumer/expected-failures/<ref>-<os>.txtlists the results that must fail on a ref, so a job goes red when a listed failure starts passing too..github/workflows/extra-unit-tests.yml: HiGHSlatestwith the extra unit tests fromgalabovaa/highs-unit-tests..github/workflows/ortools-cmake.yml,ortools-bazel.yml: the newest OR-Tools release built against HiGHSlatest(CPU). Scripts live inortools/..github/workflows/packagers.yml: HiGHS built with the recipes that downstream packagers use, fetched from their repos, with only the source swapped for the HiGHS ref (packagers/use_highs_source.py):- vcpkg port
highsandhighs[extras]on Linux and Windows, andhighs:x64-windows-static. The installedhighssolves afiro, thenfind_package(highs)fromhipo-consumer/. The port's patches are applied first: one that no longer applies fails the job, and one already in HiGHS is reported so the port can drop it. - conda-forge
highsfeedstock on Linux, macOS (arm64) and Windows, andhighspyon Linux, built and tested withrattler-build. - Homebrew
highsformula:brew install,brew testandbrew linkage --teston macOS. - conan-center
highsrecipe,conan createwith cppstd 17 and 20, which also runs itstest_package. - nixpkgs (
nixos-unstable) with itshighsbuilt from the HiGHS ref (packagers/nixpkgs.nix), thenhighsand the nixpkgs packages that use it, each with its own checks: highspy, qpsolvers, cvxpy, sleqp, casadi and or-tools.
- vcpkg port
.github/workflows/interfaces.yml: interface tests that HiGHS's CI runs only on pull requests or some branches: highspy and OR-Tools in one process, theHighs.NativeNuGet package used from a new .NET project, and the Rusthighs-syscrate with its HiGHS submodule replaced by the ref, each on Linux, macOS and Windows. HiGHS's CI covers HiGHS.jl and Fortran on push.- or-tools-readme.md: commands for testing OR-Tools with
the HiGHS GPU solver by hand (Bazel and CMake/
HIGHS_GPU_LIB, Linux and Windows). Notes are in gpu-interfaces/.
The scripts/smoke_*, version_bump_check.sh and dump_options.py scripts
are copies of galabovaa/test-build scripts/ at 30bed1d. That repo is
private, so CI cannot check it out. When one copy changes, copy it to the other.
Not run here: the regression campaigns (test-runtimes, timed on highs01 and
highs02), GPU builds, and the G4 packaging checks, which download HiGHS CI
artifacts (TestPyPI wheels, NuGet preview, release-cpack) and would need a
token with access to them.
A PR to main runs cmake-* and extra-unit-tests always, and the others
when it changes their scripts or workflow file. To
test a PR's workflow changes against all of them, run pre-release.yml on the
PR branch: gh workflow run pre-release.yml --ref <branch> -f highs_ref=latest.