-
Notifications
You must be signed in to change notification settings - Fork 4.1k
server: server orchestrator can fail to start tenant #112077
Copy link
Copy link
Closed
Labels
C-test-failureBroken test (automatically or manually discovered).Broken test (automatically or manually discovered).T-disaster-recoverybranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2release-blockerIndicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
Description
Seen here on #110932 that shouldn't cause this flake:
Failed
=== RUN TestRevertTenantToTimestamp/reverts_changes_inside_a_tenant
stream_ingestion_manager_test.go:85: condition failed to evaluate within 45s: pq: service unavailable for target tenant (target)
--- FAIL: TestRevertTenantToTimestamp/reverts_changes_inside_a_tenant (46.91s)
I'm assuming we want to skip this test under stress.
Jira issue: CRDB-32225
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-test-failureBroken test (automatically or manually discovered).Broken test (automatically or manually discovered).T-disaster-recoverybranch-masterFailures and bugs on the master branch.Failures and bugs on the master branch.branch-release-23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2Used to mark GA and release blockers, technical advisories, and bugs for 23.2release-blockerIndicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.