Skip to content

Conversation

@dotnet-maestro
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Oct 28, 2025

Note

This is a codeflow update. It may contain both source code changes from the source repo as well as dependency updates. Learn more here.

This pull request brings the following source code changes

From https://github.com/dotnet/sdk

@dotnet-maestro
Copy link
Contributor Author

@dotnet-maestro
Copy link
Contributor Author

Note

PRs from original repository included in this codeflow update:

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@dotnet-maestro
Copy link
Contributor Author

Note

PRs from original repository included in this codeflow update:

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@dotnet-maestro
Copy link
Contributor Author

Note

PRs from original repository included in this codeflow update:

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 1, 2025

Note

PRs from original repository included in this codeflow update:

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 3, 2025

Note

PRs from original repository included in this codeflow update:

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@dotnet-maestro
Copy link
Contributor Author

dotnet-maestro bot commented Nov 4, 2025

Important

There was a conflict in the PR branch when flowing source from https://github.com/dotnet/sdk/tree/0292a8566a346cfda579824d25eafbb7784bb2c2
Files conflicting with the head branch:

  • src/sdk/eng/Signing.props
    🔍 View file in dotnet/sdk vs VMR
  • src/sdk/src/Layout/Directory.Build.props
    🔍 View file in dotnet/sdk vs VMR
  • src/sdk/src/Layout/redist/targets/Crossgen.targets
    🔍 View file in dotnet/sdk vs VMR
  • src/sdk/src/Layout/redist/targets/GenerateLayout.targets
    🔍 View file in dotnet/sdk vs VMR

Updates from this subscription will be blocked until the conflict is resolved, or the PR is merged

💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance.

@akoeplinger
Copy link
Member

@MichaelSimons from what I can see the initial error was

