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

flaky test TestKillAutoAnalyzeIndex #51968

Closed
lance6716 opened this issue Mar 21, 2024 · 1 comment
Closed

flaky test TestKillAutoAnalyzeIndex #51968

lance6716 opened this issue Mar 21, 2024 · 1 comment
Labels
sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@lance6716
Copy link
Contributor

lance6716 commented Mar 21, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

    analyze_test.go:1874: 

        	Error Trace:	pkg/executor/test/analyzetest/analyze_test.go:1874

        	            				pkg/executor/test/analyzetest/analyze_test.go:2027

        	            				pkg/executor/test/analyzetest/analyze_test.go:2030

        	Error:      	Not equal: 

        	            	expected: "[executor:1317]Query execution was interrupted"

        	            	actual  : "runtime error: invalid memory address or nil pointer dereference"

        	            	

        	            	Diff:

        	            	--- Expected

        	            	+++ Actual

        	            	@@ -1 +1 @@

        	            	-[executor:1317]Query execution was interrupted

        	            	+runtime error: invalid memory address or nil pointer dereference

        	Test:       	TestKillAutoAnalyzeIndex

        	Messages:   	kill pending analyze job
[2024/03/21 04:27:17.568 +00:00] [ERROR] [exec.go:65] ["auto analyze failed"] [category=stats] [sql="analyze table `test`.`t` index `idx`"] [cost_time=5.920899ms] [error="runtime error: invalid memory address or nil pointer dereference"] [stack="github.com/pingcap/tidb/pkg/statistics/handle/autoanalyze/exec.AutoAnalyze\n\tpkg/statistics/handle/autoanalyze/exec/exec.go:65\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze/priorityqueue.(*NonPartitionedTableAnalysisJob).analyzeIndexes\n\tpkg/statistics/handle/autoanalyze/priorityqueue/non_partitioned_table_analysis_job.go:184\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze/priorityqueue.(*NonPartitionedTableAnalysisJob).Analyze.func1\n\tpkg/statistics/handle/autoanalyze/priorityqueue/non_partitioned_table_analysis_job.go:81\ngithub.com/pingcap/tidb/pkg/statistics/handle/util.CallWithSCtx\n\tpkg/statistics/handle/util/util.go:103\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze/priorityqueue.(*NonPartitionedTableAnalysisJob).Analyze\n\tpkg/statistics/handle/autoanalyze/priorityqueue/non_partitioned_table_analysis_job.go:76\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze/refresher.(*Refresher).PickOneTableAndAnalyzeByPriority\n\tpkg/statistics/handle/autoanalyze/refresher/refresher.go:105\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze.HandleAutoAnalyze\n\tpkg/statistics/handle/autoanalyze/autoanalyze.go:284\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze.(*statsAnalyze).HandleAutoAnalyze.func1\n\tpkg/statistics/handle/autoanalyze/autoanalyze.go:240\ngithub.com/pingcap/tidb/pkg/statistics/handle/util.CallWithSCtx\n\tpkg/statistics/handle/util/util.go:103\ngithub.com/pingcap/tidb/pkg/statistics/handle/autoanalyze.(*statsAnalyze).HandleAutoAnalyze\n\tpkg/statistics/handle/autoanalyze/autoanalyze.go:239\npkg/executor/test/analyzetest/analyzetest_test.TestKillAutoAnalyzeIndex.func2\n\tpkg/executor/test/analyzetest/analyze_test.go:2018\npkg/executor/test/analyzetest/analyzetest_test.TestKillAutoAnalyzeIndex\n\tpkg/executor/test/analyzetest/analyze_test.go:2030\ntesting.tRunner\n\tGOROOT/src/testing/testing.go:1595"]

https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fghpr_unit_test/detail/ghpr_unit_test/6388/pipeline

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

@lance6716 lance6716 added the type/bug The issue is confirmed as a bug. label Mar 21, 2024
@jiyfhust
Copy link
Contributor

duplicated with #51928.

@jebter jebter added the sig/planner SIG: Planner label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants