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

unstable test: TestAnalyzePartitionUnderV1Dynamic #38883

Closed
purelind opened this issue Nov 4, 2022 · 2 comments · Fixed by #38990
Closed

unstable test: TestAnalyzePartitionUnderV1Dynamic #38883

purelind opened this issue Nov 4, 2022 · 2 comments · Fixed by #38990
Assignees
Labels
component/test severity/major type/bug The issue is confirmed as a bug.

Comments

@purelind
Copy link
Contributor

purelind commented Nov 4, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

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

3. What did you see instead (Required)

analyze_test.go:2980: 
        	Error Trace:	/home/jenkins/.tidb/tmp/cbd54d2e94f3b8ea3be1e953ff68550a/sandbox/processwrapper-sandbox/6965/execroot/__main__/bazel-out/k8-fastbuild/bin/executor/analyzetest/analyzetest_test_/analyzetest_test.runfiles/__main__/executor/analyzetest/analyze_test.go:2980
        	Error:      	Not equal: 
        	            	expected: 3
        	            	actual  : 0
        	Test:       	TestAnalyzePartitionUnderV1Dynamic

link https://ci.pingcap.net/blue/organizations/jenkins/tidb-unit-test-bazel-with-cache/detail/tidb-unit-test-bazel-with-cache/6401/tests

4. What is your TiDB version? (Required)

@purelind purelind added the type/bug The issue is confirmed as a bug. label Nov 4, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 labels Nov 4, 2022
@ChenPeng2013 ChenPeng2013 removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 labels Nov 4, 2022
@mjonss
Copy link
Contributor

mjonss commented Nov 7, 2022

Looks like these logs are related (and same in #38882):

[2022/11/03 20:30:32.201 +08:00] [WARN] [plan_stats.go:106] ["SyncWaitStatsLoad timeout"]
[2022/11/03 20:30:32.202 +08:00] [WARN] [plan_stats.go:68] ["SyncWaitStatsLoad failed"]

@mjonss
Copy link
Contributor

mjonss commented Nov 9, 2022

There are other tests that are unstable as well (tested with running 100 instances concurrently), like TestSavedAnalyzeOptions.

Looks like the SyncWaitStatsLoad failure is the cause, and I will check if it is OK to fail or not (if OK, then some kind of retry would be needed for stabilising the tests).

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

Successfully merging a pull request may close this issue.

4 participants