Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Change JUnit terraform test output to include test failure details inside <failure> elements, use the error message as the message attribute into v1.11 #36386

Conversation

github-actions[bot]
Copy link
Contributor

Backport

This PR is auto-generated from #36316 to be assessed for backporting due to the inclusion of the label 1.11-backport.

The below text is copied from the body of the original PR.


This PR

Related:

  • Update docs for -junit-xml flag

Target Release

1.11.x

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

This change relates to a feature that isn't released yet


Overview of commits

@github-actions github-actions bot force-pushed the backport/junit-add-failure-details/centrally-relaxing-labrador branch from ed625b0 to d4bb505 Compare January 22, 2025 16:42
@github-actions github-actions bot requested a review from SarahFrench January 22, 2025 16:42
@SarahFrench SarahFrench marked this pull request as ready for review January 22, 2025 16:56
@SarahFrench SarahFrench requested a review from a team as a code owner January 22, 2025 16:56
@SarahFrench SarahFrench merged commit dba8e40 into v1.11 Jan 22, 2025
7 checks passed
@SarahFrench SarahFrench deleted the backport/junit-add-failure-details/centrally-relaxing-labrador branch January 22, 2025 17:09
Copy link
Contributor Author

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant