[Greg McKaskle]

I saw the issue with deploying with a few teams this year. I'll probably be disabling the safety config in the disabled code next year. We are also asking the RT team to make the deploy more aggressive. Currently, it is too easy for a busy cRIO to take a long time to do the deploy.

It isn't clear why this is called the double timeout, or how the deploy is related to the excessive CPU usage.

We're there diagnostic errors due to timing or other issues? That seems like a possible reason for the CPU usage to be high.

Greg McKaskle