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: TestTenantStreamingUnavailableStreamAddress failed #105956

Closed
cockroach-teamcity opened this issue Jul 1, 2023 · 7 comments · Fixed by #106310
Closed
Assignees
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. skipped-test sync-me T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Jul 1, 2023

ccl/streamingccl/streamingest.TestTenantStreamingUnavailableStreamAddress failed with artifacts on release-23.1 @ e12e85479312972b551677203849d29aeb38ad5f:

=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2756112255
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:367: condition failed to evaluate within 45s: stream ingestion has not recorded any progress yet, waiting to advance pos 1688195267.796178305,0
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2756112255
--- FAIL: TestTenantStreamingUnavailableStreamAddress (500.33s)

Parameters: TAGS=bazel,gss,deadlock

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-29284

@cockroach-teamcity cockroach-teamcity added branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-disaster-recovery labels Jul 1, 2023
@cockroach-teamcity cockroach-teamcity added this to the 23.1 milestone Jul 1, 2023
@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingUnavailableStreamAddress failed with artifacts on release-23.1 @ e12e85479312972b551677203849d29aeb38ad5f:

=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2276726807
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:367: condition failed to evaluate within 45s: stream ingestion has not recorded any progress yet, waiting to advance pos 1688281123.781038089,0
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2276726807
--- FAIL: TestTenantStreamingUnavailableStreamAddress (532.68s)

Parameters: TAGS=bazel,gss,deadlock

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.TestTenantStreamingUnavailableStreamAddress failed with artifacts on release-23.1 @ e12e85479312972b551677203849d29aeb38ad5f:

=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress809722336
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:367: condition failed to evaluate within 45s: stream ingestion has not recorded any progress yet, waiting to advance pos 1688368802.484397016,0
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress809722336
--- FAIL: TestTenantStreamingUnavailableStreamAddress (578.63s)

Parameters: TAGS=bazel,gss,deadlock

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.TestTenantStreamingUnavailableStreamAddress failed with artifacts on release-23.1 @ a26ee7efd223c92cda531152837302f03a14f461:

=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress4241893779
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:367: condition failed to evaluate within 45s: stream ingestion has not recorded any progress yet, waiting to advance pos 1688450696.941843740,0
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress4241893779
--- FAIL: TestTenantStreamingUnavailableStreamAddress (593.06s)

Parameters: TAGS=bazel,gss,deadlock

Help

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

This test on roachdash | Improve this report!

@tbg
Copy link
Member

tbg commented Jul 4, 2023

#106104 also got this on master here. Seems unrelated. Also, this seems to have started failing very regularly on 23.1, did something get backported?

test_server_shim.go:467: migration-job-find-already-completed: failed to connect to n1 at 127.0.0.1:43615: initial connection heartbeat failed: grpc: connection error: desc = "error reading server preface: http2: frame too large" [code 14/Unavailable]

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingUnavailableStreamAddress failed with artifacts on release-23.1 @ f1108313b2b51ffab176b6b230bcc15b0259f170:

=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress3527897146
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:367: condition failed to evaluate within 45s: waiting for stream ingestion job progress 1688541124.298665829,0 to advance beyond 1688541133.778928428,0
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress3527897146
--- FAIL: TestTenantStreamingUnavailableStreamAddress (507.43s)

Parameters: TAGS=bazel,gss,deadlock

Help

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

This test on roachdash | Improve this report!

@tbg
Copy link
Member

tbg commented Jul 5, 2023

and again here: https://teamcity.cockroachdb.com/viewLog.html?buildId=10786073&buildTypeId=Cockroach_BazelEssentialCi

replication_stream_e2e_test.go:542: error executing 'SELECT * FROM d.t1': pq: failed to connect to n1 at 127.0.0.1:35415: initial connection heartbeat failed: grpc: client cluster ID "6b445207-5c57-4bc2-b1b5-8b62627806f3" doesn't match server cluster ID "40f5a19a-3ff0-4930-ba72-bdb97e8bf3df" [code 2/Unknown]

msbutler added a commit to msbutler/cockroach that referenced this issue Jul 5, 2023
craig bot pushed a commit that referenced this issue Jul 5, 2023
106149: c2c: skip TestTenantStreamingUnavailableStreamAddress r=msbutler a=msbutler

Informs #105956

Release note: None

Co-authored-by: Michael Butler <[email protected]>
blathers-crl bot pushed a commit that referenced this issue Jul 5, 2023
@lidorcarmel lidorcarmel self-assigned this Jul 5, 2023
craig bot pushed a commit that referenced this issue Jul 13, 2023
106310: streamingest: unskip a multi-node c2c test, and skip under deadlock r=lidorcarmel a=lidorcarmel

These tests are slow and flaky under deadlock.

Epic: none
Fixes: #105956
Fixes: #99900

Release note: None

106765: rfcs: rename the filename to adhere to the pattern r=yuzefovich a=yuzefovich

Recently merged RFC on query SST metrics was missing the prepended date in the filename.

Epic: None.

Release note: None

Co-authored-by: Lidor Carmel <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
@craig craig bot closed this as completed in 8f009ec Jul 13, 2023
lidorcarmel added a commit to lidorcarmel/cockroach that referenced this issue Jul 13, 2023
These tests are slow and flaky under deadlock.

Epic: none
Fixes: cockroachdb#105956
Fixes: cockroachdb#99900

Release note: None
lidorcarmel added a commit to lidorcarmel/cockroach that referenced this issue Jul 14, 2023
These tests are slow and flaky under deadlock.

Epic: none
Fixes: cockroachdb#105956
Fixes: cockroachdb#99900

Release note: None
@cucaroach
Copy link
Contributor

I just hit this variation in 23.1 CI:

Failed
=== RUN   TestTenantStreamingUnavailableStreamAddress
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2833981180
    test_log_scope.go:79: use -show-logs to present logs inline
    replication_stream_e2e_test.go:514: error executing 'SELECT * FROM d.t1': pq: no inbound stream connection
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingUnavailableStreamAddress2833981180
--- FAIL: TestTenantStreamingUnavailableStreamAddress (50.53s)

https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_BazelEssentialCi/10949986?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&expandBuildChangesSection=true&expandBuildProblemsSection=true&expandBuildTestsSection=true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release-23.1 Used to mark GA and release blockers, technical advisories, and bugs for 23.1 C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. skipped-test sync-me T-disaster-recovery
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants