Skip to content
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

an unstable SQL execution in copr-test #14280

Closed
iosmanthus opened this issue Dec 30, 2019 · 2 comments
Closed

an unstable SQL execution in copr-test #14280

iosmanthus opened this issue Dec 30, 2019 · 2 comments
Assignees
Labels
invalid priority/P2 The issue has P2 priority. severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Milestone

Comments

@iosmanthus
Copy link
Contributor

iosmanthus commented Dec 30, 2019

Bug Report

  1. What did you do?
    This is an unstable bug. Run make no-push-down in Add more make targets: `clean/no-push-down/push-down-without-v… tikv/copr-test#115. We will find at the very first beginning the following SQL will fail. After a while, it produces a correct result, an empty set.
SELECT EXP( `col_set` ) AS field1, `col_timestamp_key` % '2013-03-22' AS field2, DEGREES( '15:00:34.037137' ) AS field3 FROM `table1_int_autoinc` WHERE `col_binary_8_key` AND '2006-04-04 16:25:30.047980'

And here is the warning log:

[2019/12/30 14:30:39.569 +08:00] [WARN] [conn.go:688] ["command dispatched failed"] [conn=3] [connInfo="id:3, addr:127.0.0.1:57478 status:10, collation:utf8_general_ci, user:root"] [command=Query] [status="inTxn:0, autocommit:1"] [sql="SELECT EXP( `col_set` ) AS field1, `col_timestamp_key` % '2013-03-22' AS field2, DEGREES( '15:00:34.037137' ) AS field3 FROM `table1_int_autoinc` WHERE `col_binary_8_key` AND '2006-04-04 16:25:30.047980'"] [err="[types:1690]DOUBLE value is out of range in 'exp(cast(test.table1_int_autoinc.col_set))'\ngit.luolix.top/pingcap/errors.AddStack\n\t/home/iosmanthus/go/pkg/mod/github.com/pingcap/errors@v0.11.5-0.20190809092503-95897b64e011/errors.go:174\ngit.luolix.top/pingcap/parser/terror.(*Error).GenWithStackByArgs\n\t/home/iosmanthus/go/pkg/mod/github.com/pingcap/parser@v0.0.0-20191223023445-b93660cf3e4e/terror/terror.go:240\ngit.luolix.top/pingcap/tidb/expression.(*builtinExpSig).vecEvalReal\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/expression/builtin_math_vec.go:289\ngit.luolix.top/pingcap/tidb/expression.(*ScalarFunction).VecEvalReal\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/expression/scalar_function.go:51\ngit.luolix.top/pingcap/tidb/expression.evalOneVec\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/expression/chunk_executor.go:115\ngit.luolix.top/pingcap/tidb/expression.(*defaultEvaluator).run\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/expression/evaluator.go:51\ngit.luolix.top/pingcap/tidb/expression.(*EvaluatorSuite).Run\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/expression/evaluator.go:123\ngit.luolix.top/pingcap/tidb/executor.(*projectionWorker).run\n\t/home/iosmanthus/Projects/iosmanthus/copr-test/push-down-test/build/tidb_master/tidb-master/executor/projection.go:425\nruntime.goexit\n\t/usr/lib/golang/src/runtime/asm_amd64.s:1357"]
  1. TiDB version
Release Version: 180ea4f
Git Commit Hash: 180ea4fd69fc5bb57be872b68d30f484f9b95fc9
Git Branch: split-tests
UTC Build Time: 2019-12-30 06:29:44
GoVersion: go1.13.1
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
@qw4990
Copy link
Contributor

qw4990 commented Aug 26, 2020

Can we close it now? @iosmanthus

@fzhedu fzhedu added the priority/P2 The issue has P2 priority. label Aug 27, 2020
@scsldb scsldb added this to the v4.0.9 milestone Nov 4, 2020
@ichn-hu
Copy link
Contributor

ichn-hu commented Nov 10, 2020

Hi @iosmanthus @qw4990 , what's the current status of this issue? Is it already fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid priority/P2 The issue has P2 priority. severity/critical sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

7 participants