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

Don't log test results on success #16116

Closed
wants to merge 1 commit into from
Closed

Don't log test results on success #16116

wants to merge 1 commit into from

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented May 3, 2024

Description

Don't log the test stdout/err unless it failed. These logs are very verbose and printing them all, all of the time is unproductive for seeing how the failed tests failed.

@Frassle Frassle added the impact/no-changelog-required This issue doesn't require a CHANGELOG update label May 3, 2024
@Frassle Frassle marked this pull request as ready for review May 3, 2024 12:01
@Frassle Frassle requested a review from a team as a code owner May 3, 2024 12:01
@pulumi-bot
Copy link
Contributor

Changelog

[uncommitted] (2024-05-03)

Copy link
Contributor

@lunaris lunaris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@Frassle Frassle enabled auto-merge May 3, 2024 12:33
@Frassle Frassle added this pull request to the merge queue May 3, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 3, 2024
@tgummerer
Copy link
Collaborator

Looking at the failure in the merge queue here, this doesn't quite do what we want unfortunately. I had another look at the test output, and I think #16117 will solve this.

github-merge-queue bot pushed a commit that referenced this pull request May 6, 2024
This debug log output can get way too long, and GitHub Actions logs
can't even display it anymore when there are test failures. Cut each
individual message short, with an escape hatch in case someone wants to
run with the full output locally.

I had a look at the test failure in
#16116 and it seems like it's still
having the same issue. Looking again at the test output it's actually
this t.Log that includes the registered resource outputs, that contains
the large amounts of data. I arbitrarily decided to make the cutoff 100
chars, but that could be adjusted.
@Frassle Frassle closed this May 8, 2024
@Frassle Frassle deleted the fraser/testLog branch May 8, 2024 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants