Skip to content

libdatadog update to 98016adb#3944

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

libdatadog update to 98016adb#3944
dd-octo-sts[bot] wants to merge 1 commit into
masterfrom
bot/libdatadog-latest

Conversation

@dd-octo-sts
Copy link
Copy Markdown
Contributor

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

Summary

Automated update of the libdatadog submodule to the latest HEAD.

SHA
Previous 93e97238020b5cf1165b2583ec555d58307af3c1
New 98016adb6ea73454ea4804a3847724d7b215b677

Full 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:

98016adb6 chore(release): merge release branch to main (proposal for libdd-sampling (#2087)) (#2089)

The net diff this merge introduces to main touches no Rust source files
only version metadata:

Cargo.lock
libdd-data-pipeline/Cargo.toml
libdd-sampling/Cargo.toml         (-> 3.0.0)
libdd-sampling/CHANGELOG.md
libdd-trace-obfuscation/Cargo.toml
libdd-trace-stats/Cargo.toml
libdd-trace-utils/Cargo.toml
libdd-trace-utils/CHANGELOG.md
libdd-tracer-flare/Cargo.toml

These are crate version bumps (e.g. libdd-sampling 2.1.0 → 3.0.0) and
changelog 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 API
surface change, no signature change, and no behavioural change in this delta.

Sub-pipeline results:

Sub-pipeline Result
package-trigger ✅ success
appsec-trigger ✅ success
profiler-trigger ✅ success
shared-trigger ✅ success
tracer-trigger ❌ failed (3 test jobs, below)

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 compilation
failures). The three failures are all in the test stage, 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 .rs changes), so none of the
observed failures can originate from a libdatadog code change.

Flaky / ignored failures

All three failing jobs are in the tracer test stage and are unrelated to the
(metadata-only) libdatadog update:

  1. 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.

  2. 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).

  3. ASAN test_c with multiple observers: [8.4]failure_reason: script_failure after ~286s. This is the Linux ASAN variant of the C test
    suite 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.json metadata and a
    junit 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

@dd-octo-sts dd-octo-sts Bot requested review from a team as code owners June 3, 2026 05:22
@dd-octo-sts dd-octo-sts Bot requested review from sameerank and typotter and removed request for a team June 3, 2026 05:22
@datadog-prod-us1-6
Copy link
Copy Markdown

datadog-prod-us1-6 Bot commented Jun 3, 2026

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 6 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-php | ASAN test_c with multiple observers: [8.3]   View in Datadog   GitLab

DataDog/apm-reliability/dd-trace-php | ASAN test_c: [8.5, arm64]   View in Datadog   GitLab

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

View all 6 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

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

Useful? React with 👍 / 👎

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

@dd-octo-sts dd-octo-sts Bot changed the title libdatadog update to a1da9fc3 libdatadog update to 48da0d82 Jun 4, 2026
@dd-octo-sts dd-octo-sts Bot force-pushed the bot/libdatadog-latest branch 2 times, most recently from bbf5aea to 5c82d3b Compare June 5, 2026 05:10
@dd-octo-sts dd-octo-sts Bot changed the title libdatadog update to 48da0d82 libdatadog update to a76412cc Jun 5, 2026
@dd-octo-sts dd-octo-sts Bot changed the title libdatadog update to a76412cc libdatadog update to 98016adb Jun 6, 2026
@dd-octo-sts dd-octo-sts Bot force-pushed the bot/libdatadog-latest branch from 5c82d3b to c36e6cb Compare June 6, 2026 06:21
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