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

Investigate the behavior difference in System.Runtime.Numeric when running on desktop #19874

Open
Tracked by #47244
tarekgh opened this issue Jan 11, 2017 · 3 comments
Open
Tracked by #47244
Labels
area-System.Numerics Cost:S Work that requires one engineer up to 1 week help wanted [up-for-grabs] Good issue for external contributors test-bug Problem in test source code (most likely)
Milestone

Comments

@tarekgh
Copy link
Member

tarekgh commented Jan 11, 2017

System.Runtime.Numeric has some different behaviors when running on desktop than when running on netcore. the PR dotnet/corefx#15050 has the places needed to be investigated which are marked with [SkipOnTargetFramework(TargetFrameworkMonikers.NetFramework)]

@tarekgh
Copy link
Member Author

tarekgh commented Jan 11, 2017

cc @mellinoe

@mellinoe mellinoe self-assigned this Jan 11, 2017
@tarekgh
Copy link
Member Author

tarekgh commented Jan 12, 2017

The following case is giving different results on desktop too

        public static void RunDoubleExplicitCastFromLargeBigIntegerTests()
        {
            DoubleExplicitCastFromLargeBigIntegerTests(0, 4, 32, 3);
        }
System.Numerics.Tests.cast_fromTest.RunDoubleExplicitCastFromLargeBigIntegerTests [FAIL]
    Assert.Equal() Failure
    Expected: ∞
    Actual:   0

@tarekgh
Copy link
Member Author

tarekgh commented Jan 12, 2017

one more case:

        public static void RunLargeValueLogTests()
        {
            LargeValueLogTests(0, 4, 64, 3);
        }
  System.Numerics.Tests.logTest.RunLargeValueLogTests [FAIL]
        Assert.True() Failure
        Expected: True
        Actual:   False

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
@maryamariyan maryamariyan added the untriaged New issue has not been triaged by the area owner label Feb 23, 2020
@tannergooding tannergooding removed the untriaged New issue has not been triaged by the area owner label Jul 6, 2020
@tannergooding tannergooding added the Cost:S Work that requires one engineer up to 1 week label Jan 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Numerics Cost:S Work that requires one engineer up to 1 week help wanted [up-for-grabs] Good issue for external contributors test-bug Problem in test source code (most likely)
Projects
None yet
Development

No branches or pull requests

5 participants