ci: Check macos-cross executables on macOS #33509

pull maflcko wants to merge 4 commits into bitcoin:master from maflcko:2509-ci-mac-cross changing 5 files +105 −17
  1. maflcko commented at 11:19 am on September 30, 2025: member

    Currently, the cross-compiled exe files for Windows are tested in CI on a native Windows VM. However, the same is not done for the cross-compiled macOS executables.

    This will add about 17 minutes of additional sequential CI delay, and I am not sure if it will ever catch an issue.

    So leaving as draft for now.

  2. Drop support for EOL macOS 13 fa407eeadb
  3. fuzz: Drop unused workaround after Apple-Clang bump fa1506bdc6
  4. DrahtBot added the label Tests on Sep 30, 2025
  5. DrahtBot commented at 11:20 am on September 30, 2025: contributor

    The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

    Code Coverage & Benchmarks

    For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/33509.

    Reviews

    See the guideline for information on the review process.

    Type Reviewers
    Concept ACK katesalazar, hodlinator

    If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

    Conflicts

    Reviewers, this pull request conflicts with the following ones:

    • #32380 (Modernize use of UTF-8 in Windows code by hebasto)

    If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

  6. maflcko renamed this:
    ci: Check macos-cross
    ci: Check macos-cross executables on macOS
    on Sep 30, 2025
  7. katesalazar commented at 2:04 pm on September 30, 2025: contributor
    Concept ACK
  8. Merge commit 'fa1506bdc6c072b022493c2f75ae80e762c9994b' into HEAD 28006fabfd
  9. ci: Add native test for mac-cross result d40e61e87c
  10. maflcko force-pushed on Sep 30, 2025
  11. hodlinator commented at 8:23 am on October 1, 2025: contributor

    Concept ACK d40e61e87cfb18f75742c2efa6e705f38e3b36c9

    It feels more complete to test something closer to what the end user will be running (although we are still not using Guix builds).

    Since we don’t have high hopes of this actually detecting any issues that the rest of the CI would not have found, seems to make more sense as a nightly job?

    Runs fine: https://github.com/bitcoin/bitcoin/actions/runs/18132888148/job/51606766678?pr=33509

  12. maflcko commented at 3:06 pm on October 6, 2025: member

    Since we don’t have high hopes of this actually detecting any issues that the rest of the CI would not have found, seems to make more sense as a nightly job?

    Thx, done in #33549 and https://github.com/maflcko/b-c-nightly/actions/runs/18282485376/job/52056370818

  13. maflcko closed this on Oct 6, 2025

  14. maflcko deleted the branch on Oct 6, 2025
  15. fanquake commented at 10:03 am on October 8, 2025: member

    It’s not completely clear to me why we should have cross tests for Windows, but not for macOS, regardless of how-likely we think they are to find issues (or the runtime). Putting things in nightly repos also increases the likelyhood of double-handling changes, to fix things later (also assuming they are reported).

    Since we don’t have high hopes of this actually detecting any issues that the rest of the CI would not have found, seems to make more sense as a nightly job? @hodlinator could you elaborate on this? Why do we think the rest of the CI would detect issues in the cross-compiled binaries, if the other macOS CIs are using a different compiler, dependencies, build logic, SDK etc?

  16. maflcko commented at 10:51 am on October 8, 2025: member

    I just wonder if there ever was a single issue found if this was run in the CI in the past.

    If this has never found an issue, the overhead doesn’t seem worth it:

    I can understand the desire to test as much as possible, but it will never be possible to test everything, so we’ll have to accept and decide where to stop.

    I’d say any platform config that exposes less than 1 issue per year should not be added to the main CI, but I am happy to hear other thoughts.

  17. hodlinator commented at 2:10 pm on October 8, 2025: contributor

    Broadly agree with maflcko. Despite WSL (not sure of the status of that on CI), Windows is overall less similar to Linux than macOS is to Linux, so it is probably more likely to uncover issues.

    I guess the downside of nightly is that figuring out which commit introduces a failure lands on build-oriented people. Until we learn CI to git bisect. So assuming that CI-cost is low, I can see how this PR may be preferable. Maybe there’s a middle ground of only running upon merge into master?


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-10-10 12:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me