Skip to content

Conversation

@TonyCTHsu
Copy link
Contributor

What does this PR do?

Motivation:

Change log entry

Additional Notes:

How to test the change?

@TonyCTHsu TonyCTHsu added the dev/tooling Involves tools (e.g. Rubocop, CodeCov) label Mar 4, 2025
@github-actions github-actions bot added the dev/github Github repository maintenance and automation label Mar 4, 2025
@github-actions
Copy link

github-actions bot commented Mar 4, 2025

👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description.

If changes need to be present in CHANGELOG.md you can state it this way

**Change log entry**

Yes. A brief summary to be placed into the CHANGELOG.md

(possible answers Yes/Yep/Yeah)

Or you can opt out like that

**Change log entry**

None.

(possible answers No/Nope/None)

Visited at: 2025-03-04 15:01:33 UTC

@datadog-datadog-prod-us1
Copy link
Contributor

datadog-datadog-prod-us1 bot commented Mar 4, 2025

Datadog Report

Branch report: tonycthsu/zizmore
Commit report: 27e6c58
Test service: dd-trace-rb

✅ 0 Failed, 20623 Passed, 1370 Skipped, 3m 11.93s Total Time

@codecov-commenter
Copy link

codecov-commenter commented Mar 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.69%. Comparing base (20cbec9) to head (27e6c58).
Report is 876 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4454   +/-   ##
=======================================
  Coverage   97.69%   97.69%           
=======================================
  Files        1375     1375           
  Lines       83813    83812    -1     
  Branches     4251     4251           
=======================================
  Hits        81879    81879           
+ Misses       1934     1933    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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
Copy link

pr-commenter bot commented Mar 4, 2025

Benchmarks

Benchmark execution time: 2025-03-04 21:43:07

Comparing candidate commit 27e6c58 in PR branch tonycthsu/zizmore with baseline commit 20cbec9 in branch master.

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

scenario:line instrumentation - targeted

  • 🟥 throughput [-11228.754op/s; -10789.407op/s] or [-6.749%; -6.485%]

scenario:method instrumentation

  • 🟥 throughput [-10390.122op/s; -9596.152op/s] or [-5.919%; -5.467%]

@TonyCTHsu TonyCTHsu force-pushed the tonycthsu/zizmore branch from f3b0c83 to d3ce676 Compare March 4, 2025 21:09
@TonyCTHsu TonyCTHsu force-pushed the tonycthsu/zizmore branch from d3ce676 to b664a79 Compare March 4, 2025 21:12
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@TonyCTHsu TonyCTHsu force-pushed the tonycthsu/zizmore branch from b664a79 to 27e6c58 Compare March 4, 2025 21:19
@TonyCTHsu TonyCTHsu added the do-not-merge/WIP Not ready for merge label Mar 4, 2025
@TonyCTHsu TonyCTHsu closed this Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dev/github Github repository maintenance and automation dev/tooling Involves tools (e.g. Rubocop, CodeCov) do-not-merge/WIP Not ready for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants