Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Publish Assets failed with "PublishArtifactsInManifest.proj(51,5): error : File does not exist"

See original GitHub issue

https://dev.azure.com/dnceng/internal/_build/results?buildId=299900

 Decompressing https://dotnetfeed.blob.core.windows.net/dotnet-windowsdesktop/sleet.packageindex.json
D:\a\1\s\.packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.19406.7\tools\SdkTasks\PublishArtifactsInManifest.proj(51,5): error : File does not exist. Remote: https://dotnetfeed.blob.core.windows.net/dotnet-windowsdesktop/flatcontainer/runtime.win-x64.microsoft.dotnet.wpf.dnceng/4.8.0-preview9.19407.26/runtime.win-x64.microsoft.dotnet.wpf.dnceng.4.8.0-preview9.19407.26.nupkg Local: C:\Users\VssAdministrator\AppData\Local\Temp\16f1c0ad-a75c-4f1e-955b-e9a4c1aab432\ea3c7c4f-9909-4f63-a57d-b01141049190.tmp
##[error].packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.19406.7\tools\SdkTasks\PublishArtifactsInManifest.proj(51,5): error : File does not exist. Remote: https://dotnetfeed.blob.core.windows.net/dotnet-windowsdesktop/flatcontainer/runtime.win-x64.microsoft.dotnet.wpf.dnceng/4.8.0-preview9.19407.26/runtime.win-x64.microsoft.dotnet.wpf.dnceng.4.8.0-preview9.19407.26.nupkg Local: C:\Users\VssAdministrator\AppData\Local\Temp\16f1c0ad-a75c-4f1e-955b-e9a4c1aab432\ea3c7c4f-9909-4f63-a57d-b01141049190.tmp
  Uploading 1 items:
  Async uploading d:\a\1\a/BlobArtifacts\runtime.win-x64.Microsoft.DotNet.Wpf.DncEng.4.8.0-preview9.19407.26.symbols.nupkg

Can someone please take a look at this failure?

/cc @riarenas, @JohnTortugo /cc @MattGal in case this is a build-infrastructure problem /cc @dotnet/wpf-developers

Issue Analytics

State:
Created 4 years ago
Comments:15 (15 by maintainers)

Top GitHub Comments

1reaction

vatsan-madhavancommented, Aug 8, 2019

/cc @wtgodbe

1reaction

vatsan-madhavancommented, Aug 8, 2019

I’ve removed .NET Core 5 Dev for now.

λ darc get-default-channels --source-repo dotnet-wpf-int
(130)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/master -> .NET Core 3 Dev
(140)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/release/3.0 -> .NET Core 3 Release
(298)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/master -> .NET Core 5 Dev
(382)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/dev/vatsan/yamlstages -> .NET Tools - Validation

λ darc delete-default-channel --channel ".NET Core 5 Dev" --branch refs/heads/master --repo https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int

λ darc get-default-channels --source-repo dotnet-wpf-int
(130)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/master -> .NET Core 3 Dev
(140)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/release/3.0 -> .NET Core 3 Release
(382)  https://dev.azure.com/dnceng/internal/_git/dotnet-wpf-int @ refs/heads/dev/vatsan/yamlstages -> .NET Tools - Validation

We can add it back once this has been resolved and the publishing tools have been separately validated to be able to publish simultaneously to 2 or more channels from the same branch.

/cc a few folks who tend to be interested in channel associations and flow of wpf into .NET 5: @mmitche, @zsd4yr, @AdamYoblick , @dagood, @rladuca, @ericstj