[fix](be) Make the BE unit tests build and run on macOS - #68520

What problem does this PR solve?

Issue Number: N/A

Problem Summary:

Context. run-be-ut.sh is the only entry point for the BE unit tests, and on macOS it is also the only way to run them: the BE UT (macOS) workflow runs build.sh --be, which configures with -DMAKE_TEST=OFF, so nothing under be/test is compiled there (the workflow says so in its own comment at .github/workflows/be-ut-mac.yml:123). On a clean worktree the script therefore fails twice before a single test executes, and then stops seven more times while compiling be/test.

1. The problem, and what it cost

The script never initializes two of the submodules it needs. run-be-ut.sh initializes three submodules (contrib/datasketches-cpp, contrib/apache-orc, contrib/clucene); build.sh initializes five, and the two it adds — contrib/faiss and contrib/openblas — are required before a single file is compiled. be/CMakeLists.txt:1038 adds be/src/storage/index/ann unconditionally, and that directory's cmake-protect/CMakeLists.txt:48,66 calls add_subdirectory() on both. On a fresh clone or a new git worktree the configure step therefore ends with

CMake Error at src/storage/index/ann/cmake-protect/CMakeLists.txt:48 (add_subdirectory):
  The source directory .../contrib/openblas does not contain a CMakeLists.txt file.
CMake Error at src/storage/index/ann/cmake-protect/CMakeLists.txt:66 (add_subdirectory):
  The source directory .../contrib/faiss does not contain a CMakeLists.txt file.

Running build.sh once first hides it, which is why it goes unnoticed.

Seven be/test translation units do not compile on macOS. The Linux BE UT build is green for all seven. run-be-ut.sh invokes ninja without -k, so the developer fixes one file, waits out another full compile, and meets the next one — seven round trips, each of them tens of minutes, for a task whose whole point is to run a test.

None of the seven is related to a local change; a clean master reproduces all of them. #2 arrived on 2026-09-24 with #68397 ([fix](be) Preserve decimal precision in format_round, by TengJianPing), which is the commit that added function_format_round_test.cpp — after the last full macOS sweep. So this class of breakage is still being produced: "green on Linux, red on macOS" is invisible to every CI job we have, and the two obstacles above make the one manual path that would find it expensive enough that nobody walks it.

2. What this PR does, and why it helps

• run-be-ut.sh: the update_submodule list gains contrib/openblas and contrib/faiss, with the same archive URLs build.sh:941 already uses, plus a comment that the list has to stay in sync with build.sh.
• be/test/CMakeLists.txt: the APPLE branch links ann_index in addition to the force_load flag. ann_index is the target that exports the faiss include directories PUBLIC, so the APPLE link line now feeds the same compile and link inputs as every other platform, instead of being a macOS special case.
• Six test files: the smallest change that removes the platform difference, each spelled the way the file's neighbours already spell it — PRIu64 / PRId64 (core/decimal12.h, util/histogram.cpp), int64_t(...) around the literals (storage/key_coder_test.cpp:392, runtime/jsonb_document_test.cpp:433), #if defined(POSIX_FADV_DONTNEED) around the call.

Linux behaviour is unchanged: every edit is either inside an APPLE-only path or a strictly more portable spelling of the same value. On macOS run-be-ut.sh becomes a usable test line for the first time.

One cost worth naming: because the APPLE link line now propagates include directories, the compile command of every be/test TU changes once, so the first macOS build after this lands rebuilds be/test (about 1230 TUs). Later builds are incremental again.

Branch pick. #68397 was never picked to branch-4.1, so function_format_round_test.cpp does not exist there. Of the seven files, only storage/segment/hierarchical_data_iterator_test.cpp exists on branch-4.1, with the same three std::min(*rows, ROWS - current_ordinal) sites and the same types (ROWS is size_t, ordinal_t is uint64_t), so it fails to compile on macOS there too; that branch also has no APPLE force_load branch in be/test/CMakeLists.txt, so the faiss part is master-only. If 4.1 is meant to run BE UT on macOS, the pick is that one file's hunk.

3. The classes, and how they call each other

• run-be-ut.sh (changed): update_submodule() calls git submodule update --init --recursive <path> and falls back to the branch tarball; the two added lines are identical in shape to the three that were already there.
• be/test/CMakeLists.txt (changed): the APPLE branch of the doris_be_test link step.
• be/src/storage/index/ann/cmake-protect/CMakeLists.txt (unchanged, the reason the submodules are mandatory): add_subdirectory() on contrib/openblas and contrib/faiss, reached unconditionally from be/CMakeLists.txt:1038.
• ann_index (unchanged target in be/src/storage/index/ann): links faiss PUBLIC, so its INTERFACE_INCLUDE_DIRECTORIES carry the faiss include path.
• vector_search_test (unchanged target in be/test/storage/index/ann): links ann_index PUBLIC; on APPLE it reaches doris_be_test as forced-in objects rather than as a target.
• The seven test TUs: unchanged in behaviour, three of them compiled in a portable spelling.

run-be-ut.sh
  |- update_submodule contrib/{datasketches-cpp, apache-orc, clucene}   [already there]
  '- update_submodule contrib/{openblas, faiss}                        [added here]
        '- git submodule update --init --recursive

be/CMakeLists.txt:1038  add_subdirectory(be/src/storage/index/ann)
  '- storage/index/ann/CMakeLists.txt:18  add_subdirectory(cmake-protect)
        '- cmake-protect/CMakeLists.txt:48,66  add_subdirectory(contrib/{openblas, faiss})
              '- target faiss --(PUBLIC)--> target ann_index --(PUBLIC)--> vector_search_test
                                                                              |
be/test/CMakeLists.txt:170  if (APPLE)                                        |
  |- before: -Wl,-force_load,<path to libvector_search_test.a>  -- propagates nothing
  '- after:  the same flag + ann_index                          -- propagates the faiss include dirs
                                                                              |
                                        function_map_inner_product_test.cpp <--'
                                        (and every other be/test TU, which now
                                         compiles with the same inputs as on Linux)

be/test/CMakeLists.txt  add_executable(doris_be_test ${UT_FILES})   <- the other six TUs, no link involvement

Release note

None

Check List (For Author)

• Test

  • Manual test (add detailed scripts or steps below)

  Build. BUILD_TYPE_UT=Debug bash run-be-ut.sh on macOS 26.5 / arm64 / clang 20 / libc++: 1231 translation units, 0 failures, doris_be_test linked (340 MB after the dsymutil + llvm-strip post-build step). Before this PR the same command stops at configure, and after contrib/{faiss,openblas} are initialized by hand it stops at the first line of the table above and at six more after that.

  Tests. run-be-ut.sh --run with a filter over the affected suites: 43 tests from 5 suites ran, all passed — FormatRoundTest 8, FunctionMapInnerProductTest 11, BkdCorruptionTest 16, SniiSpimiLocalityBenchTest 3 (its InternSetReserveUpperBound is the case that exercises the key_equal fix, and it still asserts intern.size() == distinct), HierarchicalDataIteratorTest 5. The two bench files contain DISABLED_ cases only, so compilation is the whole check for them.

  Per-file compile check. Each of the seven TUs was also compiled on its own with the exact command line from the build's own compile_commands.json (clang++ -fsyntax-only ...), which is how the seventh was found without a full rebuild.

  Not run: Linux. The portability of each edit was argued from the Linux compile flags (libstdc++'s key_equal call order, LP64 PRIu64) rather than from a Linux build; the CI BE UT job covers that side.

• Behavior changed:

  • No.

• Does this need documentation?

  • No.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label