Skip to content

Switch to FsCheck for fsi restore tests - #20210

Merged
abonie merged 2 commits into
mainfrom
fscheck-fsi-restore-tests
Aug 6, 2026
Merged

Switch to FsCheck for fsi restore tests#20210
abonie merged 2 commits into
mainfrom
fscheck-fsi-restore-tests

Conversation

@abonie

Copy link
Copy Markdown
Member

#20205 did not unblock internal CI, probably because MessagePack has dependencies on net472 that are not cached on signed builds. FsCheck depends on FSharp.Core, but that should be cached.

MessagePack has dependencies on net472 that are not cached on signed
builds. FsCheck depends on FSharp.Core, but that should be cached.
@github-actions

Copy link
Copy Markdown
Contributor

✅ No release notes required

T-Gro
T-Gro previously approved these changes Aug 5, 2026
@github-project-automationgithub-project-automationBot moved this from New to In Progress in F# Compiler and ToolingAug 5, 2026
@github-actionsgithub-actionsBot added the AI-Tooling-Check-Bypassed Tooling check: non-fork PR, not diff-analyzed label Aug 5, 2026
@abonie
abonie enabled auto-merge (squash) August 6, 2026 09:22
@abonie
abonie merged commit e4d4473 into mainAug 6, 2026
48 checks passed
bartelink pushed a commit to bartelink/fsharp that referenced this pull request Aug 6, 2026
* Switch to FsCheck for fsi restore tests
MessagePack has dependencies on net472 that are not cached on signed
builds. FsCheck depends on FSharp.Core, but that should be cached.
* Add logging in case of failed test
abonie added a commit that referenced this pull request Aug 19, 2026
* Switch from Newtonsoft to MessagePack restore in fsi tests (#20205)
* Bump Newtonsoft version restored in fsi tests
* Switch from Newtonsoft to FsCheck for #r test
* Make FSI nuget-restore tests robust to central package management
The two FsiCliTests that exercise `#r "nuget:"` restore hardcoded
Newtonsoft.Json 13.0.3. After central package management with transitive
pinning was enabled, only the centrally-pinned version is restored into the
offline cache used by the internal signed build, so requesting 13.0.3 failed
there (version-resolution NUxxxx diagnostics on stdout).
Instead of hardcoding a version (which would silently drift on every central
bump), bake the centrally-pinned version into the test assembly via
AssemblyMetadata and read it at runtime. Switch the target package from
Newtonsoft.Json (a removal candidate) to MessagePack, which is actively
maintained, published on public nuget.org (so online public CI restore works)
and centrally pinned + restored transitively by the product (so it is present
in the internal offline cache).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df9d1550-25ab-4466-ae43-8c7f106f4e49
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df9d1550-25ab-4466-ae43-8c7f106f4e49
* Switch to FsCheck for fsi restore tests (#20210)
* Switch to FsCheck for fsi restore tests
MessagePack has dependencies on net472 that are not cached on signed
builds. FsCheck depends on FSharp.Core, but that should be cached.
* Add logging in case of failed test
* Bump FSharp.Core servicing version to 10.1.401
10.1.400 is already published on nuget.org, so Check_Published_Package_Versions FSCore fails. Bump FSBuildVersion 400->401.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 7d778863-b4d5-4e3d-95ba-980fd2eafc81
---------
Co-authored-by: Adam Boniecki <20281641+abonie@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: df9d1550-25ab-4466-ae43-8c7f106f4e49
Copilot-Session: 7d778863-b4d5-4e3d-95ba-980fd2eafc81
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AI-Tooling-Check-BypassedTooling check: non-fork PR, not diff-analyzed

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants

@abonie@T-Gro