ccl/crosscluster/physical: TestStreamingRegionalConstraint failed

[cockroach-teamcity]

ccl/crosscluster/physical.TestStreamingRegionalConstraint failed on release-24.2.1-rc @ 23a8ffc28d2f31eef0cd13eca69693dc249d1196:

=== RUN   TestStreamingRegionalConstraint
    test_log_scope.go:170: test logs captured to: outputs.zip/logTestStreamingRegionalConstraint1898422763
    test_log_scope.go:81: use -show-logs to present logs inline
    replication_stream_e2e_test.go:1386: -- test log scope end --
test logs left over in: outputs.zip/logTestStreamingRegionalConstraint1898422763
--- FAIL: TestStreamingRegionalConstraint (182.16s)
    --- FAIL: TestStreamingRegionalConstraint/fromSys=true (102.59s)

Parameters:

• attempt=1
• deadlock=true
• run=2
• shard=9

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

[tbg]

I just had this fail here: here on #137750. I have no idea what the error is. I downloaded the artifacts and the logs all look like a clean shutdown.

[dt]

In the full test shard log we see testcluster.go:485: unable to retrieve conf reader: span configs not available, but the output in that area looks a little funny -- maybe something somewhere printed 108 to stderr at the wrong moment -- so engflow isn't correctly including that line with the specific test's logs and you only see it in the whole shard log.

That line does however correspond to a fatal during server start:

		if err := tc.WaitForFullReplication(); err != nil {
			tc.Stopper().Stop(ctx)
			t.Fatal(err)
		}
	}```

[dt]

I don't think the failure @tbg linked to has anything to do with this test. I just saw the same error in a failed test in kvcoord's TestMuxRangeFeedDoesNotStallOnError over here: https://mesolite.cluster.engflow.com/invocations/default/69c843f7-e5a7-4ff6-9a70-65b9b58bf0ef

[arulajmani]

The span config related failures should be papered over by 71cdabc.

[blathers-crl]

Based on the specified backports for linked PR #137925, I applied the following new label(s) to this issue: branch-release-23.2, branch-release-24.1. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}