[ci] indicate support of Big Sur and drop High Sierra #3749
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires recent
pip
version: pypa/packaging#319.pytest
doesn't work on Big Sur:https://github.com/microsoft/LightGBM/runs/1681244674?check_suite_focus=true#step:3:637
But all our examples work OK: https://github.com/microsoft/LightGBM/runs/1681660188?check_suite_focus=true
Compilation with both
gcc
andAppleClang
works fine.But running examples with
gcc
results inerror. I believe it is due to some conflicts between multiple OpenMP installations again. For example, one excess Intel OpneMP comes from conda deps
intel-openmp pkgs/main/osx-64::intel-openmp-2019.4-233
. And probably requires something likeLightGBM/.ci/test.sh
Lines 73 to 76 in 1abc2e0
but for
gcc
now. I'm not trying to find a workaround right now.macos-11
is a preview image now on GitHub Actions, therefore environment might be changed later. Also, builds onmacos-11
are queried for 45+ mins before starting to run, so debugging process is is extremely annoying now. It is better to wait for full release of the image and then testgcc
again.