This repository was archived by the owner on Feb 20, 2020. It is now read-only.
Bug 1486800 - don't start max run timer before task initialisation has completed. #125
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion (feature initialisation) has completed
imbstack
approved these changes
Oct 3, 2018
main.go
Outdated
|
|
||
| func (task *TaskRun) setMaxRunTimer() *time.Timer { | ||
| return time.AfterFunc( | ||
| // Round(0) forces wall time calculation instead of monotonic time in case machine slept etc |
Contributor
There was a problem hiding this comment.
I guess you can delete this comment now?
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See bug 1486800 for details.