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

panic: test timed out after 5m0s #20

Open
inevity opened this issue Jul 24, 2019 · 1 comment
Open

panic: test timed out after 5m0s #20

inevity opened this issue Jul 24, 2019 · 1 comment

Comments

@inevity
Copy link

inevity commented Jul 24, 2019

When running the last test changlog, met this error as title show.
My test env is a kvm vm .

Have set mysqld,
innodb_lock_wait_timeout=500
transaction-isolation = READ-COMMITTED

But cannot fix this issue.
Then i change the test timeout to 3000s /50m to check whether the test pass.

first met some datarace warning,
then
2019-07-24T15:36:13.563+0800 ERROR changelog/mysql.go:505 Error 1205: Lock wait timeout exceeded; try restarting transaction
2019-07-24T15:44:34.629+0800 ERROR changelog/mysql.go:841 Error 1205: Lock wait timeout exceeded; try restarting transaction {"cluster": "test_cluster1"}
then
2019-07-24T15:44:34.733+0800 DEBUG runtime/asm_amd64.s:1337 Finished binlog worker in test
panic: test timed out after 50m0s

Do you have some suggest?
Detail log at https://paste.ubuntu.com/p/HxJ9bNmzrn/

@efirs
Copy link
Contributor

efirs commented Sep 11, 2019

Please rerun the tests with current master, it has been updated with many bugfixes.
We will look into if it still reproducible. Thanks for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants