libdatadog update to 98016adb#3944
Open
dd-octo-sts[bot] wants to merge 1 commit into
Open
Conversation
|
bbf5aea to
5c82d3b
Compare
Automated update by CI pipeline https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/117507316 Full CI result: ❌ 3 job(s) failed
5c82d3b to
c36e6cb
Compare
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
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.
Summary
Automated update of the libdatadog submodule to the latest HEAD.
93e97238020b5cf1165b2583ec555d58307af3c198016adb6ea73454ea4804a3847724d7b215b677Full CI result: ❌ 3 job(s) failed
CI pipeline: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/117507316
libdatadog Integration Report
libdatadog SHA: 98016adb6ea73454ea4804a3847724d7b215b677
Analysis date: 2026-06-06
Overall status
✅ Clean update
No code changes were required. The new libdatadog revision is a release
version-bump merge with no functional/API changes, and all compilation jobs
passed. The three failing jobs are runtime test failures (Windows hangs and one
ASAN test) that cannot be attributed to this libdatadog update.
Build & test summary
The only new libdatadog commit since the pinned SHA is:
The net diff this merge introduces to
maintouches no Rust source files —only version metadata:
These are crate version bumps (e.g.
libdd-sampling2.1.0 → 3.0.0) andchangelog entries that were already present in the source tree dd-trace-php was
building against; the merge simply lands them on
main. There is no APIsurface change, no signature change, and no behavioural change in this delta.
Sub-pipeline results:
All Rust/native build steps compiled and linked successfully against the new
libdatadog (every build/package job passed, and the compilation-trace directory
tmp/artifacts/traces/is empty — the harness captured no compilationfailures). The three failures are all in the
teststage, not the build stage.Non-trivial changes made
No code changes required.
Identified libdatadog issues
None identified.
The libdatadog delta is version metadata only (no
.rschanges), so none of theobserved failures can originate from a libdatadog code change.
Flaky / ignored failures
All three failing jobs are in the tracer
teststage and are unrelated to the(metadata-only) libdatadog update:
windows test_c: [7.3]—failure_reason: job_execution_timeout.The job ran for the full ~3602s (1-hour) job limit and was killed, i.e. it
hung rather than failing a specific assertion. Windows runners are prone to
this class of hang/timeout. No build output or compilation failure precedes
it.
windows test_c: [7.2]—failure_reason: job_execution_timeout.Same signature as the 7.3 job: ran the full ~3602s and timed out. Two
simultaneous Windows-only timeouts on the same runner group point at runner
infrastructure / a flaky hang, not at a libdatadog change (which contains no
code).
ASAN test_c with multiple observers: [8.4]—failure_reason: script_failureafter ~286s. This is the Linux ASAN variant of the C testsuite under the multiple-observers configuration. Because the libdatadog
delta introduces no functional code, this failure is not attributable to the
update; it is treated as pre-existing flakiness/infra noise. (Full job logs
were not available in the artifacts — only
all_failures.jsonmetadata and ajunit archive that was not extracted — so no specific assertion could be
correlated; the version-only nature of the libdatadog change is sufficient to
exclude it as a cause.)
These same three jobs are the ones the CI harness already retried
(
tmp/artifacts/retried_jobs.tsv), consistent with transient/flaky behaviour./cc @bwoebi