vamossagar12 commented on pull request #11424:
URL: https://github.com/apache/kafka/pull/11424#issuecomment-1019720346


   > There are still some failures in Jenkins, I'm gonna retrigger them.
   > 
   > If they still fails @vamossagar12 please take a look and see if they are 
relevant.
   
   Thanks @guozhangwang . These are the tests that failed =>
   
   ```
   Build / JDK 17 and Scala 2.13 / kafka.admin.LeaderElectionCommandTest.[1] 
Type=Raft, Name=testElectionResultOutput, Security=PLAINTEXT
   Build / ARM / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / ARM / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / ARM / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / ARM / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 8 and Scala 2.12 / 
kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 17 and Scala 2.13 / 
kafka.api.PlaintextAdminIntegrationTest.testReplicaCanFetchFromLogStartOffsetAfterDeleteRecords()
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.integration.KStreamAggregationIntegrationTest.shouldCountUnlimitedWindows
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldNotSendOldValuesOnMaterialization
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.streams.kstream.internals.KTableFilterTest.shouldPassThroughOnMaterialization
   ```
   
   and these were the ones that had failed on my local as well. I am assuming 
these aren't relevant to this change. WDYT?


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


Reply via email to