-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.1.1
-
Component/s: None
-
Labels:
The function __wt_clock_to_nsec converts the clock ticks to nanoseconds. there have been failure in this function because the value returned is not in the valid range of the type uint64_t.
Here is the failure snippet from an evergreen test:
[js_test:max_acceptable_logical_clock_drift_secs_parameter] 2018-08-21T14:06:48.606+0000 c20528| src/third_party/wiredtiger/src/support/time.c:92:10: runtime error: value 2.53358e+19 is outside the range of representable values of type 'unsigned long'
[js_test:max_acceptable_logical_clock_drift_secs_parameter] 2018-08-21T14:06:48.840+0000 c20528| #0 0x5615784336ac in __wt_clock_to_nsec /data/mci/fba56704713e30d0aa3d5f043dfd9ac0/src/src/third_party/wiredtiger/src/support/time.c:92:10
[js_test:max_acceptable_logical_clock_drift_secs_parameter] 2018-08-21T14:06:48.840+0000 c20528| #1 0x5615785828d7 in __log_server /data/mci/fba56704713e30d0aa3d5f043dfd9ac0/src/src/third_party/wiredtiger/src/conn/conn_log.c:1018:14
[js_test:max_acceptable_logical_clock_drift_secs_parameter] 2018-08-21T14:06:48.869+0000 c20528| SUMMARY: AddressSanitizer: undefined-behavior src/third_party/wiredtiger/src/support/time.c:92:10
There is a chance that tsc_nsec_ratio is not initialised appropriately.