This change is 

bors r+

bors p=9999 r+

bors r-

Canceled.

bors r+ p=9999

@irfansharif if this is related to the ReverseScan issue, perhaps it would be better to simply temporary omit that operation? In generator.go within NewDefaultConfig(), you could disable the operation with the following:

config.Ops.DB.ReverseScan = 0
config.Ops.DB.ReverseScanForUpdate = 0
config.Ops.Batch.Ops.ReverseScan = 0
config.Ops.Batch.Ops.ReverseScanForUpdate = 0
config.Ops.ClosureTxn.TxnClientOps.ReverseScan = 0
config.Ops.ClosureTxn.TxnClientOps.ReverseScanForUpdate = 0
config.Ops.ClosureTxn.TxnBatchOps.Ops.ReverseScan = 0
config.Ops.ClosureTxn.TxnBatchOps.Ops.ReverseScanForUpdate = 0
config.Ops.ClosureTxn.CommitBatchOps.ReverseScan = 0
config.Ops.ClosureTxn.CommitBatchOps.ReverseScanForUpdate = 0

Build succeeded:

• GitHub CI (Cockroach)

Oh, woops, sorry didn't see this until now. I'd have happily skipped the specific operation. I forget where we left off -- if the actual fix is forthcoming, might just be worth fixing ReverseScan for good.