Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add latest .NET 8 runtime to global.json #10659

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

DustinCampbell
Copy link
Member

Since we updated to a .NET 9 SDK, the
MS.ANC.Razor.Microbenchmarks.Generator unit tests have failed to run locally. This is because these test use Benchmark.NET, which performs a builder at runtime targeting .NET 8. This works fine in CI because it uses a .NET 8 SDK.

This change just adds the most recent .NET 8 runtime version to the list of runtimes in Razor's global.json. So, it'll get installed into the .dotnet folder and the Microbenchmarks.Generator will run and stop reporting a spurious error.

Since we updated to a .NET 9 SDK, the
MS.ANC.Razor.Microbenchmarks.Generator unit tests have failed to run
locally. This is because these test use Benchmark.NET, which performs a
builder at runtime targeting .NET 8. This works fine in CI because it
uses a .NET 8 SDK.

This change just adds the most recent .NET 8 runtime version to the
list of runtimes in Razor's global.json. So, it'll get installed into
the .dotnet folder and the Microbenchmarks.Generator will run and stop
reporting a spurious error.
@DustinCampbell DustinCampbell requested review from a team as code owners July 22, 2024 19:03
@@ -5,7 +5,8 @@
"dotnet": [
"2.1.30",
"$(MicrosoftNETCoreBrowserDebugHostTransportPackageVersion)",
"3.1.30"
"3.1.30",
"8.0.7"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if this is needed then 9e8dbcc or if the correct runtime will be installed in CI as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I imagine it isn't needed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll try removing it and see if CI passes with this global.json tweak.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jjonescz: It looks like you were right. This is no longer needed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the better fix!

@DustinCampbell DustinCampbell merged commit f54c416 into dotnet:main Jul 22, 2024
12 checks passed
@DustinCampbell DustinCampbell deleted the add-8.0-to-global-json branch July 22, 2024 23:00
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Jul 22, 2024
@RikkiGibson RikkiGibson modified the milestones: Next, 17.12 Preview 1 Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants