-
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
DisableBitTests.EnabledThroughFeatureSwitch/DisabledAlwaysInBrowser failures #103683
Comments
@tmds BinaryFormatter was moved to an OOB package (not part of shared SDK) in #103255 The code that checks whether it's enabled can be found here: runtime/src/libraries/Common/tests/TestUtilities/System/PlatformDetection.cs Lines 728 to 756 in 5c53e8e
I am afraid that it's going to require some debugging to see what does not work as expected |
Thanks for the pointers @adamsitnik! |
@adamsitnik and @ViktorHofer (because @adamsitnik's status indicates he is unavailable), I dug into this a bit deeper. I have a dll that is version 8.1. According to The test results are different when I run In Lines 74 to 78 in 7946e6f
|
The System.Runtime.Serialization.Formatters assembly with an 8.1.0.0 version is the one that supports serialization. The 9.0.0.0 assembly is the PNSE throwing one. |
I assumed 8.1 should not support serialization based on: runtime/src/libraries/Common/tests/TestUtilities/System/PlatformDetection.cs Lines 745 to 752 in 2fe4afa
I looked further into this difference. The assembly that is used by the In both cases the assembly version is 8.1.0.0. For the first invocation, the serialization implementation is present in the assembly, while the second command uses an assembly that throws PNSE. |
Oh sorry, I got this wrong. You are right, that the inbox implementation is pinned to 8.1.0.0. The OOB one has 9.0.0.0. runtime/src/libraries/System.Runtime.Serialization.Formatters/Directory.Build.targets Lines 5 to 12 in 2fe4afa
|
These tests are failing in our CI which is building with these flags:
The test failures are:
Probably this is triggered by the changes in: #103255.
@bartonjs do you have an idea what may be the issue?
cc @omajid
The text was updated successfully, but these errors were encountered: