ci: add NetBSD Clang cross job #35412

pull fanquake wants to merge 2 commits into bitcoin:master from fanquake:netbsd_clang_cross changing 4 files +63 −27
  1. fanquake commented at 1:42 PM on May 29, 2026: member

    This adds a Linux cross job for NetBSD; similar to #34491 (FreeBSD).

    This uses the upcoming NetBSD 11.0 release (rc4), as the GCC shipped with 10, is old, and doesn't support bitset, source_location etc.

  2. DrahtBot added the label Tests on May 29, 2026
  3. DrahtBot commented at 1:42 PM on May 29, 2026: contributor

    <!--e57a25ab6845829454e8d69fc972939a-->

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

    <!--006a51241073e994b41acfe9ec718e94-->

    Code Coverage & Benchmarks

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

    <!--021abf342d371248e50ceaed478a90ca-->

    Reviews

    See the guideline for information on the review process. A summary of reviews will appear here.

    <!--5faf32d7da4f0f540f40219e4f7537a3-->

  4. depends: netBSD cross with Clang
    Need to think about this more, given unlike OpenBSD and FreeBSD, NetBSD
    is still shipping with GCC/binutils as the system compiler.
    241813038e
  5. ci: add netBSD cross CI job
    Use 11.0rc4, as the 10.x sysroot ships with a GCC that is too old to
    have bitset, source_location etc.
    b2006c61af
  6. fanquake force-pushed on May 29, 2026
  7. DrahtBot added the label CI failed on May 29, 2026
  8. DrahtBot commented at 2:02 PM on May 29, 2026: contributor

    <!--85328a0da195eb286784d51f73fa0af9-->

    🚧 At least one of the CI tasks failed. <sub>Task lint: https://github.com/bitcoin/bitcoin/actions/runs/26640734145/job/78512803098</sub> <sub>LLM reason (✨ experimental): CI failed linting because ci/test/00_setup_env_netbsd_cross.sh has a shebang but incorrect permissions (644 instead of executable 755).</sub>

    <details><summary>Hints</summary>

    Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

    • Possibly due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

    • A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

    • An intermittent issue.

    Leave a comment here, if you need help tracking down a confusing failure.

    </details>

  9. fanquake marked this as ready for review on May 29, 2026
  10. DrahtBot removed the label CI failed on May 29, 2026

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: 2026-05-31 17:50 UTC

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