New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

overlord/snapstate: have an explicit code path last-refresh unset/zero => immediately refresh try #3389

Merged
merged 1 commit into from May 23, 2017

Conversation

Projects
None yet
3 participants
@pedronis
Contributor

pedronis commented May 23, 2017

This makes that a clear explicit policy decision, also timeutil.Next is relatively slow when given zero-Time starting-point.

have an explicit last-refresh unset/zero => immediatey refresh try co…
…de path (NB: timeutil.Next is relatively slow if given zero time)
@mvo5

mvo5 approved these changes May 23, 2017

@pedronis pedronis changed the title from overlord/snapstate: have an explicit code path last-refresh unset/zero => immediatey refresh try to overlord/snapstate: have an explicit code path last-refresh unset/zero => immediately refresh try May 23, 2017

@mvo5 mvo5 merged commit c47d472 into snapcore:master May 23, 2017

3 of 7 checks passed

artful-amd64 autopkgtest running
Details
xenial-amd64 autopkgtest running
Details
xenial-i386 autopkgtest running
Details
yakkety-amd64 autopkgtest running
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
xenial-ppc64el autopkgtest finished (success)
Details
zesty-amd64 autopkgtest finished (success)
Details

@pedronis pedronis deleted the pedronis:no-last-refresh-refresh-immediately branch May 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment