GH-48395: [C++][Dev] Update fuzzing CMake preset by pitrou · Pull Request #48396 · apache/arrow

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

pitrou · 2025-12-08T10:05:27Z

Rationale for this change

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Are these changes tested?

Manually.

Are there any user-facing changes?

No.

GitHub Issue: [C++][Dev] Update fuzzing CMake preset #48395

pitrou · 2025-12-08T10:05:49Z

@kou Does this look ok?

WillAyd

small comment but lgtm

WillAyd · 2025-12-08T20:23:55Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


Any particular reason we have to use the BUNDLED approach for this?

I want to know it too. Is it for generating more information in backtrace?

It's so that dependencies are properly instrumented by ASan/UBSan. Otherwise we might miss some bugs.

(if only JSON allowed comments, I could add one here...)

We can use "$comment" key in CMakePresets.json: https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#format

Only with CMake 3.31 and higher apparently, is that ok for us?

Oh... We can't use it for now...

kou

+1

kou · 2025-12-09T00:51:22Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",
+ "ARROW_CSV": "ON",
 "ARROW_IPC": "ON",
 "ARROW_PARQUET": "ON",
+ "PARQUET_REQUIRE_ENCRYPTION": "ON",
 "ARROW_FUZZING": "ON",
- "ARROW_WITH_SNAPPY": "ON"
+ "ARROW_WITH_BROTLI": "ON",
+ "ARROW_WITH_LZ4": "ON",
+ "ARROW_WITH_SNAPPY": "ON",
+ "ARROW_WITH_ZLIB": "ON",
+ "ARROW_WITH_ZSTD": "ON"


Could you sort them like other presets do?

Ok, will do.

kou · 2025-12-09T00:51:29Z

 "CMAKE_BUILD_TYPE": "Debug",
 "CMAKE_C_COMPILER": "clang",
 "CMAKE_CXX_COMPILER": "clang++",
+ "ARROW_DEPENDENCY_SOURCE": "BUNDLED",


I want to know it too. Is it for generating more information in backtrace?

We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

conbench-apache-arrow · 2025-12-21T12:07:13Z

After merging your PR, Conbench analyzed the 3 benchmarking runs that have been run so far on merge-commit f65ee2c.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

### Rationale for this change We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset. ### Are these changes tested? Manually. ### Are there any user-facing changes? No. * GitHub Issue: apache#48395 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Sutou Kouhei <kou@clear-code.com>

github-actionsBot added Component: C++ awaiting review Awaiting review labels Dec 8, 2025

WillAyd approved these changes Dec 8, 2025
View reviewed changes

github-actionsBot added awaiting committer review Awaiting committer review and removed awaiting review Awaiting review labels Dec 8, 2025

kou approved these changes Dec 9, 2025
View reviewed changes

github-actionsBot added awaiting review Awaiting review awaiting merge Awaiting merge awaiting committer review Awaiting committer review and removed awaiting committer review Awaiting committer review awaiting review Awaiting review awaiting merge Awaiting merge labels Dec 9, 2025

pitrou added 2 commits December 9, 2025 09:07

apacheGH-48395: [C++][Dev] Update fuzzing CMake preset
4ffce8c
We have more features enabled on our fuzzing setup but we haven't updated the corresponding CMake preset.

Sort alphabetically
b737876

pitrou force-pushed the gh48395-cmake-fuzzing-preset branch from 885d7c7 to b737876Compare December 9, 2025 08:13

github-actionsBot added awaiting changes Awaiting changes and removed awaiting committer review Awaiting committer review labels Dec 9, 2025

kou merged commit f65ee2c into apache:mainDec 9, 2025
43 checks passed

kou removed the awaiting changes Awaiting changes label Dec 9, 2025

github-actionsBot added the awaiting changes Awaiting changes label Dec 9, 2025

kou mentioned this pull request Dec 9, 2025
[C++][Dev] Update fuzzing CMake preset #48395
Closed

pitrou deleted the gh48395-cmake-fuzzing-preset branch December 10, 2025 09:37