#8669 Coordinate OSS-Fuzz target for Android immutable collection construction

Guava Version

33.7.1-android and master commit 4afb1e04a4246c261be4742e1f2e2c39ebaf6266

Description

Hi Guava maintainers,

I’m an external contributor, and I opened the following OSS-Fuzz pull request to add fuzzing coverage for Android immutable-collection construction:

OSS_FUZZ_PR_URL

The target exercises the Android variants of:

ImmutableMap
ImmutableSet
ImmutableBiMap

The existing Guava OSS-Fuzz targets did not cover construction of these Android implementations.

Local validation completed:

clean OSS-Fuzz build;
check_build passed;
the target was discovered and executed by Jazzer;
a small-input negative control completed normally;
a mutation campaign starting from an empty corpus reached the intended Android collection code.

The OSS-Fuzz reviewer asked me to coordinate with the Guava maintainers before proceeding.

Could you please confirm which integration approach you prefer?

Keep the fuzz target and Android build integration in the OSS-Fuzz repository; or
Maintain the fuzz target in the Guava repository and have OSS-Fuzz build it from upstream.

I’m happy to adjust the contribution based on your preference.

Thank you.

Example

The tested Jazzer target and OSS-Fuzz integration are available in:

https://github.com/google/oss-fuzz/pull/16117

The target exercises construction of the Android implementations of
ImmutableMap, ImmutableSet, and ImmutableBiMap. It includes a small-input
negative control and has been verified with a clean OSS-Fuzz build and
check_build.

This issue is primarily intended to coordinate ownership and placement of
the fuzz target, as requested during OSS-Fuzz review.

Expected Behavior

I would like the Guava maintainers to confirm the preferred ownership and location of this fuzz target:

Keep the target in the OSS-Fuzz repository; or
Maintain the target in the Guava repository and have OSS-Fuzz build it from upstream.

I will adapt the contribution according to the maintainers' preference.

Actual Behavior

The target is currently implemented in an OSS-Fuzz pull request. During review, I was asked to coordinate with the Guava maintainers before the OSS-Fuzz contribution can proceed.

Packages

com.google.common.collect

Platforms

Android

Checklist

I agree to follow the code of conduct.
I can reproduce the bug with the latest version of Guava available.