pkg/sql/schemachanger/schemachanger_test: TestConcurrentDeclarativeSchemaChanges failed #106732
Description
pkg/sql/schemachanger/schemachanger_test.TestConcurrentDeclarativeSchemaChanges failed with artifacts on master @ b19302fd436f7e8667b289677723e337d333bb50:
=== RUN TestConcurrentDeclarativeSchemaChanges
test_log_scope.go:167: test logs captured to: /artifacts/tmp/_tmp/3e4c90800e6eae84b5bf83507e7ef6e8/logTestConcurrentDeclarativeSchemaChanges1906842654
test_log_scope.go:81: use -show-logs to present logs inline
schemachanger_test.go:169:
Error Trace: pkg/sql/schemachanger/schemachanger_test_test/pkg/sql/schemachanger/schemachanger_test.go:169
Error: Should not be zero, but was 0
Test: TestConcurrentDeclarativeSchemaChanges
panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/3e4c90800e6eae84b5bf83507e7ef6e8/logTestConcurrentDeclarativeSchemaChanges1906842654
--- FAIL: TestConcurrentDeclarativeSchemaChanges (3.74s)
The failing assertion is
// The ALTER PRIMARY KEY schema change must have been blocked.
require.NotZero(t, alterPrimaryKeyBlockedCounter.Load())
This test on roachdash | Improve this report!
Jira issue: CRDB-29694
Metadata
Metadata
Assignees
Labels
Broken test (automatically or manually discovered).Originated from a bot.SQL Foundations Team (formerly SQL Schema + SQL Sessions)Failures and bugs on the master branch.Used to mark GA and release blockers, technical advisories, and bugs for 22.2Used to mark GA and release blockers, technical advisories, and bugs for 23.1Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.