Merge ~ltrager/maas:remote-script-runner-reliability into maas:master
Proposed by
Lee Trager
Status: | Merged |
---|---|
Approved by: | Lee Trager |
Approved revision: | c9a6de66a77f0d6f961a4ece706c5448e1fdfaea |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~ltrager/maas:remote-script-runner-reliability |
Merge into: | maas:master |
Diff against target: |
135 lines (+13/-19) 5 files modified
src/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+2/-1) src/provisioningserver/refresh/__init__.py (+2/-1) src/provisioningserver/refresh/maas_api_helper.py (+4/-9) src/provisioningserver/refresh/tests/test_maas_api_helper.py (+3/-6) src/provisioningserver/refresh/tests/test_refresh.py (+2/-2) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andres Rodriguez (community) | Approve | ||
Review via email: mp+331995@code.launchpad.net |
Commit message
LP: #1710092 - Use a monotonic clock instead of relative time.
Previously MAAS was using datetime.now() to calculate timeout. datetime.now()
may change use to NTP running or under high system load. time.monotonic()
gives a consistent incrementing time rate.
Description of the change
Mike started this branch[1] to fix some issues he was seeing. On my system this does make the stress-ng tests more reliable. However the test system does lock up if I run all tests including stress-ng-cpu-long and stress-
[1] https:/
To post a comment you must log in.
Let’s not revert the padding of time. Regardless of the improvements I
still think we should have better padding time!
On Sun, Oct 8, 2017 at 9:28 PM Lee Trager <email address hidden> wrote:
> The proposal to merge ~ltrager/ maas:remote- script- runner- reliability into /code.launchpad .net/~mpontillo /maas/+ git/maas/ +merge/ 331030 /code.launchpad .net/~ltrager/ maas/+git/ maas/+merge/ 331995
> maas:master has been updated.
>
> Description changed to:
>
> Mike started this branch[1] to fix some issues he was seeing. On my system
> after switching to a monotonic clock the stress-ng tests no longer time
> out. I've reverted the 5 minutes padding back to 60 seconds as the cause
> seems to be the clock not the timeout.
>
> [1] https:/
>
> For more details, see:
> https:/
> --
> Your team MAAS Committers is subscribed to branch maas:master.
>
--
Andres Rodriguez
Engineering Manager, MAAS
Canonical USA, Inc.