-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[BUG]: PythonScript@0 doesn't seem to get SIGINIT/SIGTERM #19390
Comments
@nkr0, can you provide additional downloadable logs? |
I'm not sure if it is safe to share downloadable logs. But I've it and if you ask for something I can share relevant info here.
Quite weird that |
From the timestamps, I would say that the last 4 lines are from the same run. And it looks like the agent is sending force kill, before the worker gets to try
|
New issue checklist
Task name
PythonScript
Task version
0.231.0
Issue Description
This page says that
SIGINT
orSIGTERM
is sent on job cancellation. Below is a simplified task callingtestSigint.py
.But the logs show that
cancelJob
was not called, suggesting that the process was not ended with any of the signals I tried. Running the script locally and pressingCtrl+C
triggersSIGINT
and is caught as expected.Issue #16731 is similar in that
SIGINT
from the agent becomesSIGTERM
by the time it reached the child process. But here it's none of those.Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 22.04
Relevant log output
Full task logs with system.debug enabled
Repro steps
No response
The text was updated successfully, but these errors were encountered: