-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: sqlsmith/setup=empty/setting=no-mutations failed #68308
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
E-quick-win
Likely to be a quick win for someone experienced.
O-roachtest
O-robot
Originated from a bot.
T-sql-queries
SQL Queries Team
Comments
cockroach-teamcity
added
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
labels
Aug 1, 2021
@otan does this seem related to any recent work you have been doing? |
Nope, this is a problem in v21.1.
the problem is the NULL family doesn't exist as a cast. |
I'll take a look. |
This was referenced Aug 10, 2021
Removing release-blocker label since this was also a bug in 21.1
|
rytaft
removed
the
release-blocker
Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked.
label
Aug 23, 2021
craig bot
pushed a commit
that referenced
this issue
Aug 23, 2021
68627: sql: fix cast from unknown to unknown r=mgartner a=mgartner Previously, an implicit cast performed in a set operation, like `UNION`, on a tuple type with an unknown inner type would cause an internal error. The cast failed because the volatility of a cast from unknown to unknown was not specified in the `validCasts` list. This commit fixes the issue by marking a such a cast as immutable. Fixes #68308 Release note (bug fix): A bug has been fixed that caused internal errors with set operations, like `UNION`, and columns with tuple types that contained constant `NULL` values. This bug was introduced in version 20.2. 69253: sql: change column in tenant_usage table r=RaduBerinde a=RaduBerinde The tenant usage table currently has the "last update" timestamp as an instance-only field. This field is necessary for the per-tenant state as well (it corresponds to the current bucket level). This change renames the `instance_last_update` column to `last_update` and moves it up to the group of columns that apply to all rows. Since this table was introduced only on `master`, we don't add a new migration. Release justification: category 2, code only used for Serverless. Release note: None 69261: settings: retire a setting only present on 21.1 branch r=yuzefovich a=yuzefovich `sql.distsql.prefer_local_execution.enabled` was introduced during a backport to 21.1 branch and is only present on that branch. This commit is retiring that setting on 21.2 branch. Retiring a setting introduced in #68613. Release note: None Release justification: This commit is safe for this release because it is kinda non-production code change. Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Radu Berinde <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
Aug 24, 2021
Previously, an implicit cast performed in a set operation, like `UNION`, on a tuple type with an unknown inner type would cause an internal error. The cast failed because the volatility of a cast from unknown to unknown was not specified in the `validCasts` list. This commit fixes the issue by marking a such a cast as immutable. Fixes #68308 Release note (bug fix): A bug has been fixed that caused internal errors with set operations, like `UNION`, and columns with tuple types that contained constant `NULL` values. This bug was introduced in version 20.2.
blathers-crl bot
pushed a commit
that referenced
this issue
Aug 24, 2021
Previously, an implicit cast performed in a set operation, like `UNION`, on a tuple type with an unknown inner type would cause an internal error. The cast failed because the volatility of a cast from unknown to unknown was not specified in the `validCasts` list. This commit fixes the issue by marking a such a cast as immutable. Fixes #68308 Release note (bug fix): A bug has been fixed that caused internal errors with set operations, like `UNION`, and columns with tuple types that contained constant `NULL` values. This bug was introduced in version 20.2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
E-quick-win
Likely to be a quick win for someone experienced.
O-roachtest
O-robot
Originated from a bot.
T-sql-queries
SQL Queries Team
roachtest.sqlsmith/setup=empty/setting=no-mutations failed with artifacts on master @ 31af9e32a55a166166e9ba9c5327b7cd847ae236:
Reproduce
See: roachtest README
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: