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

[dotnet-eng-status]

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.<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

[epananth]

@SteveSandersonMS, I see maestro promotion is failing cos of

Duplicates in the merge manifest

[SteveSandersonMS]

Pinging @pavelsavara for any insight on the WASI workload build issue.

[pavelsavara]

I have no idea @radical @lewing

[lewing]

@steveisok any idea what is going on here?

[riarenas]

In general, you want to make sure that only one leg of the build produces the assets that will be published and therefore only one of the individual publishing manifests has the individual package entries. Multiple entries for the same package in the manifests is not allowed, as we can only push the package version once, and we wouldn't know which one you meant we should publish.

[steveisok]

@steveisok any idea what is going on here?

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

[radical]

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?