Skip to content

solo5: should not set booted_at to the new reboot time after a solo5_exec#1401

Merged
fwsGonzo merged 1 commit intoincludeos:devfrom
ricarkol:solo5_should_not_set_boot_at
Jun 29, 2017
Merged

solo5: should not set booted_at to the new reboot time after a solo5_exec#1401
fwsGonzo merged 1 commit intoincludeos:devfrom
ricarkol:solo5_should_not_set_boot_at

Conversation

@ricarkol
Copy link
Copy Markdown
Contributor

When doing a solo5_exec we are resetting uptime and micros_since_boot. This is wrong as micros_since_boot should measure the time since the first boot (not the reboot due to the exec).
This change fixes that by not setting the booted_at_ variable at every boot; instead, it leaves it at 0. This is a good approximation as booted_at_ usually has less than 1 ms (~700000 nanoseconds).

@fwsGonzo ^^^

@jenkins-includeos
Copy link
Copy Markdown

Can one of the admins verify this patch with one of the following commands:

  • "jenkins test please" for a one time test run
  • "ok to test" to accept latest and future commits on this pull request for testing
  • "add to whitelist" to add the author to the whitelist

@fwsGonzo fwsGonzo merged commit 0f66f55 into includeos:dev Jun 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants