databend
databend copied to clipboard
ci(test): add tpch stateless test of factor 0.1
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
Add tpch stateless test of factor 0.1.
Results have no difference between databend and postsql.
Fixes #6689
The latest updates on your projects. Learn more about Vercel for Git โ๏ธ
| Name | Status | Preview | Updated |
|---|---|---|---|
| databend | โ Ready (Inspect) | Visit Preview | Aug 23, 2022 at 1:36AM (UTC) |
This pull request's title is not fulfill the requirements. @edPanda please update it ๐.
Valid format:
fix(query): fix group by string bug
^ ^---------------------^
| |
| +-> Summary in present tense.
|
+-------> Type: feat, fix, refactor, ci, build, docs, website, chore
Valid types:
feat: this PR introduces a new feature to the codebasefix: this PR patches a bug in codebaserefactor: this PR changes the code base without new features or bugfixci|build: this PR changes build/testing/ci stepsdocs|website: this PR changes the documents or websiteschore: this PR only has small changes that no need to record
The data is too large to commit into git history. I suggest uploading them into a website like https://repo.databend.rs/.
Is it possible to download the data from other places? This PR will add 869k lines.
@edPanda Thanks for the contribution
- I have upload the datasets to
http://repo.databend.rs/dataset/stateful/tpch.tar.gz, you can modify the script in13_0000_prepare.shusingwgetto download the data.
โ curl --HEAD http://repo.databend.rs/dataset/stateful/tpch.tar.gz
HTTP/1.1 200 OK
Content-Type: application/x-tar
Content-Length: 30371995
Connection: keep-alive
Date: Fri, 22 Jul 2022 03:35:03 GMT
Last-Modified: Fri, 22 Jul 2022 03:30:05 GMT
ETag: "f2fc54240b1162fcfa6dd586eb2ab129-4"
Accept-Ranges: bytes
Server: AmazonS3
X-Cache: Miss from cloudfront
Via: 1.1 79e5bd56174a0ac9fbc66556743812d6.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: HKG62-C2
X-Amz-Cf-Id: XXDSDDvylZN71BzeA9jGMyk6cbN95cyVJbYVZ7_5zNElWJMQliMHtg==
- You can migrate these the directory to be
statefultests.
Better to give it a force-push, this can remove the history caused by large tests data.
@sundy-li Thanks a lot.
Every time I run 'make stateless-test', I find that the last few digits of the decimal point of some sql results are different. Can you help me find the reason? Like sql1 sql5 and so on.
Having 9 errors! 258 tests passed. 0 tests skipped.
The failure tests:
/workspace/tests/suites/0_stateless/13_tpch/13_0001_q1.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0005_q5.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0009_q9.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0010_q10.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0014_q14.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0015_q15.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0017_q17.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0019_q19.sql
/workspace/tests/suites/0_stateless/13_tpch/13_0022_q22.sql
This looks strange, like:
--- /workspace/tests/suites/0_stateless/13_tpch/13_0022_q22.result 2022-07-22 23:27:25.080615735 +0000
+++ /workspace/tests/suites/0_stateless/13_tpch/13_0022_q22.stdout 2022-07-22 23:33:36.822927253 +0000
@@ -2,6 +2,6 @@
17 96 722560.1499999998
18 99 738012.5199999999
23 93 708285.2499999998
-29 85 632693.4599999998
-30 87 646748.02
-31 87 647372.4999999999
+29 85 632693.4599999997
+30 87 646748.0199999999
+31 87 647372.4999999998
cc @xudong963
Seems related to https://github.com/datafuselabs/databend/issues/6213
Q16 result is too large, we can use order by + limit to output shorter result.
I find that the last few digits of the decimal point of some sql results are different.
We can wrap the query with truncate temporarily until we have decimal types.
ok, thanks!
Since it has been a long time since the last submission, I will re-check the results with pg tomorrow.
I think we can also add tpch q6 (previously not added due to accuracy issues) @edPanda
We can add this data directory into .gitignore
I found that the calculation results of sql5 in the cluster of the mac system are very different, and the standalone and cluster of linux do not have the wget command, which causes the test to fail. Here are results of sql5 in the cluster of the mac system: -CHINA 7822103.0 -INDIA 6376121.508 -JAPAN 6000077.218 -INDONESIA 5580475.402 -VIETNAM 4497840.546 +CHINA 2426891.126 +VIETNAM 1946778.709 +JAPAN 1702347.973 +INDONESIA 1579815.696 +INDIA 1169566.051
I found that the calculation results of sql5 in the cluster of the mac system are very different,
It's optional ci, we will take deep look into cc @zhang2014
the standalone and cluster of linux do not have the wget command, which causes the test to fail.
@everpcpc Can u help this?
I found that the calculation results of sql5 in the cluster of the mac system are very different,
It's optional ci, we will take deep look into cc @zhang2014
the standalone and cluster of linux do not have the wget command, which causes the test to fail.
@everpcpc Can u help this?
maybe we can use curl instead of wget
I found that the calculation results of sql5 in the cluster of the mac system are very different, and the standalone and cluster of linux do not have the wget command, which causes the test to fail. Here are results of sql5 in the cluster of the mac system: -CHINA 7822103.0 -INDIA 6376121.508 -JAPAN 6000077.218 -INDONESIA 5580475.402 -VIETNAM 4497840.546 +CHINA 2426891.126 +VIETNAM 1946778.709 +JAPAN 1702347.973 +INDONESIA 1579815.696 +INDIA 1169566.051
Linux not work too:
13_0005_q5: [ FAIL ] - result differs with:
--- /workspace/tests/suites/0_stateless/13_tpch/13_0005_q5.result 2022-08-21 13:31:21.715785826 +0000
+++ /workspace/tests/suites/0_stateless/13_tpch/13_0005_q5.stdout 2022-08-21 13:34:04.362243534 +0000
@@ -1,5 +1,5 @@
-CHINA 7822103.0
-INDIA 6376121.508
-JAPAN 6000077.218
-INDONESIA 5580475.402
-VIETNAM 4497840.546
+CHINA 2426891.126
+VIETNAM 1946778.709
+JAPAN 170[234](https://github.com/datafuselabs/databend/runs/7939197859?check_suite_focus=true#step:4:245)7.973
+INDONESIA 1579815.696
+INDIA 1169566.051
https://github.com/datafuselabs/databend/runs/7939197859?check_suite_focus=true#step:4:241
cc @xudong963
Can sql5 be skipped to let this pr end๏ผ
Can sql5 be skipped to let this pr end๏ผ
Yes, you can uncomment the test.
@mergify update
update
โ Branch has been successfully updated
How about making a squash on this PR so that we don't introduce not related changes like delete out.log?