jiafu1115 commented on PR #20845:
URL: https://github.com/apache/kafka/pull/20845#issuecomment-3508395324

   append more detail log. I checked at least 3 builds fail about this test 
cases. This is the earliest timeout occurrence time.
   To be honest, I think it is caused by timeout is too short which won't cover 
GC stop/Class Load/Log initial etc.  It doesn't matter with the case self. So 
the solution is just to increase the timeout to 1 second from 100ms.
   [the statement _verify(rlmCopyQuotaManager, times(1)).getThrottleTimeMs();_ 
already verify the case]
   
   BTW, if one case requires ≤100 ms, I think it must be quite flaky with a 
high failure ratio.
   
   ` org.junit.jupiter.api.AssertTimeoutPreemptively$ExecutionTimeoutException: 
Execution timed out in thread junit-timeout-thread-1
               at 
[email protected]/java.lang.StringCoding.hasNegatives(StringCoding.java:78)
               at [email protected]/java.lang.String.isASCII(String.java:941)
               at 
[email protected]/java.lang.String.getBytesNoRepl1(String.java:964)
               at 
[email protected]/java.lang.String.getBytesNoRepl(String.java:949)
               at 
[email protected]/java.lang.System$1.uncheckedGetBytesNoRepl(System.java:2137)
               at 
[email protected]/java.util.zip.ZipCoder$UTF8ZipCoder.compare(ZipCoder.java:292)
               at 
[email protected]/java.util.zip.ZipFile$Source.getEntryPos(ZipFile.java:1860)
               at 
[email protected]/java.util.zip.ZipFile.getEntry(ZipFile.java:294)
               at 
[email protected]/java.util.jar.JarFile.getEntry(JarFile.java:505)
               at 
[email protected]/java.util.jar.JarFile.getJarEntry(JarFile.java:460)
               at 
[email protected]/jdk.internal.loader.URLClassPath$JarLoader.getResource(URLClassPath.java:764)
               at 
[email protected]/jdk.internal.loader.URLClassPath.getResource(URLClassPath.java:332)
               at 
[email protected]/java.net.URLClassLoader.findClass(URLClassLoader.java:364)
               at 
[email protected]/java.lang.ClassLoader.loadClass(ClassLoader.java:557)
               at 
[email protected]/java.lang.ClassLoader.loadClass(ClassLoader.java:490)
               at 
org.gradle.internal.io.LineBufferingOutputStream.<init>(LineBufferingOutputStream.java:45)
               at 
org.gradle.internal.io.LineBufferingOutputStream.<init>(LineBufferingOutputStream.java:40)
               at 
org.gradle.internal.io.LineBufferingOutputStream.<init>(LineBufferingOutputStream.java:36)
               at 
org.gradle.internal.io.LinePerThreadBufferingOutputStream.getStream(LinePerThreadBufferingOutputStream.java:36)
               at 
org.gradle.internal.io.LinePerThreadBufferingOutputStream.write(LinePerThreadBufferingOutputStream.java:250)
               at 
app//org.apache.logging.log4j.core.util.CloseShieldOutputStream.write(CloseShieldOutputStream.java:53)
               at 
app//org.apache.logging.log4j.core.appender.OutputStreamManager.writeToDestination(OutputStreamManager.java:263)
               at 
app//org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:296)
               at 
app//org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:307)
               at 
app//org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:229)
               at 
app//org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:220)
               at 
app//org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:211)
               at 
app//org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:160)
               at 
app//org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:133)
               at 
app//org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:124)
               at 
app//org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:88)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:711)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:669)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:645)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:702)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:671)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:645)
               at 
app//org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:554)
               at 
app//org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:67)
               at 
app//org.apache.logging.log4j.core.Logger.logMessage(Logger.java:173)
               at 
app//org.apache.logging.slf4j.Log4jLogger.log(Log4jLogger.java:374)
               at 
app//org.apache.kafka.common.utils.LogContext$LocationAwareKafkaLogger.writeLog(LogContext.java:441)
               at 
app//org.apache.kafka.common.utils.LogContext$LocationAwareKafkaLogger.info(LogContext.java:394)
               at 
app//org.apache.kafka.server.log.remote.storage.RemoteLogManager$RLMCopyTask.maybeUpdateLogStartOffsetOnBecomingLeader(RemoteLogManager.java:888)
               at 
app//org.apache.kafka.server.log.remote.storage.RemoteLogManager$RLMCopyTask.copyLogSegmentsToRemote(RemoteLogManager.java:936)
               at 
app//org.apache.kafka.server.log.remote.storage.RemoteLogManagerTest.lambda$testCopyQuota$2(RemoteLogManagerTest.java:3425)`


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to