-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
os.kill(pid, signal.SIGTERM) has no effect using paddlepaddle/paddle:latest-dev #11509
Comments
@velconia Can you please take a look at this? |
OK |
具体是说, 只能支持SIGINT, 不能支持SIGTERM是吗? |
需要支持SIGINT, SIGTERM,不能使用SIGKILL |
How to reproduce the hang ISSUE? |
抱歉, 我也没能复现, 请问方便描述下具体的复现方法吗? 是在 paddlepaddle/paddle:latest-dev 这个 image里编译后执行ctest吗? @typhoonzero |
I got some problems in running paddle_build.sh in paddlepaddle/paddle:latest-dev, maybe the code below in paddle_build.sh was wrong
It seems that the PYTHON_FLAGS should be
|
After some effort, I got the stack, it seems that libusb_exit was the reason why our psever hangs up So, I walks through the depencecies of libusb and got this information follow: So, the opencv-python depends on the libusb, and after I installed opencv via According to this answer in stackoverflow, we should install both of them to avoid this problem |
Some unit tests like
test_listen_and_serv_op.py
, run the test withpaddlepaddle/paddle:latest-dev
docker image, the callos.kill(pid, signal.SIGTERM)
have no effect, while runkill pid
in the shell can successfully terminate the process. When using manylinux docker images, this issue is gone.More info: #11470
The text was updated successfully, but these errors were encountered: