-
Notifications
You must be signed in to change notification settings - Fork 132
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
dotnet format tests are failing in main #3004
Comments
Underlying issue has been resolved, closing. |
@MichaelSimons what was the underlying issue? how did you solve this? |
I'm not sure why this was closed. Trying this today I still see the issue in main and the source-build unit test is still disabled. re-opening. |
This seems related to dotnet/format#1785 |
I tried running the dotnet format tests and it appears a ref assemblies is being loaded. This needs to be addressed for .NET 8.0
|
Fixed with dotnet/installer#17238 |
The fix from dotnet/installer#17238 didn't pass in the internal CI run. It's failing on the Alpine leg:
|
Well, this is odd. I'll test this locally to understand why it doesn't work on Alpine. |
This seems like another issue with MSBuildLocator - on Alpine it's not finding hostfxr library which is used for discovery of SDK/MSBuild paths. @mthalman @MichaelSimons should we condition this test to not run on Alpine? |
Yes and link to a product issue. |
Where would the comment/link go - vmr yaml file (this is where we condition OmniSharp tests - https://github.com/dotnet/installer/blob/6fa2d3d9a6b9c445d396080845c375dc5b5480a4/eng/pipelines/templates/stages/vmr-build.yml#L85) or source file for dotnet-format tests? |
I would say the build definition. We should also have a tracking issue on our side that links to the product issue so that we re-enable this test. |
Fixed with dotnet/installer#17238 and conditioned the Alpine leg with dotnet/installer#17247 |
Failing CI build (internal Microsoft link)
This last passed CI on dotnet/installer@319773e. There were a few commits after that before the next failing CI run on dotnet/installer@d117d57.
The text was updated successfully, but these errors were encountered: