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

[REGRESSION]: VSBuild@1 doesn't work on latest windows image #20435

Closed
4 of 7 tasks
Skintkingle opened this issue Sep 18, 2024 · 2 comments
Closed
4 of 7 tasks

[REGRESSION]: VSBuild@1 doesn't work on latest windows image #20435

Skintkingle opened this issue Sep 18, 2024 · 2 comments

Comments

@Skintkingle
Copy link

New issue checklist

Task name

VSBuild

Breaking task version

1.245.0

Last working task version

1.245.0

Regression Description

COPIED FROM Runner Images issue which subsequently was copied from
Azure Pipelines Issue

Last week, we were using VSBuild@1 (version 1.245.0), last used Friday 13th September at 8pm UTC to successfully build and package an APPX.
On sunday (and today) we are using the same version (1.245.0), and the build is now failing with the following error:

fatal error CMF1106: failed to open input PDB file for reading (PDB error code = 13)

The task is configured as such (and has been like this for many months):

- task: VSBuild@1
  displayName: Build Our Product
  inputs:
    platform: 'x64' 
    solution: 'Our Solution.sln'
    msbuildArgs: '/p:AppxBundlePlatforms="x64" /p:AppxBundle=Always /p:UapAppxPackageBuildMode=SideLoadOnly /p:AppxPackageSigningEnabled=false'

Critically - we can run this on the same commit that previously passed, and it now fails.

This is preventing us from releasing any changes and as such, for us, is critical to get a fix or workaround

Wondering if the fix deployed for this event was the cause

Which would be related to #10601

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-latest Microsoft hosted image

Relevant log output

_GenerateAppxSymbolPackage:
  C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\\x64\mspdbcmf.exe /check "D:\a\1\s\Our App\bin\x64\Debug\net8.0-windows10.0.19041.0\win-x64\msixpublish\Our App.pdb" 
  Microsoft (R) FastLink To Full PDB Converter Version 14.41.33923.0
  Copyright (C) Microsoft Corporation.  All rights reserved.
  
  D:\a\1\s\Our App\bin\x64\Debug\net8.0-windows10.0.19041.0\win-x64\msixpublish\Our App.pdb : fatal error CMF1106: failed to open input PDB file for reading (PDB error code = 13)
##[error]C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets(3715,5): Error MSB6006: "mspdbcmf.exe" exited with code 1106.
##[debug]Processed: ##vso[task.logissue type=Error;sourcepath=C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets;linenumber=3715;columnnumber=5;code=MSB6006;]"mspdbcmf.exe" exited with code 1106.
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.AppXPackage.Targets(3715,5): error MSB6006: "mspdbcmf.exe" exited with code 1106. [D:\a\1\s\OurApp.Package\OurApp.Package.wapproj]

Full task logs with system.debug enabled

No response

Repro steps

No response

@Skintkingle Skintkingle added bug regression This used to work, but a change in the service/tasks broke it. labels Sep 18, 2024
@max-zaytsev max-zaytsev added External and removed triage regression This used to work, but a change in the service/tasks broke it. labels Sep 19, 2024
@max-zaytsev
Copy link
Contributor

This does not appear to be a regression in the task, as the version of the task has not changed as indicated in the issue description.

Most likely the changes in the image caused this. Image team is investigating the problem:
actions/runner-images#10617

@Skintkingle
Copy link
Author

I agree, thank you for confirming this.

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