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

SdkAssemblyResolver improvements #2797

Merged
merged 5 commits into from
Aug 30, 2024

Conversation

Thorium
Copy link
Member

@Thorium Thorium commented Aug 6, 2024

It still seems we have unreliable integration tests.

I still blame the SdkAssemblyResolver not being able to pick proper .NET versions.

There were some "try finds" which just took first ever found version, and I think it should rather collect a list of versions to make the decision of proper version later.

Also added verbosity to intergration-test-log so we could better see what goes wrong, if something goes wrong.

…nt to collect all versions and evaluate the selection later.
@xperiandri
Copy link
Collaborator

I would prefer release pipeline to be fixed and run to completion before we merge new fixes

@Thorium
Copy link
Member Author

Thorium commented Aug 7, 2024

This one may actually help the pipeline. :-)

@xperiandri
Copy link
Collaborator

For now the issue is that pushing the same version of the package to NuGet does not skip it but fails

@Thorium
Copy link
Member Author

Thorium commented Aug 7, 2024

That's intentional I guess, NuGet packages cannot be updated.

@xperiandri xperiandri merged commit eeae957 into fsprojects:master Aug 30, 2024
3 checks passed
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.

2 participants