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 .NET Standard 2.1 support #3530

Merged
merged 29 commits into from
Apr 2, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
29 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -38,24 +38,6 @@ let ``#2289 Paket 4.x install command takes hours to complete``() =
nunitVersion
|> shouldBeSmallerThan (SemVer.Parse "3.0")

[<Test; Flaky>]
let ``#2294 Cannot pin NETStandard.Library = 1.6.0``() =
Copy link
Member

Choose a reason for hiding this comment

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

I feel like both of these are good tests, we should somehow keep them or set them to ignore.
In fact I think if they fail this indicates a regression in the resolver unable to find a solution in the specified test-timeout.
So what looked like "flaky" might just be a perf regression here?

Copy link
Member

Choose a reason for hiding this comment

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

On the other hand, yes resolving this might have become harder with the release of new packages.

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 don't think it was a regression - we fixed a resolver bug and it that made it slower. shit happens

Copy link
Member

Choose a reason for hiding this comment

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

we fixed a resolver bug and it that made it slower

Isn't that the definition of a perf regression ;)
Anyway I think getting the CI green again is more important than these tests, so fine by me.

Copy link
Member Author

Choose a reason for hiding this comment

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

no. it never was faster - it was just wrong

let lockFile = update "i002294-pin-netstd16"
lockFile.Groups.[Constants.MainDependencyGroup].Resolution.[PackageName "NETStandard.Library"].Version
|> shouldEqual (SemVer.Parse "1.6")

//lots of downloaded files => big disk size, better cleanup if test pass
System.IO.Directory.Delete(scenarioTempPath "i002294-pin-netstd16", true)

[<Test; Flaky>]
let ``#2294 pin NETStandard.Library = 1.6.0 Strategy Workaround``() =
let lockFile = update "i002294-withstrategy"
lockFile.Groups.[Constants.MainDependencyGroup].Resolution.[PackageName "NETStandard.Library"].Version
|> shouldEqual (SemVer.Parse "1.6")

//lots of downloaded files => big disk size, better cleanup if test pass
System.IO.Directory.Delete(scenarioTempPath "i002294-withstrategy", true)

[<Test>]
let ``#2922 paket can jump out of loop of doom``() =
try
Expand Down

This file was deleted.

This file was deleted.