large connectTimeouts are only useful when you're dealing with a flaky network - eg trying to connect to something over 3G. In this case, having the timeouts at 40 means that if xctestserver isn't running on the other side, the connection will hang for 40 seconds, then die. We use those connections inside a retry loop, which means the retry loop is 40x slower than it should be
readtimeout is set to 100 seconds, but there are cases (eg getting a flutter view hierarchy) where it actually takes longer than that to complete. Bumping it up.
same applies to the installer:
if connection is taking more than 1 seconds, it's an indication the installer is hung, so it doesn't make sense to wait more.
large connectTimeouts are only useful when you're dealing with a flaky network - eg trying to connect to something over 3G. In this case, having the timeouts at 40 means that if xctestserver isn't running on the other side, the connection will hang for 40 seconds, then die. We use those connections inside a retry loop, which means the retry loop is 40x slower than it should be
readtimeout is set to 100 seconds, but there are cases (eg getting a flutter view hierarchy) where it actually takes longer than that to complete. Bumping it up.
same applies to the installer: