github-actions[bot] commented on PR #14795:
URL: https://github.com/apache/kafka/pull/14795#issuecomment-1977907234
This PR is being marked as stale since it has not had any activity in 90
days. If you would like to keep this PR alive, please ask a committer for
review. If the PR has merge
gharris1727 commented on PR #14795:
URL: https://github.com/apache/kafka/pull/14795#issuecomment-1841693899
@mimaison I've raised a ticket to ask the Infra team what they think about
this change: https://issues.apache.org/jira/browse/INFRA-25245
--
This is an automated message from the Ap
mimaison commented on PR #14795:
URL: https://github.com/apache/kafka/pull/14795#issuecomment-1839170339
Thanks @gharris1727 for looking into this. That seems an interesting option
and it would definitively help debugging.
The only concern I have is about the retained size per build. x5 i
gharris1727 commented on PR #14795:
URL: https://github.com/apache/kafka/pull/14795#issuecomment-1832781742
Also worth a follow-up is maybe tackling the outliers that do experience
truncation, and try to reduce their log volume to a more reasonable level.
The biggest offenders above 10MB
gharris1727 commented on PR #14795:
URL: https://github.com/apache/kafka/pull/14795#issuecomment-1832757011
I did some statistics on the current state of log truncation in CI. I
learned that:
* A full run of `./gradlew test` writes 1.73GB of logs
* 814 of 1532 test suites (53%) pro
gharris1727 opened a new pull request, #14795:
URL: https://github.com/apache/kafka/pull/14795
Jenkins truncates stdout/stderr from tests which exceed 100,000 bytes. This
truncation is computed once per-suite, meaning that each suite gets a 100kb
budget for logs, and suites that log too muc
