-
Notifications
You must be signed in to change notification settings - Fork 4.1k
storage: missing intent in TestMVCCHistories/range_tombstone_writes #87489
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Description
A testrace run on #87403 resulted in this test failure:
=== RUN TestMVCCHistories/range_tombstone_writes
mvcc_history_test.go:342:
/go/src/github.com/cockroachdb/cockroach/pkg/storage/testdata/mvcc_histories/range_tombstone_writes:443: del_range_ts k=+ end=z ts=1
output didn't match expected:
@@ -12,7 +12,7 @@
data: "g"/4.000000000,0 -> /<empty>
data: "g"/2.000000000,0 -> /BYTES/g2
meta: "h"/0,0 -> txn={<nil>} ts=0,0 del=false klen=0 vlen=0 raw=/BYTES/inline mergeTs=<nil> txnDidNotUpdateMeta=false
meta: "i"/0,0 -> txn={id=00000000 key=/Min pri=0.00000000 epo=0 ts=7.000000000,0 min=0,0 seq=0} ts=7.000000000,0 del=false klen=12 vlen=7 mergeTs=<nil> txnDidNotUpdateMeta=true
data: "i"/7.000000000,0 -> /BYTES/i7
-error: (*assert.withAssertionFailure:) can't write MVCC range tombstone across local keyspan {\x00-z}/1.000000000,0
+error: (*withstack.withStack:) intentIter at intent, but iter not at provisional value
--- FAIL: TestMVCCHistories/range_tombstone_writes (0.08s)
The change in that PR should not have caused this failure. Instead, it indicates a problem either with the intentInterleavingIter or with Pebble itself, possibly a point key not being surfaced.
Jira issue: CRDB-19371
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.