-
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: unoptimized-query-oracle/disable-rules=half/rand-multi-region failed [BIT(0) type needed for distSQL] #131346
Comments
roachtest.unoptimized-query-oracle/disable-rules=half/rand-multi-region failed with artifacts on master @ dcce4cafa234525fc859d32745c11ed87890dc7b:
Parameters:
Same failure on other branches
|
I'm unable to reproduce the difference in the outputs when running:
However, the output on master is different from the output on v24.2.0 in exactly the same way that the failure is above. On v24.2.0:
On master:
This is quite peculiar. I'll try to find the commit that caused the change. |
I was just able to reproduce one of the inconsistent results above. It appears to happen non-deterministically, which will make it more difficult to pin down. |
Drew and I believe this is related to #129007. I'm trying to confirm that now. |
We also don't think this is a release-blocker, so moving to GA-blocker. |
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes cockroachdb#131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes cockroachdb#131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout. roachtest.unoptimized-query-oracle/disable-rules=half/rand-multi-region failed with artifacts on master @ 1e5b3c212b45419c960038718c48a5dd75a111a0:
Parameters:
|
132944: sql: add `BIT(0)` type r=mgartner a=mgartner #### sql: add `BIT(0)` type The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes #131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None Co-authored-by: Marcus Gartner <[email protected]>
132944: sql: add `BIT(0)` type r=mgartner a=mgartner #### sql: add `BIT(0)` type The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes #131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None Co-authored-by: Marcus Gartner <[email protected]>
Based on the specified backports for linked PR #132944, I applied the following new label(s) to this issue: branch-release-23.2, branch-release-24.1, branch-release-24.2. 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 `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes #131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes #131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes cockroachdb#131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
The `BIT(0)` type is now supported. It represents a `BIT` type with unspecified length. This is a divergence from Postgres which does not allow this type and has no way to represent it in SQL. It is required in order for it to be correctly serialized into SQL and evaluated during distributed query execution.VARBIT cannot be used because it has a different OID. Fixes #131346 There is no release note because this bug is not present in any previous releases and there is no need to document this new type. Release note: None
roachtest.unoptimized-query-oracle/disable-rules=half/rand-multi-region failed with artifacts on master @ 41084720464c4144f64d9ddcb46508b4d762c4e8:
Parameters:
ROACHTEST_arch=amd64
ROACHTEST_cloud=gce
ROACHTEST_coverageBuild=false
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_fs=ext4
ROACHTEST_localSSD=true
ROACHTEST_runtimeAssertionsBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-42511
The text was updated successfully, but these errors were encountered: