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

WASM: Enable System.Memory tests #39319

Merged
merged 1 commit into from
Jul 15, 2020

Conversation

akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Jul 14, 2020

One test failed with an issue: #39311

Also noticed that StringTests.cs is included from the CommonTestPath, this is a historical artifact from when System.Memory built for netfx/netstandard so we could run tests on those configs.
We no longer need it since StringTests.cs is already ran in System.Runtime.Tests.

One test failed with an issue: dotnet#39311

Also noticed that StringTests.cs is included from the CommonPath, this is a historical artifact from when System.Memory built for netfx/netstandard so we could run tests on those configs.
We no longer need it since StringTests.cs is already ran in System.Runtime.Tests.
@@ -171,8 +171,6 @@
<Compile Include="ReadOnlySpan\ToArray.cs" />
<Compile Include="ReadOnlySpan\ToString.cs" />
<Compile Include="ReadOnlySpan\ToUpperLower.cs" />
<Compile Include="$(CommonTestPath)Tests\System\StringTests.cs"
Copy link
Member

Choose a reason for hiding this comment

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

We're just removing the file from the csproj and not moving it down to System.Runtime.Tests to avoid conflicts since I'll be putting up a PR soon to fix tests on Browser in that file.

@akoeplinger akoeplinger merged commit 5929baa into dotnet:master Jul 15, 2020
@akoeplinger akoeplinger deleted the wasm-system-memory branch July 15, 2020 10:08
@karelz karelz added this to the 5.0.0 milestone Aug 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants