[release/8.0-preview1] Branding of .NET 8.0 Preview1

[carlossanlop]

Changing alpha to preview, like we did for .NET 7.0 Preview1: #64123

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Changing alpha to preview, like we did for .NET 7.0 Preview1: #64123

Author:	carlossanlop
Assignees:	carlossanlop
Labels:	area-Infrastructure
Milestone:	8.0.0

[carlossanlop]

@radical @lewing @akoeplinger @steveisok are the emscripten failures related to the branding?

[akoeplinger]

Yes it's related:

eng\testing\workloads-testing.targets(226,5): error : (NETCORE_ENGINEERING_TELEMETRY=Build) Could not restore Microsoft.NET.Workload.Emscripten.Current.Manifest-8.0.100-preview.1/8.0.0-alpha.1.23077.4 (can't find C:\Users\cloudtest\AppData\Local\Temp\workload-s1vkosld.1ds\nuget-cache\microsoft.net.workload.emscripten.current.manifest-8.0.100-preview.1\8.0.0-alpha.1.23077.4)

@radical can you please take a look?

[carlossanlop]

@lewing @radical there's a new browser error. Related?

Unhandled exception: Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException:
Could not find workload 'microsoft-net-runtime-android' extended by workload
'android' in manifest 'microsoft.net.sdk.android'
[/__w/1/s/artifacts/bin/dotnet-latest/sdk-manifests/7.0.100/microsoft.net.sdk.android/WorkloadManifest.json]

[carlossanlop]

The other CI failures consistently showing up are unrelated:

• "../sysdeps/nptl/futex-internal.h: No such file or directory."

• Libraries Test Run release mono linux arm64 Debug

• Roslyn source generator crash on mono/linux/arm64 #81123

  • https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-81398-merge-b7fb6c7e35e14ffa9a/Microsoft.Extensions.Logging.Generators.Roslyn3.11.Tests/1/console.bb427099.log?helixlogtype=result

• "The operation has timed out."

• Libraries Test Run release coreclr linux x64 Debug

• CI failure in System.Net.Http.Functional.Tests - Operation timeout #75611

• https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-81398-merge-a9778b6128c4415693/System.Net.Http.Functional.Tests/3/console.02dfb573.log?helixlogtype=result

[lewing]

there is currently a chicken and egg problem with the feature banding of the workloads when installer branding in main is behind runtime, this should resolve once the latest dotnet/installer build finishes. we'll add this to the list of issues with the feature banding logic.

the current installer is alpha.1 so it doesn't look into the preview.1 feature band so workload tests are finding the alpha.1 workload packs that came with installer not the newly built ones.