Skip to content

Conversation

@p-datadog
Copy link
Member

What does this PR do?

Increases the upper bound that the "long_method" is expected to take from 1 to 4 seconds.

Motivation:
CI has a run where the method took 1.8 seconds:
https://github.com/DataDog/dd-trace-rb/actions/runs/19936903071/job/57164209793?pr=5109

Change log entry
None

Additional Notes:

How to test the change?

@p-datadog p-datadog requested a review from a team as a code owner December 5, 2025 17:14
@github-actions github-actions bot added the dev/testing Involves testing processes (e.g. RSpec) label Dec 5, 2025
Copy link
Member

@ivoanjo ivoanjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Timing-based tests and CI can be a big pain. If this reoccurs, check if there's any background threads and maybe disable GC for the test duration, to make sure Ruby really doesn't decide to do the wrong things and the wrong time :)

@datadog-official
Copy link

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
Patch Coverage: 100.00%
Total Coverage: 95.23% (+0.01%)

View detailed report

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

@pr-commenter
Copy link

pr-commenter bot commented Dec 5, 2025

Benchmarks

Benchmark execution time: 2025-12-05 17:43:11

Comparing candidate commit df629ef in PR branch di-duration-flake with baseline commit 6cb632a in branch master.

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

@p-datadog p-datadog merged commit 08135ba into master Dec 8, 2025
276 checks passed
@p-datadog p-datadog deleted the di-duration-flake branch December 8, 2025 12:45
@github-actions github-actions bot added this to the 2.23.0 milestone Dec 8, 2025
p-datadog pushed a commit that referenced this pull request Dec 8, 2025
* master: (523 commits)
  DI: relax upper bound for reported long method duration (#5113)
  Change development guide to use Ruby 3.4 by default (#5112)
  Fix exception in RC on OpenFeature::Engine absence
  [🤖] Update Latest Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/19996135509
  [🤖] Update System Tests: https://github.com/DataDog/dd-trace-rb/actions/runs/19996155319
  Add ruby guikld to all dsm files
  add DSM to codeowners
  feat: add process tags to traces (#5033)
  DEBUG-3558 DI: chunk snapshot payloads (#5086)
  CI: enable push_to_test_optimization unless this is a pull request from a fork
  fix steep checks
  [🤖] Lock Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/19827679824
  [🤖] Lock Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/19827296218
  Add test to verify consumer backlog serialization with kafka_commit tag
  Remove one diagnostic output
  Install rubygems
  Add diagnostic steps
  Use default rubygems+bundler for each Ruby version
  Revert "Disable profiling specs for 4.0"
  Use git `datadog-ruby_core_source` having 4.0
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dev/testing Involves testing processes (e.g. RSpec)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants