Closed niketagrawal closed 5 months ago
The CI workflow for MacOS starts with the macos-latest
runner image and then installs boost-cpp
via conda, so I would assume that the boost libraries that are installed are compatible for MacOS. Since the conda environment cache is cleared daily, the case of old x86 boost libraries lingering around in the runner environment is also ruled out.
The version of the conda package boost-cpp
hasn't changed between the last successful CI run and the first failure.
Current CI workflow uses version 2 of the setup-miniconda GitHub action. Latest version is 3.0.4. It includes a bug fix for MacOS. Thanks @yiquintero for spotting this.
Two important system differences are observed between the last successful workflow execution and the first failing one:
This issue has been addressed in the latest push to develop.
Build fails on MacOS in the CI pipeline from the commit 1a9aa2e onwards. The failure is not related to the code changes in the commit.
This failure seems to be due to a dependency incompatibility, for example, a potential upgrade in the version of the
boost-cpp
conda package that is downloaded and installed as part of the CI workflow.Error text in CI log points to missing osx compatible boost libraries.