apurtell commented on PR #2482:
URL: https://github.com/apache/phoenix/pull/2482#issuecomment-4505008078

   FWIW @mnpoonia I put this to my robot and it suggests CI host CPU starvation 
is the cause because the timeouts are too tight. 
   
   > On a busy Yetus worker, the brand-new single-thread pool created on line 
100 of the test may not be scheduled for several seconds. The thread isn't 
sleeping — it just hasn't been picked yet. The 5s timeout is just too tight. It 
was almost certainly chosen by eye, not by measurement, and offers very little 
margin.


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