Wheel build - Skip tests for cp37 and cp38-macosx_x86_64

[PrimozGodec]

Overview

Description of the changes proposed in this pull request:
Fix tests in the wheel build

• Skip cp37: since many packages that Shap depend on do not provide cp37 wheel anymore. They would need to be built before tests can run. One of the packages is Catboost which would need Ninja to build; also, if Ninja is installed, it takes a long time to build, so I suggest skipping cp37.
• Skip cp38-macosx_x86_64: In the MacOS and Python 3.8 case, pip will not download the universal Catboost wheel but will take .tar.gz and try to build it. It is likely due to: GitHub actions Build fails on macOS with python 3.8 - catboost 1.2 catboost/catboost#2371

Checklist

• Related: BUG: Tests fail when running from built wheel using cibuildwheel #3012
• EDITED: may not fully close this issue
• All pre-commit checks pass.
• Unit tests added (if fixing a bug or adding a new feature)
• Added entry to CHANGELOG.md (if changes will affect users)

[codecov]

Codecov Report

Merging #3015 (32a60a8) into master (edb3464) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3015      +/-   ##
==========================================
- Coverage   54.79%   54.78%   -0.01%     
==========================================
  Files          90       90              
  Lines       12895    12895              
==========================================
- Hits         7066     7065       -1     
- Misses       5829     5830       +1     

see 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[connortann]

This looks good, thanks for the PR!

Just one request, please add a comment in the YAML file to explain the rationale behind the skipped tests, that the catboost wheel is not available. You could reference this PR number for more info.

FYI I edited the description to change "closes #3012" to "related: #3012", as I don't think this PR by itself will fully close that issue.

[connortann]

@PrimozGodec I noticed one other change to address, please see the thread above.

[PrimozGodec]

I changed the PR to draft since I want to test what work and what doesn't will change it to ready later

[connortann]

I would like to get the main changed merged in soon, so we can keep progressing towards a release. So, if the win32 build issue is not something that can be resolved quickly, I'd suggest removing that from the scope of this PR and raising a separate issue.

[PrimozGodec]

I added this for easier debugging. That one build does not finish because of another. E.g. the Windows build does not finish because of failing MacOS. The whole building will still fail at the end, and no upload will happen.

[PrimozGodec]

I would like to get the main changed merged in soon, so we can keep progressing towards a release. So, if the win32 build issue is not something that can be resolved quickly, I'd suggest removing that from the scope of this PR and raising a separate issue.

Good. I made a PR ready to merge and will continue with debugging in a separate PR after #3021 and #3020 are merged.

[connortann]

Thanks, LGTM! I merged in master to update the branch, so will merge once the tests pass.