-
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=all/rand-tables failed #128296
Comments
roachtest.unoptimized-query-oracle/disable-rules=all/rand-tables failed with artifacts on release-23.1 @ 7748ab2d671c6e8d021af1ca577d2de4578751db:
Parameters:
Same failure on other branches
|
roachtest.unoptimized-query-oracle/disable-rules=all/rand-tables failed with artifacts on release-23.1 @ fc515e47e7f23977cf83f5696102266224c6ff03:
Parameters:
Same failure on other branches
|
I reduced the first failure to: CREATE TABLE t (
b INT4,
c FLOAT4,
d FLOAT4 AS (abs(c)) VIRTUAL
);
INSERT INTO t (c, b) VALUES (-1.1445338726043701, 0);
SET testing_optimizer_disable_rule_probability = 1;
SELECT abs(c), d FROM t ORDER BY b NULLS LAST;
-- abs | d
-- ---------------------+------------
-- 1.1445338726043701 | 1.1445339
-- (1 row)
RESET testing_optimizer_disable_rule_probability;
SELECT abs(c), d FROM t ORDER BY b NULLS LAST;
-- abs | d
-- ---------------------+---------------------
-- 1.1445338726043701 | 1.1445338726043701
-- (1 row) All the other failures appear to be the same problem. |
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs cockroachdb#128296 Release note: None
Interestingly, this does not reproduce on 23.2+. I'll try to hunt down the commit that fixed this. |
It looks like #105736 fixed this particular case. I'll backport it to 23.1. |
128843: roachtest: fix `admission-control/disk-bandwidth-limiter` on azure r=sumeerbhola a=aadityasondhi The CRDB data mount is different on azure when compared to AWS and GCE. We use `sda1` instead of `data1` in this case. Fixes: #128364. Release note: None 128932: catalog: rename ByID to ByIDWithoutLeased r=rafiss a=rafiss This makes the function name much more clear. Previously, it would be easy to assume that ByID would also include leased descriptors. fixes #99506 Release note: None 128985: kvflowcontrolpb,kvserverpb: add AdmittedResponseForRange r=kvoli a=sumeerbhola For piggybacking a MsgAppResp message from a follower to the leader, to advance admitted. Also, RaftMessageRequest.AdmittedResponse contains these piggybacked messages Informs #128309 Epic: CRDB-37515 Release note: None 128988: sql/randgen: do not generate expressions of type FLOAT4 r=mgartner a=mgartner There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs #128296 Release note: None Co-authored-by: Aaditya Sondhi <[email protected]> Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: sumeerbhola <[email protected]> Co-authored-by: Marcus Gartner <[email protected]>
I'm going to close this as all the bugs mentioned above are tracked by other issues. |
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs cockroachdb#128296 Release note: None
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs cockroachdb#128296 Release note: None
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs #128296 Release note: None
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs #128296 Release note: None
There are several known issues with the `FLOAT4` type. Our randomized tests commonly fail due to these issues. They are not trivially fixed, so for now we'll stop generating columns and expressions of type `FLOAT4` in randomized tests. Informs #128296 Release note: None
roachtest.unoptimized-query-oracle/disable-rules=all/rand-tables failed with artifacts on release-23.1 @ 7748ab2d671c6e8d021af1ca577d2de4578751db:
Parameters:
ROACHTEST_arch=arm64
ROACHTEST_cloud=gce
ROACHTEST_cpu=4
ROACHTEST_encrypted=false
ROACHTEST_metamorphicBuild=false
ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-40927
The text was updated successfully, but these errors were encountered: