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 TestIndexMergeCoprGoroutinesLeak #42681

Closed
Tracked by #41316
tiancaiamao opened this issue Mar 29, 2023 · 1 comment
Closed
Tracked by #41316

unstable test TestIndexMergeCoprGoroutinesLeak #42681

tiancaiamao opened this issue Mar 29, 2023 · 1 comment
Labels
type/question The issue belongs to a question.

Comments

@tiancaiamao
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

make failpoint-enable
cd executor
go test -tags intest -run TestIndexMergeCoprGoroutinesLeak

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

no error

3. What did you see instead (Required)

--- FAIL: TestIndexMergeCoprGoroutinesLeak (0.82s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x475f071]

goroutine 40 [running]:
testing.tRunner.func1.2({0x4cd7ac0, 0x7bb85e0})
        /home/genius/project/go/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
        /home/genius/project/go/src/testing/testing.go:1529 +0x39f
panic({0x4cd7ac0, 0x7bb85e0})
        /home/genius/project/go/src/runtime/panic.go:884 +0x213
github.com/pingcap/tidb/executor_test.TestIndexMergeCoprGoroutinesLeak(0x18b2af9?)
        /home/genius/project/src/github.com/pingcap/tidb/executor/index_merge_reader_test.go:932 +0x291
testing.tRunner(0xc0005529c0, 0x54651b0)
        /home/genius/project/go/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
        /home/genius/project/go/src/testing/testing.go:1629 +0x3ea
exit status 2
FAIL    github.com/pingcap/tidb/executor        0.866s

4. What is your TiDB version? (Required)

master af62a5c

@tiancaiamao tiancaiamao added the type/bug The issue is confirmed as a bug. label Mar 29, 2023
@tiancaiamao
Copy link
Contributor Author

can't reproduce

I remove tools/bin/failpoint-ctl and then make failpoint-enable again, the issue is gone.

@tiancaiamao tiancaiamao added type/question The issue belongs to a question. and removed type/bug The issue is confirmed as a bug. labels Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question The issue belongs to a question.
Projects
None yet
Development

No branches or pull requests

1 participant