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.

Sign up for GitHub

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

Jump to bottom

ccl/streamingccl/streamingest: TestRevertTenantToTimestamp failed #112389

Closed
cockroach-teamcity opened this issue Oct 15, 2023 · 1 comment
Closed

ccl/streamingccl/streamingest: TestRevertTenantToTimestamp failed #112389

cockroach-teamcity opened this issue Oct 15, 2023 · 1 comment
Assignees
@stevendanna
Labels
branch-master Failures and bugs on the master branch. 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
Milestone
23.2

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Oct 15, 2023 •
edited by cockroach-jira-scripts
Loading

ccl/streamingccl/streamingest.TestRevertTenantToTimestamp failed with artifacts on master @ 96ab72f95759b6a40c5c2bc67c37101f3590ddd3:

=== RUN   TestRevertTenantToTimestamp
    test_log_scope.go:170: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestRevertTenantToTimestamp213974788
    test_log_scope.go:81: use -show-logs to present logs inline
    stream_ingestion_manager_test.go:126: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestRevertTenantToTimestamp213974788
--- FAIL: TestRevertTenantToTimestamp (51.72s)
=== RUN   TestRevertTenantToTimestamp/reverts_changes_inside_a_tenant
    stream_ingestion_manager_test.go:90: condition failed to evaluate within 45s: pq: service unavailable for target tenant (target)
    --- FAIL: TestRevertTenantToTimestamp/reverts_changes_inside_a_tenant (45.92s)

Parameters: TAGS=bazel,gss,deadlock , stress=true

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-32391
@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. 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 Oct 15, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.2 milestone Oct 15, 2023
@stevendanna stevendanna self-assigned this Oct 16, 2023
This was referenced Oct 17, 2023
Merged
Merged
@stevendanna
Copy link
Collaborator

Fixed by #112403

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevendanna stevendanna

Labels
branch-master Failures and bugs on the master branch. 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
No open projects
Disaster Recovery Backlog
Archived in project
Milestone
23.2
Development

No branches or pull requests
2 participants
@stevendanna @cockroach-teamcity