Skip to content

Conversation

@pawelchcki
Copy link
Contributor

Automatic PR. Updates .gitlab/one-pipeline.locked.yml

@pawelchcki pawelchcki requested a review from a team as a code owner November 28, 2025 15:52
@github-actions
Copy link

👋 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-11-28 15:52:27 UTC

@datadog-datadog-prod-us1
Copy link
Contributor

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
Patch Coverage: 100.00%
Total Coverage: 95.16% (-0.00%)

View detailed report

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

@pr-commenter
Copy link

pr-commenter bot commented Nov 28, 2025

Benchmarks

Benchmark execution time: 2025-11-28 16:22:48

Comparing candidate commit b3cb677 in PR branch auto-update-one-pipeline with baseline commit 508ecc6 in branch master.

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

scenario:profiling - stack collector (varying depth)

  • 🟥 throughput [-53.249op/s; -52.612op/s] or [-5.531%; -5.465%]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants