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

eth/catalyst, core/txpool/blobpool: make tests output less logs #30563

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

holiman
Copy link
Contributor

@holiman holiman commented Oct 9, 2024

While debugging one failing test in my locals-rewrite, I noticed that the ci-testrunner-output was 18MB.

A couple of unrelated tests set the debug level to TRACE on stdout, and all subsequent tests in the same package would thus also be affected by that.

This PR removes such calls from two packages where it was prevalent. This makes getting a summary of failing tests simpler, and possibly reduces some strain from the CI pipeline.

Copy link
Member

@MariusVanDerWijden MariusVanDerWijden left a comment

Choose a reason for hiding this comment

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

Yes thanks, I often find myself scrolling through hundreds of lines just to find out the name of a failing test

@holiman holiman added this to the 1.14.12 milestone Oct 10, 2024
@holiman holiman merged commit 58cf152 into ethereum:master Oct 10, 2024
3 checks passed
holiman added a commit that referenced this pull request Nov 19, 2024
A couple of tests set the debug level to `TRACE` on stdout,
and all subsequent tests in the same package are also affected
by that, resulting in outputs of tens of megabytes. 

This PR removes such calls from two packages where it was prevalent.
This makes getting a summary of failing tests simpler, and possibly
reduces some strain from the CI pipeline.
zfy0701 pushed a commit to sentioxyz/go-ethereum that referenced this pull request Dec 3, 2024
…reum#30563)

A couple of tests set the debug level to `TRACE` on stdout,
and all subsequent tests in the same package are also affected
by that, resulting in outputs of tens of megabytes. 

This PR removes such calls from two packages where it was prevalent.
This makes getting a summary of failing tests simpler, and possibly
reduces some strain from the CI pipeline.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants