martinezmatias commented on pull request #3570:
URL: https://github.com/apache/rocketmq/pull/3570#issuecomment-989874217


   Hi, we are researchers in software engineering, working on a novel GitHub 
bot for helping understand build failures.
   
   We have run our prototype bot 
[flacocobot](https://github.com/SpoonLabs/flacoco) on this failing PR and below 
are the results.
   
   What do you think?
   
   Thanks a lot! --Davide (@dginelli), André (@andre15silva), Matias 
(@martinezmatias), Benjamin (@danglotb), Martin (@monperrus)
   
   **********************************
   
   The line (32) of the file 
org/apache/rocketmq/client/consumer/rebalance/AllocateMessageQueueAveragely has 
been identified with a suspiciousness value of 56.20%.
   
   <details>
        <summary>Failing tests that cover this line</summary>
   
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMachineRoomNearByTest#testRun10RandomCase`
   - 
`org.apache.rocketmq.client.impl.consumer.ConsumeMessageOrderlyServiceTest#testConsumeMessageDirectly_WithException`
   - 
`org.apache.rocketmq.client.impl.consumer.ConsumeMessageOrderlyServiceTest#testConsumeMessageDirectly_WithNoException`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMachineRoomNearByTest#test1`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMachineRoomNearByTest#test3`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMachineRoomNearByTest#test2`
   </details>
   
   **********************************
   
   The line (47) of the file 
org/apache/rocketmq/client/consumer/rebalance/AllocateMessageQueueConsistentHash
 has been identified with a suspiciousness value of 45.88%.
   
   <details>
        <summary>Failing tests that cover this line</summary>
   
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMessageQueueConsitentHashTest#testRun100RandomCase`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMessageQueueConsitentHashTest#testAllocate1`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMessageQueueConsitentHashTest#testAllocate2`
   - 
`org.apache.rocketmq.client.consumer.rebalance.AllocateMessageQueueConsitentHashTest#testMessageQueueIllegalArgument`
   </details>
   
   
   **********************************
   
   The line (106) of the file org/apache/rocketmq/client/Validators has been 
identified with a suspiciousness value of 45.88%.
   
   <details>
        <summary>Failing tests that cover this line</summary>
   
   - 
`org.apache.rocketmq.client.ValidatorsTest#testCheckTopic_HasIllegalCharacters`
   - `org.apache.rocketmq.client.ValidatorsTest#testCheckTopic_BlankTopic`
   - `org.apache.rocketmq.client.ValidatorsTest#testCheckTopic_Success`
   - `org.apache.rocketmq.client.ValidatorsTest#testCheckTopic_TooLongTopic`
   </details>
   
   
   **********************************
   
   The line (41) of the file 
org/apache/rocketmq/client/impl/consumer/ProcessQueue has been identified with 
a suspiciousness value of 39.74%.
   
   <details>
        <summary>Failing tests that cover this line</summary>
   
   - 
`org.apache.rocketmq.client.impl.consumer.ProcessQueueTest#testFillProcessQueueInfo`
   - 
`org.apache.rocketmq.client.impl.consumer.ProcessQueueTest#testCachedMessageSize`
   - 
`org.apache.rocketmq.client.impl.consumer.ProcessQueueTest#testCachedMessageCount`
   </details>
   
   
   **********************************
   
   The line (24) of the file 
org/apache/rocketmq/client/producer/selector/SelectMessageQueueByHash has been 
identified with a suspiciousness value of 22.94%.
   
   <details>
        <summary>Failing tests that cover this line</summary>
   
   - 
`org.apache.rocketmq.client.producer.selector.SelectMessageQueueByHashTest#testSelect`
   </details>
   
   
   **********************************
   


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