test(libdd-data-pipeline-ffi): remove redundant trace exporter builder tests by VianneyRuhlmann · Pull Request #2838 · DataDog/libdatadog

VianneyRuhlmann · 2026-11-09T19:44:00Z

What does this PR do?

Removes redundant tests from libdd-data-pipeline-ffi/src/trace_exporter/builder/tests.rs on top of #2689:

legacy_boolean_setters_still_support_disabling and legacy_exporter_new_does_not_consume_config (legacy config API).
exporter_send_check_rate_test, which duplicates exporter_send_empty_array_test (same build → send → rate-response path; the kept test also asserts request headers).
Imports left unused by these removals.

Motivation

Keep one test per behavior in the new builder FFI test suite.

Additional Notes

This branch is based on vianney/remove-config-in-ffi (#2689), so against main the diff also includes that PR's commits; the change specific to this PR is the last commit.

How to test the change?

Run locally:

cargo nextest run -p libdd-data-pipeline-ffi builder::: 20 passed.
cargo +stable clippy -p libdd-data-pipeline-ffi --all-targets -- -D warnings: clean.

…mirroring the Rust builder Add a ddog_trace_exporter_builder_* FFI that maps 1:1 onto TraceExporterBuilder, alongside the existing ddog_trace_exporter_config_* API which is now deprecated (Rust #[deprecated] plus a portable DDOG_TRACE_EXPORTER_DEPRECATED macro in the generated header; behavior unchanged). - enable-only setters for health metrics, stats and client-computed stats/headers; enable_stats takes a bucket interval in seconds - ddog_trace_exporter_builder_build consumes the builder, including on error - new C types: ddog_ExporterTelemetryConfig (2 fields), ddog_ExporterTagList, ddog_ExporterHeader(List) for Vec-based builder methods; telemetry enable and instrumentation sessions are separate bindings - parity: 47 of 48 builder methods bound (build_async is not representable; the 2 stats-obfuscation-gated ones are excluded because cbindgen does not evaluate #[cfg]) - migrate examples/ffi/trace_exporter.c to the builder API

…r tests

github-actions · 2026-11-09T19:46:07Z

📚 Documentation Check Results

⚠️ 1422 documentation warning(s) found

📦 `libdd-data-pipeline-ffi` - 1422 warning(s)

Updated: 2026-11-09 19:46:06 UTC | Commit: 7d843b2 | missing-docs job results

github-actions · 2026-11-09T19:47:44Z

🔒 Cargo Deny Results

⚠️ 5 issue(s) found, showing only errors (advisories, bans, sources)

📦 `libdd-data-pipeline-ffi` - 5 error(s)

Show output

info: syncing channel updates for 1.91.1-x86_64-unknown-linux-gnu
info: latest update on 2025-11-10 for version 1.91.1 (ed61e7d7e 2025-11-07)
info: downloading 6 components
warn: the missing active toolchain `1.91.1-x86_64-unknown-linux-gnu` has been auto-installed
warn: this might cause rustup commands to take longer time to finish than expected
info: you may opt out with `RUSTUP_AUTO_INSTALL=0` or `rustup set auto-install disable`
error[vulnerability]: TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:255:1
    │
255 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0285
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0285
    ├ Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
      when they followed a key-changing message in the same record. For example,
      a plaintext `EncryptedExtensions` message packed into the same record as the
      `ServerHello` was accepted.
      
      RFC 8446 section 5.1 requires that handshake messages do not span key changes,
      and that implementations terminate the connection with an "unexpected_message"
      alert if they do.
      
      The handshake transcript is still authenticated, so a network-position attacker
      cannot use this to alter or complete a handshake; the practical effect is that
      a peer could send handshake messages that should be encrypted in plaintext
      without rustls rejecting the connection.
      
      This is functionally the same bug as Go's
      [GO-2026-4340](https://pkg.go.dev/vuln/GO-2026-4340) (CVE-2025-61730).
    ├ Announcement: https://github.com/rustls/rustls/pull/3265
    ├ Solution: Upgrade to >=0.23.45 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v9.0.0
      │       ├── libdd-capabilities-impl v8.0.0
      │       │   ├── libdd-data-pipeline v13.0.0
      │       │   │   └── libdd-data-pipeline-ffi v48.0.0
      │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   ├── libdd-shared-runtime v7.0.0
      │       │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v9.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0
      │       │   │   │       └── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-telemetry v11.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v11.0.0 (*)
      │       │   ├── libdd-trace-stats v12.0.0 (*)
      │       │   └── libdd-trace-utils v15.0.0
      │       │       ├── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v4.0.0
      │       │       │   └── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v11.0.0
      │       │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v4.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       │   └── libdd-trace-stats v12.0.0 (*)
      │       │       ├── libdd-trace-stats v12.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v15.0.0 (*)
      │       ├── libdd-common-ffi v48.0.0
      │       │   └── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-data-pipeline v13.0.0 (*)
      │       ├── libdd-data-pipeline-core v4.0.0 (*)
      │       ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-dogstatsd-client v9.0.0 (*)
      │       ├── libdd-shared-runtime v7.0.0 (*)
      │       ├── libdd-telemetry v11.0.0 (*)
      │       ├── libdd-trace-obfuscation v11.0.0 (*)
      │       ├── libdd-trace-stats v12.0.0 (*)
      │       └── libdd-trace-utils v15.0.0 (*)
      ├── libdd-common v9.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v9.0.0 (*)
      └── tokio-rustls v0.26.0
          ├── hyper-rustls v0.27.7 (*)
          └── (dev) libdd-common v9.0.0 (*)

error[vulnerability]: `Debug` impls for client session values expose TLS secrets
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:255:1
    │
255 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0346
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0346
    ├ The `Debug` implementations of `Tls12ClientSessionValue` and
      `Tls13ClientSessionValue` were derived, and so included the TLS 1.2 master
      secret or TLS 1.3 resumption PSK in their output.
      
      Custom `ClientSessionStore` implementations that format these values with
      `Debug` (for example, when logging) could disclose these secrets to readers of
      the logs. This conflicts with rustls's
      [key-material redaction policy](https://github.com/rustls/rustls/blob/99f2358cae2954837dbb866faf6727de75489ab9/SECURITY.md#boundary-public-api).
      
      Ordinary connection and built-in session cache `Debug` output is redacted and
      is not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3299
    ├ Solution: Upgrade to >=0.23.46 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v9.0.0
      │       ├── libdd-capabilities-impl v8.0.0
      │       │   ├── libdd-data-pipeline v13.0.0
      │       │   │   └── libdd-data-pipeline-ffi v48.0.0
      │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   ├── libdd-shared-runtime v7.0.0
      │       │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v9.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0
      │       │   │   │       └── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-telemetry v11.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v11.0.0 (*)
      │       │   ├── libdd-trace-stats v12.0.0 (*)
      │       │   └── libdd-trace-utils v15.0.0
      │       │       ├── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v4.0.0
      │       │       │   └── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v11.0.0
      │       │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v4.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       │   └── libdd-trace-stats v12.0.0 (*)
      │       │       ├── libdd-trace-stats v12.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v15.0.0 (*)
      │       ├── libdd-common-ffi v48.0.0
      │       │   └── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-data-pipeline v13.0.0 (*)
      │       ├── libdd-data-pipeline-core v4.0.0 (*)
      │       ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-dogstatsd-client v9.0.0 (*)
      │       ├── libdd-shared-runtime v7.0.0 (*)
      │       ├── libdd-telemetry v11.0.0 (*)
      │       ├── libdd-trace-obfuscation v11.0.0 (*)
      │       ├── libdd-trace-stats v12.0.0 (*)
      │       └── libdd-trace-utils v15.0.0 (*)
      ├── libdd-common v9.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v9.0.0 (*)
      └── tokio-rustls v0.26.0
          ├── hyper-rustls v0.27.7 (*)
          └── (dev) libdd-common v9.0.0 (*)

error[vulnerability]: Brotli certificate decompression can allocate up to 1 GiB before authentication
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:255:1
    │
255 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0348
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0348
    ├ The built-in Brotli certificate decompressor (enabled by the non-default
      `brotli` crate feature) bounded the size of the decompressed output, but
      accepted a peer-selected history window. Brotli's large-window extension was
      enabled, so a five-byte header could cause an allocation of 1 GiB. A peer can
      abort a process whose allocator cannot satisfy that request.
      
      No trusted certificate is required by the attacker. Affected configurations are:
      
      - clients that enable the `brotli` feature and connect to a malicious server, and
      - servers that enable the `brotli` feature and request client certificates.
      
      Applications that do not enable the `brotli` feature are not affected.
    ├ Announcement: https://github.com/rustls/rustls/pull/3297
    ├ Solution: Upgrade to >=0.23.46 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v9.0.0
      │       ├── libdd-capabilities-impl v8.0.0
      │       │   ├── libdd-data-pipeline v13.0.0
      │       │   │   └── libdd-data-pipeline-ffi v48.0.0
      │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   ├── libdd-shared-runtime v7.0.0
      │       │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v9.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0
      │       │   │   │       └── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-telemetry v11.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v11.0.0 (*)
      │       │   ├── libdd-trace-stats v12.0.0 (*)
      │       │   └── libdd-trace-utils v15.0.0
      │       │       ├── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v4.0.0
      │       │       │   └── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v11.0.0
      │       │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v4.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       │   └── libdd-trace-stats v12.0.0 (*)
      │       │       ├── libdd-trace-stats v12.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v15.0.0 (*)
      │       ├── libdd-common-ffi v48.0.0
      │       │   └── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-data-pipeline v13.0.0 (*)
      │       ├── libdd-data-pipeline-core v4.0.0 (*)
      │       ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-dogstatsd-client v9.0.0 (*)
      │       ├── libdd-shared-runtime v7.0.0 (*)
      │       ├── libdd-telemetry v11.0.0 (*)
      │       ├── libdd-trace-obfuscation v11.0.0 (*)
      │       ├── libdd-trace-stats v12.0.0 (*)
      │       └── libdd-trace-utils v15.0.0 (*)
      ├── libdd-common v9.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v9.0.0 (*)
      └── tokio-rustls v0.26.0
          ├── hyper-rustls v0.27.7 (*)
          └── (dev) libdd-common v9.0.0 (*)

error[vulnerability]: Unauthenticated ServerHello can downgrade later connections to classical key exchange
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:255:1
    │
255 │ rustls 0.23.37 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0349
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0349
    ├ The client recorded the server-selected key exchange group for each server
      name when processing the ServerHello, before the server was authenticated.
      This record is used to predict which key share to send in future ClientHellos
      to that server name.
      
      A network attacker can answer one connection attempt with a ServerHello
      selecting X25519, and then close the connection. Later ClientHellos for that
      name carry only an X25519 key share, while `supported_groups` still lists
      X25519MLKEM768 first. If the genuine server accepts that share rather than
      sending a HelloRetryRequest for its preferred hybrid group, the handshake
      completes with classical-only key exchange and no error. This persists for as
      long as the entry stays in the client's session store.
      
      The impact is loss of post-quantum confidentiality for affected connections
      ("harvest now, decrypt later"). There is no key compromise and no
      authentication bypass.
      
      The following are not affected:
      
      - connections to servers which send a HelloRetryRequest for their preferred group,
      - clients with resumption disabled (as nothing is stored), and
      - other server names.
      
      This behaviour is discussed in
      [draft-ietf-tls-key-share-prediction](https://www.ietf.org/archive/id/draft-ietf-tls-key-share-prediction-01.html#name-security-considerations),
      so the practical impact depends largely on server policy.
    ├ Announcement: https://github.com/rustls/rustls/pull/3355
    ├ Solution: Upgrade to >=0.23.46 (try `cargo update -p rustls`)
    ├ rustls v0.23.37
      ├── hyper-rustls v0.27.7
      │   └── libdd-common v9.0.0
      │       ├── libdd-capabilities-impl v8.0.0
      │       │   ├── libdd-data-pipeline v13.0.0
      │       │   │   └── libdd-data-pipeline-ffi v48.0.0
      │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   ├── libdd-shared-runtime v7.0.0
      │       │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │   │   ├── libdd-dogstatsd-client v9.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0
      │       │   │   │       └── libdd-data-pipeline v13.0.0 (*)
      │       │   │   ├── libdd-telemetry v11.0.0
      │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │   │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   │   └── libdd-trace-stats v12.0.0 (*)
      │       │   ├── (dev) libdd-telemetry v11.0.0 (*)
      │       │   ├── libdd-trace-stats v12.0.0 (*)
      │       │   └── libdd-trace-utils v15.0.0
      │       │       ├── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── libdd-data-pipeline-core v4.0.0
      │       │       │   └── libdd-data-pipeline v13.0.0 (*)
      │       │       ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       ├── libdd-trace-obfuscation v11.0.0
      │       │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-core v4.0.0 (*)
      │       │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       │       │   └── libdd-trace-stats v12.0.0 (*)
      │       │       ├── libdd-trace-stats v12.0.0 (*)
      │       │       └── (dev) libdd-trace-utils v15.0.0 (*)
      │       ├── libdd-common-ffi v48.0.0
      │       │   └── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-data-pipeline v13.0.0 (*)
      │       ├── libdd-data-pipeline-core v4.0.0 (*)
      │       ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │       ├── libdd-dogstatsd-client v9.0.0 (*)
      │       ├── libdd-shared-runtime v7.0.0 (*)
      │       ├── libdd-telemetry v11.0.0 (*)
      │       ├── libdd-trace-obfuscation v11.0.0 (*)
      │       ├── libdd-trace-stats v12.0.0 (*)
      │       └── libdd-trace-utils v15.0.0 (*)
      ├── libdd-common v9.0.0 (*)
      ├── rustls-platform-verifier v0.6.2
      │   └── libdd-common v9.0.0 (*)
      └── tokio-rustls v0.26.0
          ├── hyper-rustls v0.27.7 (*)
          └── (dev) libdd-common v9.0.0 (*)

error[unsound]: `AsyncFd::new` and related constructors violate I/O safety
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:316:1
    │
316 │ tokio 1.49.0 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0386
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0386
    ├ `tokio::io::unix::AsyncFd` provides safe constructors (`new`, `with_interest`, `try_new`, and `try_with_interest`) that accept any `T: AsRawFd` rather than requiring proof of ownership or validity of the file descriptor. Because `RawFd` implements `AsRawFd`, safe code can construct an `AsyncFd` from an arbitrary or closed file descriptor, or close/replace the underlying file descriptor while the `AsyncFd` is still alive.
      
      This violates I/O safety in two ways:
      
      1. `AsyncFd<T>` implements `AsFd` for all `T: AsRawFd` by calling `BorrowedFd::borrow_raw(self.as_raw_fd())`, allowing safe code to obtain an arbitrary `BorrowedFd<'_>` without owning the file descriptor.
      2. Tokio's I/O driver stores a pointer to an internal allocation in the `epoll`/`kqueue` user data for registered file descriptors. If the underlying file descriptor is duplicated and then closed while an `AsyncFd` is alive, and the OS reuses that file descriptor number for a another IO resource on the same runtime, dropping the first `AsyncFd` deregisters the reused file descriptor number and frees the first while the original file description remains registered in `epoll`, leading to a use-after-free when a readiness event fires.
      
      Starting in Tokio 1.51.6, 1.53.3, and 1.54.0, `AsyncFd::new`, `AsyncFd::with_interest`, `AsyncFd::try_new`, and `AsyncFd::try_with_interest` are deprecated in favor of the `unsafe` constructors `AsyncFd::register` and `AsyncFd::register_with_interest`. Callers must ensure that the file descriptor remains valid, open, and unchanged for the lifetime of the `AsyncFd`.
    ├ Announcement: https://github.com/tokio-rs/tokio/pull/8587
    ├ Solution: Upgrade to >=1.51.6, <1.52.0 OR >=1.53.3 (try `cargo update -p tokio`)
    ├ tokio v1.49.0
      ├── h2 v0.4.19
      │   ├── hyper v1.11.1
      │   │   ├── httpmock v0.8.0-alpha.1
      │   │   │   ├── (dev) libdd-data-pipeline v13.0.0
      │   │   │   │   └── libdd-data-pipeline-ffi v48.0.0
      │   │   │   ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │   ├── (dev) libdd-telemetry v11.0.0
      │   │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v12.0.0
      │   │   │   │       └── libdd-data-pipeline v13.0.0 (*)
      │   │   │   ├── (dev) libdd-trace-stats v12.0.0 (*)
      │   │   │   └── libdd-trace-utils v15.0.0
      │   │   │       ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       ├── libdd-data-pipeline-core v4.0.0
      │   │   │       │   └── libdd-data-pipeline v13.0.0 (*)
      │   │   │       ├── (dev) libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       ├── libdd-trace-obfuscation v11.0.0
      │   │   │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       │   ├── libdd-data-pipeline-core v4.0.0 (*)
      │   │   │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       │   └── libdd-trace-stats v12.0.0 (*)
      │   │   │       ├── libdd-trace-stats v12.0.0 (*)
      │   │   │       └── (dev) libdd-trace-utils v15.0.0 (*)
      │   │   ├── hyper-rustls v0.27.7
      │   │   │   └── libdd-common v9.0.0
      │   │   │       ├── libdd-capabilities-impl v8.0.0
      │   │   │       │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       │   ├── libdd-shared-runtime v7.0.0
      │   │   │       │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       │   │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       │   │   ├── libdd-dogstatsd-client v9.0.0
      │   │   │       │   │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       │   │   │   └── libdd-trace-stats v12.0.0 (*)
      │   │   │       │   │   ├── libdd-telemetry v11.0.0 (*)
      │   │   │       │   │   └── libdd-trace-stats v12.0.0 (*)
      │   │   │       │   ├── (dev) libdd-telemetry v11.0.0 (*)
      │   │   │       │   ├── libdd-trace-stats v12.0.0 (*)
      │   │   │       │   └── libdd-trace-utils v15.0.0 (*)
      │   │   │       ├── libdd-common-ffi v48.0.0
      │   │   │       │   └── libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       ├── libdd-data-pipeline v13.0.0 (*)
      │   │   │       ├── libdd-data-pipeline-core v4.0.0 (*)
      │   │   │       ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │   │   │       ├── libdd-dogstatsd-client v9.0.0 (*)
      │   │   │       ├── libdd-shared-runtime v7.0.0 (*)
      │   │   │       ├── libdd-telemetry v11.0.0 (*)
      │   │   │       ├── libdd-trace-obfuscation v11.0.0 (*)
      │   │   │       ├── libdd-trace-stats v12.0.0 (*)
      │   │   │       └── libdd-trace-utils v15.0.0 (*)
      │   │   ├── hyper-util v0.1.17
      │   │   │   ├── httpmock v0.8.0-alpha.1 (*)
      │   │   │   ├── hyper-rustls v0.27.7 (*)
      │   │   │   ├── libdd-common v9.0.0 (*)
      │   │   │   └── libdd-data-pipeline v13.0.0 (*)
      │   │   ├── libdd-common v9.0.0 (*)
      │   │   ├── libdd-common-ffi v48.0.0 (*)
      │   │   ├── libdd-data-pipeline v13.0.0 (*)
      │   │   └── libdd-trace-utils v15.0.0 (*)
      │   └── (dev) libdd-data-pipeline v13.0.0 (*)
      ├── httpmock v0.8.0-alpha.1 (*)
      ├── hyper v1.11.1 (*)
      ├── hyper-rustls v0.27.7 (*)
      ├── hyper-util v0.1.17 (*)
      ├── (dev) libdd-capabilities-impl v8.0.0 (*)
      ├── libdd-common v9.0.0 (*)
      ├── (dev) libdd-data-pipeline v13.0.0 (*)
      ├── (dev) libdd-dogstatsd-client v9.0.0 (*)
      ├── libdd-shared-runtime v7.0.0 (*)
      ├── (dev) libdd-telemetry v11.0.0 (*)
      ├── (dev) libdd-trace-protobuf v5.1.1
      │   ├── libdd-data-pipeline v13.0.0 (*)
      │   ├── libdd-trace-normalization v4.3.0
      │   │   └── libdd-trace-utils v15.0.0 (*)
      │   ├── libdd-trace-obfuscation v11.0.0 (*)
      │   ├── libdd-trace-stats v12.0.0 (*)
      │   └── libdd-trace-utils v15.0.0 (*)
      ├── (dev) libdd-trace-stats v12.0.0 (*)
      ├── libdd-trace-utils v15.0.0 (*)
      ├── tokio-rustls v0.26.0
      │   ├── hyper-rustls v0.27.7 (*)
      │   └── (dev) libdd-common v9.0.0 (*)
      ├── tokio-stream v0.1.16
      │   └── tonic v0.14.2
      │       └── libdd-data-pipeline v13.0.0 (*)
      ├── tokio-util v0.7.12
      │   ├── h2 v0.4.19 (*)
      │   ├── libdd-data-pipeline v13.0.0 (*)
      │   ├── libdd-data-pipeline-ffi v48.0.0 (*)
      │   └── libdd-telemetry v11.0.0 (*)
      └── (dev) tools v48.0.0
          ├── (dev) libdd-common v9.0.0 (*)
          ├── (dev) libdd-telemetry v11.0.0 (*)
          └── (dev) libdd-trace-utils v15.0.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-11-09 19:47:43 UTC | Commit: 7d843b2 | dependency-check job results

pr-commenter · 2026-11-09T19:49:29Z

Benchmarks

Comparison

Candidate

Candidate benchmark details

Baseline

Baseline benchmark details

datadog-prod-us1-4 · 2026-11-09T19:53:18Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 85.46%
• Overall Coverage: 81.05% (-2.44%)

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: abd6db0 | Docs | View more details | Give us feedback!}

dd-octo-sts · 2026-11-09T20:15:54Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	96.62 MB	96.65 MB	+.02% (+29.19 KB) 🔍
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	9.08 MB	9.27 MB	+2.10% (+195.58 KB) ⚠️

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.29 MB	12.50 MB	+1.72% (+217.10 KB) ⚠️
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	107.97 MB	107.85 MB	--.11% (-125.35 KB) 💪

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	29.22 MB	29.81 MB	+2.00% (+600.50 KB) ⚠️
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	99.56 KB	116.98 KB	+17.49% (+17.41 KB) 🚨
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	193.12 MB	195.02 MB	+.98% (+1.90 MB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	821.45 MB	823.45 MB	+.24% (+2.00 MB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	9.81 MB	9.82 MB	+.12% (+13.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	99.56 KB	116.98 KB	+17.49% (+17.41 KB) 🚨
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	27.61 MB	27.89 MB	+1.01% (+288.00 KB) ⚠️
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	55.89 MB	56.26 MB	+.65% (+373.56 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	25.64 MB	26.24 MB	+2.32% (+611.00 KB) ⚠️
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	101.12 KB	118.76 KB	+17.44% (+17.63 KB) 🚨
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	198.73 MB	200.43 MB	+.85% (+1.69 MB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	807.68 MB	808.52 MB	+.10% (+853.69 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	7.60 MB	7.58 MB	--.23% (-18.50 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	101.12 KB	118.76 KB	+17.44% (+17.63 KB) 🚨
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	29.75 MB	30.01 MB	+.86% (+264.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	52.83 MB	53.10 MB	+.51% (+280.29 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	86.53 MB	87.19 MB	+.76% (+674.99 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	10.12 MB	10.11 MB	--.15% (-16.39 KB) 💪

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	102.44 MB	102.82 MB	+.36% (+387.58 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.37 MB	12.40 MB	+.18% (+23.72 KB) 🔍

VianneyRuhlmann added 2 commits October 19, 2026 14:44

test(libdd-data-pipeline-ffi): remove redundant trace exporter builde…

abd6db0

…r tests

github-actions Bot added the data-pipeline label Nov 9, 2026

Navigation Menu

Repository navigation

test(libdd-data-pipeline-ffi): remove redundant trace exporter builder tests - #2838

test(libdd-data-pipeline-ffi): remove redundant trace exporter builder tests#2838
VianneyRuhlmann wants to merge 2 commits into
mainfrom
vianney/remove-redundant-tests-from-pr-2689-d01731f9

VianneyRuhlmann commented Nov 9, 2026

Uh oh!

github-actions Bot commented Nov 9, 2026

Uh oh!

github-actions Bot commented Nov 9, 2026

Uh oh!

pr-commenter Bot commented Nov 9, 2026 •

edited

Loading

Uh oh!

datadog-prod-us1-4 Bot commented Nov 9, 2026

Uh oh!

dd-octo-sts Bot commented Nov 9, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

VianneyRuhlmann commented Nov 9, 2026

What does this PR do?

Motivation

Additional Notes

How to test the change?

Uh oh!

github-actions Bot commented Nov 9, 2026

📚 Documentation Check Results

📦 libdd-data-pipeline-ffi - 1422 warning(s)

Uh oh!

github-actions Bot commented Nov 9, 2026

🔒 Cargo Deny Results

📦 libdd-data-pipeline-ffi - 5 error(s)

Uh oh!

pr-commenter Bot commented Nov 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Comparison

Candidate

Baseline

Uh oh!

datadog-prod-us1-4 Bot commented Nov 9, 2026

Uh oh!

dd-octo-sts Bot commented Nov 9, 2026

Artifact Size Benchmark Report

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

📦 `libdd-data-pipeline-ffi` - 1422 warning(s)

📦 `libdd-data-pipeline-ffi` - 5 error(s)

pr-commenter Bot commented Nov 9, 2026 •

edited

Loading