Auto-activate ruby easy wins for feature-flagging-and-experimentation-sdk

[dd-octo-sts]

Automated activation of easy-win tests for ruby owned by feature-flagging-and-experimentation-sdk
View nightly workflow run

• If you approve this PR please also merge it.
• If the tests are failing it might be due to a change made since the last nightly system-tests run. You can close the PR, an updated one will be available tomorrow.
• If you close the PR please also delete the branch

[github-actions]

CODEOWNERS have been resolved as:

manifests/ruby.yml                                                      @DataDog/ruby-guild @DataDog/asm-ruby

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3979338806

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep subject-limit tests disabled until they assert enrichment

With this file-level activation, Test_Span_Enrichment_Max_Subjects is now enabled for Ruby because it is the only subject-enrichment class not listed below as missing_feature. I checked tests/parametric/test_ffe/test_span_enrichment.py: test_max_10_subjects_enforced only validates the limit inside if "ffe_subjects_enc" in meta, so Ruby can emit no ffe_subjects_enc at all and still pass, while the adjacent subject-enrichment classes remain marked unsupported. This makes the easy-win activation report subject enrichment support even when the tracer does not provide it; either keep this class disabled too or make the test fail when the tag is absent.

Useful? React with 👍 / 👎.

[dd-prapprover-prod-77c48c]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule system-tests-auto-activate-easy-wins - 2026-08-16T07:04:26Z
• ⬜ CI tests passed
• ⬜ Approved
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: CI tests failed. Please fix the failing tests and rerun the workflow, click Workflow Link -> Workflow Starter Link -> Start Workflow

[datadog-prod-us1-5]

 

⚠️ Warnings

🚦 3 Pipeline jobs failed

Testing the test | System Tests (ruby, prod) / End-to-end #1 / rails72 1     

🔧 Fix in code. This looks caused by changes in this PR.

Timed out waiting for EVP flagevaluation count >= 12000 for flag 'evp-degradation-flag' during test execution in tests/ffe/test_flag_eval_evp.py:511.

🧪 1 Test failed · 🎯 related to the job error above

🎯 tests.ffe.test_flag_eval_evp.Test_FFE_EVP_Flagevaluation_Degradation.test_ffe_evp_flagevaluation_degradation[rails72] from system_tests_suite  

AssertionError: Timed out waiting for EVP flagevaluation count >= 12000 for flag evp-degradation-flag
assert False
 +  where False = <bound method ProxyBasedInterfaceValidator.wait_for of AgentInterfaceValidator('agent')>(<function wait_for_evp_flagevaluation_count.<locals>.<lambda> at 0x7f923bbd0400>, timeout=60)
 +    where <bound method ProxyBasedInterfaceValidator.wait_for of AgentInterfaceValidator('agent')> = AgentInterfaceValidator('agent').wait_for
 +      where AgentInterfaceValidator('agent') = interfaces.agent

self = <tests.ffe.test_flag_eval_evp.Test_FFE_EVP_Flagevaluation_Degradation object at 0x7f9268122cc0>

    def test_ffe_evp_flagevaluation_degradation(self) -> None:
        for index, response in enumerate(self.responses):
...

Testing the test | System Tests (ruby, dev) / End-to-end #1 / rails72 1     

🔧 Fix in code. This looks caused by changes in this PR.

2 failed tests. Timed out waiting for exposure event for flags ['exp-5-missing-targeting-key-flag'] and subject ''.

Testing the test | all-jobs-are-green     

See error

Some CI checks or statuses failed during system tests.

📋 Copy prompt for your agent

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Branch: easy-win/feature-flagging-and-experimentation-sdk/ruby

Testing the test | System Tests (ruby, prod) / End-to-end #1 / rails72 1
Commit: 41050d261ecb79d5db2ee06d05649c168c9d08c6
Error (code / test):
Timed out waiting for EVP flagevaluation count >= 12000 for flag 'evp-degradation-flag' during test execution in tests/ffe/test_flag_eval_evp.py:511.
CI job: https://github.com/DataDog/system-tests/actions/runs/31932968435/job/95131093263

Testing the test | System Tests (ruby, dev) / End-to-end #1 / rails72 1
Commit: 41050d261ecb79d5db2ee06d05649c168c9d08c6
Error (code / test):
2 failed tests. Timed out waiting for exposure event for flags ['exp-5-missing-targeting-key-flag'] and subject ''.
CI job: https://github.com/DataDog/system-tests/actions/runs/31932968435/job/95131065214

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f83612e | Docs | Datadog PR Page | Give us feedback!}