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 #101281

Closed
cockroach-teamcity opened this issue Apr 12, 2023 · 36 comments
Closed
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-disaster-recovery
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Apr 12, 2023

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed with artifacts on release-23.1.0 @ f1921dbd499fd258a606c4e7180aff7b82b6f900:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2028868122
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2028868122
--- FAIL: TestTenantStreamingMultipleNodes (348.59s)

Parameters: TAGS=bazel,gss,deadlock

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

@cockroach-teamcity
Copy link
Member Author

ccl/streamingccl/streamingest.TestTenantStreamingMultipleNodes failed with artifacts on release-23.1.0 @ ada9871ea92cfc467b045a6a1b8ed2783a243c2f:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2738231713
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2738231713
--- FAIL: TestTenantStreamingMultipleNodes (358.93s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 5e9f0c062e6b166b76148f7a6e10c2f509658d37:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2588958697
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2588958697
--- FAIL: TestTenantStreamingMultipleNodes (353.47s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 3c51a373e8c272c5fd3fef0179321df51cbf401e:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3445688649
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3445688649
--- FAIL: TestTenantStreamingMultipleNodes (346.24s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ d9427da31576a61b9390d86258fd7ad4c35c88d5:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3572219691
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3572219691
--- FAIL: TestTenantStreamingMultipleNodes (350.18s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ d9427da31576a61b9390d86258fd7ad4c35c88d5:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2459707166
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2459707166
--- FAIL: TestTenantStreamingMultipleNodes (378.98s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ c7f71068d537c2f82f06f000299144c31d9ddf7a:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1527193457
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1527193457
--- FAIL: TestTenantStreamingMultipleNodes (333.93s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ dc5c429acb69496f1f7678bf41e608c05f1062d8:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes92037979
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes92037979
--- FAIL: TestTenantStreamingMultipleNodes (332.08s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 4524616140097c0f6b921e5d1e94ebd405f0809f:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1899089716
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1899089716
--- FAIL: TestTenantStreamingMultipleNodes (341.63s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 06fea49dd3b665758ff016a38622e3ce0f1ccfc5:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1459962836
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1459962836
--- FAIL: TestTenantStreamingMultipleNodes (354.59s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ ca2fae8b11a761af8ac7e5334aa5642c15dfb42f:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2581374049
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2581374049
--- FAIL: TestTenantStreamingMultipleNodes (354.53s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ ca2fae8b11a761af8ac7e5334aa5642c15dfb42f:

Fatal error:

panic: use of Span after Finish. Span: stream-ingestion-processor. Finish previously called at: <stack not captured. Set debugUseAfterFinish>

Stack:

goroutine 424858 [running]:
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).detectUseAfterFinish(0xc01080cbe0?)
	github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:181 +0x12b
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Tracer).startSpanGeneric(0xc00a986360, {0x70d9d00, 0xc018b93780}, {0x5b86cff, 0x16}, {{0x0}, 0x0, {0x0, 0x0, {{0x0, ...}, ...}, ...}, ...})
	github.com/cockroachdb/cockroach/pkg/util/tracing/tracer.go:1231 +0xa4e
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Tracer).StartSpanCtx(0xc014de0400?, {0x70d9d00?, 0xc018b93780?}, {0x5b86cff?, 0x16?}, {0xc00e1acc78?, 0x1?, 0x0?})
	github.com/cockroachdb/cockroach/pkg/util/tracing/tracer.go:1085 +0xde
github.com/cockroachdb/cockroach/pkg/util/tracing.ChildSpan({0x70d9d00, 0xc018b93780}, {0x5b86cff, 0x16})
	github.com/cockroachdb/cockroach/pkg/util/tracing/tracer.go:1584 +0x9c
github.com/cockroachdb/cockroach/pkg/ccl/streamingccl/streamclient.(*partitionedStreamSubscription).Subscribe(0xc00484ae10, {0x70d9d00?, 0xc018b93780?})
	github.com/cockroachdb/cockroach/pkg/ccl/streamingccl/streamclient/partitioned_stream_client.go:301 +0x65
github.com/cockroachdb/cockroach/pkg/util/ctxgroup.Group.GoCtx.func1()
	github.com/cockroachdb/cockroach/pkg/util/ctxgroup/ctxgroup.go:168 +0x25
golang.org/x/sync/errgroup.(*Group).Go.func1()
	golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
	golang.org/x/sync/errgroup/external/org_golang_x_sync/errgroup/errgroup.go:72 +0xa5
Log preceding fatal error

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes4056917108
    test_log_scope.go:79: use -show-logs to present logs inline

Parameters: TAGS=bazel,gss

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 with artifacts on release-23.1.0 @ 25a0174fb8e259fd3fdfbc2587a546d4433d1224:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1086640522
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1086640522
--- FAIL: TestTenantStreamingMultipleNodes (352.78s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ f23e5bca28bf8529d8afaea0aec072f9c0f000d1:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes9881328
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes9881328
--- FAIL: TestTenantStreamingMultipleNodes (376.91s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ afba2c1e66d787a39e0a13a125b33d940b2e1c54:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2498725180
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2498725180
--- FAIL: TestTenantStreamingMultipleNodes (353.88s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ f52cc7035ce190d2b705de87b1c0fe3b3b268f92:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2480497540
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2480497540
--- FAIL: TestTenantStreamingMultipleNodes (334.92s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ f1a130b93c47ddd9a11408d23f48cb6ee96eb38e:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1037017563
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1037017563
--- FAIL: TestTenantStreamingMultipleNodes (325.98s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ c227c00ea38887929aecdeb400a4d1104eb9d7a8:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1145525862
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1145525862
--- FAIL: TestTenantStreamingMultipleNodes (320.45s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 344d752c483d39dedf7e2282932aa83b30301607:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes4113118360
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes4113118360
--- FAIL: TestTenantStreamingMultipleNodes (327.73s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 36ee6c802b18ab8a544b20d03dec68d82d99604b:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2305269745
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2305269745
--- FAIL: TestTenantStreamingMultipleNodes (322.68s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 360923fbbf41db7a30e0b5af66b7b2fbf04fd290:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1245533371
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1245533371
--- FAIL: TestTenantStreamingMultipleNodes (328.70s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 5efa6ff20f56d2ce8111b710190d1b378adb26d9:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3402080292
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3402080292
--- FAIL: TestTenantStreamingMultipleNodes (370.52s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 5efa6ff20f56d2ce8111b710190d1b378adb26d9:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2716544594
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2716544594
--- FAIL: TestTenantStreamingMultipleNodes (324.52s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 5efa6ff20f56d2ce8111b710190d1b378adb26d9:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2586475758
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes2586475758
--- FAIL: TestTenantStreamingMultipleNodes (507.40s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 5efa6ff20f56d2ce8111b710190d1b378adb26d9:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3760846929
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3760846929
--- FAIL: TestTenantStreamingMultipleNodes (474.37s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 29ed08a512389e42ccccdde0906e34a301c28b4a:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3357281147
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3357281147
--- FAIL: TestTenantStreamingMultipleNodes (459.28s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 29ed08a512389e42ccccdde0906e34a301c28b4a:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3669596736
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3669596736
--- FAIL: TestTenantStreamingMultipleNodes (436.23s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 29ed08a512389e42ccccdde0906e34a301c28b4a:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1446519293
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1446519293
--- FAIL: TestTenantStreamingMultipleNodes (466.22s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes4284324032
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes4284324032
--- FAIL: TestTenantStreamingMultipleNodes (459.24s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1144938259
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1144938259
--- FAIL: TestTenantStreamingMultipleNodes (370.04s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1228098453
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1228098453
--- FAIL: TestTenantStreamingMultipleNodes (375.33s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes258813514
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
--- FAIL: TestTenantStreamingMultipleNodes (364.52s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes987824660
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes987824660
--- FAIL: TestTenantStreamingMultipleNodes (423.36s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1154652960
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1154652960
--- FAIL: TestTenantStreamingMultipleNodes (451.75s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3088376125
    test_log_scope.go:79: use -show-logs to present logs inline
    testutils.go:181: condition failed to evaluate within 2m0s: expected job status succeeded, but got running
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes3088376125
--- FAIL: TestTenantStreamingMultipleNodes (402.53s)

Parameters: TAGS=bazel,gss,deadlock

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 with artifacts on release-23.1.0 @ 358e0d87912365b8976c55ab9b3292e999cf720d:

=== RUN   TestTenantStreamingMultipleNodes
    test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1061436632
    test_log_scope.go:79: use -show-logs to present logs inline
    replication_stream_e2e_test.go:680: 
        	Error Trace:	github.com/cockroachdb/cockroach/pkg/ccl/streamingccl/streamingest/replication_stream_e2e_test.go:680
        	Error:      	"1" is not greater than "1"
        	Test:       	TestTenantStreamingMultipleNodes
    panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/90c1b75d835f45b8488807abb5b1092d/logTestTenantStreamingMultipleNodes1061436632
--- FAIL: TestTenantStreamingMultipleNodes (42.02s)

Parameters: TAGS=bazel,gss

Help

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

Same failure on other branches

This test on roachdash | Improve this report!

@msbutler
Copy link
Collaborator

.0 branch no longer relevant. closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. T-disaster-recovery
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants