changefeedccl: tests using RangeFeed take too long

[danhhz]

We currently set kv.closed_timestamp.target_duration to 1s in the rangefeed tests (since they check resolved timestamps which ultimately depend on closed timestamps) because they flake if it's set lower. But this leads to them taking a while, the package takes ~60s to run, which seems far longer than necessary.

IIRC, the flakes had something to do with schema changes not finishing because they had a txn that was continually pushed by the closed timestamps, but it's been a while.

[danhhz]

@tbg we talked about adding a mechanism (usable from a unit test) that proactively tells closedts to try to close a certain timestamp. i suspect that would be a tremendous help here, do you think you could pick that off? (or at least design it?)

[tbg]

Yep

…

On Thu, Feb 14, 2019, 20:18 Daniel Harrison ***@***.*** wrote: @tbg <https://github.com/tbg> we talked about adding a mechanism that proactively tells closedts to try to close a certain timestamp. i suspect that would be a tremendous help here, do you think you could pick that off? (or at least design it?) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34455 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE135Jh9tIVeU2AuZdVXdmDAi7JhgQSQks5vNbaegaJpZM4ac5gC> .