chore(crashtracking): bump os_info crate to 3.14 by gyuheon0h · Pull Request #1507 · DataDog/libdatadog

gyuheon0h · 2026-02-03T21:44:38Z

What does this PR do?

This PR bumps the os_info crate used to compute the os info of the machine the crashing application is running on to the latest version. We have had issues where sometimes, customer application code returns an unknown os_info and this is a step towards diagnosing this issue.

This PR also adds a small unit test for coverage.

Additional Notes

3.7 was already pretty old; we should have bumped this sooner.

How to test the change?

Unit tests check for os_info. Bin tests also check for os_info

github-actions · 2026-02-03T21:45:51Z

📚 Documentation Check Results

⚠️ 996 documentation warning(s) found

📦 `libdd-crashtracker` - 996 warning(s)

Updated: 2026-02-03 23:50:44 UTC | Commit: 1e671f1 | missing-docs job results

github-actions · 2026-02-03T21:48:33Z

🔒 Cargo Deny Results

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

📦 `libdd-crashtracker` - 7 error(s)

Show output

error[vulnerability]: Integer overflow in `BytesMut::reserve`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:26:1
   │
26 │ bytes 1.8.0 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0007
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0007
   ├ In the unique reclaim path of `BytesMut::reserve`, the condition
     ```rs
     if v_capacity >= new_cap + offset
     ```
     uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB.
     
     This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.
     
     ## PoC
     
     ```rs
     use bytes::*;
     
     fn main() {
         let mut a = BytesMut::from(&b"hello world"[..]);
         let mut b = a.split_off(5);
     
         // Ensure b becomes the unique owner of the backing storage
         drop(a);
     
         // Trigger overflow in new_cap + offset inside reserve
         b.reserve(usize::MAX - 6);
     
         // This call relies on the corrupted cap and may cause UB & HBO
         b.put_u8(b'h');
     }
     ```
     
     # Workarounds
     
     Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.
   ├ Announcement: https://github.com/advisories/GHSA-434x-w66g-qw3r
   ├ Solution: Upgrade to >=1.11.1 (try `cargo update -p bytes`)
   ├ bytes v1.8.0
     ├── http v1.1.0
     │   ├── http-body v1.0.1
     │   │   ├── http-body-util v0.1.2
     │   │   │   ├── libdd-common v1.1.0
     │   │   │   │   ├── (build) libdd-crashtracker v1.0.0
     │   │   │   │   └── libdd-telemetry v2.0.0
     │   │   │   │       └── libdd-crashtracker v1.0.0 (*)
     │   │   │   └── libdd-telemetry v2.0.0 (*)
     │   │   ├── hyper v1.6.0
     │   │   │   ├── hyper-rustls v0.27.3
     │   │   │   │   └── libdd-common v1.1.0 (*)
     │   │   │   ├── hyper-util v0.1.17
     │   │   │   │   ├── hyper-rustls v0.27.3 (*)
     │   │   │   │   ├── libdd-common v1.1.0 (*)
     │   │   │   │   └── libdd-telemetry v2.0.0 (*)
     │   │   │   ├── libdd-common v1.1.0 (*)
     │   │   │   └── libdd-telemetry v2.0.0 (*)
     │   │   ├── hyper-util v0.1.17 (*)
     │   │   └── libdd-common v1.1.0 (*)
     │   ├── http-body-util v0.1.2 (*)
     │   ├── hyper v1.6.0 (*)
     │   ├── hyper-rustls v0.27.3 (*)
     │   ├── hyper-util v0.1.17 (*)
     │   ├── libdd-common v1.1.0 (*)
     │   ├── libdd-crashtracker v1.0.0 (*)
     │   └── libdd-telemetry v2.0.0 (*)
     ├── http-body v1.0.1 (*)
     ├── http-body-util v0.1.2 (*)
     ├── hyper v1.6.0 (*)
     ├── hyper-util v0.1.17 (*)
     ├── prost v0.14.3
     │   └── libdd-ddsketch v1.0.0
     │       └── libdd-telemetry v2.0.0 (*)
     ├── tokio v1.49.0
     │   ├── hyper v1.6.0 (*)
     │   ├── hyper-rustls v0.27.3 (*)
     │   ├── hyper-util v0.1.17 (*)
     │   ├── (dev) libdd-common v1.1.0 (*)
     │   ├── libdd-crashtracker v1.0.0 (*)
     │   ├── (dev) libdd-telemetry v2.0.0 (*)
     │   ├── tokio-rustls v0.26.0
     │   │   ├── hyper-rustls v0.27.3 (*)
     │   │   └── libdd-common v1.1.0 (*)
     │   └── tokio-util v0.7.12
     │       └── libdd-telemetry v2.0.0 (*)
     └── tokio-util v0.7.12 (*)

error[vulnerability]: Lenient `hyper` header parsing of `Content-Length` could allow request smuggling
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:93:1
   │
93 │ hyper 0.10.16 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2021-0078
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2021-0078
   ├ `hyper`'s HTTP header parser accepted, according to RFC 7230, illegal contents inside `Content-Length` headers.
     Due to this, upstream HTTP proxies that ignore the header may still forward them along if it chooses to ignore the error.
     
     To be vulnerable, `hyper` must be used as an HTTP/1 server and using an HTTP proxy upstream that ignores the header's contents
     but still forwards it. Due to all the factors that must line up, an attack exploiting this vulnerability is unlikely.
   ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c
   ├ Solution: Upgrade to >=0.14.10 (try `cargo update -p hyper`)
   ├ hyper v0.10.16
     ├── iron v0.6.1
     │   └── multipart v0.18.0
     │       └── (dev) libdd-common v1.1.0
     │           ├── (build) libdd-crashtracker v1.0.0
     │           └── libdd-telemetry v2.0.0
     │               └── libdd-crashtracker v1.0.0 (*)
     ├── multipart v0.18.0 (*)
     └── nickel v0.11.0
         └── multipart v0.18.0 (*)

error[vulnerability]: Integer overflow in `hyper`'s parsing of the `Transfer-Encoding` header leads to data loss
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:93:1
   │
93 │ hyper 0.10.16 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2021-0079
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2021-0079
   ├ When decoding chunk sizes that are too large, `hyper`'s code would encounter an integer overflow. Depending on the situation,
     this could lead to data loss from an incorrect total size, or in rarer cases, a request smuggling attack.
     
     To be vulnerable, you must be using `hyper` for any HTTP/1 purpose, including as a client or server, and consumers must send
     requests or responses that specify a chunk size greater than 18 exabytes. For a possible request smuggling attack to be possible,
     any upstream proxies must accept a chunk size greater than 64 bits.
   ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-5h46-h7hh-c6x9
   ├ Solution: Upgrade to >=0.14.10 (try `cargo update -p hyper`)
   ├ hyper v0.10.16
     ├── iron v0.6.1
     │   └── multipart v0.18.0
     │       └── (dev) libdd-common v1.1.0
     │           ├── (build) libdd-crashtracker v1.0.0
     │           └── libdd-telemetry v2.0.0
     │               └── libdd-crashtracker v1.0.0 (*)
     ├── multipart v0.18.0 (*)
     └── nickel v0.11.0
         └── multipart v0.18.0 (*)

error[vulnerability]: `idna` accepts Punycode labels that do not produce any non-ASCII when decoded
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:99:1
   │
99 │ idna 0.1.5 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2024-0421
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2024-0421
   ├ `idna` 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with `idna` 0.5.0 or earlier.
     
     Concretely, `example.org` and `xn--example-.org` become equal after processing by `idna` 0.5.0 or earlier. Also, `example.org.xn--` and `example.org.` become equal after processing by `idna` 0.5.0 or earlier.
     
     In applications using `idna` (but not in `idna` itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an `xn--`-masked name that turns into the name of the target when processed by `idna` 0.5.0 or earlier.
     
     ## Remedy
     
     Upgrade to `idna` 1.0.3 or later, if depending on `idna` directly, or to `url` 2.5.4 or later, if depending on `idna` via `url`. (This issue was fixed in `idna` 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)
     
     When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).
     
     If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an [issue](https://github.com/servo/rust-url/issues/992) about combining them with `url` 2.5.4 and `idna` 1.0.3.
     
     ## Additional information
     
     This issue resulted from `idna` 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in [revision 33 of UTS 46](https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).
     
     ## Acknowledgements
     
     Thanks to kageshiron for recognizing the security implications of this behavior.
   ├ Announcement: https://bugzilla.mozilla.org/show_bug.cgi?id=1887898
   ├ Solution: Upgrade to >=1.0.0 (try `cargo update -p idna`)
   ├ idna v0.1.5
     └── url v1.7.2
         ├── hyper v0.10.16
         │   ├── iron v0.6.1
         │   │   └── multipart v0.18.0
         │   │       └── (dev) libdd-common v1.1.0
         │   │           ├── (build) libdd-crashtracker v1.0.0
         │   │           └── libdd-telemetry v2.0.0
         │   │               └── libdd-crashtracker v1.0.0 (*)
         │   ├── multipart v0.18.0 (*)
         │   └── nickel v0.11.0
         │       └── multipart v0.18.0 (*)
         ├── iron v0.6.1 (*)
         ├── nickel v0.11.0 (*)
         └── tiny_http v0.6.4
             └── multipart v0.18.0 (*)

error[unmaintained]: multipart is Unmaintained
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:135:1
    │
135 │ multipart 0.18.0 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
    │
    ├ ID: RUSTSEC-2023-0050
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2023-0050
    ├ The `multipart` crate is unmaintained. The author has archived the github
      repository.
      
      Alternatives:
      
      - [multer](https://crates.io/crates/multer)
      - [multiparty](https://crates.io/crates/multiparty)
    ├ Solution: No safe upgrade is available!
    ├ multipart v0.18.0
      └── (dev) libdd-common v1.1.0
          ├── (build) libdd-crashtracker v1.0.0
          └── libdd-telemetry v2.0.0
              └── libdd-crashtracker v1.0.0 (*)

error[vulnerability]: Potential segfault in the time crate
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:250:1
    │
250 │ time 0.1.45 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2020-0071
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2020-0071
    ├ ### Impact
      
      The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.
      
      The affected functions from time 0.2.7 through 0.2.22 are:
      
      - `time::UtcOffset::local_offset_at`
      - `time::UtcOffset::try_local_offset_at`
      - `time::UtcOffset::current_local_offset`
      - `time::UtcOffset::try_current_local_offset`
      - `time::OffsetDateTime::now_local`
      - `time::OffsetDateTime::try_now_local`
      
      The affected functions in time 0.1 (all versions) are:
      
      - `time::at_utc`
      - `time::at`
      - `time::now`
      - `time::tzset`
      
      Non-Unix targets (including Windows and wasm) are unaffected.
      
      ### Patches
      
      Pending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.
      
      Users and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.
      
      Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.
      
      ### Workarounds
      
      A possible workaround for crates affected through the transitive dependency in `chrono`, is to avoid using the default `oldtime` feature dependency of the `chrono` crate by disabling its `default-features` and manually specifying the required features instead.
      
      #### Examples:
      
      `Cargo.toml`:  
      
      ```toml
      chrono = { version = "0.4", default-features = false, features = ["serde"] }
      ```
      
      ```toml
      chrono = { version = "0.4.22", default-features = false, features = ["clock"] }
      ```
      
      Commandline:  
      
      ```bash
      cargo add chrono --no-default-features -F clock
      ```
      
      Sources:  
       - [chronotope/chrono#602 (comment)](https://github.com/chronotope/chrono/issues/602#issuecomment-1242149249)  
       - [vityafx/serde-aux#21](https://github.com/vityafx/serde-aux/issues/21)
    ├ Announcement: https://github.com/time-rs/time/issues/293
    ├ Solution: Upgrade to >=0.2.23 (try `cargo update -p time`)
    ├ time v0.1.45
      ├── hyper v0.10.16
      │   ├── iron v0.6.1
      │   │   └── multipart v0.18.0
      │   │       └── (dev) libdd-common v1.1.0
      │   │           ├── (build) libdd-crashtracker v1.0.0
      │   │           └── libdd-telemetry v2.0.0
      │   │               └── libdd-crashtracker v1.0.0 (*)
      │   ├── multipart v0.18.0 (*)
      │   └── nickel v0.11.0
      │       └── multipart v0.18.0 (*)
      └── nickel v0.11.0 (*)

error[vulnerability]: Logging user input may result in poisoning logs with ANSI escape sequences
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:263:1
    │
263 │ tracing-subscriber 0.3.19 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2025-0055
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0055
    ├ Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:
      
      - Manipulate terminal title bars
      - Clear screens or modify terminal display
      - Potentially mislead users through terminal manipulation
      
      In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.
      
      This was patched in [PR #3368](https://github.com/tokio-rs/tracing/pull/3368) to escape ANSI control characters from user input.
    ├ Announcement: https://github.com/advisories/GHSA-xwfj-jgwm-7wp5
    ├ Solution: Upgrade to >=0.3.20 (try `cargo update -p tracing-subscriber`)
    ├ tracing-subscriber v0.3.19
      └── (dev) libdd-telemetry v2.0.0
          └── libdd-crashtracker v1.0.0

advisories FAILED, bans ok, sources ok

Updated: 2026-02-03 23:53:26 UTC | Commit: 1e671f1 | dependency-check job results

gyuheon0h · 2026-02-03T22:24:56Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-02-03T22:24:59Z

View all feedbacks in Devflow UI.

2026-02-03 22:24:59 UTC ℹ️ Start processing command /merge

2026-02-03 22:25:04 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

2026-02-03 23:14:46 UTC ⚠️ MergeQueue: This merge request was unqueued

gyuheon.oh@datadoghq.com unqueued this merge request

codecov-commenter · 2026-02-03T22:28:42Z

Codecov Report

❌ Patch coverage is 81.81818% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.07%. Comparing base (7986270) to head (b4f0923).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1507      +/-   ##
==========================================
+ Coverage   71.04%   71.07%   +0.02%     
==========================================
  Files         424      424              
  Lines       69307    69329      +22     
==========================================
+ Hits        49240    49276      +36     
+ Misses      20067    20053      -14

Components	Coverage Δ
libdd-crashtracker	`62.35% <81.81%> (+0.37%)`	⬆️
libdd-crashtracker-ffi	`16.80% <ø> (+2.68%)`	⬆️
libdd-alloc	`98.73% <ø> (ø)`
libdd-data-pipeline	`86.86% <ø> (ø)`
libdd-data-pipeline-ffi	`78.68% <ø> (ø)`
libdd-common	`80.53% <ø> (ø)`
libdd-common-ffi	`74.54% <ø> (ø)`
libdd-telemetry	`59.78% <ø> (-0.04%)`	⬇️
libdd-telemetry-ffi	`21.17% <ø> (ø)`
libdd-dogstatsd-client	`83.75% <ø> (ø)`
datadog-ipc	`82.70% <ø> (+0.10%)`	⬆️
libdd-profiling	`81.73% <ø> (-0.02%)`	⬇️
libdd-profiling-ffi	`64.71% <ø> (ø)`
datadog-sidecar	`34.38% <ø> (-0.33%)`	⬇️
datdog-sidecar-ffi	`7.67% <ø> (-1.48%)`	⬇️
spawn-worker	`55.18% <ø> (ø)`
libdd-tinybytes	`93.43% <ø> (ø)`
libdd-trace-normalization	`82.33% <ø> (ø)`
libdd-trace-obfuscation	`94.17% <ø> (ø)`
libdd-trace-protobuf	`61.18% <ø> (ø)`
libdd-trace-utils	`89.37% <ø> (ø)`
datadog-tracer-flare	`62.06% <ø> (ø)`
libdd-log	`75.57% <ø> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

pr-commenter · 2026-02-03T22:29:34Z

Benchmarks

Comparison

Benchmark execution time: 2026-02-03 23:35:22

Comparing candidate commit b4f0923 in PR branch gyuheon0h/os-info-bump with baseline commit 7986270 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 57 metrics, 2 unstable metrics.

Candidate

Candidate benchmark details

Group 1

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...	execution_time	205.865µs	206.402µs ± 0.285µs	206.383µs ± 0.196µs	206.593µs	206.861µs	207.061µs	207.430µs	0.51%	0.446	0.105	0.14%	0.020µs	1	200
normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...	throughput	4820898.412op/s	4844915.763op/s ± 6696.719op/s	4845370.160op/s ± 4615.523op/s	4849793.379op/s	4854995.840op/s	4857011.064op/s	4857542.076op/s	0.25%	-0.438	0.088	0.14%	473.530op/s	1	200
normalization/normalize_name/normalize_name/bad-name	execution_time	18.604µs	18.684µs ± 0.044µs	18.676µs ± 0.026µs	18.704µs	18.766µs	18.819µs	18.876µs	1.07%	1.157	1.934	0.24%	0.003µs	1	200
normalization/normalize_name/normalize_name/bad-name	throughput	52978110.612op/s	53521317.712op/s ± 126889.259op/s	53544996.402op/s ± 73741.664op/s	53610776.675op/s	53691810.193op/s	53722222.503op/s	53750461.206op/s	0.38%	-1.139	1.865	0.24%	8972.426op/s	1	200
normalization/normalize_name/normalize_name/good	execution_time	10.751µs	10.864µs ± 0.034µs	10.861µs ± 0.020µs	10.884µs	10.919µs	10.958µs	10.965µs	0.96%	0.164	0.661	0.31%	0.002µs	1	200
normalization/normalize_name/normalize_name/good	throughput	91197619.673op/s	92051173.871op/s ± 290202.366op/s	92073750.382op/s ± 172462.512op/s	92217689.405op/s	92503361.648op/s	92720389.842op/s	93013744.733op/s	1.02%	-0.139	0.659	0.31%	20520.406op/s	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...	execution_time	[206.363µs; 206.442µs] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...	throughput	[4843987.662op/s; 4845843.864op/s] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_name/normalize_name/bad-name	execution_time	[18.678µs; 18.690µs] or [-0.033%; +0.033%]	None	None	None
normalization/normalize_name/normalize_name/bad-name	throughput	[53503732.081op/s; 53538903.343op/s] or [-0.033%; +0.033%]	None	None	None
normalization/normalize_name/normalize_name/good	execution_time	[10.859µs; 10.868µs] or [-0.044%; +0.044%]	None	None	None
normalization/normalize_name/normalize_name/good	throughput	[92010954.615op/s; 92091393.128op/s] or [-0.044%; +0.044%]	None	None	None

Group 2

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
benching serializing traces from their internal representation to msgpack	execution_time	14.045ms	14.098ms ± 0.036ms	14.091ms ± 0.013ms	14.107ms	14.178ms	14.242ms	14.332ms	1.71%	2.806	11.926	0.25%	0.003ms	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
benching serializing traces from their internal representation to msgpack	execution_time	[14.093ms; 14.103ms] or [-0.035%; +0.035%]	None	None	None

Group 3

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
sql/obfuscate_sql_string	execution_time	85.234µs	85.521µs ± 0.223µs	85.490µs ± 0.062µs	85.559µs	85.692µs	85.862µs	87.860µs	2.77%	7.152	66.910	0.26%	0.016µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
sql/obfuscate_sql_string	execution_time	[85.491µs; 85.552µs] or [-0.036%; +0.036%]	None	None	None

Group 4

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
credit_card/is_card_number/	execution_time	3.892µs	3.912µs ± 0.003µs	3.912µs ± 0.001µs	3.914µs	3.917µs	3.918µs	3.920µs	0.21%	-1.467	13.869	0.07%	0.000µs	1	200
credit_card/is_card_number/	throughput	255099623.037op/s	255605968.305op/s ± 177491.975op/s	255630596.304op/s ± 87601.919op/s	255705369.813op/s	255808283.647op/s	255851631.496op/s	256923547.008op/s	0.51%	1.496	14.100	0.07%	12550.578op/s	1	200
credit_card/is_card_number/ 3782-8224-6310-005	execution_time	77.053µs	77.554µs ± 0.453µs	77.430µs ± 0.265µs	77.733µs	78.544µs	78.833µs	79.304µs	2.42%	1.277	1.303	0.58%	0.032µs	1	200
credit_card/is_card_number/ 3782-8224-6310-005	throughput	12609681.009op/s	12894642.990op/s ± 74749.341op/s	12914943.235op/s ± 44183.894op/s	12957428.294op/s	12968001.478op/s	12973723.339op/s	12978002.989op/s	0.49%	-1.248	1.195	0.58%	5285.577op/s	1	200
credit_card/is_card_number/ 378282246310005	execution_time	70.632µs	70.965µs ± 0.407µs	70.786µs ± 0.101µs	71.051µs	71.780µs	72.558µs	72.947µs	3.05%	2.389	6.327	0.57%	0.029µs	1	200
credit_card/is_card_number/ 378282246310005	throughput	13708573.614op/s	14091931.884op/s ± 79666.107op/s	14127143.189op/s ± 20250.580op/s	14141788.278op/s	14150166.234op/s	14156582.800op/s	14157857.500op/s	0.22%	-2.345	6.063	0.56%	5633.244op/s	1	200
credit_card/is_card_number/37828224631	execution_time	3.896µs	3.913µs ± 0.003µs	3.913µs ± 0.002µs	3.914µs	3.918µs	3.920µs	3.921µs	0.22%	-0.606	7.309	0.07%	0.000µs	1	200
credit_card/is_card_number/37828224631	throughput	255010339.592op/s	255558897.317op/s ± 180644.545op/s	255574736.438op/s ± 99038.452op/s	255660124.879op/s	255800975.152op/s	255867495.650op/s	256696092.314op/s	0.44%	0.625	7.416	0.07%	12773.498op/s	1	200
credit_card/is_card_number/378282246310005	execution_time	67.421µs	67.708µs ± 0.321µs	67.568µs ± 0.073µs	67.820µs	68.368µs	69.012µs	69.255µs	2.50%	2.355	6.333	0.47%	0.023µs	1	200
credit_card/is_card_number/378282246310005	throughput	14439423.059op/s	14769575.286op/s ± 69310.602op/s	14799982.241op/s ± 15980.481op/s	14811614.158op/s	14823490.564op/s	14830314.335op/s	14832257.193op/s	0.22%	-2.316	6.092	0.47%	4901.000op/s	1	200
credit_card/is_card_number/37828224631000521389798	execution_time	44.787µs	45.184µs ± 0.146µs	45.203µs ± 0.111µs	45.308µs	45.388µs	45.457µs	45.469µs	0.59%	-0.305	-0.620	0.32%	0.010µs	1	200
credit_card/is_card_number/37828224631000521389798	throughput	21992912.536op/s	22131784.655op/s ± 71708.329op/s	22122349.448op/s ± 54446.025op/s	22189522.662op/s	22254404.129op/s	22296751.776op/s	22327932.354op/s	0.93%	0.317	-0.608	0.32%	5070.545op/s	1	200
credit_card/is_card_number/x371413321323331	execution_time	6.029µs	6.038µs ± 0.013µs	6.036µs ± 0.002µs	6.038µs	6.043µs	6.107µs	6.111µs	1.24%	4.665	21.499	0.21%	0.001µs	1	200
credit_card/is_card_number/x371413321323331	throughput	163649326.653op/s	165620084.115op/s ± 352159.375op/s	165682868.391op/s ± 57431.362op/s	165740747.364op/s	165811103.401op/s	165848740.448op/s	165865019.108op/s	0.11%	-4.654	21.415	0.21%	24901.428op/s	1	200
credit_card/is_card_number_no_luhn/	execution_time	3.892µs	3.912µs ± 0.003µs	3.912µs ± 0.001µs	3.914µs	3.916µs	3.918µs	3.919µs	0.17%	-2.103	18.805	0.07%	0.000µs	1	200
credit_card/is_card_number_no_luhn/	throughput	255196203.048op/s	255602120.072op/s ± 170561.020op/s	255621178.226op/s ± 86892.630op/s	255695994.669op/s	255791226.974op/s	255844488.332op/s	256965824.752op/s	0.53%	2.136	19.106	0.07%	12060.485op/s	1	200
credit_card/is_card_number_no_luhn/ 3782-8224-6310-005	execution_time	65.172µs	65.774µs ± 0.084µs	65.786µs ± 0.048µs	65.831µs	65.877µs	65.911µs	65.923µs	0.21%	-2.448	13.404	0.13%	0.006µs	1	200
credit_card/is_card_number_no_luhn/ 3782-8224-6310-005	throughput	15169138.388op/s	15203563.166op/s ± 19482.408op/s	15200832.246op/s ± 11059.651op/s	15212637.139op/s	15232307.041op/s	15254599.729op/s	15343986.434op/s	0.94%	2.484	13.725	0.13%	1377.614op/s	1	200
credit_card/is_card_number_no_luhn/ 378282246310005	execution_time	52.966µs	53.047µs ± 0.037µs	53.047µs ± 0.027µs	53.071µs	53.109µs	53.129µs	53.147µs	0.19%	0.219	-0.496	0.07%	0.003µs	1	200
credit_card/is_card_number_no_luhn/ 378282246310005	throughput	18815759.961op/s	18851207.921op/s ± 13125.406op/s	18851378.526op/s ± 9756.465op/s	18861901.788op/s	18870836.820op/s	18878214.786op/s	18880141.867op/s	0.15%	-0.216	-0.498	0.07%	928.106op/s	1	200
credit_card/is_card_number_no_luhn/37828224631	execution_time	3.893µs	3.914µs ± 0.003µs	3.915µs ± 0.002µs	3.916µs	3.918µs	3.919µs	3.920µs	0.14%	-2.112	13.713	0.07%	0.000µs	1	200
credit_card/is_card_number_no_luhn/37828224631	throughput	255087325.493op/s	255471211.254op/s ± 183648.957op/s	255444523.691op/s ± 108931.973op/s	255571778.491op/s	255742282.221op/s	255852714.428op/s	256839946.208op/s	0.55%	2.136	13.936	0.07%	12985.942op/s	1	200
credit_card/is_card_number_no_luhn/378282246310005	execution_time	49.753µs	49.805µs ± 0.027µs	49.802µs ± 0.018µs	49.822µs	49.852µs	49.876µs	49.884µs	0.16%	0.409	-0.050	0.05%	0.002µs	1	200
credit_card/is_card_number_no_luhn/378282246310005	throughput	20046553.883op/s	20078183.001op/s ± 10724.862op/s	20079409.570op/s ± 7079.253op/s	20085678.911op/s	20095167.815op/s	20098502.662op/s	20099127.698op/s	0.10%	-0.407	-0.053	0.05%	758.362op/s	1	200
credit_card/is_card_number_no_luhn/37828224631000521389798	execution_time	44.821µs	45.184µs ± 0.151µs	45.192µs ± 0.105µs	45.295µs	45.417µs	45.501µs	45.514µs	0.71%	-0.157	-0.431	0.33%	0.011µs	1	200
credit_card/is_card_number_no_luhn/37828224631000521389798	throughput	21971233.322op/s	22132112.920op/s ± 73960.134op/s	22127576.444op/s ± 51173.394op/s	22179506.739op/s	22266214.601op/s	22299476.624op/s	22310826.801op/s	0.83%	0.172	-0.423	0.33%	5229.771op/s	1	200
credit_card/is_card_number_no_luhn/x371413321323331	execution_time	6.029µs	6.038µs ± 0.015µs	6.036µs ± 0.003µs	6.039µs	6.046µs	6.108µs	6.176µs	2.32%	5.807	39.065	0.25%	0.001µs	1	200
credit_card/is_card_number_no_luhn/x371413321323331	throughput	161929630.484op/s	165606903.932op/s ± 416305.494op/s	165683075.474op/s ± 81249.373op/s	165761916.223op/s	165823124.504op/s	165858966.709op/s	165875579.301op/s	0.12%	-5.751	38.271	0.25%	29437.244op/s	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
credit_card/is_card_number/	execution_time	[3.912µs; 3.913µs] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number/	throughput	[255581369.624op/s; 255630566.986op/s] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number/ 3782-8224-6310-005	execution_time	[77.491µs; 77.617µs] or [-0.081%; +0.081%]	None	None	None
credit_card/is_card_number/ 3782-8224-6310-005	throughput	[12884283.450op/s; 12905002.530op/s] or [-0.080%; +0.080%]	None	None	None
credit_card/is_card_number/ 378282246310005	execution_time	[70.909µs; 71.021µs] or [-0.079%; +0.079%]	None	None	None
credit_card/is_card_number/ 378282246310005	throughput	[14080890.927op/s; 14102972.840op/s] or [-0.078%; +0.078%]	None	None	None
credit_card/is_card_number/37828224631	execution_time	[3.913µs; 3.913µs] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number/37828224631	throughput	[255533861.720op/s; 255583932.913op/s] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number/378282246310005	execution_time	[67.664µs; 67.753µs] or [-0.066%; +0.066%]	None	None	None
credit_card/is_card_number/378282246310005	throughput	[14759969.503op/s; 14779181.069op/s] or [-0.065%; +0.065%]	None	None	None
credit_card/is_card_number/37828224631000521389798	execution_time	[45.164µs; 45.205µs] or [-0.045%; +0.045%]	None	None	None
credit_card/is_card_number/37828224631000521389798	throughput	[22121846.570op/s; 22141722.739op/s] or [-0.045%; +0.045%]	None	None	None
credit_card/is_card_number/x371413321323331	execution_time	[6.036µs; 6.040µs] or [-0.030%; +0.030%]	None	None	None
credit_card/is_card_number/x371413321323331	throughput	[165571278.213op/s; 165668890.018op/s] or [-0.029%; +0.029%]	None	None	None
credit_card/is_card_number_no_luhn/	execution_time	[3.912µs; 3.913µs] or [-0.009%; +0.009%]	None	None	None
credit_card/is_card_number_no_luhn/	throughput	[255578481.955op/s; 255625758.189op/s] or [-0.009%; +0.009%]	None	None	None
credit_card/is_card_number_no_luhn/ 3782-8224-6310-005	execution_time	[65.763µs; 65.786µs] or [-0.018%; +0.018%]	None	None	None
credit_card/is_card_number_no_luhn/ 3782-8224-6310-005	throughput	[15200863.091op/s; 15206263.240op/s] or [-0.018%; +0.018%]	None	None	None
credit_card/is_card_number_no_luhn/ 378282246310005	execution_time	[53.042µs; 53.052µs] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number_no_luhn/ 378282246310005	throughput	[18849388.867op/s; 18853026.976op/s] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number_no_luhn/37828224631	execution_time	[3.914µs; 3.915µs] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number_no_luhn/37828224631	throughput	[255445759.275op/s; 255496663.234op/s] or [-0.010%; +0.010%]	None	None	None
credit_card/is_card_number_no_luhn/378282246310005	execution_time	[49.802µs; 49.809µs] or [-0.007%; +0.007%]	None	None	None
credit_card/is_card_number_no_luhn/378282246310005	throughput	[20076696.639op/s; 20079669.364op/s] or [-0.007%; +0.007%]	None	None	None
credit_card/is_card_number_no_luhn/37828224631000521389798	execution_time	[45.163µs; 45.205µs] or [-0.046%; +0.046%]	None	None	None
credit_card/is_card_number_no_luhn/37828224631000521389798	throughput	[22121862.756op/s; 22142363.083op/s] or [-0.046%; +0.046%]	None	None	None
credit_card/is_card_number_no_luhn/x371413321323331	execution_time	[6.036µs; 6.041µs] or [-0.035%; +0.035%]	None	None	None
credit_card/is_card_number_no_luhn/x371413321323331	throughput	[165549207.994op/s; 165664599.869op/s] or [-0.035%; +0.035%]	None	None	None

Group 5

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
profile_add_sample2_frames_x1000	execution_time	531.424µs	532.165µs ± 0.380µs	532.105µs ± 0.194µs	532.301µs	532.893µs	533.148µs	534.391µs	0.43%	1.598	5.477	0.07%	0.027µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
profile_add_sample2_frames_x1000	execution_time	[532.113µs; 532.218µs] or [-0.010%; +0.010%]	None	None	None

Group 6

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
redis/obfuscate_redis_string	execution_time	33.614µs	34.188µs ± 0.984µs	33.734µs ± 0.042µs	33.805µs	36.301µs	36.380µs	37.095µs	9.96%	1.703	0.973	2.87%	0.070µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
redis/obfuscate_redis_string	execution_time	[34.052µs; 34.324µs] or [-0.399%; +0.399%]	None	None	None

Group 7

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
concentrator/add_spans_to_concentrator	execution_time	10.600ms	10.638ms ± 0.015ms	10.636ms ± 0.009ms	10.646ms	10.664ms	10.683ms	10.702ms	0.62%	0.936	1.891	0.14%	0.001ms	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
concentrator/add_spans_to_concentrator	execution_time	[10.636ms; 10.640ms] or [-0.020%; +0.020%]	None	None	None

Group 8

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
two way interface	execution_time	17.905µs	26.080µs ± 9.412µs	18.298µs ± 0.259µs	34.054µs	43.628µs	44.564µs	58.118µs	217.62%	0.678	-0.625	36.00%	0.665µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
two way interface	execution_time	[24.775µs; 27.384µs] or [-5.001%; +5.001%]	None	None	None

Group 9

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
profile_add_sample_frames_x1000	execution_time	3.981ms	3.986ms ± 0.007ms	3.985ms ± 0.001ms	3.987ms	3.989ms	3.992ms	4.072ms	2.19%	11.407	147.028	0.16%	0.000ms	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
profile_add_sample_frames_x1000	execution_time	[3.985ms; 3.986ms] or [-0.023%; +0.023%]	None	None	None

Group 10

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
ip_address/quantize_peer_ip_address_benchmark	execution_time	4.986µs	5.064µs ± 0.052µs	5.066µs ± 0.057µs	5.094µs	5.144µs	5.151µs	5.154µs	1.73%	0.196	-1.263	1.02%	0.004µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
ip_address/quantize_peer_ip_address_benchmark	execution_time	[5.057µs; 5.071µs] or [-0.142%; +0.142%]	None	None	None

Group 11

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
receiver_entry_point/report/2597	execution_time	9.650ms	9.898ms ± 0.073ms	9.896ms ± 0.042ms	9.938ms	10.012ms	10.108ms	10.128ms	2.35%	0.042	1.315	0.74%	0.005ms	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
receiver_entry_point/report/2597	execution_time	[9.888ms; 9.908ms] or [-0.102%; +0.102%]	None	None	None

Group 12

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
single_flag_killswitch/rules-based	execution_time	189.048ns	192.755ns ± 2.530ns	192.267ns ± 1.582ns	193.899ns	197.886ns	199.909ns	201.704ns	4.91%	1.024	0.677	1.31%	0.179ns	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
single_flag_killswitch/rules-based	execution_time	[192.404ns; 193.106ns] or [-0.182%; +0.182%]	None	None	None

Group 13

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...	execution_time	535.134µs	536.950µs ± 1.499µs	536.381µs ± 0.572µs	537.524µs	539.695µs	541.593µs	544.666µs	1.54%	1.845	4.272	0.28%	0.106µs	1	200
normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...	throughput	1835985.973op/s	1862384.627op/s ± 5174.106op/s	1864347.550op/s ± 1991.008op/s	1865868.068op/s	1867267.006op/s	1868157.454op/s	1868690.422op/s	0.23%	-1.821	4.130	0.28%	365.865op/s	1	200
normalization/normalize_service/normalize_service/Data🐨dog🐶 繋がっ⛰てて	execution_time	380.258µs	382.099µs ± 0.535µs	382.194µs ± 0.193µs	382.385µs	382.673µs	383.028µs	383.722µs	0.40%	-1.519	3.052	0.14%	0.038µs	1	200
normalization/normalize_service/normalize_service/Data🐨dog🐶 繋がっ⛰てて	throughput	2606053.636op/s	2617124.953op/s ± 3670.831op/s	2616475.090op/s ± 1317.180op/s	2617746.971op/s	2626265.074op/s	2628770.416op/s	2629790.449op/s	0.51%	1.530	3.070	0.14%	259.567op/s	1	200
normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters	execution_time	189.605µs	190.071µs ± 0.202µs	190.060µs ± 0.151µs	190.217µs	190.414µs	190.521µs	190.562µs	0.26%	0.088	-0.461	0.11%	0.014µs	1	200
normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters	throughput	5247643.001op/s	5261189.152op/s ± 5596.124op/s	5261508.082op/s ± 4186.551op/s	5265294.036op/s	5270629.777op/s	5273060.903op/s	5274116.099op/s	0.24%	-0.083	-0.462	0.11%	395.706op/s	1	200
normalization/normalize_service/normalize_service/[empty string]	execution_time	36.473µs	36.589µs ± 0.049µs	36.589µs ± 0.035µs	36.623µs	36.673µs	36.706µs	36.745µs	0.42%	0.237	0.159	0.13%	0.003µs	1	200
normalization/normalize_service/normalize_service/[empty string]	throughput	27214873.576op/s	27330864.911op/s ± 36750.354op/s	27330480.660op/s ± 25850.310op/s	27356837.346op/s	27390436.565op/s	27406982.289op/s	27417617.810op/s	0.32%	-0.229	0.149	0.13%	2598.642op/s	1	200
normalization/normalize_service/normalize_service/test_ASCII	execution_time	45.924µs	46.037µs ± 0.115µs	46.027µs ± 0.028µs	46.057µs	46.114µs	46.153µs	47.534µs	3.27%	11.145	142.733	0.25%	0.008µs	1	200
normalization/normalize_service/normalize_service/test_ASCII	throughput	21037563.270op/s	21721941.134op/s ± 52759.580op/s	21726522.230op/s ± 13308.928op/s	21738828.507op/s	21756858.337op/s	21767466.632op/s	21775196.261op/s	0.22%	-10.991	140.061	0.24%	3730.666op/s	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...	execution_time	[536.742µs; 537.158µs] or [-0.039%; +0.039%]	None	None	None
normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...	throughput	[1861667.546op/s; 1863101.708op/s] or [-0.039%; +0.039%]	None	None	None
normalization/normalize_service/normalize_service/Data🐨dog🐶 繋がっ⛰てて	execution_time	[382.025µs; 382.174µs] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_service/normalize_service/Data🐨dog🐶 繋がっ⛰てて	throughput	[2616616.211op/s; 2617633.695op/s] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters	execution_time	[190.043µs; 190.099µs] or [-0.015%; +0.015%]	None	None	None
normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters	throughput	[5260413.583op/s; 5261964.721op/s] or [-0.015%; +0.015%]	None	None	None
normalization/normalize_service/normalize_service/[empty string]	execution_time	[36.582µs; 36.596µs] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_service/normalize_service/[empty string]	throughput	[27325771.666op/s; 27335958.157op/s] or [-0.019%; +0.019%]	None	None	None
normalization/normalize_service/normalize_service/test_ASCII	execution_time	[46.021µs; 46.053µs] or [-0.035%; +0.035%]	None	None	None
normalization/normalize_service/normalize_service/test_ASCII	throughput	[21714629.164op/s; 21729253.105op/s] or [-0.034%; +0.034%]	None	None	None

Group 14

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
normalization/normalize_trace/test_trace	execution_time	240.806ns	254.213ns ± 14.749ns	246.951ns ± 4.222ns	267.872ns	287.889ns	290.513ns	290.807ns	17.76%	1.124	-0.138	5.79%	1.043ns	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
normalization/normalize_trace/test_trace	execution_time	[252.169ns; 256.257ns] or [-0.804%; +0.804%]	None	None	None

Group 15

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
benching deserializing traces from msgpack to their internal representation	execution_time	48.091ms	48.333ms ± 1.200ms	48.165ms ± 0.039ms	48.211ms	48.341ms	54.960ms	60.186ms	24.96%	8.322	70.825	2.48%	0.085ms	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
benching deserializing traces from msgpack to their internal representation	execution_time	[48.167ms; 48.499ms] or [-0.344%; +0.344%]	None	None	None

Group 16

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
write only interface	execution_time	1.246µs	3.223µs ± 1.415µs	3.008µs ± 0.034µs	3.038µs	3.672µs	13.928µs	14.658µs	387.31%	7.303	54.650	43.79%	0.100µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
write only interface	execution_time	[3.027µs; 3.419µs] or [-6.085%; +6.085%]	None	None	None

Group 17

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
tags/replace_trace_tags	execution_time	2.433µs	2.458µs ± 0.024µs	2.452µs ± 0.007µs	2.461µs	2.508µs	2.512µs	2.685µs	9.51%	4.674	35.978	0.99%	0.002µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
tags/replace_trace_tags	execution_time	[2.455µs; 2.462µs] or [-0.138%; +0.138%]	None	None	None

Group 18

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
sdk_test_data/rules-based	execution_time	143.876µs	146.203µs ± 1.663µs	145.998µs ± 0.546µs	146.543µs	147.800µs	152.138µs	161.966µs	10.94%	5.249	41.826	1.13%	0.118µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
sdk_test_data/rules-based	execution_time	[145.973µs; 146.434µs] or [-0.158%; +0.158%]	None	None	None

Group 19

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`b4f0923`	1770160750	gyuheon0h/os-info-bump

scenario	metric	min	mean ± sd	median ± mad	p75	p95	p99	max	peak_to_median_ratio	skewness	kurtosis	cv	sem	runs	sample_size
benching string interning on wordpress profile	execution_time	160.671µs	161.317µs ± 0.991µs	161.177µs ± 0.173µs	161.394µs	161.865µs	162.388µs	174.431µs	8.22%	11.720	151.762	0.61%	0.070µs	1	200

scenario	metric	95% CI mean	Shapiro-Wilk pvalue	Ljung-Box pvalue (lag=1)	Dip test pvalue
benching string interning on wordpress profile	execution_time	[161.180µs; 161.455µs] or [-0.085%; +0.085%]	None	None	None

Baseline

Omitted due to size.

gyuheon0h · 2026-02-03T23:14:38Z

/remove

gh-worker-devflow-routing-ef8351 · 2026-02-03T23:14:40Z

View all feedbacks in Devflow UI.

2026-02-03 23:14:40 UTC ℹ️ Start processing command /remove

2026-02-03 23:14:43 UTC ℹ️ Devflow: /remove

gyuheon0h · 2026-02-03T23:14:42Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-02-03T23:14:46Z

View all feedbacks in Devflow UI.

2026-02-03 23:14:46 UTC ℹ️ Start processing command /merge

2026-02-03 23:14:52 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals. View in MergeQueue UI.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

2026-02-03 23:49:21 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 33m (p90).

2026-02-04 00:18:57 UTC ℹ️ MergeQueue: This merge request was merged

# Release proposal for libdd-crashtracker and its dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-crashtracker **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v2.0.0` ### Commits - chore(crashtracking): add tag for target triple (#1741) - refactor(libdd-crashtracker)!: avoid leaking Endpoint through the public API (#1705) - chore(cargo): bump to 29.0.0 (#1702) - fix(crashtracking): use libunwind to unwind frames (#1663) - chore(deps): bump blazesym to 0.2.3 and blazesym-c to 0.1.7 (#1654) - chore(ci): fix crashtracker receiver binary rpath setting (#1652) - chore(crashtracking): emit a best effort stacktrace for Mac (#1645) - chore(crashtracker): use default-features=false for aws-lc-sys (#1625) - feat(crashtracking): report unhandled exceptions (#1596) - refactor(ddcommon)!: remove direct dependency on hyper client everywhere in common (#1604) - feat(crashtracking): include `Kind` in crash ping and clarify requirements (#1595) - fix(crashtracking): add process_tags to application field (#1576) - ci: update nightly in CI to 2026-02-08 (#1539) - fix(telemetry)!: fix logs payload format [APMSP-2590] (#1498) - chore(crashtracking): bump os_info crate to 3.14 (#1507) - Don't bail (#1494) - feat(crashtracking)!: emit crashing thread name in crash report for linux crashes (#1485) - test(crashtracking): add minimal LD preload test for crashtracker collector (#1428) - chore: release libddcommon-v1.1.0 (#1456) - chore: prepare libdd-telemetry-v2.0.0 (#1457) - [crashtracker] Retrieve panic message when crashing (#1361) - fix(sidecar): AWS lambda also can return EACCESS for shm_open (#1446) - chore(crashtracking): add `is_crash_debug` tag to crashtracker receiver debug logs (#1445) - [crashtracker] Log errors in crashtracker receiver (#1395) - chore: add changelog for every published crate (#1396) - Fix CI (#1389) - [crashtracker] Set OS info in the crash info builder when receiving report (#1388) - crashtracker: support cxx bindings for crashinfo (#1379) [APMSP-2590]: https://datadoghq.atlassian.net/browse/APMSP-2590?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com>

# Release proposal for libdd-crashtracker and its dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-crashtracker **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v2.0.0` ### Commits - chore(ci): give libdd-libunwind-sys its own version (#1743) - chore(crashtracking): add tag for target triple (#1741) - refactor(libdd-crashtracker)!: avoid leaking Endpoint through the public API (#1705) - chore(cargo): bump to 29.0.0 (#1702) - fix(crashtracking): use libunwind to unwind frames (#1663) - chore(deps): bump blazesym to 0.2.3 and blazesym-c to 0.1.7 (#1654) - chore(ci): fix crashtracker receiver binary rpath setting (#1652) - chore(crashtracking): emit a best effort stacktrace for Mac (#1645) - chore(crashtracker): use default-features=false for aws-lc-sys (#1625) - feat(crashtracking): report unhandled exceptions (#1596) - refactor(ddcommon)!: remove direct dependency on hyper client everywhere in common (#1604) - feat(crashtracking): include `Kind` in crash ping and clarify requirements (#1595) - fix(crashtracking): add process_tags to application field (#1576) - ci: update nightly in CI to 2026-02-08 (#1539) - fix(telemetry)!: fix logs payload format [APMSP-2590] (#1498) - chore(crashtracking): bump os_info crate to 3.14 (#1507) - Don't bail (#1494) - feat(crashtracking)!: emit crashing thread name in crash report for linux crashes (#1485) - test(crashtracking): add minimal LD preload test for crashtracker collector (#1428) - chore: release libddcommon-v1.1.0 (#1456) - chore: prepare libdd-telemetry-v2.0.0 (#1457) - [crashtracker] Retrieve panic message when crashing (#1361) - fix(sidecar): AWS lambda also can return EACCESS for shm_open (#1446) - chore(crashtracking): add `is_crash_debug` tag to crashtracker receiver debug logs (#1445) - [crashtracker] Log errors in crashtracker receiver (#1395) - chore: add changelog for every published crate (#1396) - Fix CI (#1389) - [crashtracker] Set OS info in the crash info builder when receiving report (#1388) - crashtracker: support cxx bindings for crashinfo (#1379) [APMSP-2590]: https://datadoghq.atlassian.net/browse/APMSP-2590?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com>

# Release proposal for libdd-crashtracker and its dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-crashtracker **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v2.0.0` ### Commits - chore(crashtracking): rename target triple to runtime platform (#1747) - chore(ci): give libdd-libunwind-sys its own version (#1743) - chore(crashtracking): add tag for target triple (#1741) - refactor(libdd-crashtracker)!: avoid leaking Endpoint through the public API (#1705) - chore(cargo): bump to 29.0.0 (#1702) - fix(crashtracking): use libunwind to unwind frames (#1663) - chore(deps): bump blazesym to 0.2.3 and blazesym-c to 0.1.7 (#1654) - chore(ci): fix crashtracker receiver binary rpath setting (#1652) - chore(crashtracking): emit a best effort stacktrace for Mac (#1645) - chore(crashtracker): use default-features=false for aws-lc-sys (#1625) - feat(crashtracking): report unhandled exceptions (#1596) - refactor(ddcommon)!: remove direct dependency on hyper client everywhere in common (#1604) - feat(crashtracking): include `Kind` in crash ping and clarify requirements (#1595) - fix(crashtracking): add process_tags to application field (#1576) - ci: update nightly in CI to 2026-02-08 (#1539) - fix(telemetry)!: fix logs payload format [APMSP-2590] (#1498) - chore(crashtracking): bump os_info crate to 3.14 (#1507) - Don't bail (#1494) - feat(crashtracking)!: emit crashing thread name in crash report for linux crashes (#1485) - test(crashtracking): add minimal LD preload test for crashtracker collector (#1428) - chore: release libddcommon-v1.1.0 (#1456) - chore: prepare libdd-telemetry-v2.0.0 (#1457) - [crashtracker] Retrieve panic message when crashing (#1361) - fix(sidecar): AWS lambda also can return EACCESS for shm_open (#1446) - chore(crashtracking): add `is_crash_debug` tag to crashtracker receiver debug logs (#1445) - [crashtracker] Log errors in crashtracker receiver (#1395) - chore: add changelog for every published crate (#1396) - Fix CI (#1389) - [crashtracker] Set OS info in the crash info builder when receiving report (#1388) - crashtracker: support cxx bindings for crashinfo (#1379) Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com>

# Release proposal for libdd-crashtracker and its dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-common **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-common-v3.0.0` ### Commits - refactor(trace-utils)!: change header name type to accept dynamic values (#1722) ## libdd-crashtracker **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v2.0.0` ### Commits - chore(crashtracking): rename target triple to runtime platform (#1747) - chore(ci): give libdd-libunwind-sys its own version (#1743) - chore(crashtracking): add tag for target triple (#1741) - refactor(libdd-crashtracker)!: avoid leaking Endpoint through the public API (#1705) - chore(cargo): bump to 29.0.0 (#1702) - fix(crashtracking): use libunwind to unwind frames (#1663) - chore(deps): bump blazesym to 0.2.3 and blazesym-c to 0.1.7 (#1654) - chore(ci): fix crashtracker receiver binary rpath setting (#1652) - chore(crashtracking): emit a best effort stacktrace for Mac (#1645) - chore(crashtracker): use default-features=false for aws-lc-sys (#1625) - feat(crashtracking): report unhandled exceptions (#1596) - refactor(ddcommon)!: remove direct dependency on hyper client everywhere in common (#1604) - feat(crashtracking): include `Kind` in crash ping and clarify requirements (#1595) - fix(crashtracking): add process_tags to application field (#1576) - ci: update nightly in CI to 2026-02-08 (#1539) - fix(telemetry)!: fix logs payload format [APMSP-2590] (#1498) - chore(crashtracking): bump os_info crate to 3.14 (#1507) - Don't bail (#1494) - feat(crashtracking)!: emit crashing thread name in crash report for linux crashes (#1485) - test(crashtracking): add minimal LD preload test for crashtracker collector (#1428) - chore: release libddcommon-v1.1.0 (#1456) - chore: prepare libdd-telemetry-v2.0.0 (#1457) - [crashtracker] Retrieve panic message when crashing (#1361) - fix(sidecar): AWS lambda also can return EACCESS for shm_open (#1446) - chore(crashtracking): add `is_crash_debug` tag to crashtracker receiver debug logs (#1445) - [crashtracker] Log errors in crashtracker receiver (#1395) - chore: add changelog for every published crate (#1396) - Fix CI (#1389) - [crashtracker] Set OS info in the crash info builder when receiving report (#1388) - crashtracker: support cxx bindings for crashinfo (#1379) [APMSP-2590]: https://datadoghq.atlassian.net/browse/APMSP-2590?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com>

Bump os-info and also add some unit tests

3293749

gyuheon0h requested review from a team as code owners February 3, 2026 21:44

github-actions Bot added the crashtracker label Feb 3, 2026

License file

6c593bd

danielsn approved these changes Feb 3, 2026

View reviewed changes

gyuheon0h added 4 commits February 3, 2026 16:55

Miri skip

0a309ad

License file

21811a1

Licesne

e7bf429

License

bd8f8ee

dd-devflow Bot added the mergequeue-status: waiting label Feb 3, 2026

Merge branch 'main' into gyuheon0h/os-info-bump

17676fd

dd-devflow Bot added mergequeue-status: removed and removed mergequeue-status: waiting labels Feb 3, 2026

dd-devflow Bot added mergequeue-status: waiting and removed mergequeue-status: removed labels Feb 3, 2026

Merge conf:

b4f0923

dd-devflow Bot added mergequeue-status: queued and removed mergequeue-status: waiting mergequeue-status: queued labels Feb 3, 2026

dd-devflow Bot added the mergequeue-status: in_progress label Feb 3, 2026

gh-worker-dd-mergequeue-cf854d Bot merged commit aa61ebb into main Feb 4, 2026
71 checks passed

dd-devflow Bot removed the mergequeue-status: in_progress label Feb 4, 2026

gh-worker-dd-mergequeue-cf854d Bot deleted the gyuheon0h/os-info-bump branch February 4, 2026 00:18

dd-devflow Bot added the mergequeue-status: done label Feb 4, 2026

dd-octo-sts Bot mentioned this pull request Mar 17, 2026

chore(release): proposal for libdd-crashtracker #1745

Merged

dd-octo-sts Bot mentioned this pull request Mar 17, 2026

chore(release): proposal for libdd-crashtracker #1746

Merged

dd-octo-sts Bot mentioned this pull request Mar 17, 2026

chore(release): proposal for libdd-crashtracker #1748

Merged

dd-octo-sts Bot mentioned this pull request Mar 17, 2026

chore(release): proposal for libdd-crashtracker #1752

Merged

dd-octo-sts Bot mentioned this pull request Mar 17, 2026

chore(release): proposal for libdd-crashtracker #1755

Merged

dd-octo-sts Bot mentioned this pull request Mar 18, 2026

chore(release): proposal for libdd-crashtracker #1756

Merged

Conversation

gyuheon0h commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Additional Notes

How to test the change?

Uh oh!

github-actions Bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Documentation Check Results

📦 libdd-crashtracker - 996 warning(s)

Uh oh!

github-actions Bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Cargo Deny Results

📦 libdd-crashtracker - 7 error(s)

Uh oh!

gyuheon0h commented Feb 3, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov-commenter commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

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

Uh oh!

Benchmarks

Comparison

Candidate

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 8

Group 9

Group 10

Group 11

Group 12

Group 13

Group 14

Group 15

Group 16

Group 17

Group 18

Group 19

Baseline

Uh oh!

gyuheon0h commented Feb 3, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gyuheon0h commented Feb 3, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

gyuheon0h commented Feb 3, 2026 •

edited

Loading

github-actions Bot commented Feb 3, 2026 •

edited

Loading

📦 `libdd-crashtracker` - 996 warning(s)

github-actions Bot commented Feb 3, 2026 •

edited

Loading

📦 `libdd-crashtracker` - 7 error(s)

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 •

edited

Loading

codecov-commenter commented Feb 3, 2026 •

edited

Loading

pr-commenter Bot commented Feb 3, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Feb 3, 2026 •

edited

Loading