[xUnit.net 00:00:07.84]         Executing: /__w/1/s/artifacts/obj/extracted-dotnet-sdk/dotnet publish /p:RestoreAdditionalProjectSources= --self-contained true -r centos.10-x64 /bl:/__w/1/s/artifacts/TestResults/Release/WebScenarioTests_WebApp_CSharp-publish-self-contained-centos.10-x64.binlog -o /__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/bin/publish
  Failed Microsoft.DotNet.SourceBuild.Tests.WebScenarioTests.VerifyScenario(scenario: TestScenario { Commands = PublishSelfContained, NoHttps = False, ScenarioName = "WebScenarioTests", Template = WebApp, Validate = Action`1 { Method = Void VerifyRuntimePacksForSelfContained(System.String), Target = null } }) [7 s]
  Error Message:
   System.InvalidOperationException : Failed to execute /__w/1/s/artifacts/obj/extracted-dotnet-sdk/dotnet publish /p:RestoreAdditionalProjectSources= --self-contained true -r centos.10-x64 /bl:/__w/1/s/artifacts/TestResults/Release/WebScenarioTests_WebApp_CSharp-publish-self-contained-centos.10-x64.binlog -o /__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/bin/publish
Exit code: 1
Determining projects to restore...
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102: Unable to find package Microsoft.NETCore.App.Runtime.linux-x64 with version (= 10.0.0-ci)
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 1485 version(s) in dotnet10 [ Nearest version: 10.0.0-preview.1.25077.19 ]
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 1417 version(s) in dotnet9 [ Nearest version: 9.0.0-rtm.24516.5 ]
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 206 version(s) in dotnet-public [ Nearest version: 10.0.0-preview.1.25080.5 ]
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 0 version(s) in /__w/1/s/artifacts/obj/extracted-dotnet-sdk/library-packs
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 0 version(s) in darc-pub-dotnet-aspnetcore-3cc83de
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 0 version(s) in darc-pub-dotnet-runtime-d398172
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 0 version(s) in dotnet10-transport
/__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj : error NU1102:   - Found 0 version(s) in dotnet9-transport
  Failed to restore /__w/1/s/artifacts/bin/Microsoft.DotNet.SourceBuild.Tests/Release/projects-202511030258018417/WebScenarioTests_WebApp_CSharp/WebScenarioTests_WebApp_CSharp.csproj (in 577 ms).

why is it trying to restore the linux-x64 runtime pack and not the centos.10-x64 which was produced by the build? I think this is the real issue and we were just masking it before.

@dotnet-maestro
Copy link
Contributor Author

Important

The source repository has received code changes from an opposite flow. Any additional codeflows into this PR may potentially result in lost changes.

Please continue with one of the following options:

  1. Close or merge this PR and let the codeflow continue normally
  2. Close or merge this PR and receive the new codeflow immediately by triggering the subscription:
    darc trigger-subscriptions --id b80ccdd7-504a-4efb-b58b-d6480d0a64d9
  3. Force-flow new changes into this PR at your own risk (some PR commits might be reverted):
    darc trigger-subscriptions --force --id b80ccdd7-504a-4efb-b58b-d6480d0a64d9

💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance.

@MichaelSimons
Copy link
Member

why is it trying to restore the linux-x64 runtime pack and not the centos.10-x64 which was produced by the build? I think this is the real issue and we were just masking it before.

The reason for this stems from https://github.com/dotnet/dotnet/pull/3123/files#diff-b3a09e242d3219b910364fa94d2654b8ec17d19a5f79a924eba97da538fba4a0R707. Source-build dynamically adds the current RID to NetCoreAppHostRids, NetCoreRuntimePackRids, and AspNetCoreRuntimePackRids here because those are the packs it builds. Because the 10 known framework reference was updated to Net100RuntimePackRids, it no longer get the current rid added.

The other problem is that all of the Known references for 10 aren't reference the 10.0 versions - example. Updating this to 10 introduces other issues in tests because the 10 runtime is not installed with the 11 SDK. It feels like these issues all stem from the templates not being updated to 11 yet.

I don't think that is something to fix in this PR. My recommendation is to disable the source-build web scenario test until the templates have been updated and log a tracking issue to re-enable them.

@MichaelSimons MichaelSimons requested review from a team as code owners November 24, 2025 16:34
@ViktorHofer
Copy link
Member

ViktorHofer commented Dec 3, 2025

Hmm this is blocking the rebranding work to some degree. We can workaround it (by making changes directly there) but no dependency flow from sdk into the VMR for over 6 weeks is tragic. cc @marcpopMSFT

Doesn't look like there's much work left here? Some assembly that fails to get invoked via dotnet in the fsharp repo.

@mthalman
Copy link
Member

mthalman commented Dec 4, 2025

In the bootstrap of fsharp of source build stage 2, it's trying to reference Microsoft.NETCore.App.Runtime.linux-x64 (the portable package) when it should be using microsoft.netcore.app.runtime.centos.10-x64 (non-portable).

/__w/1/s/src/fsharp/buildtools/fslex/fslex.fsproj error NU1100: Unable to resolve 'Microsoft.NETCore.App.Runtime.linux-x64 (= 10.0.0-ci)' for 'net10.0'. PackageSourceMapping is enabled, the following source(s) were not considered: /__w/1/s/.dotnet/library-packs, /__w/1/s/.dotnet/sdk/10.0.100-ci/FSharp/library-packs, prebuilt, previously-source-built, reference-packages, source-built-source-build-reference-packages, source-built-transport-arcade. [/__w/1/s/src/fsharp/buildtools/fslex/fslex.fsproj]

Investigating...

@mthalman
Copy link
Member

mthalman commented Dec 4, 2025

In the bootstrap of fsharp of source build stage 2, it's trying to reference Microsoft.NETCore.App.Runtime.linux-x64 (the portable package) when it should be using microsoft.netcore.app.runtime.centos.10-x64 (non-portable).

/__w/1/s/src/fsharp/buildtools/fslex/fslex.fsproj error NU1100: Unable to resolve 'Microsoft.NETCore.App.Runtime.linux-x64 (= 10.0.0-ci)' for 'net10.0'. PackageSourceMapping is enabled, the following source(s) were not considered: /__w/1/s/.dotnet/library-packs, /__w/1/s/.dotnet/sdk/10.0.100-ci/FSharp/library-packs, prebuilt, previously-source-built, reference-packages, source-built-source-build-reference-packages, source-built-transport-arcade. [/__w/1/s/src/fsharp/buildtools/fslex/fslex.fsproj]

Investigating...

This is caused by the same issue described in #3123 (comment), specifically this change: dotnet/sdk#51429.

It causes the KnownFrameworkReference of the built SDK to be this:

<KnownFrameworkReference Include="Microsoft.NETCore.App"
                              TargetFramework="net10.0"
                              RuntimeFrameworkName="Microsoft.NETCore.App"
                              DefaultRuntimeFrameworkVersion="10.0.0-ci"
                              LatestRuntimeFrameworkVersion="10.0.0-ci"
                              TargetingPackName="Microsoft.NETCore.App.Ref"
                              TargetingPackVersion="10.0.0-ci"
                              RuntimePackNamePatterns="Microsoft.NETCore.App.Runtime.**RID**"
                              RuntimePackRuntimeIdentifiers="linux-arm;linux-arm64;linux-musl-arm64;linux-musl-x64;linux-x64;osx-x64;tizen.4.0.0-armel;tizen.5.0.0-armel;win-arm64;win-x64;win-x86;linux-musl-arm;osx-arm64;linux-s390x;linux-loongarch64;linux-bionic-arm;linux-bionic-arm64;linux-bionic-x64;linux-bionic-x86;linux-ppc64le;freebsd-x64;freebsd-arm64;linux-riscv64;linux-musl-riscv64;linux-musl-loongarch64;android-arm64;android-x64"
                              />

This lacks the centos.10-x64 RID in RuntimePackRuntimeIdentifiers.

@akoeplinger - You mention that this could be resolved by the .NET 11 rebranding? dotnet/sdk#51429 (comment)

@mthalman
Copy link
Member

mthalman commented Dec 5, 2025

@dotnet-maestro dotnet-maestro bot merged commit d65136b into main Dec 9, 2025
16 checks passed
@dotnet-maestro dotnet-maestro bot deleted the darc-main-7afc171a-4c5d-4bc3-bc39-a7dba167d7c7 branch December 9, 2025 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

6 participants