On Wed, Dec 2, 2020 at 3:41 AM Luis Gomez <ecelgp@...> wrote:

Hi Anil,

I think increasing the vexhost quota might not be the right solution here because: 1) it may impact the vexhost bill (this is why you added a quota in first place) and 2) it is hard to adjust the quota so that no CSIT fails.

If you see my last comment in the ticket, I remember when we hit this issue in the past, Thanh adjusted the maximum number of robot minions that are allowed to run in parallel and by doing so the CSIT jobs where queuing in Jenkins without failing. If we do this again, we can avoid impact on vexhost bill as well as we can internally adjust the maximum number of robot minions without involving vexhost.

BR/Luis

Hello Luis: 

The max no of instances for the robot node type is set to 25, let's decrease the value to 20 going forward? 

This would imply that the dist-test would take a bit longer to complete.

Cheers.