chore(ci): using the official workflow for system-tests#18160
Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 4 commits intoMay 19, 2026
Conversation
Contributor
🎉 All green!🧪 All tests passed 🔗 Commit SHA: a900198 | Docs | Datadog PR Page | Give us feedback! |
Codeowners resolved as |
81993bf to
8e975cd
Compare
8e975cd to
bc7006d
Compare
brettlangdon
approved these changes
May 19, 2026
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: db6a842a0e
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
cbeauchesne
previously requested changes
May 19, 2026
Contributor
Author
|
/remove |
|
View all feedbacks in Devflow UI.
|
This was referenced May 19, 2026
This was referenced May 19, 2026
Contributor
|
Stacked follow-up to restore the FFE scenario coverage: #18172. It keeps this workflow migration and only removes the FEATURE_FLAGGING_AND_EXPERIMENTATION exclusion. |
gh-worker-dd-mergequeue-cf854d Bot
pushed a commit
that referenced
this pull request
May 20, 2026
## Motivation #18163 was closed in favor of #18160, which also excludes the FEATURE_FLAGGING_AND_EXPERIMENTATION scenario from the tracer-release system-tests group. That exclusion is no longer the desired rollback path because it hides the FFE coverage we need while validating the Python startup issue. ## Changes Remove the `excluded_scenarios: FEATURE_FLAGGING_AND_EXPERIMENTATION` override from the #18160 system-tests workflow migration so the tracer-release group includes the FFE scenario again. ## Decisions This PR is stacked on #18160 instead of #18163 because #18163 was closed unmerged. It keeps the official system-tests workflow migration intact and only reverts the FFE scenario exclusion. Co-authored-by: oleksii.shmalko <oleksii.shmalko@datadoghq.com>
vlad-scherbich
pushed a commit
that referenced
this pull request
May 20, 2026
## Description <!-- Provide an overview of the change and motivation for the change --> ## Testing <!-- Describe your testing strategy or note what tests are included --> ## Risks <!-- Note any risks associated with this change, or "None" if no risks --> ## Additional Notes <!-- Any other information that would be helpful for reviewers --> Co-authored-by: nicolas.catoni <nicolas.catoni@datadoghq.com>
vlad-scherbich
pushed a commit
that referenced
this pull request
May 20, 2026
## Motivation #18163 was closed in favor of #18160, which also excludes the FEATURE_FLAGGING_AND_EXPERIMENTATION scenario from the tracer-release system-tests group. That exclusion is no longer the desired rollback path because it hides the FFE coverage we need while validating the Python startup issue. ## Changes Remove the `excluded_scenarios: FEATURE_FLAGGING_AND_EXPERIMENTATION` override from the #18160 system-tests workflow migration so the tracer-release group includes the FFE scenario again. ## Decisions This PR is stacked on #18160 instead of #18163 because #18163 was closed unmerged. It keeps the official system-tests workflow migration intact and only reverts the FFE scenario exclusion. Co-authored-by: oleksii.shmalko <oleksii.shmalko@datadoghq.com>
gh-worker-dd-mergequeue-cf854d Bot
pushed a commit
that referenced
this pull request
May 26, 2026
## Description Following: #18160, the update-system-tests-version.py script is unable to detect the current system-tests version to perform an automatic update. This PR fixes the script. Additionally two other occurences of the system-tests workflow were not properly pinned (integration-framework and serverless). ## Testing <!-- Describe your testing strategy or note what tests are included --> ## Risks <!-- Note any risks associated with this change, or "None" if no risks --> ## Additional Notes <!-- Any other information that would be helpful for reviewers --> Co-authored-by: avara1986 <alberto.vara@datadoghq.com> Co-authored-by: florentin.labelle <florentin.labelle@datadoghq.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Testing
Risks
Additional Notes