On 2011/05/03 17:51:18, rjrjr wrote:
Running ant clean dist-dev test, this appears to break the i18n suite
under
html unit.

Oops! Only tested with a -Dgwt.junit.testcase.includes (which obviously
didn't include I18N tests)

That seems weird though that simply running the JVM in a different
locale suddenly breaks tests of things that are emulated.

Testcase: testMessageDateTime took 0.15 sec
FAILED
Remote test failed at 172.31.131.172 / Mozilla/5.0 (Windows; U;
Windows NT
5.1; en-US; rv:1.9.0.19) Gecko/2010031422 Firefox/3.0.19
  expected=It is Feb 15, 2010 actual=It is 2010 Feb 15
junit.framework.AssertionFailedError: Remote test failed at
172.31.131.172 /
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.19)
Gecko/2010031422 Firefox/3.0.19
  expected=It is Feb 15, 2010 actual=It is 2010 Feb 15

Actually, 3 tests always fail for me, whichever locale I'm running them
in (including using es_MX, or removing the -Duser.language/user.region
system props altogether!)
And they always fail with the exact same error; so it looks more like a
regression in the I18N code (particularly as all other I18N tests pass).

test.dev.htmlunit:
     [echo] Writing test results to C:\Documents and Settings\tbr\Mes
documents\Mes Projets\gwt\trunk\build\out\user\test/dev-htmlunit/reports
for test.dev.htmlunit.tests
    [junit] WARNING: multiple versions of ant detected in path for junit

    [junit]
jar:file:/C:/eclipse/plugins/org.apache.ant_1.7.1.v20100518-1145/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit]      and
jar:file:/C:/Documents%20and%20Settings/tbr/Mes%20documents/Mes%20Projets/gwt/trunk/build/lib/gwt-dev.jar!/org/apache/tools/ant/Project.class
    [junit] Running com.google.gwt.i18n.I18NSuite
    [junit]  expected=It is Feb 15, 2010 actual=It is 2010 Feb 15)
    [junit]  expected=Es ist 15. Feb 2010 actual=It is 2010 Feb 15)
    [junit]  expected=Short: 2010-02-01 actual=Short: 2010-02-02)


http://gwt-code-reviews.appspot.com/1430801/

--
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to