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: TestProtectedTimestampManagement failed #124167

Closed
github-actions bot opened this issue May 14, 2024 · 1 comment
Closed

ccl/streamingccl/streamingest: TestProtectedTimestampManagement failed #124167

github-actions bot opened this issue May 14, 2024 · 1 comment
Labels
branch-master Failures 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
Disaster Recovery Backlog

Comments

@github-actions
Copy link

github-actions bot commented May 14, 2024 •
edited by cockroach-jira-scripts

ccl/streamingccl/streamingest.TestProtectedTimestampManagement failed on master @ f33e65d1035daf6e0628ca6b19f3860cf1a9eb8a:

=== RUN   TestProtectedTimestampManagement
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestProtectedTimestampManagement3685914525
    test_log_scope.go:81: use -show-logs to present logs inline
    replication_stream_e2e_test.go:1095: -- test log scope end --
test logs left over in: outputs.zip/logTestProtectedTimestampManagement3685914525
--- FAIL: TestProtectedTimestampManagement (151.81s)
=== RUN   TestProtectedTimestampManagement/pause-before-terminal=true
    --- FAIL: TestProtectedTimestampManagement/pause-before-terminal=true (67.20s)
=== RUN   TestProtectedTimestampManagement/pause-before-terminal=true/complete-replication=true
    testutils.go:251: condition failed to evaluate within 45s: from testutils.go:264: Unexpected status succeeded
        --- FAIL: TestProtectedTimestampManagement/pause-before-terminal=true/complete-replication=true (54.62s)

Parameters:

  • attempt=1
  • run=1
  • shard=3
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-38739
@github-actions github-actions bot added branch-master Failures 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 May 14, 2024
@andrewbaptist andrewbaptist mentioned this issue May 15, 2024
Open
@msbutler
Copy link
Collaborator

should be fixed by #124162

Disaster Recovery Backlog automation moved this from Backlog to Done May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
branch-master Failures 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
Disaster Recovery Backlog
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msbutler