You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Installer Build and Test coreclr windows_x64 Release lane failing with missing pgort140.dll in manifest #48169
Installer Build and Test coreclr windows_x64 Release Lane is failing on PRs that seem unrelated with this error message:
D:\workspace\_work\1\s\.packages\microsoft.dotnet.sharedframework.sdk\6.0.0-beta.21105.5\targets\sharedfx.targets(273,5): error : pgort140.dll. Add these file names with extensions to the 'PlatformManifestFileEntry' item group for the runtime pack and corresponding ref pack to include them in the platform manifest. [D:\workspace\_work\1\s\src\installer\pkg\sfx\Microsoft.NETCore.App\Microsoft.NETCore.App.Runtime.sfxproj]
##[error].packages\microsoft.dotnet.sharedframework.sdk\6.0.0-beta.21105.5\targets\sharedfx.targets(273,5): error : (NETCORE_ENGINEERING_TELEMETRY=Build) The following files are missing entries in the templated manifest:
pgort140.dll. Add these file names with extensions to the 'PlatformManifestFileEntry' item group for the runtime pack and corresponding ref pack to include them in the platform manifest.
@jozkee it seems like you were doing retry. Retry will use the same YAML. The fix for this issue was remove the two build that were failing from the YAML. You would have had to rebase on top of master and push, or open and close your PR to get the build to pass.
ghost locked as resolved and limited conversation to collaborators on Mar 20, 2021
Activity
safern commentedon Feb 11, 2021
Seems possibly related to: a9d6beb
@agocke is taking a look.
safern commentedon Feb 12, 2021
Thanks, @tarekgh this was just fixed by: #48170
jozkee commentedon Feb 18, 2021
I'm hitting this issue consistently on #46101
build: https://dev.azure.com/dnceng/public/_build/results?buildId=990999&view=logs&j=8568df52-d94f-59a3-cf78-357510bb4d77&t=46f3998b-4412-560c-c2a3-70b5b38b861a
@safern any idea why is that?
safern commentedon Feb 18, 2021
@jozkee it seems like you were doing retry. Retry will use the same YAML. The fix for this issue was remove the two build that were failing from the YAML. You would have had to rebase on top of master and push, or open and close your PR to get the build to pass.