Add Oxpecker repository to build check - #20065
Conversation
✅ No release notes required |
This comment has been minimized.
This comment has been minimized.
|
CI fails at I've no idea why, locally it builds fine with 10.0.100 or later |
It loads ns20 FSharp.Core which has no IAD support. |
This doesn't make sense, all Oxpecker projects target .NET 10, so ns21 should be chosen, not ns20. |
|
I think it's the shims to use local compiler in the CI, they probably add the reference to ns20 library. That msbuild prefers it is another story. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
…Core
The regression-test harness referenced the netstandard2.0 FSharp.Core for every
consuming project. A net5.0+/.NET 10 project resolves the FSharp.Core NuGet
package to its netstandard2.1 assembly, which (unlike netstandard2.0) exposes the
IAsyncDisposable-based task-builder 'Using' overload. Forcing netstandard2.0 broke
Oxpecker projects that use 'use'/'use!' with IAsyncDisposable inside task { }.
Select the FSharp.Core assembly the way NuGet would (netstandard2.0 for .NET
Framework/netstandard2.0 consumers, netstandard2.1 otherwise). The reference is
added in a target so TargetFramework is known, and runs before ResolvePackageAssets
so it still wins package conflict resolution over any transitively pulled FSharp.Core.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…NU1902/NU1903 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
…Bug4861) The module used the no-op RunTestCasesInSequence marker, so its #r/#load script tests ran concurrently with other collections while sharing the global checker and process-global reference resolver. This intermittently dropped closure diagnostics, causing ExactlyOneError.Bug4861 to observe 0 diagnostics for a missing '#r' reference. Use the NotThreadSafeResourceCollection (DisableParallelization) like other reference-resolution-sensitive test modules. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…termittent MSB4057 The EndToEndBuildTests job runs '.\Build.cmd -c Release -pack' without -ci, so Arcade treats it as a local build and re-enables UpdateXlfOnBuild. This intermittently fails on the multi-targeted FSharp.Core build with: error MSB4057: The target "UpdateXlf" does not exist in the project. [TargetFramework=netstandard2.1] (dotnet#19961). Updating xlf files is never needed in CI, so disable it for this step, matching the existing pattern used by tests/ILVerify/ilverify.ps1. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
|
🔍 Tooling Safety Check — Affects-Build-Infra, Affects-Restore
|
|
@copilot resolve the merge conflicts in this pull request |
Description
Added Oxpecker repository to build check to prevent issues like #20059