chore(ci): add final_status property on junit XML [APMSP-2610]#178
Merged
cbeauchesne merged 5 commits intomainfrom Mar 11, 2026
Merged
chore(ci): add final_status property on junit XML [APMSP-2610]#178cbeauchesne merged 5 commits intomainfrom
cbeauchesne merged 5 commits intomainfrom
Conversation
cbeauchesne
force-pushed
the
cbeauchesne/final_status
branch
from
f2464f0 to
01dfca9
Compare
iunanua
reviewed
Mar 11, 2026
iunanua
approved these changes
Mar 11, 2026
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
2 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.
What does this PR do?
Add a
<property name="dd_tags[test.final_status]" value="pass" />on every test case reported through junitAlso updated system-tests SHA, the used one was very old, and the support for
final_statusin system-tests has been introduced recentlyMotivation
Some repositories intentionally use mechanisms that ignore test failures (there are valid reasons to still execute those tests behind the scenes).
In these cases, the reported test status cannot be relied upon by Test Optimization to monitor repository health or trigger team notifications.
To ensure a consistent and unified approach, we will instead use final_status — the property specifically designed and used by the Test Optimization integration for this purpose.
how to test it ?
Now more
N/Aon the last commit on this queryAdditional Notes
I'm using the not-that-ideal XSLT here as this change, because it must be done over 17+ repos, and it's a workaround until this gets integrated into a better place, such as datadog-ci or the backend.
We're trying to work with the team on this, please have a look on this RFC for more context.