Currently, we maintain two separate integration test workflows:
These have diverged over time and it is unclear how much of that is accidental and how much is necessary (i.e., macOS may require slightly different setup). We should merge the workflows into one using a GitHub matrix and add conditional steps (i.e., if) for any necessary variations between OS.
As a bonus, some of these steps could be wrapped in scripts, allowing users to replicate what CI is doing more conveniently (e.g., ci/build, ci/test) and reducing the overall workflow verbosity.
Currently, we maintain two separate integration test workflows:
integration-tests-cpu, which builds and runs tests on an Ubuntu runnerintegration-tests-macos, which does almost exactly the same thing on macOS, with slight variations.These have diverged over time and it is unclear how much of that is accidental and how much is necessary (i.e., macOS may require slightly different setup). We should merge the workflows into one using a GitHub matrix and add conditional steps (i.e.,
if) for any necessary variations between OS.As a bonus, some of these steps could be wrapped in scripts, allowing users to replicate what CI is doing more conveniently (e.g.,
ci/build,ci/test) and reducing the overall workflow verbosity.