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/streamingccl/streamingest: TestTenantStreamingMultipleNodes failed #112784

Closed
cockroach-teamcity opened this issue Oct 20, 2023 · 8 comments
Closed
Assignees
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-remote-execution An issue found only using Bazel Remote Execution function. 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

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Oct 20, 2023

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes908541395
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:466: condition failed to evaluate within 45s: from testutils.go:495: stream ingestion has not recorded any progress yet, waiting to advance pos 1697827592.910242658,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes908541395
--- FAIL: TestTenantStreamingMultipleNodes (404.80s)

Parameters: attempt=1 , run=28 , shard=12

Help

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

Same failure on other branches

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-32593

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-remote-execution An issue found only using Bazel Remote Execution function. 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 20, 2023
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Oct 20, 2023
@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes3776668797
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:466: condition failed to evaluate within 45s: from testutils.go:495: stream ingestion has not recorded any progress yet, waiting to advance pos 1697827154.781656957,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes3776668797
--- FAIL: TestTenantStreamingMultipleNodes (416.13s)

Parameters: attempt=1 , run=18 , shard=12

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes960000913
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:466: condition failed to evaluate within 45s: from testutils.go:495: stream ingestion has not recorded any progress yet, waiting to advance pos 1697826416.571631979,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes960000913
--- FAIL: TestTenantStreamingMultipleNodes (285.81s)

Parameters: attempt=1 , run=2 , shard=12

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes2213655219
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:466: condition failed to evaluate within 45s: from testutils.go:495: stream ingestion has not recorded any progress yet, waiting to advance pos 1697827039.611150260,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes2213655219
--- FAIL: TestTenantStreamingMultipleNodes (401.79s)

Parameters: attempt=1 , run=16 , shard=12

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes199586692
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:264: condition failed to evaluate within 2m0s: from jobs_verification.go:100: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes199586692
--- FAIL: TestTenantStreamingMultipleNodes (431.11s)

Parameters: attempt=1 , run=17 , shard=12

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ 59a69ae0c5474a8b323afac269055bf6ce8afa34:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes2792238039
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:466: condition failed to evaluate within 45s: from testutils.go:495: stream ingestion has not recorded any progress yet, waiting to advance pos 1697826543.876371301,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes2792238039
--- FAIL: TestTenantStreamingMultipleNodes (311.45s)

Parameters: attempt=1 , run=7 , shard=12

Help

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

This test on roachdash | Improve this report!

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed on master @ bf9a22dc85683966ee65e84d3eeadf2b44185127:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestTenantStreamingMultipleNodes3891176763
    test_log_scope.go:81: use -show-logs to present logs inline

pkg/ccl/streamingccl/replicationtestutils/testutils.go:149: ((*TenantStreamingClusters).init)
	NOTICE: .WaitForTenantCapabilities() called via implicit interface TenantControlInterface;
HINT: consider using .TenantController().WaitForTenantCapabilities() instead.
    testutils.go:467: condition failed to evaluate within 45s: from testutils.go:496: stream ingestion has not recorded any progress yet, waiting to advance pos 1698090115.079705273,0
    panic.go:522: -- test log scope end --
test logs left over in: outputs.zip/logTestTenantStreamingMultipleNodes3891176763
--- FAIL: TestTenantStreamingMultipleNodes (328.41s)

Parameters: attempt=1 , run=14 , shard=12

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@rickystewart
Copy link
Collaborator

FYI: The test failure above was before #112827.

@msbutler
Copy link
Collaborator

Praying that #112827 fixed this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-remote-execution An issue found only using Bazel Remote Execution function. 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
Archived in project
Development

No branches or pull requests

3 participants