cheeeee commented on PR #23928:
URL: https://github.com/apache/kafka/pull/23928#issuecomment-6434054842

   Test notes for 1ff873a700, on trunk d18f93f985. It changes only
   comments and the name of the private method `mayBeFileReadFailure`.
   
   * Checkstyle, spotless, spotbugs and the javadoc of `clients` pass.
   * A full run of `:clients:test` (13757 tests), `:storage:test` (1355)
     and `LogDirFailureTest`, `AlterReplicaLogDirsRequestTest` and
     `ReplicaManagerTest` in `core` (144) passed.
   * Three other full runs, one of this commit and two of an earlier
     local version that differed only in comments, had failures:
     * `TransactionsTest.testRecoveryFromEpochOverflow` timed out after
       60 s in all three;
     * `TransactionsWithTieredStoreTest.testFailureToFenceEpochWithTV1`
       timed out in two;
     * `SaslAuthenticatorTest.testSslClientAuthRequiredForSaslSslListener`
       expected `AUTHENTICATION_FAILED` but got `AUTHENTICATE` in one.
   
     Alone, each of the three classes passes 3 times out of 3 on
     1ff873a700. On trunk `TransactionsTest` and `SaslAuthenticatorTest`
     pass 3 times out of 3 alone, and `TransactionsWithTieredStoreTest`
     failed once out of 3. The tiered storage tests run over PLAINTEXT
     with healthy disks, and `SaslAuthenticatorTest` does not transfer
     records from a file.
   
   End to end, the four-system runs of b7708148e2 above were repeated on
   1ff873a700, with the jars checked against the build on each, and gave
   the same results: the same directories went offline, each with one
   ERROR from `LogDirFailureChannel`, no TLS run re-read the region, and
   in the TLS disconnect stress (183 consumers on Linux, 185 on macOS)
   the scheduler read no segment file.
   


-- 
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