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

Error: The process dotnet.exe failed with exit code 1 #10621

Open
2 of 13 tasks
verback2308 opened this issue Sep 16, 2024 · 4 comments
Open
2 of 13 tasks

Error: The process dotnet.exe failed with exit code 1 #10621

verback2308 opened this issue Sep 16, 2024 · 4 comments

Comments

@verback2308
Copy link

verback2308 commented Sep 16, 2024

Description

Copied from Azure Pipelines Tasks

All our pipelines started crashing with an error on dotnet publish since last Saturday (September 14):
image

There are no details in the logs except that the command returned error 1:
image

Version of the last successful pipeline the same as other - 2.245.1

Old pipelines for previous branches were checked - they also started crashing with an error, however - code is the same:

image

Diff between latest successful (left) and current (right) build:
image

Temporarily switched to a self-hosted agent, everything works there.
Solution compiles on a dev machine (osx, win) with a success.

upd1: just found a workaround - added step with SDK installation:

- task: UseDotNet@2 
displayName: 'Install .NET Core SDK' 
inputs: version: 7.x 
performMultiLevelLookup: true 
includePreviewVersions: true # Required for preview versions

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Image: windows-2022
Version: 20240912.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20240912.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240912.1

Is it regression?

Expected behavior

Build should finish with a success

Actual behavior

The process dotnet.exe failed with exit code 1

Repro steps

pool:
  vmImage: 'windows-latest'

variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages
  pvs-solution: 'PVS/PVS.sln'
  client: 'PVS.Clients.WebClient.Core'

steps:

  - task: NuGetToolInstaller@1
    displayName: 'Install NuGet'

  - task: Cache@2
    displayName: 'NuGet Cache'
    inputs:
      key: 'nuget | "$(Agent.OS)" | **/packages.lock.json,!**/bin/**,!**/obj/**'
      restoreKeys: |
        nuget | "$(Agent.OS)"
        nuget
      path: '$(NUGET_PACKAGES)'
      cacheHitVar: 'CACHE_RESTORED'

  - task: NuGetCommand@2
    displayName: 'Restore NuGet packages for PVS'
    condition: ne(variables.CACHE_RESTORED, true)
    inputs:
      command: 'restore'
      restoreSolution: '$(pvs-solution)'
      feedsToUse: 'config'
      nugetConfigPath: 'PVS/NuGet.Config'

  - task: DotNetCoreCLI@2
    displayName: 'Publish $(Client)'
    inputs:
      command: 'publish'
      publishWebProjects: false
      projects: 'PVS/$(Client)/$(Client).csproj'
      arguments: '-c Release --no-self-contained -f net7.0 /p:ExcludeApp_Data=False -o "$(Build.BinariesDirectory)/$(Client)"'
      zipAfterPublish: false
      modifyOutputPath: false
@SotnikovMaksym
Copy link

Description

Copied from Azure Pipelines Tasks

All our pipelines started crashing with an error on dotnet publish since last Saturday (September 14): image

There are no details in the logs except that the command returned error 1: image

Version of the last successful pipeline the same as other - 2.245.1

Old pipelines for previous branches were checked - they also started crashing with an error, however - code is the same:

image

Diff between latest successful (left) and current (right) build: image

Temporarily switched to a self-hosted agent, everything works there. Solution compiles on a dev machine (osx, win) with a success.

upd1: just found a workaround - added step with SDK installation: - task: UseDotNet@2 displayName: 'Install .NET Core SDK' inputs: version: 7.x performMultiLevelLookup: true includePreviewVersions: true # Required for preview versions

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Image: windows-2022 Version: 20240912.1.0 Included Software: https://github.com/actions/runner-images/blob/win22/20240912.1/images/windows/Windows2022-Readme.md Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240912.1

Is it regression?

Expected behavior

Build should finish with a success

Actual behavior

The process dotnet.exe failed with exit code 1

Repro steps

pool:
  vmImage: 'windows-latest'

variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages
  pvs-solution: 'PVS/PVS.sln'
  client: 'PVS.Clients.WebClient.Core'

steps:

  - task: NuGetToolInstaller@1
    displayName: 'Install NuGet'

  - task: Cache@2
    displayName: 'NuGet Cache'
    inputs:
      key: 'nuget | "$(Agent.OS)" | **/packages.lock.json,!**/bin/**,!**/obj/**'
      restoreKeys: |
        nuget | "$(Agent.OS)"
        nuget
      path: '$(NUGET_PACKAGES)'
      cacheHitVar: 'CACHE_RESTORED'

  - task: NuGetCommand@2
    displayName: 'Restore NuGet packages for PVS'
    condition: ne(variables.CACHE_RESTORED, true)
    inputs:
      command: 'restore'
      restoreSolution: '$(pvs-solution)'
      feedsToUse: 'config'
      nugetConfigPath: 'PVS/NuGet.Config'

  - task: DotNetCoreCLI@2
    displayName: 'Publish $(Client)'
    inputs:
      command: 'publish'
      publishWebProjects: false
      projects: 'PVS/$(Client)/$(Client).csproj'
      arguments: '-c Release --no-self-contained -f net7.0 /p:ExcludeApp_Data=False -o "$(Build.BinariesDirectory)/$(Client)"'
      zipAfterPublish: false
      modifyOutputPath: false

Have the same problem since Friday the 13th of September!

@kishorekumar-anchala
Copy link
Contributor

Hi @verback2308 ,

Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

@kishorekumar-anchala kishorekumar-anchala added the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Sep 18, 2024
@kishorekumar-anchala
Copy link
Contributor

Hi @verback2308 ,

Could you please try to build with latest version 20240915.1 . thank you !

@kishorekumar-anchala kishorekumar-anchala removed the awaiting-deployment Code complete; awaiting deployment and/or deployment in progress label Sep 20, 2024
@kishorekumar-anchala
Copy link
Contributor

HI @verback2308 ,

  Could you please share your update on this issue ?

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

3 participants