This test failed under maybe_stressrace on Bazel Extended CI on #135613. Seems a little weird given we backported the PR protecting the zones table in #130622.
=== RUN TestPTSRecordProtectsTargetsAndSystemTables
test_log_scope.go:165: test logs captured to: /artifacts/tmp/_tmp/905465f697dc04c39f7d8a82cb057bfe/logTestPTSRecordProtectsTargetsAndSystemTables2369024512
test_log_scope.go:76: use -show-logs to present logs inline
protected_timestamps_test.go:500: updating PTS reader cache to 1731962155.517292301,0
protected_timestamps_test.go:512: enqueuing range 7 for mvccGC
protected_timestamps_test.go:500: updating PTS reader cache to 1731962158.896807831,0
protected_timestamps_test.go:512: enqueuing range 9 for mvccGC
protected_timestamps_test.go:500: updating PTS reader cache to 1731962162.143584093,0
protected_timestamps_test.go:512: enqueuing range 27 for mvccGC
protected_timestamps_test.go:500: updating PTS reader cache to 1731962165.419260368,0
protected_timestamps_test.go:512: enqueuing range 26 for mvccGC
protected_timestamps_test.go:500: updating PTS reader cache to 1731962168.663082802,0
protected_timestamps_test.go:512: enqueuing range 8 for mvccGC
protected_timestamps_test.go:544:
Error Trace: pkg/ccl/changefeedccl/protected_timestamps_test.go:544
Error: Received unexpected error:
batch timestamp 1731962150.678137806,0 must be after replica GC threshold 1731962159.471710070,0 (r9: /Table/{5-6})
Test: TestPTSRecordProtectsTargetsAndSystemTables
panic.go:626: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/905465f697dc04c39f7d8a82cb057bfe/logTestPTSRecordProtectsTargetsAndSystemTables2369024512
This test failed under
maybe_stressrace
on Bazel Extended CI on #135613. Seems a little weird given we backported the PR protecting the zones table in #130622.See https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_BazelExtendedCi/17824471?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildProblemsSection=true&expandBuildChangesSection=true&expandBuildTestsSection=true
Jira issue: CRDB-44660