-
Notifications
You must be signed in to change notification settings - Fork 344
Change test projects to target netcoreapp2.1 #1736
Conversation
looks good |
FYI, I removed unnecessary or redundant project/package references. cc @davidfowl |
@@ -8,10 +8,8 @@ | |||
<PackageIconUrl>http://go.microsoft.com/fwlink/?linkid=833199</PackageIconUrl> | |||
</PropertyGroup> | |||
<ItemGroup> | |||
<PackageReference Include="System.Buffers" Version="$(CoreFxVersion)" /> | |||
<PackageReference Include="System.Buffers" Version="$(CoreFxStableVersion4_4)" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question: For a netstandard library, like System.Buffers.Primitives for example, is it better to reference a lower version of a package or higher (4.4.0 vs 4.3.0)? This change results in us referencing the higher version.
cc @ericstj
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typical best practice is to reference the lowest version that satisfies your dependency (both direct and indirect). Be careful not to reference a version lower than any of your other dependencies or you will cause a downgrade.
There are sometimes requirements that folks have (limiting test matrix, or limiting number of packages downloaded) that will cause them to break from this best practice and reference higher versions then they actually need, so don't be surprised if you find that this advice is not followed consistently.
error CS0433: The type 'ReadOnlySpan' exists in both 'System.Memory, Version=4.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'System.Runtime, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' [D:\j\workspace\windows_nt_de---4b678204\tests\System.Text.Primitives.Tests\System.Text.Primitives.Tests.csproj] This issue will be resolved after this PR/fix: |
The other issues will get fixed after the cli picks up the new shared framework. Right now it is picking up an old one from Aug 16. |
FYI - dotnet/cli#7606 moves the CLI to the latest shared framework. |
The test failures (such as the one shown below) will go away once we get a new dotnet CLI with the latest shared framework (which has the AsReadOnlySpan API). This is blocked on https://github.com/dotnet/coreclr/issues/13919 [xUnit.net 00:00:02.2852907] System.Text.Utf8.Tests.Utf8StringTests.SubstringFromTests(expected: "abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", s: "abbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", substring: "abbbbbbbb") [FAIL] |
Waiting for CLI with new shared framework (above 2.1.0-preview1-25719-04) which has the following changes: dotnet/coreclr#14057 |
@livarcocc @nguerrera @dsplaisted - it looks like the |
Adding @johnbeisner re: broken master CLI builds. Is it due to signing issues? |
@nguerrera https://devdiv.visualstudio.com/DevDiv/_build/index?buildId=1030130&_a=summary |
@johnbeisner, you fixed that, right? Is the fix just not RIed to master? Can you do that now? |
@nguerrera |
@VSadov, any idea what could be causing these build failures when we change the test projects to target netcoreapp2.1? I cannot reproduce this failure locally (on my Windows machine).
Edit: I was able to reproduce a failure on Ubuntu. Here are more detailed logs.
Build FAILED. |
@dotnet-bot test this please |
cc @dotnet/corefxlab-contrib |
After validating that tests targeting netcoreapp2.0 will pass using the latest packages (#1735), update the tests to target netcoreapp2.1.
Do NOT merge until the above mentioned PR is green.
We could update to 2.1 right away, but we should wait and make sure that the packages we depend on still work on netcoreapp2.0 first.
cc @shiftylogic, @KrzysztofCwalina