[CHAOSPLT-932] Add support for internal fuzzing infra #1372
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1372 +/- ##
==========================================
- Coverage 71.16% 71.14% -0.03%
==========================================
Files 403 404 +1
Lines 64368 64492 +124
==========================================
+ Hits 45810 45883 +73
- Misses 18558 18609 +51
🚀 New features to boost your workflow:
|
BenchmarksComparisonBenchmark execution time: 2025-12-15 14:26:26 Comparing candidate commit c46f03b in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 57 metrics, 2 unstable metrics. CandidateCandidate benchmark detailsGroup 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Group 9
Group 10
Group 11
Group 12
Group 13
Group 14
Group 15
Group 16
Group 17
Group 18
Group 19
BaselineOmitted due to size. |
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-apple-darwin
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-apple-darwin
x86_64-unknown-linux-gnu
|
edznux-dd
force-pushed
the
edouard/add-fuzzing-infra
branch
from
a470af9 to
ff918ab
Compare
VianneyRuhlmann
approved these changes
Dec 15, 2025
r1viollet
reviewed
Dec 16, 2025
| .gitignore @Datadog/libdatadog | ||
| .gitlab-ci.yml @Datadog/apm-common-components-core | ||
| .gitlab/benchmarks.yml @Datadog/apm-common-components-core | ||
| .gitlab/fuzz.yml @Datadog/chaos-platform |
Contributor
There was a problem hiding this comment.
thanks for flagging ownership
r1viollet
approved these changes
Dec 16, 2025
Contributor
r1viollet
left a comment
r1viollet
left a comment
There was a problem hiding this comment.
LGTM
Thank you for adding the infra to do this.
NIT: it was not totally clear where I should look up the reports from the readme (I understand I can go to gitlab, though you might want a more explicit mechanism)
duncanista
approved these changes
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds a fuzzer using
cargo-fuzzthat then runs in our internal fuzzing infrastructure.Motivation
This aims to enable fuzz testing via cargo fuzz in this repository. Adding a initial fuzzer is simply a bootstraping part.
The end goal is to find bugs before customers do.
There's already some existing property test / fuzz test with
boleroin other crate (i.e:libdd-profiling{,-protobuf}) but these run only in Github's CI for short amount of time (30sec). The fuzzing infra will let these run last for hours.This new pipeline will NOT run in feature branches and will NOT block CI. We only use the CI system to build the binaries and upload it to our internal infra, to be run for extended period of time.
Because blocking CI on "very wrong" failure is still valuable during quick developement cycle, the other existing fuzz test and property tests will still run for 30sec on github actions. These fuzz test will NOT be part of the fuzzing infrastructure (and so you won't have access to the enrichment, auto fix proposal, stats, ...)
Additional Notes
How to test the change?
Click the
fuzzpipeline in gitlab of this branch.Example result here