ci(fuzz): fix gitlab fuzz job that has started to fail on main due to pulling in packages above MSRV - #2185
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit intoJul 1, 2026
Conversation
…n packages above MSRV
|
🎯 Code Coverage (details) 🔗 Commit SHA: 9b16b84 | Docs | Datadog PR Page | Give us feedback! |
Aaalibaba42
approved these changes
Jul 1, 2026
Collaborator
Author
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
Contributor
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
gh-worker-dd-mergequeue-cf854d
Bot
deleted the
ekump/APMSP-3618-fix-failing-fuzz-ci-job
branch
July 1, 2026 15:02
taegyunkim
pushed a commit
that referenced
this pull request
Jul 8, 2026
… pulling in packages above MSRV (#2185) # What does this PR do? The fuzz job on gitlab has started to [fail on main](https://gitlab.ddbuild.io/DataDog/apm-reliability/libdatadog/-/jobs/1820649675 ). The job does rustup default nightly-2026-02-08 (rustc 1.95) at line 26, but cargo install then runs inside the repo directory, where rust-toolchain.toml pins channel = "1.87.0". A rust-toolchain.toml directory override beats the rustup default, so cargo-fuzz gets compiled with 1.87.0. # Motivation What inspired you to submit this pull request? # Additional Notes Anything else we should know when reviewing? # How to test the change? [Ran the fuzz job manually on my PR](https://gitlab.ddbuild.io/DataDog/apm-reliability/libdatadog/-/jobs/1820747534) Co-authored-by: edmund.kump <edmund.kump@datadoghq.com> Signed-off-by: Taegyun Kim <taegyun.kim@datadoghq.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
The fuzz job on gitlab has started to fail on main.
The job does rustup default nightly-2026-02-08 (rustc 1.95) at line 26, but cargo install then runs inside the repo directory, where rust-toolchain.toml pins channel = "1.87.0". A rust-toolchain.toml directory override beats the rustup default, so cargo-fuzz gets compiled with 1.87.0.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Ran the fuzz job manually on my PR