Closed KristofKuli closed 12 months ago
Hi @KristofKuli, thank you for reporting this issue.
From what I saw in the logs the issue seems related to the machine environment or to the ADO agent, Could you please provide some additional information, that can help with the investigation?
1) Could you please specify what agent version is deployed on a self-hosted machine?
2) What PythonScript
task version was used on successful runs?
Hi Maksim, Most probably the issue is generated by the env vars, which are defined in the task. As I have mentioned earlier, in bash task everything worked fined, however when the envs were added, we experienced the same issue. We have also tried variable groups, but no luck.
The agent version of the self-hosted pool is 3.227.2 and the task version is the same on the previous successful runs, 0.229.3.
Hi Maksim,
Today the pipeline finished successfully, without any change from our side. Was there any update released to the PythonSrcipt task?
@KristofKuli there were no updates for the PythonScript task - you can validate it by comparing the task version mentioned in the logs.
Those environment variables that you mentioned earlier - could you please provide more context about them? Are they somehow used in Python/Bash scripts, or are they used in some background service? Since they affect the pipeline execution, perhaps the issue here is related to the agent itself, and not to the tasks.
@KristofKuli could you please confirm that the issue still occurs?
I think we can close this issue for now.
Thank you, we will close it then - please feel free to reopen it in case of issue reoccurs.
Task name
PythonScript@0
Task version
0.229.3
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 20.04
Task log
Relevant log output
Aditional info