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.

Build failed: Maestro Build Promotion/main #Promoting dotnet-wasi-sdk build 20230428.1 (176253) to channel(s) '.NET 8' #

See original GitHub issue

Build #Promoting dotnet-wasi-sdk build 20230428.1 (176253) to channel(s) ‘.NET 8’ # failed

❌ : internal / Maestro Build Promotion failed

Summary

Finished - Fri, 28 Apr 2023 17:28:12 GMT Duration - 2 minutes Requested for - DotNet Bot Reason - manual

Details

Publishing

❌ - [Log] - .packages\microsoft.dotnet.arcade.sdk\8.0.0-beta.23226.4\tools\SdkTasks\PublishArtifactsInManifest.proj(135,5): error : Sequence contains more than one element

at System.Linq.ThrowHelper.ThrowMoreThanOneElementException() at System.Linq.Enumerable.TryGetSingle[TSource](IEnumerable`1 source, Boolean& found) at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source) at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.LookupAsset(String name, Dictionary`2 buildAssets) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 254 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.TryAddAssetLocation(String assetId, String assetVersion, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, LocationType assetLocationType) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 294 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.<>c__DisplayClass171_0.<<PublishAssetsUsingStreamingPublishingAsync>b__0>d.MoveNext() in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1753 --- End of stack trace from previous location --- at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.PublishAssetsUsingStreamingPublishingAsync(IAssetPublisher assetPublisher, HashSet`1 assetsToPublish, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1724 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.PublishAssetsAsync(IAssetPublisher assetPublisher, HashSet`1 assetsToPublish, Dictionary`2 buildAssets, TargetFeedConfig feedConfig, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1673 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestBase.HandleBlobPublishingAsync(Dictionary`2 buildAssets, SemaphoreSlim clientThrottle) in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestBase.cs:line 1045 at Microsoft.DotNet.Build.Tasks.Feed.PublishArtifactsInManifestV3.ExecuteAsync() in /_/src/Microsoft.DotNet.Build.Tasks.Feed/src/PublishArtifactsInManifestV3.cs:line 196

Changes

Issue Analytics

State:
Created 5 months ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

steveisokcommented, Apr 28, 2023

@steveisok any idea what is going on here?

Yeah, the manifest is getting built too many times and needs a condition. As @riarenas said.

0reactions

radicalcommented, Apr 28, 2023

I don’t know how these are being generated, but I wonder if the *Current.Manifest* entry is getting repeated once for every platform, like linux-x64, osx-x64 etc.

Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.linux-arm64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.linux-x64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.osx-arm64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.osx-x64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.win-arm64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Runtime.Wasi.19.0.0.Sdk.win-x64@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)
Package Microsoft.NET.Workload.Wasi.Current.Manifest-8.0.100@19.0.0-preview.4.23228.1 (Shipping) should go to https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json (Non-Isolated, Public)

Where is it getting these files from? And where is the merged manifest generated?