Comment 1 for bug 1774959

Revision history for this message
Sean Feole (sfeole) wrote : Re: clock test in monotonic_time will fail on Azure Standard_E4s_v3 / Standard_E64-16s / AWS m5a.large

Added Logs from AWS instance failure. This test only appears to fail on the instance types backed via AMD EPYC 7000 series processors with an all core turbo clock speed of 2.5 GHz

may or may not be relevant info

11/22 00:04:50 INFO |monotonic_:0048| Time test command exit status: 1
11/22 00:04:50 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_f
unction
    return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
    postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_on
ce
    self.run_once(*args, **dargs)
  File "/home/ubuntu/autotest/client/tests/monotonic_time/monotonic_time.py", l
ine 54, in run_once
    raise error.TestFail(line)
TestFail: FAIL: tsc-worst-warp=-44