-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Unit Tests failing for .NET 4.0 #69
Comments
Thanks for reporting this. I think that you've (possibly) surfaced that the changes in my commit here d8b8acd may not in fact correctly resolve the (similar/same?) issue I'd been seeing on my own system. Prior to that commit, when I ran the entire test-suite on ,my system those same tests also failed under .NET 4.0 (and passed under .NET 3.5). From this, I concluded that (perhaps) some changes to .NET 4.0 libs may have introduced the failure I'd been seeing. As you can see from the commit, my response had been to provide a different set of expectations for these same tests under .NET 4.0 than .NET 3.5. This change has fixed the issue on my system, but apparently broken these same tests on your system :( This suggests that it may NOT in fact be .NET 4.0 changes that are in play here but instead potentially something else entirely. If possible, to help us isolate the actual cause of the pass/fail results being one way on my system and another way on yours, could you please provide us some info (as follows) as well as perform an experiment for us? Requested Information:
The experiment: Thanks again for identifying (and reporting!) this issue; hopefully your additional data-points will permit us to isolate the underlying cause of the issue that results in the different test-pass/fails you and I are seeing on our respective systems. |
Oh, and one more piece of information if possible: can you tell me the locale for which your OS is configured when you run the tests (e.g., EN-US or other)? Thanks! |
My machine is Win7 64bit with Visual Studio 2010. I was using EN-AU but changed it to EN-US with the same result. I reverted my code to the commit you mentioned and as you expected, the tests passed. Hope this helps. |
Yes, it very much does help, thanks for taking the time to do this. I'm on Windows 8.1, x64, and VS 2013. Your results help to confirm my suspicion that this is in fact NOT a change introduced in .NET 4.0 but is instead a change made in Windows itself. I suspect strongly that what's happened here is that the localization support on Windows 8.x is different than that on Windows 7 (for the locale used in those tests) and that this is the source of the behavior you and I are each seeing here. Its not at all uncommon for such minor tweaks in localization to be rolled out in OS releases, either to correct improper localization elements (e.g., bug-fix) or to permit localizations to continue to evolve as various locales change their 'rules' for the "official" representations of various elements in their respective languages. There are 'standards' that govern most of these things, and the two things we know about standards are a) everybody has their own :) but more importantly, b) they do change and evolve over time. I'll dig into whether I can confirm that this is indeed the case here, and if so I'll try to work some recognition of the ambient OS into the tests or the #ifdef that's in these tests before we go to GA. The good news (if there is any to be found here) is that this points to the ASSERTS being (possibly) incorrect based on the platform on which the tests are run, but also points to the actual behavior of the system-under-test actually still behaving 100% correctly, so its likely NOT a bug in the code per se. Thanks again for your identifying this issue and and for working with us to gather more info to assist in isolating it. I'd like to leave this issue open until I'm able to confirm my hypothesis and to work a fix into the test code. Cheers, -Steve B. |
Tracked under https://jira.spring.io/browse/SPRNET-1570 and fixed in 0311d36. Please do a fresh pull from ORIGIN/MASTER and verify that these changes result in passing tests for you on Windows7. If so, comment here and I'll close this issue and the corresponding JIRA ticket. |
@vivf86 have you had the time to test this? |
Closing issue as machine-specific or other since .NET 4.0 tests pass on several other computers as well as the latest CI builds as well. |
For the .NET 4.0 build for the RC1 code, the following tests are failing in Spring.Core.Tests.2010:
Spring.Globalization.Formatters.CurrencyFormatterTests
-FormatUsingCustomSettings
-FormatUsingDefaults
-ParseUsingCustomSettings
-ParseUsingDefaults
Spring.Globalization.Formatters.DateTimeFormatterTests
-FormatUsingDefaults
-ParseUsingDefaults
I have verified on my machine commented these tests out on my machine and the build completes successfully. I haven't attempted to fix them because some of the assertions have funny characters in them and I'm not sure what's required there.
Also I'm not sure if this is machine specific. It's possible there are issues with my environment. However, I have compiled the milestone versions in the past with no issues.
Build log extract is included below.
The text was updated successfully, but these errors were encountered: