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

goleak: Errors on successful test run: found unexpected goroutines #38731

Closed
tiancaiamao opened this issue Oct 28, 2022 · 0 comments · Fixed by #38734
Closed

goleak: Errors on successful test run: found unexpected goroutines #38731

tiancaiamao opened this issue Oct 28, 2022 · 0 comments · Fixed by #38734
Assignees
Labels
component/test severity/moderate type/bug The issue is confirmed as a bug.

Comments

@tiancaiamao
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

cd executor;
go test -run TestGlobalMemoryControl

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

Success

3. What did you see instead (Required)

[2022/10/28 20:05:50.306 +08:00] [INFO] [ddl.go:639] ["[ddl] stop DDL"] [ID=9d4da259-d7b1-44f9-aef1-743fba5805be]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1094] ["closestReplicaReadCheckLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:742] ["loadSchemaInLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [handle_hist.go:168] ["SubLoadWorker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1541] ["dumpFileGcChecker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [handle_hist.go:168] ["SubLoadWorker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [handle_hist.go:168] ["SubLoadWorker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [handle_hist.go:168] ["SubLoadWorker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [handle_hist.go:168] ["SubLoadWorker exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1331] ["LoadSysVarCacheLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1281] ["loadPrivilegeInLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1456] ["handleEvolvePlanTasksLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:1412] ["globalBindHandleWorkerLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:607] ["topologySyncerKeeper exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:584] ["globalConfigSyncerKeeper exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:559] ["infoSyncerKeeper exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:530] ["topNSlowQueryLoop exited."]
[2022/10/28 20:05:50.306 +08:00] [INFO] [domain.go:870] ["domain closed"] ["take time"=710.055µs]
[2022/10/28 20:05:50.311 +08:00] [INFO] [db.go:567] ["Closing database"]
[2022/10/28 20:05:50.312 +08:00] [INFO] [db.go:592] ["Memtable flushed"]
[2022/10/28 20:05:50.312 +08:00] [INFO] [db.go:596] ["Compaction finished"]
[2022/10/28 20:05:50.312 +08:00] [INFO] [db.go:615] ["BlobManager finished"]
[2022/10/28 20:05:50.312 +08:00] [INFO] [db.go:619] ["ResourceManager finished"]
[2022/10/28 20:05:50.312 +08:00] [INFO] [db.go:625] ["Waiting for closer"]
PASS
goleak: Errors on successful test run: found unexpected goroutines:
[Goroutine 10614 in state sleep, with time.Sleep on top of the stack:
goroutine 10614 [sleep]:
time.Sleep(0xdf8475800)
        /home/genius/project/go/src/runtime/time.go:195 +0x135
github.com/pingcap/tidb/util/gctuner.(*memoryLimitTuner).tuning.func1()
        /home/genius/project/src/github.com/pingcap/tidb/util/gctuner/memory_limit_tuner.go:69 +0x45
created by github.com/pingcap/tidb/util/gctuner.(*memoryLimitTuner).tuning
        /home/genius/project/src/github.com/pingcap/tidb/util/gctuner/memory_limit_tuner.go:61 +0x110
]
exit status 1
FAIL    github.com/pingcap/tidb/executor        6.165s

4. What is your TiDB version? (Required)

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

Successfully merging a pull request may close this issue.

2 participants