PublishTestResults task "hangs forever"

[mastrzyz]

Note

Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo

For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

If you have an issue or request for the Azure Pipelines service, use developer community instead:

https://developercommunity.visualstudio.com/spaces/21/index.html )

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: PublishTestResults -> Version 2.210.0

list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks

Environment

• Server - Azure Pipelines or TFS on-premises?

  • If using Azure Pipelines, provide the account name, team project name, build definition name/build number: Microsoft Internal

• Agent - Hosted or Private: Hosted

Issue Description

Intermitently we are seeing the PublishTestResults task "Freeze or Disappear" completely

The task is :

  - task: PublishTestResults@2
    displayName: Publish Test Results
    retryCountOnTaskFailure: 4
    timeoutInMinutes: 30
    inputs:
      testResultsFiles: |
        $(Build.SourcesDirectory)/logs/test-results/unit/unit-tests-report.xml
      testRunTitle: UnitTests_$(System.JobPositionInPhase)
      platform: $(Build.DefinitionName)
      configuration: Tests
    condition: succeededOrFailed()

Keep in mind `timeoutInMinutes

Unfortunately, there is nothing here in the logs, even the timeline logs of the pipeline :

This happens a couple of times a week for us and is a bit frustrating for our developers as they are not sure what is happening since the build is taking 4+h

[mastrzyz]

Anyone ? this at least happens once a day for us.

[initions-david]

I have the same problem & suspect that it could be due to firewall restrictions, but I'm unsure.

Edit: Setting publishRunAttachments: false fixed the issue for me.

[github-actions[bot]]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[ChristoWolf]

Bump.

[github-actions[bot]]

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

[ChristoWolf]

Bump.

The issue still persists. I also observed it while running tests via dotnet test whenever IO pipes where not fully closed, see #17548.

[bwbusacker]

Bump. We still see this issue even when publishRunAttachments: false is set. This happens only when running on ADO services not when running on local ADO instance.

[ghost]

We have the same problem. For us it seems to happen when the same pipeline is triggered multiple times at the same time.

[ovaar]

I am also experiencing this same issue.

[ekbaramundi]

We also still experiencing this problem in Azure DevOps Online with VSS building Agents.