libdatadog update to 3a9e983a

[dd-octo-sts]

Summary

Automated update of the libdatadog submodule to the latest HEAD.

	SHA
Previous	$LIBDATADOG_PINNED_SHA
New	3a9e983a58532d65bb42e6ab80e6d6cbe7f3f66c

Full CI result: ❌ 1 job(s) failed
CI pipeline: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/145584717

---

libdatadog Integration Report

libdatadog SHA: 3a9e983a58532d65bb42e6ab80e6d6cbe7f3f66c
Analysis date: 2026-10-19

Overall status

✅ Clean update

Build & test summary

Pipeline: https://gitlab.ddbuild.io/DataDog/apm-reliability/dd-trace-php/-/pipelines/145584717

Every compilation, unit-test, and integration-test job passed in every
sub-pipeline (tracer, appsec, profiler, shared, package). The
package-trigger child pipeline (145579204) finished as success. One job
failed even after a retry:

Sub-pipeline	Job	Stage	allow_failure	Reason
package-trigger	publish docker image for system tests	release	true	script_failure

No compilation-failure traces were collected (tmp/artifacts/traces/ is
empty), which confirms that dd-trace-php still builds against the new
libdatadog. That holds even though the changelog has several breaking (!)
commits: ShmSafe for shm payloads, AtomicOption → AtomicOptionBox,
sidecar state bound by Connection, the telemetry debugger namespace, the
APM_PROFILING RC product, no_std for common/telemetry/library-config, and
the FFE bounded submission.

Non-trivial changes made

No code changes required.

Identified libdatadog issues

None identified.

Flaky / ignored failures

• publish docker image for system tests (package-trigger, job
  2150241957). This release-stage job is defined in
  .gitlab/generate-package.php (around line 1799) and has
  allow_failure: true. It only publishes the already-built packages as an
  image to ghcr.io for system tests. It does not build or test any code
  that depends on libdatadog. Its script calls the GitHub API to look for an
  open PR on the branch and runs exit 3 when there is none (no
  allow_failure: exit_codes is set, so this counts as a script failure).
  It can also fail on ghcr.io login or push. The bot branch
  bot/libdatadog-latest most likely has no open PR, which would explain a
  failure that is deterministic and survives a retry. The job log was not in
  the artifacts, so I could not confirm the exact exit path. In any case the
  failure comes from CI/release infrastructure, not from libdatadog.

---

/cc @bwoebi

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[datadog-datadog-prod-us1]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 68.39% (-0.08%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 278672b | Docs | View more details | Give us feedback!}