GH-38041: [C++][CI] Improve IPC fuzzing seed corpus

[pitrou]

1. Add fuzz seeds with newer datatypes such as Run-End Encoded and String Views
2. Add fuzz seeds with buffer compression
3. Build seed corpus generation utilities even when fuzzing isn't enabled, for convenience

• GitHub Issue: [C++] Add new datatypes to the IPC fuzz seed corpus #38041

[github-actions]

⚠️ GitHub issue #38041 has been automatically assigned in GitHub to PR creator.

[pitrou]

@github-actions crossbow submit -g cpp

[pitrou]

Ok, test-build-cpp-fuzz will require google/oss-fuzz#12320 to pass successfully

[pitrou]

@github-actions crossbow submit -g cpp

[mapleFU]

I'm afraid this would meet same problem ( #41025 ) in gcc 7.5.0, sigh...

[pitrou]

I don't think so. #41025 involved an implicit conversion from unique_ptr to shared_ptr, IIUC, which isn't the case here.

[mapleFU]

So this would not casting implicit cast PlatformFilename to Result<PlatformFilename> or did I miss something?

[pitrou]

In #41025 the cast is from std::unique_ptr to Result<std::shared_ptr>, which is more complex (there are two cascaded casts).

[pitrou]

Let's try anyway.

[github-actions]

Unable to match any tasks for `test-r-rstudio-r-base-4.1-opensuse153`
The Archery job run can be found at: https://github.com/apache/arrow/actions/runs/10389980694

[pitrou]

@github-actions crossbow submit -g cpp -g r

[github-actions]

Revision: 9f6f1f6

Submitted crossbow builds: ursacomputing/crossbow @ actions-92e99ffb33

Task	Status
r-binary-packages
test-alpine-linux-cpp
test-build-cpp-fuzz
test-conda-cpp
test-conda-cpp-valgrind
test-cuda-cpp
test-debian-12-cpp-amd64
test-debian-12-cpp-i386
test-fedora-39-cpp
test-r-arrow-backwards-compatibility
test-r-clang-sanitizer
test-r-depsource-bundled
test-r-depsource-system
test-r-dev-duckdb
test-r-devdocs
test-r-gcc-11
test-r-gcc-12
test-r-install-local
test-r-install-local-minsizerel
test-r-linux-as-cran
test-r-linux-rchk
test-r-linux-valgrind
test-r-minimal-build
test-r-offline-maximal
test-r-offline-minimal
test-r-rhub-debian-gcc-devel-lto-latest
test-r-rhub-debian-gcc-release-custom-ccache
test-r-rhub-ubuntu-release-latest
test-r-rocker-r-ver-latest
test-r-rstudio-r-base-4.1-opensuse155
test-r-rstudio-r-base-4.2-focal
test-r-ubuntu-22.04
test-r-versions
test-ubuntu-20.04-cpp
test-ubuntu-20.04-cpp-bundled
test-ubuntu-20.04-cpp-minimal-with-formats
test-ubuntu-20.04-cpp-thread-sanitizer
test-ubuntu-22.04-cpp
test-ubuntu-22.04-cpp-20
test-ubuntu-22.04-cpp-emscripten
test-ubuntu-22.04-cpp-no-threading
test-ubuntu-24.04-cpp
test-ubuntu-24.04-cpp-gcc-13-bundled
test-ubuntu-24.04-cpp-gcc-14
test-ubuntu-r-sanitizer

[pitrou]

CI failures look unrelated for now.

[conbench-apache-arrow]

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

There were 2 benchmark results indicating a performance regression:

• Commit Run on amd64-m5-4xlarge-linux at 2024-08-15 09:57:07Z
  • file-write (R) with compression=lz4, dataset=nyctaxi_2010-01, file_type=feather, input_type=dataframe, language=R
  • file-write (R) with compression=uncompressed, dataset=nyctaxi_2010-01, file_type=feather, input_type=dataframe, language=R

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