AMI430 test: fix flakiness from asserting timestamps of Parameters

[astafan8]

The Parameter uses datetime.now() to define a timestamp of when it's value was set. datetime.now() may not always provide good resolution, so adding a time.sleep to the test code is a quick solution for the flakiness.

[codecov]

Codecov Report

Merging #1718 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1718   +/-   ##
=======================================
  Coverage   67.21%   67.21%           
=======================================
  Files         145      145           
  Lines       17951    17951           
=======================================
  Hits        12066    12066           
  Misses       5885     5885

[jenshnielsen]

I agree. In principle 0.1 s should be more than enough On windows I get:

In [6]: time.get_clock_info('time')
Out[6]: namespace(adjustable=True, implementation='GetSystemTimeAsFileTime()', monotonic=False, resolution=0.015625)

[astafan8]

@jenshnielsen shall i used then time.get_clock_info('time').resolution instead of a number? :)

[jenshnielsen]

Yes as I understand the docs here that is the time resolution used https://docs.python.org/3/library/datetime.html#datetime.datetime.now To be save i would do 2*time.get_clock_info('time').resolution or some such thing?

[astafan8]

@jenshnielsen 2*time.get_clock_info('time').resolution - magnifico! thanks!

[jenshnielsen]

Great