.NET core: DotNetCoreCLI takes suddenly too long

[FrancescElies]

Description

DotNetCoreCLI@2 is suddenly extremely slow around 30 minutes without any code changes.
example build (not open source)

Could someone help me understand if we are doing something wrong or something is going on with the windows images?

Area for Triage:
.NET Core

Question, Bug, or Feature?:
Bug

Virtual environments affected

• macOS 10.15
• Ubuntu 16.04 LTS
• Ubuntu 18.04 LTS
• Ubuntu 20.04 LTS
• Windows Server 2016 R2
• Windows Server 2019

Expected behavior
I expect that task to take around ~5min instead of ~30min

Actual behavior
Linked task takes ~30min

[dibir-magomedsaygitov]

Hello, @FrancescElies!
Thank you for your report. Could you please provide minimal repro steps since we don't have permissions to the build that you have linked. And also could you please let us know what image version you are using.

[FrancescElies]

This is the task we are using. more details about what we are doing I cant post it here.

- task: DotNetCoreCLI@2
    displayName: UnitTests 
    inputs:
      command: test
      projects: 'myproj.csproj'
      arguments: '--configuration $(buildConfig) --no-restore'
      testRunTitle: UnitTests 

Image version Infos:

Agent name: 'Azure Pipelines 12'
Agent machine name: 'WIN-LHABSG1F61T'
Current agent version: '2.175.2'
Current image version: '20200920.1'

[dibir-magomedsaygitov]

@FrancescElies Thank you for the provided information. Looks like your issue is not related to the image since it has not been updated for a long time. We do not have much context about this task since they are maintained by https://github.com/microsoft/azure-pipelines-tasks, so we would suggest you to ask related team.

[FrancescElies]

@dibir-magomedsaygitov thanks for your reply. I will open an issue an reference this one on that repo.

ℹHere I have two example builds that shows the problem:

• This build: unittest takes less than 1 minute.
• This build: unittest takes 30 minutes

Between this two commits there are no changes on that c# project, therefore if we are not wrong, something in the cloud must be going on.

[dibir-magomedsaygitov]

In this case I`m going to close this issue. If you will have any questions feel free contact us.

[jetersen]

Actually we are seeing the same behavior on GitHub actions running a shell command for dotnet restore takes a very long time on windows even when using actions/cache 😅

Current runner version: '2.278.0'
Operating System
  Microsoft Windows Server 2019
  10.0.17763
  Datacenter
Virtual Environment
  Environment: windows-2019
  Version: 20210531.1
  Included Software: actions/virtual-environments@win19/20210531.1/images/win/Windows2019-Readme.md
  Image Release: actions/virtual-environments@win19%2F20210531.1 (release)