gharris1727 commented on PR #14917: URL: https://github.com/apache/kafka/pull/14917#issuecomment-1839438204
I was looking into this too, and haven't figured out a stabilization yet. I profiled the tests under a 40% CPU limited environment, and got pretty similar flakes to happen in several of the tests in this suite. Since i'm profiling one test at a time, I'm seeing a lot of impact from loading classes (`loadClass` highlighted in purple, wall clock trace)  In terms of runtime, the JsonRestServer.start is taking up 75% of the test duration and doesn't seem to have any obvious slowdowns. My current working theory is that this test is arbitrarily picked to be the first test in the suite, and the loadClass overhead is enough to tip over the 2-minute test timeout. If that's the case, we might expect disabling the test to cause one of the other tests to become flaky. I would support merging this change just to test that hypothesis. I was planning on exploring "warming" the classloader cache before the test timer starts, or increasing the test timer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
