-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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] System.Numerics.Tensors tests failing on windows/helix #52134
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsSimilar issue to
|
dotnet-issue-labeler
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Apr 30, 2021
ViktorHofer
removed
the
untriaged
New issue has not been triaged by the area owner
label
May 5, 2021
radekdoulik
added a commit
to radekdoulik/runtime
that referenced
this issue
May 10, 2021
When running `System.Numerics.Tensors` tests on windows and targeting `Browser`,the line ending differs between host and target systems. Compensate for that by using `Assert.Equal(..., ignoreLineEndingDifferences: true)`. Also replace the compile time new line when creating `expectedNoSpace` string. The `Browser` Environment.NewLine is `\n`, while windows use `\r\n`. https://github.com/dotnet/runtime/blob/5bd0edfe860e41bdfd690d3743e730594307292e/src/libraries/System.Private.CoreLib/src/System/Environment.UnixOrBrowser.cs#L51
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
May 10, 2021
radekdoulik
added a commit
that referenced
this issue
May 13, 2021
* Fixes: #52134 When running `System.Numerics.Tensors` tests on windows and targeting `Browser`,the line ending differs between host and target systems. Compensate for that by using `Assert.Equal(..., ignoreLineEndingDifferences: true)`. Also replace the compile time new line when creating `expectedNoSpace` string. The `Browser` Environment.NewLine is `\n`, while windows use `\r\n`. https://github.com/dotnet/runtime/blob/5bd0edfe860e41bdfd690d3743e730594307292e/src/libraries/System.Private.CoreLib/src/System/Environment.UnixOrBrowser.cs#L51 * Use LineEndingsHelper, make CompiledNewline public * Enable fixed tests
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
May 13, 2021
ghost
locked as resolved and limited conversation to collaborators
Jun 12, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Similar issue to
S.T.Json
, the line endings are different after round trip.The text was updated successfully, but these errors were encountered: