-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
pkg/ccl/testccl/workload/schemachange/schemachange_test: TestWorkload failed [validation of column ... NOT NULL failed] #139816
Comments
This flaked on master for me: https://mesolite.cluster.engflow.com/invocations/default/b1d87c4c-fb2a-48b6-91e6-8f49dd1710ad |
pkg/ccl/testccl/workload/schemachange/schemachange_test.TestWorkload failed on release-24.3 @ 303bfcd84f0820ab42ac5bc2384e93ad90160d57:
Parameters:
Same failure on other branches
|
Previously, tests for dropping columns with not null constraints did not work correctly because of a syntax error. To address this, this patch fixes those tests and adds an additional drop test for not null stored columns. Informs: cockroachdb#139816 Release note: None
The latest failure is a side effect of a CTAS followed by a NOT NULL constraint:
|
The logs for the older failures are gone :(, so updating this for the latest one |
The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: cockroachdb#139816 Release note: None
141431: workload/schemachanger: handle not null violations for new tables r=fqazi a=fqazi The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: #139816 Release note: None Co-authored-by: Faizan Qazi <[email protected]>
Based on the specified backports for linked PR #141431, I applied the following new label(s) to this issue: branch-release-24.1, branch-release-25.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. |
The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: #139816 Release note: None
The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: #139816 Release note: None
The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: cockroachdb#139816 Release note: None
The workload previously assumed that NOT NULL constraint violations would only occur during the commit phase of ALTER COLUMN... SET NULL statements. However, these errors can also occur during statement execution for newly created tables. This patch addresses this issue by adding NOT NULL violation errors to the list of potential execution errors. Fixes: cockroachdb#139816 Release note: None
pkg/ccl/testccl/workload/schemachange/schemachange_test.TestWorkload failed on release-24.3 @ 3bb549350582192ffa091bfecba15527e545e30b:
Parameters:
attempt=1
run=25
shard=1
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-46834
The text was updated successfully, but these errors were encountered: