[ci] [python-package] build macOS x86_64 wheels on macOS 13 (Ventura)

[jameslamb]

I recently noticed warnings like this on Azure DevOps:

A brownout will take place on November 4, 14:00 UTC - November 5, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see actions/runner-images#10721

This proposes moving Azure DevOps x86_64 macOS jobs in this project to macOS 13 (Ventura).

Notes for Reviewers

Some relevant links.

• GitHub Actions x86_64 jobs moved to this macOS version in [ci] [python-package] run macOS x86_64 tests on macOS 12 (Monterey), stop manually setting macOS wheel tags #6487
• macOS 12 (Monterey) reached end of life in September 2024: https://endoflife.date/macos
• available XCode versions on runners:
  • macos-13: https://github.com/actions/runner-images/blob/main/images/macos/macos-13-Readme.md#xcode
  • macos-14: https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md#xcode

[StrikerRUS]

This PR is a blocker now.

Target date
Azure DevOps - January 13th, 2025

All Azure macOS jobs are failing with

##[error]No config name or imagelabel provided in request
,##[error]The remote provider was unable to process the request.

now. E.g. https://dev.azure.com/lightgbm-ci/lightgbm-ci/_build/results?buildId=17480&view=results

[jameslamb]

ugh sorry for letting it slip. I will work on this right now.

[jameslamb]

Ok, getting closer! Python jobs are producing wheels with the expected tags.

checking './dist/lightgbm-4.5.0.99-py3-none-macosx_10_15_x86_64.whl'

(Azure DevOps Python bdist job on macos-13, x86_64)

checking './dist/lightgbm-4.5.0.99-py3-none-macosx_12_0_arm64.whl'

(GitHub Actions Python bdist job on macos-14, arm64)

However, the r-package (macos-13, clang, R 4.3, cran) job is failing with this NOTE from R CMD check:

* checking for detritus in the temp directory ... NOTE
Found the following files/directories:
  ‘dsymutil-328525’ ‘dsymutil-b1ee31’ ‘dsymutil-bde960’

(build link)

I'll try to fix that.

[jameslamb]

Chose the oldest included versions of XCode from here:

• https://github.com/actions/runner-images/blob/main/images/macos/macos-13-Readme.md#xcode
• https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md#xcode

And while doing this, proposing this more-direct approach for selecting the version... depending on the actual macOS version instead of things that indirectly select it from this project's CI configs, like $AZURE and $COMPILER.

[jameslamb]

When dsymutil is run with e.g. --gen-reproducer or similar flags, it leaves behind these temporary directories with details for filing bug reports.

In some versions of clang, those are not cleaned up correctly (llvm/llvm-project#61920).

dsymutil is writing those files to TMPDIR, which is the "temp directory" referred to in this R CMD check NOTE.

Redirecting these files to anywhere else avoids the R CMD check NOTE. That can be done via environment variable DSYMUTIL_REPRODUCER_PATH. Here, I'm following the tip from golang/go#59026 (comment) and using /dev/null, so the files aren't even written to disk at all.

I think this is all fine for CI. If this kind of thing was a problem on CRAN, it'd affect every project on CRAN building with clang 14, as I LightGBM isn't doing anything custom with dsymutil.

[StrikerRUS]

Thanks a lot for fast update!