Timeout for the polling client reading the NEXT control message can now use the heart beat timeout if enabled.
Timeout for sending PROCEED control message can now use the heart beat timeout if enabled.
Neither of those operations should take 10 minutes to run.
Also increase the auth timeouts in tests, since when running 64 tests in parallel locally while building octopus server I would sometimes timeouts in the auth stage.
How to review this PR
Quality :heavy_check_mark:
Is it possible to test these timeouts?
Pre-requisites
[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.
Background
NEXTcontrol message can now use the heart beat timeout if enabled.PROCEEDcontrol message can now use the heart beat timeout if enabled.Neither of those operations should take 10 minutes to run.
Also increase the auth timeouts in tests, since when running
64tests in parallel locally while building octopus server I would sometimes timeouts in the auth stage.How to review this PR
Quality :heavy_check_mark:
Is it possible to test these timeouts?
Pre-requisites