m1a2st commented on PR #19371:
URL: https://github.com/apache/kafka/pull/19371#issuecomment-2905909017

   No, I think the fail tes are not related, but the main reason is the hatset 
order is different, I will file a PR to fix it.
   
   ```
   org.opentest4j.AssertionFailedError: expected: 
<[CoordinatorRecord(key=ShareGroupStatePartitionMetadataKey(groupId='groupId'), 
value=ApiMessageAndVersion(ShareGroupStatePartitionMetadataValue(initializingTopics=[],
 initializedTopics=[TopicPartitionsInfo(topicId=wO0yz3DfTaCC9fnfn8maXw, 
topicName='t1', partitions=[1, 0])], deletingTopics=[]) at version 0))]> but 
was: 
<[CoordinatorRecord(key=ShareGroupStatePartitionMetadataKey(groupId='groupId'), 
value=ApiMessageAndVersion(ShareGroupStatePartitionMetadataValue(initializingTopics=[],
 initializedTopics=[TopicPartitionsInfo(topicId=wO0yz3DfTaCC9fnfn8maXw, 
topicName='t1', partitions=[0, 1])], deletingTopics=[]) at version 0))]>
       at 
app//org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
       at 
app//org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
       at 
app//org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
       at 
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
       at 
app//org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
       at 
app//org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1145)
       at 
app//org.apache.kafka.coordinator.group.GroupMetadataManagerTest.testShareGroupInitializeSuccess(GroupMetadataManagerTest.java:21717)
       at [email protected]/java.lang.reflect.Method.invoke(Method.java:580)
       at [email protected]/java.util.ArrayList.forEach(ArrayList.java:1596)
       at [email protected]/java.util.ArrayList.forEach(ArrayList.java:1596)
   ```


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