cockroachdb / cockroachdb/cockroach
release-26.2: ccl/changefeedccl: TestChangefeedProtectedTimestampUpdate failed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
ccl/changefeedccl.TestChangefeedProtectedTimestampUpdate failed on release-26.2 @ b213c58ceafd70a2aa5d066a033d1e412ea9bd99:
=== RUN TestChangefeedProtectedTimestampUpdate
test_log_scope.go:172: test logs captured to: outputs.zip/logTestChangefeedProtectedTimestampUpdate4235393390
test_log_scope.go:82: use -show-logs to present logs inline
changefeed_test.go:13217: -- test log scope end --
test logs left over in: outputs.zip/logTestChangefeedProtectedTimestampUpdate4235393390
--- FAIL: TestChangefeedProtectedTimestampUpdate (6.29s)
=== RUN TestChangefeedProtectedTimestampUpdate/kafka
helpers_test.go:1606: making server as system tenant
helpers_test.go:1682: making kafka feed factory
testfeed_test.go:341: creating external connection
testfeed_test.go:344: ran create external connection
changefeed_test.go:13204:
Error Trace: pkg/ccl/changefeedccl/changefeed_test.go:13204
pkg/ccl/changefeedccl/helpers_test.go:1868
pkg/ccl/changefeedccl/helpers_test.go:1904
Error: "1" is not greater than or equal to "2"
Test: TestChangefeedProtectedTimestampUpdate/kafka
--- FAIL: TestChangefeedProtectedTimestampUpdate/kafka (6.28s)
Parameters:
attempt=1run=1shard=16
Same failure on other branches
- #173319 release-26.3: ccl/changefeedccl: TestChangefeedProtectedTimestampUpdate failed [A-cdc C-test-failure O-robot T-cdc branch-release-26.3]
This test on roachdash | Improve this report!
Jira issue: CRDB-68565
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with pkg/ccl/changefeedccl/changefeed_test.go around line 13204 and inspect the failure path through helpers_test.go lines 1868 and 1904. Re-run TestChangefeedProtectedTimestampUpdate, using the captured logs and the referenced test report to determine why the Kafka case observes 1 instead of at least 2. Done means the failure is understood and the test passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- stream-processing, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100