2.3.1 increase the build timeout default

Not really a bug per se, but the default build timeout of 10 is too low to get some of my more advanced projects compiled. I remember I also had to change it in the beta, I've just set it to the maximum of 300 now.

If you really want to impose a build timeout then I guess a default of 60 would be more appropriate.

But personally I would prefer to see an option to not have a build timeout threshold at all (like it was in the 2.2.6 sdk) (Proposal: allow 0 and implement it as no timeout)

Former Member over 9 years ago

Hey,

I've created a ticket with the suggestions you've made. I'm sure there was a good reason behind implementing a build timeout like we have now, but I'll have to ask around to find out. Thanks for the report!

-Coleman

Petr.Koula over 9 years ago

I agree with Peter as I also always had to double it to compile more complex apps.

jim_m_58 over 9 years ago

I often use a slow laptop, so I had to increase it even for simple apps. if a limit is needed, maybe make the default longer? (I'm using 60 seconds right now, and so far, no problems)

Brandon.ConnectIQ over 8 years ago

Just as an FYI, the build timeout was set to a default of 60 seconds in 2.3.3. We also allow a timeout of '0' to indicate no timeout as suggested.