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.

Sign up for GitHub

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

Jump to bottom

Timeout test `builtin_time_vec_test.go:579: testVectorizeSuite2.TestVectorizedBuiltinTimeFunc #27449

Closed
Tracked by #25899
zhouqiang-cl opened this issue Aug 20, 2021 · 2 comments
Closed
Tracked by #25899

Timeout test `builtin_time_vec_test.go:579: testVectorizeSuite2.TestVectorizedBuiltinTimeFunc #27449

zhouqiang-cl opened this issue Aug 20, 2021 · 2 comments
Labels
component/test severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@zhouqiang-cl
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

[2021-08-20T03:32:52.599Z] PASS: builtin_time_vec_test.go:579: testVectorizeSuite2.TestVectorizedBuiltinTimeFunc	6.423s

1. Minimal reproduce step (Required)

in ci https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_check_2/detail/tidb_ghpr_check_2/27683/pipeline

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)
@zhouqiang-cl zhouqiang-cl added the type/bug The issue is confirmed as a bug. label Aug 20, 2021
@zhouqiang-cl zhouqiang-cl mentioned this issue Aug 20, 2021
Closed
@karuppiah7890
Copy link
Contributor

karuppiah7890 commented Sep 13, 2021 •
edited
Loading

Noticed this in my local too

...
The following test cases take too long to finish:
...
PASS: builtin_time_vec_test.go:579: testVectorizeSuite2.TestVectorizedBuiltinTimeFunc	8.769s
...
...
The following test cases take too long to finish:
...
PASS: builtin_time_vec_test.go:579: testVectorizeSuite2.TestVectorizedBuiltinTimeFunc	5.569s
...

@jebter jebter added the sig/execution SIG execution label Dec 7, 2021
@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/test severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jebter @karuppiah7890 @zhouqiang-cl