Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Confusion about the timeoutInMinutes value for a task
See original GitHub issueI’ve set the timeoutInMinutes for a task like so:
- bash: |
$(bin_path)/distribute.py
timeoutInMinutes: 180
displayName: Distribute
Based on the documentation I’ve found here I’d expect this task to be allowed to continue for 180 minutes before being killed. Instead, we are seeing it killed after 60 minutes. As far as I can tell, it’s because the cancel timeout for the phase is set to it’s default 60 minutes. Note: We do not set the timeout for the phase explicitly.
If we need to set the phase timeout to be the sum of the timeouts for all tasks in it, that would be useful to have in the documentation.
If we don’t (which seems like the more sensible solution) then where are we going wrong?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
i’ll update the docs to clarify the lesser of the two timeouts wins
Related: https://github.com/microsoft/azure-pipelines-yaml/issues/48