We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please answer these questions before submitting your issue. Thanks!
I'm testing paging protocol by running tidb UT with a real TiKV using this branch #35647
tiup playground nightly --mode tikv-slim cd planner/core go test -run ^TestPushdownDistinctEnable$ -with-tikv 127.0.0.1:2379
Success
--- FAIL: TestPushdownDistinctEnable (3.81s) result.go:49: Error Trace: result.go:49 physical_plan_test.go:1143 physical_plan_test.go:1056 Error: Not equal: expected: "[1 2]\n" actual : "[2 2]\n" Diff: --- Expected +++ Actual @@ -1,2 +1,2 @@ -[1 2] +[2 2] Test: TestPushdownDistinctEnable Messages: sql:select /*+ HASH_AGG() */ a, count(distinct a) from t;, args:[] FAIL exit status 1 FAIL github.com/pingcap/tidb/planner/core 3.856s
master
commit 47a4f3a017768dda0b9a826451486c5539bc8427 (HEAD -> master, origin/master, origin/HEAD) Author: Weizhen Wang <wangweizhen@pingcap.com> Date: Wed Jun 29 20:16:40 2022 +0800 *: enable unconvert (#35821) ref pingcap/tidb#35345
The text was updated successfully, but these errors were encountered:
TestPushdownDistinctEnable already moved into integration test. It runs good on unistore and tikv env, so we could close this issue right now.
TestPushdownDistinctEnable
Sorry, something went wrong.
No branches or pull requests
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
I'm testing paging protocol by running tidb UT with a real TiKV using this branch #35647
2. What did you expect to see? (Required)
Success
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: