Skip to content

Conversation

@ivoanjo
Copy link
Member

@ivoanjo ivoanjo commented Dec 9, 2025

What does this PR do?

This reverts commit 551b5ae from #20.

See #20 for details. In that PR I mentioned:

To break the loop, let's:

  1. omit this test temporarily: ✅ done -> this was [PROF-13115] Temporarily skip broken Ruby 4 test to unblock gem release #20
  2. then we can release this gem: ✅ done ->
    https://github.com/DataDog/datadog-ruby_core_source/actions/runs/20059401843, version 3.4.2 is on rubygems.org
  3. then we can undo the dd-trace-rb pinning: ✅ done ->
    [PROF-13115] Bump minimum datadog-ruby_core_source dependency to 3.4.2 dd-trace-rb#5122
  4. then we can re-enable the test

This PR is step 4 and gets us back to where we were before the workaround.

Motivation:

Remove workaround now that it's not needed anymore!

Additional Notes:

N/A

How to test the change?

Validate that Ruby 4.0 + "corruption" test is running in CI and green.

…em release"

**What does this PR do?**

This reverts commit 551b5ae from #20.

See #20 for details. In that PR I mentioned:

So to break the loop, let's:

1. omit this test temporarily: ✅ done -> this was #20
2. then we can release this gem: ✅ done ->
   https://github.com/DataDog/datadog-ruby_core_source/actions/runs/20059401843,
   [version 3.4.2 is on rubygems.org](https://rubygems.org/gems/datadog-ruby_core_source/versions/3.4.2)
3. then we can undo the dd-trace-rb pinning: ✅ done ->
   DataDog/dd-trace-rb#5122
4. then we can re-enable the test

This PR is step 4 and gets us back to where we were before the
workaround.

**Motivation:**

Remove workaround now that it's not needed anymore!

**Additional Notes:**

N/A

**How to test the change?**

Validate that Ruby 4.0 + "corruption" test is running in CI and green.
@ivoanjo ivoanjo requested review from a team December 9, 2025 12:08
@ivoanjo ivoanjo merged commit a85add9 into master Dec 10, 2025
19 checks passed
@ivoanjo ivoanjo deleted the ivoanjo/prof-13115-undo-workaround branch December 10, 2025 08:46
@sarahchen6
Copy link
Contributor

BTW - thanks for such a clear PR description!

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.

3 participants