Closed cockroach-teamcity closed 1 month ago
server.TestClusterConnectivity failed with artifacts on release-23.2.11-rc @ 701e687d9491360b9f080c07bcb70e463184d2e4:
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
=== RUN TestClusterConnectivity/topology=2
test_server_shim.go:146: cluster virtualization disabled in global scope due to issue: #76378 (expected label: C-bug)
pkg/server_test/pkg/server/connectivity_test.go:210: (TestClusterConnectivity.func2.1.1)
NOTICE: .AdvRPCAddr() called via implicit interface ApplicationLayerInterface;
HINT: consider using .ApplicationLayer().AdvRPCAddr() instead.
TIP: consider replacing the test server initialization from:
ts, ... := serverutils.StartServer(t, ...)
defer ts.Stopper().Stop(...)
to:
srv, ... := serverutils.StartServer(t, ...)
defer srv.Stopper().Stop(...)
ts := srv.ApplicationLayer()
See also: https://go.crdb.dev/p/testserver-and-cluster-virtualization
pkg/server_test/pkg/server/connectivity_test.go:232: (TestClusterConnectivity.func2.1.2)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
pkg/server_test/pkg/server/connectivity_test.go:248: (TestClusterConnectivity.func2.1.3)
NOTICE: .StorageClusterID() called via implicit interface StorageLayerInterface;
HINT: consider using .StorageLayer().StorageClusterID() instead.
Parameters:
TAGS=bazel,gss
stress=true
See also: How To Investigate a Go Test Failure (internal)
- #130486 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.2 release-blocker] - #130484 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.1.5-rc release-blocker] - #130415 server: TestClusterConnectivity failed [C-test-failure O-robot T-server-and-security branch-release-23.1 release-blocker] - #130239 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-23.2 release-blocker] - #130238 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.1 release-blocker]
I'm closing this one off as 23.2.11 has been published and the rc branch has been removed. The issue only impacts testing, and there’s no issue with the server itself since the license enforcer is currently disabled. The problem only arises due to parallel test servers running in the same process.
server.TestClusterConnectivity failed with artifacts on release-23.2.11-rc @ c70f43425e66787952e3252f84bc6340c128709d:
Parameters:
TAGS=bazel,gss
stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
- #130486 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.2 release-blocker] - #130484 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.1.5-rc release-blocker] - #130415 server: TestClusterConnectivity failed [C-test-failure O-robot T-server-and-security branch-release-23.1 release-blocker] - #130239 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-23.2 release-blocker] - #130238 server: TestClusterConnectivity failed [C-test-failure O-robot branch-release-24.1 release-blocker]
/cc @cockroachdb/unowned
This test on roachdash | Improve this report!
Jira issue: CRDB-42100