lucasfang opened a new pull request, #538:
URL: https://github.com/apache/paimon-cpp/pull/538

   ### Purpose
   
   Linked issue: closes #537
   
   GCC 13.3 ARM64 Release compilation fails with `-Wmaybe-uninitialized` 
promoted to an error in the realtime store tests. Default-construct the 
affected optionals before assigning through the status macros, including the 
same pattern found in deletion-vector and file-index code, while retaining 
`-Werror`.
   
   Complete macOS regression exposed additional portability failures. Use 
fixed-width integer literals and expectations in tests, normalize temporary 
paths, convert early dates with calendar arithmetic, fix Darwin symbolizer text 
I/O, and make the REST mock server stop reliably when macOS does not wake 
`accept()` on shutdown. Add date, symbolizer and idle-server shutdown 
regression coverage.
   
   Correct the macOS optional-module build and runtime setup: Apple-native 
C/Rust dependency toolchains and frameworks, Vortex Darwin libraries, TBB 
deprecation handling, Lucene's CMake 4 script-mode compatibility, and Jindo's 
installed dylib alias.
   
   Incorporate the changes from #536: add a macOS 15 ARM64 AppleClang Release 
job with CTest, installed external CMake consumer verification and failure 
artifacts; support Homebrew ccache/libclang and macOS CPU detection. Keep all 
optional modules enabled except Lumina, whose pinned artifact is Linux x86_64 
only, and leave external network tests disabled.
   
   ### Tests
   
   Validated locally on macOS ARM64 with GCC 13.3.0, Release and strict project 
warnings, using a compatible macOS SDK. Apple-specific native dependencies use 
Apple's toolchain where required; Paimon's C++ code uses GCC.
   
   - Original realtime-store translation-unit compilation reproduced both 
reported diagnostics; the fixed source compiled successfully with `-O3 -DNDEBUG 
-Wall -Werror`.
   - Baseline Release build completed; `ctest --test-dir build-gcc13-release 
--output-on-failure -j 3 --timeout 900`: **31/31 targets passed** (7,678 
GoogleTest cases passed, 14 skipped).
   - Full-feature Release build completed; `ctest --test-dir build-gcc13-full 
--output-on-failure -j 3 --timeout 900`: **39/39 targets passed** (8,651 
GoogleTest cases passed, 35 skipped).
   - Full-feature modules: Avro, ORC, Mosaic, Lance, Vortex, Jindo, OSS, S3, 
Lucene, full-text and REST. Lumina and external network tests were disabled.
   - After incorporating #536, rebuilt the full-feature configuration and reran 
`ctest --test-dir build-gcc13-full -R '^paimon-vortex-format-test$' 
--output-on-failure --timeout 180`: passed.
   - `bash -n ci/scripts/build_paimon.sh ci/scripts/setup_flatc.sh`
   - `bash ci/scripts/test_cmake_modules.sh`: all 25 checks passed.
   - `bash ci/scripts/test_packaging_args.sh`: all 28 checks passed.
   - `bash ci/scripts/test_asan_symbolize.sh`: passed, including the Darwin 
subprocess text-I/O regression.
   - All configured pre-commit hooks passed for changed files; `git diff 
--check` passed.
   - Isolated mocked-command checks passed for Linux x86_64/AArch64 and Darwin 
x86_64/ARM64 feature selection, plus Darwin libclang setup and existing flatc 
detection.
   
   Linux ARM64, sanitizers, and the new AppleClang CI job/installed consumer 
were not run locally. The new workflow will provide those macOS CI build, CTest 
and installation results; the existing Linux matrix remains enabled.
   
   ### API and Format
   
   No public API, storage format or protocol changes. Date conversion now 
validates the Gregorian calendar directly, including year zero, instead of 
relying on platform-specific `timegm` behavior.
   
   ### Documentation
   
   No new user-facing feature. The CI workflow records the runner, build 
configuration and failure artifact paths.
   
   ### Generative AI tooling
   
   Generated-by: OpenAI Codex (GPT-6)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to