Skip to content

Conversation

@mkuratczyk
Copy link
Contributor

When debug logging is enabled, we log something at each log level to test if logs are emitted. I don't think this is particularly useful, but it's certainly annoying, because I constantly need to filter out these logs when searching if any errors happened during tests.

When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.
@michaelklishin michaelklishin added this to the 4.1.0 milestone Apr 10, 2025
Copy link
Member

@ansd ansd left a comment

Choose a reason for hiding this comment

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

I agree, this fake logging has also annoyed me multiple times.

@mkuratczyk mkuratczyk merged commit 589e0b5 into main Apr 11, 2025
273 checks passed
@mkuratczyk mkuratczyk deleted the remove-test-logs branch April 11, 2025 10:13
mergify bot pushed a commit that referenced this pull request Apr 11, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.

(cherry picked from commit 589e0b5)
mkuratczyk added a commit that referenced this pull request Apr 11, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.

(cherry picked from commit 589e0b5)

Co-authored-by: Michal Kuratczyk <[email protected]>
mergify bot added a commit that referenced this pull request Apr 11, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.

(cherry picked from commit 589e0b5)

Co-authored-by: Michal Kuratczyk <[email protected]>
(cherry picked from commit abdcd47)
mkuratczyk pushed a commit that referenced this pull request Apr 11, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.

(cherry picked from commit 589e0b5)

Co-authored-by: Michal Kuratczyk <[email protected]>
(cherry picked from commit abdcd47)

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
michaelklishin pushed a commit that referenced this pull request Apr 24, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.
ikavgo pushed a commit that referenced this pull request May 5, 2025
When debug logging is enabled, we log something at each log level
to test if logs are emitted. I don't think this is particularly useful,
but it's certainly annoying, because I constatnly need to filter
out these logs when searching if any errors happened during tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants