libdatadog update to cd90e50a#4001
Open
dd-octo-sts[bot] wants to merge 1 commit into
Open
Conversation
Automated update by CI pipeline https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/120026133 Full CI result: ❌ 2 job(s) failed
|
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.
b10b1d46577e95e057bd2b310641f965e6167d58cd90e50a5b067cf77a3e06641d838bc4c6b62abaFull CI result: ❌ 2 job(s) failed
CI pipeline: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/120026133
libdatadog Integration Report
libdatadog SHA: cd90e50a5b067cf77a3e06641d838bc4c6b62aba
Analysis date: 2026-06-20
Overall status
✅ Clean update
The new libdatadog is API-compatible with dd-trace-php. Nothing failed to
compile anywhere, and no source changes were required. The only two failing
jobs are Windows
test_cruns that hit the 1-hour CI execution timeout — aninfrastructure/flakiness issue unrelated to the libdatadog API.
Build & test summary
Sub-pipeline results (parent pipeline 120026133 / scheduled run 120020229):
test_cjobs belowPersistent failures (2):
windows test_c: [7.3]—failure_reason: job_execution_timeout, ran 3601.8swindows test_c: [7.2]—failure_reason: job_execution_timeout, ran 3602.0sBoth jobs ran for the full 60-minute job limit and were killed by GitLab, not
by a test assertion or a build error. There were no compilation-failure traces
captured (
tmp/artifacts/traces/is empty), the package build succeeded, andevery other sub-pipeline — including all Linux tracer tests — passed. This
means the code built and linked cleanly against the new libdatadog on every
platform.
Non-trivial changes made
No code changes required.
The libdatadog delta since the pinned SHA is small and contains no public API
changes that affect our call sites:
test(trace-utils): add VecMap microbenchmarks (#2126)— test-onlyrefactor(sidecar): Use oneshot flusher instead of async manual future (#2143)— internal sidecar refactor, no public signature changechore: bump version v36.0.0 (#2141)— version bumpci: proposal wf fixes and cleanup (#2140)— CI onlychore: remove redundant version from libdd-agent-client (#2139)— internalIdentified libdatadog issues
None identified.
The sidecar oneshot-flusher refactor (#2143) is the only behaviorally-relevant
change and was considered as a possible cause of a hang. It was ruled out: a
genuine flusher/sidecar hang would also manifest in the Linux sidecar and
tracer tests, and those all passed in this run. The timeout is isolated to the
two Windows
test_cjobs.Flaky / ignored failures
windows test_c: [7.3]andwindows test_c: [7.2]— both classified asflaky/infrastructure.
failure_reasonisjob_execution_timeout(the jobsexhausted the 1-hour wall-clock limit), not a test or compile failure. The
Windows V2 2019 runners for these
test_cjobs are known to be slow androutinely brush against the timeout. With all other platforms (including all
Linux tracer tests) green and no compilation traces, there is no libdatadog
API issue to fix here. Recommend a retry of these two jobs.
/cc @bwoebi