Skip to content
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]: How to investigate task failure that has no information to go by #20871

Open
1 of 4 tasks
olstakh opened this issue Feb 20, 2025 · 0 comments
Open
1 of 4 tasks

Comments

@olstakh
Copy link

olstakh commented Feb 20, 2025

Task name

Azure CLI

Task version

2.251.1

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows

Question

We have a simple AzureCli task that runs dotnet test command

  - task: AzureCLI@2
    displayName: ${{ parameters.displayName }}
    retryCountOnTaskFailure: ${{ parameters.retryCount }}
    timeoutInMinutes: ${{ parameters.timeoutInMinutes }}
    inputs:
      azureSubscription: "..."
      addSpnToEnvironment: true
      scriptType: batch
      scriptLocation: inlineScript
      inlineScript: >
        dotnet test ${{ parameters.projects }}
        ${{ parameters.additionalTestOptions }}

In certain circumstances - we see the following failure for this task:

Passed!  - Failed:     0, Passed:  1031, Skipped:    50, Total:  1081, Duration: 3 m 51 s - Microsoft.Bot.Engine.ScenarioTests.dll (net8.0)
##[debug]Agent environment resources - Disk: D:\ Available 48304.17 MB out of 131070.00 MB, Memory: Used 17936.00 MB out of 65535.00 MB, CPU: Usage 25.00%

Attachments:
  D:\a\_work\_temp\02143b08-237b-449b-80b2-4bc984d1b804\cloudtest_1b352d4ec000000_2025-02-20.03_38_31.coverage

##[debug]Process exited with code 1 and signal null for tool 'D:\a\_work\_temp\azureclitaskscript1740022675643.bat'
##[debug]STDIO streams have closed and received exit code 1 and signal null for tool 'D:\a\_work\_temp\azureclitaskscript1740022675643.bat'
##[debug]task result: Failed
##[error]Script failed with exit code: 1
##[debug]Processed: ##vso[task.issue type=error;source=TaskInternal;correlationId=f72a37c9-0f2e-4a2d-a6bc-57c3994843b1;]Script failed with exit code: 1
##[debug]Processed: ##vso[task.complete result=Failed;]Script failed with exit code: 1

The only potentially useful information i see in these logs is source=TaskInternal;correlationId=f72a37c9-0f2e-4a2d-a6bc-57c3994843b1, which is something im not aware where to look for. I've attempted to search fo this correlationId in cluster('1es.kusto.windows.net').database('AzureDevOps') cluster, but was unsuccessful.

Is there any parameter i can set for this task, or any other means i can use to figure out why the task is failing after successful test run? I have nothing to go on at this point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant