Build failed: Maestro Build Promotion/main #Promoting dotnet-wasi-sdk build 20230428.1 (176253) to channel(s) '.NET 8' #
See original GitHub issueBuild #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 Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, the manifest is getting built too many times and needs a condition. As @riarenas said.
I don’t know how these are being generated, but I wonder if the
*Current.Manifest*
entry is getting repeated once for every platform, likelinux-x64
,osx-x64
etc.Where is it getting these files from? And where is the merged manifest generated?