-
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
[Question]: The STDIO streams did not close within 10 seconds of the exit event from process '/usr/bin/bash' #18476
Comments
Hi @zlee520, this message means that the bash child process is not finished. As I see it, you are trying to run your application in the background, so in this case the pipeline task will not wait for the background process to finish. What problem are you seeing in this case? |
hello, I want to start a java app, this task is successfull but the java app not started |
With the previous version, Azure Pipeline sometimes failed the execution of the tests, not completing the test step. Looking into these failures, I also found the following message in the logs from Azure Pipelines: > The STDIO streams did not close within 10 seconds of the exit event from process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited. For discussions of the problem, see also: + microsoft/azure-pipelines-tasks#17548 + microsoft/azure-pipelines-tasks#13033 + microsoft/azure-pipelines-tasks#18476
With the previous version, Azure Pipeline sometimes failed the execution of the tests, not completing the test step. Looking into these failures, I also found the following message in the logs from Azure Pipelines: > The STDIO streams did not close within 10 seconds of the exit event from process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited. For discussions of the problem, see also: + microsoft/azure-pipelines-tasks#17548 + microsoft/azure-pipelines-tasks#13033 + microsoft/azure-pipelines-tasks#18476
With the previous version, Azure Pipeline sometimes failed the execution of the tests, not completing the test step. Looking into these failures, I also found the following message in the logs from Azure Pipelines: > The STDIO streams did not close within 10 seconds of the exit event from process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited. For discussions of the problem, see also: + microsoft/azure-pipelines-tasks#17548 + microsoft/azure-pipelines-tasks#13033 + microsoft/azure-pipelines-tasks#18476
Hi , |
@KonstantinTyukalov steps:
- pwsh: docker build . In my exemple I'm trying to build a docker image, which takes around 3 minutes. The problem I'm facing is that the error provokes a failure of the step, even though the build continues and succeeds. I don't want to use
The step actually runs to completion AND fails because of that error. I don't understand why this is a topic in the first place. |
Please note, this works fine for me on Windows agents, it only fails on Linux agents. $ uname -a
Linux hostname 3.10.0-1160.83.1.el7.x86_64 #1 SMP Wed Jan 25 16:41:43 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux |
Probably related to #19844 |
Task name
https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
Task version
2.201.1
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
Azure DevOps Server (Please specify exact version in the textbox below)
Azure DevOps Server Version (if applicable)
Azure DevOps Server 2022
Operation system
Ubuntu 20.04
Question
The text was updated successfully, but these errors were encountered: