When the oplog_visibility.js test fails, it includes the previous and next timestamps in the assertion message. A sample output looks like this:
uncaught exception: Error: [Timestamp(1621310414, 191)] != [Timestamp(1621310414, 192)] are not equal : {
"Missing" : Timestamp(1621310414, 191),
"ObservedIdx" : "190",
"PrevObserved" : Timestamp(1621310414, 190),
"NextObserved" : null
} :
doassert@src/mongo/shell/assert.js:20:14
assert.eq@src/mongo/shell/assert.js:179:9
testOplog@jstests/replsets/oplog_visibility.js:95:13
@jstests/replsets/oplog_visibility.js:116:5
@jstests/replsets/oplog_visibility.js:6:2
failed to load: jstests/replsets/oplog_visibility.js
exiting with code -3
It seems the NextObserved timestamp is always null even when the current index is not the at end of the list.
- related to
-
SERVER-59214 include query results in oplog_visibility.js assertion message
-
- Closed
-