-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Test: System.Data.Tests.SqlTypes.SqlStringTest/SqlDateTimeToSqlString failed with "Xunit.Sdk.EqualException" #23192
Comments
@tarekgh I'm guessing all of these need to be changed to run remotely:
|
(Not suggesting you do it , just thinking aloud) |
Yes, in general setting current culture or current UI culture should be done remotely in our tests. |
@corivera the correct pattern is something like public class TestFixtureName: RemoteExecutorTestBase
{
...
[Fact]
public void TestName()
{
RemoteInvoke(() =>
{
CultureInfo.CurrentCulture = new CultureInfo("en-US");
// body of test
return SuccessExitCode;
}).Dispose();
} All the tests setting CurrentCulture should follow this pattern. There's some others outside of System.Data.Common but most likely fixing these should avoid this particular test failure. |
@nchikanov perhaps you coudl grab this cleanup as a quick stocking stuffer task? |
@nchikanov can you please prepare a port to release/uwp6.0 and send mail to get commit permission. |
Opened on behalf of @JiayiLi1
The test
System.Data.Tests.SqlTypes.SqlStringTest/SqlDateTimeToSqlString
has failed.Assert.Equal() Failure\r
? (pos 0)\r
Expected: 10/22/2002 9:52:30 AM\r
Actual: 22/10/2002 9:52:30 AM\r
? (pos 0)
Build : UWP 6.0 - 20170815.01 (UWP F5 Tests)
Failing configurations:
Detail: https://mc.dot.net/#/product/netcore/uwp60/source/official~2Fcorefx~2Frelease~2Fuwp6.0~2F/type/test~2Ffunctional~2Fuwp~2F/build/20170815.01/workItem/System.Data.Common.Tests/analysis/xunit/System.Data.Tests.SqlTypes.SqlStringTest~2FSqlDateTimeToSqlString
The text was updated successfully, but these errors were encountered: