-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
There have been a few Evergreen failures with test_timestamp_abort with the new code to call prepare_transaction. Sometimes a call returns EINVAL. (I assume it is a call to prepare_transaction returning EINVAL since it is the only new recent code.)
I do not think it is a similar situation to WT-3953 because the timestamp values in timestamp_abort are guaranteed to be greater than 0 always.
The only information we get is:
[2018/03/03 00:12:03.086] FAIL: timestamp_abort/smoke.sh [2018/03/03 00:12:03.086] ============================== [2018/03/03 00:12:03.086] Parent: compatibility: false, in-mem log sync: false, timestamp in use: true [2018/03/03 00:12:03.086] Parent: Create 5 threads; sleep 10 seconds [2018/03/03 00:12:03.086] CONFIG: test_timestamp_abort -h WT_TEST.timestamp-abort -T 5-t 10 ... [2018/03/03 00:12:03.086] CONFIG: test_timestamp_abort -h WT_TEST.timestamp-abort -T 5-t 10 [2018/03/03 00:12:03.086] test_timestamp_abort: FAILED: Child process 13969 abnormally exited: Invalid argument [2018/03/03 00:12:03.086] process aborting [2018/03/03 00:12:03.086] Aborted
And I have not been able to reproduce this on AWS nor my Mac.