Skip to content

libdatadog update to cd90e50a#4001

Open
dd-octo-sts[bot] wants to merge 1 commit into
masterfrom
bot/libdatadog-latest
Open

libdatadog update to cd90e50a#4001
dd-octo-sts[bot] wants to merge 1 commit into
masterfrom
bot/libdatadog-latest

Conversation

@dd-octo-sts

@dd-octo-sts dd-octo-sts Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Summary

Automated update of the libdatadog submodule to the latest HEAD.

SHA
Previous b10b1d46577e95e057bd2b310641f965e6167d58
New cd90e50a5b067cf77a3e06641d838bc4c6b62aba

Full 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_c runs that hit the 1-hour CI execution timeout — an
infrastructure/flakiness issue unrelated to the libdatadog API.

Build & test summary

Sub-pipeline results (parent pipeline 120026133 / scheduled run 120020229):

Sub-pipeline Result Notes
shared-trigger ✅ success
profiler-trigger ✅ success
appsec-trigger ✅ success
package-trigger ✅ success full package build (~3h) completed
tracer-trigger ❌ failed only the 2 Windows test_c jobs below

Persistent failures (2):

  • windows test_c: [7.3]failure_reason: job_execution_timeout, ran 3601.8s
  • windows test_c: [7.2]failure_reason: job_execution_timeout, ran 3602.0s

Both 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, and
every 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-only
  • refactor(sidecar): Use oneshot flusher instead of async manual future (#2143) — internal sidecar refactor, no public signature change
  • chore: bump version v36.0.0 (#2141) — version bump
  • ci: proposal wf fixes and cleanup (#2140) — CI only
  • chore: remove redundant version from libdd-agent-client (#2139) — internal

Identified 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_c jobs.

Flaky / ignored failures

  • windows test_c: [7.3] and windows test_c: [7.2] — both classified as
    flaky/infrastructure. failure_reason is job_execution_timeout (the jobs
    exhausted the 1-hour wall-clock limit), not a test or compile failure. The
    Windows V2 2019 runners for these test_c jobs are known to be slow and
    routinely 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

@dd-octo-sts dd-octo-sts Bot requested review from a team as code owners June 20, 2026 06:20
@dd-octo-sts dd-octo-sts Bot requested review from leoromanovsky and sameerank and removed request for a team June 20, 2026 06:20
@datadog-prod-us1-4

datadog-prod-us1-4 Bot commented Jun 20, 2026

Copy link
Copy Markdown

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 15 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-php | appsec integration tests: [test8.4-release]   View in Datadog   GitLab

🧪 1 Test failed

All test failures are known flaky.

❄️ Known flaky: extended heartbeat re-emits configuration, dependencies and integrations() from com.datadog.appsec.php.integration.TelemetryExtendedHeartbeatTests   View in Datadog
java.lang.AssertionError: phpredis not emitted via app-started/app-integrations-change; saw: []. Expression: (phpredis in flushed). Values: flushed = []

java.lang.AssertionError: phpredis not emitted via app-started/app-integrations-change; saw: []. Expression: (phpredis in flushed). Values: flushed = []
	at org.codehaus.groovy.runtime.InvokerHelper.createAssertError(InvokerHelper.java:416)
	at com.datadog.appsec.php.integration.TelemetryExtendedHeartbeatTests.extended heartbeat re-emits configuration, dependencies and integrations(TelemetryExtendedHeartbeatTests.groovy:70)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)

Not introduced in this PR.

DataDog/apm-reliability/dd-trace-php | min install tests   View in Datadog   GitLab

DataDog/apm-reliability/dd-trace-php | test_extension_ci: [7.0]   View in Datadog   GitLab

View all 15 failed jobs.

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 54.08% (-0.04%)

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 6c16763 | Docs | Datadog PR Page | Give us feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants