Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ccl/crosscluster/logical: TestMultipleSourcesIntoSingleDest failed #136069

Open
cockroach-teamcity opened this issue Nov 23, 2024 · 0 comments
Open
Labels
A-disaster-recovery branch-release-24.3.0-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Nov 23, 2024

ccl/crosscluster/logical.TestMultipleSourcesIntoSingleDest failed on release-24.3.0-rc @ ef2ebe96f3a26fd6d6716e2ec4a0c8c6fe0fb567:

=== RUN   TestMultipleSourcesIntoSingleDest
    test_log_scope.go:165: test logs captured to: outputs.zip/logTestMultipleSourcesIntoSingleDest2471876816
    test_log_scope.go:76: use -show-logs to present logs inline
    logical_replication_job_test.go:1438: waiting for logical replication job 1023321249580515329 to reach replicated time of 1732363263.399430673,0
    jobs_verification.go:218: error scanning '&{<nil> 0xc003576c60}': sql: no rows in result set
    panic.go:626: -- test log scope end --
--- FAIL: TestMultipleSourcesIntoSingleDest (14.81s)

Parameters:

  • attempt=1
  • race=true
  • run=2
  • shard=1
Help

See also: How To Investigate a Go Test Failure (internal)

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-44852

@cockroach-teamcity cockroach-teamcity added branch-release-24.3.0-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery labels Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-disaster-recovery branch-release-24.3.0-rc C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery
Projects
None yet
Development

No branches or pull requests

1 participant