-
Notifications
You must be signed in to change notification settings - Fork 282
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
DM worker can't exit in CI #5089
Comments
This comment was marked as resolved.
This comment was marked as resolved.
the log didn't contain "dm-worker exit" cant_exit.txt from https://ci2.pingcap.net/blue/organizations/jenkins/dm_ghpr_integration_test/detail/dm_ghpr_integration_test/5696/pipeline/204 |
|
Forget to show STAT in process 😂 |
seems a zombie process, but it's ppid is 0, should be 1 normally, rare but possible, see https://stackoverflow.com/questions/37577931/how-can-i-kill-a-zombie-process-whose-parent-is-pid-0 |
|
this is dumped from macOS, the process stat is S. |
syncer is still running, not knowing the worker should be canceled. |
|
should unify process exit check |
goroutine stack by dlv
reproduced in local ! |
Which jobs are flaking?
IT-ha_cases3_1
Which test(s) are flaking?
DM IT
Jenkins logs or GitHub Actions link
DM worker log :
worker.log
Anything else we need to know
Does this test exist for other branches as well?
Has there been a high frequency of failure lately?
The text was updated successfully, but these errors were encountered: