wenbingshen commented on PR #3555:
URL: https://github.com/apache/bookkeeper/pull/3555#issuecomment-1284852000

   > I believe it was passing / not flaking on the CI.
   
   @dlg99 Thanks for your comments. I've documented in my notes the failure of 
testWriteSetWriteableCheck in the following CI test, check it out:
   https://github.com/apache/bookkeeper/actions/runs/3125949264/jobs/5070881119
   https://github.com/apache/bookkeeper/actions/runs/3124965464/jobs/5068848112
   
   As you can see it often fails. Likewise, when I tested my local, I ran 10 
times and failed 7 times.
   
![image](https://user-images.githubusercontent.com/35599757/196846304-1482d5f6-2a67-4660-86f0-f6d81672a3b6.png)
   
   
   >  Do you know what broke the test? 
   
   Please check the picture below:
   
   I printed the log before and after setting the channel `isWritable` flag . 
It can be seen that the test thread sets the channel to be unreadable, which 
occurs before the ChannelFuture listener makeWritable is triggered after the 
connection is established, causing the result of setTargetChannelState=false to 
be changed to true again.
   
   
![image](https://user-images.githubusercontent.com/35599757/196846420-6074a725-25ab-4283-9f9c-1b3704174ae5.png)
   
   
   
   


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