You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Martin Dietze <di...@fh-wedel.de> on 2009/05/18 16:49:10 UTC

Building 1.3.6 from the source, test failures

Hi,

 I just checked out wicket 1.3.6 from the svn, changed into the
wicket-1.3.6 directory, ran `mvn package' and ran across these
test failures:

Failed tests: 
  test_1(org.apache.wicket.markup.html.header.testing.HeaderTest)
  testRenderHomePage_7(org.apache.wicket.markup.html.basic.SimplePageTest)
  testHeaderContribution1(org.apache.wicket.ajax.AjaxRequestTargetTest)
  testHeaderContribution3(org.apache.wicket.ajax.AjaxRequestTargetTest)
  test_2(org.apache.wicket.markup.html.header.inheritance.InheritanceHeadTest)
  testDomReadyOrder(org.apache.wicket.ajax.DomReadyOrderTest)
  testDetachPageAjaxRequest(org.apache.wicket.ComponentTest)

This is the test log for the first test:

-------------------------------------------------------------------------------
Test set: org.apache.wicket.markup.html.header.testing.HeaderTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.101 sec <<< FAILURE!
test_1(org.apache.wicket.markup.html.header.testing.HeaderTest)  Time elapsed: 0.022 sec  <<< FAILURE!
junit.framework.ComparisonFailure: org/apache/wicket/markup/html/header/testing/TestPage_ExpectedResult.html expected:<...languange="javascript" id="org-apache-wicket-mark
up-html-header-testing-TestExtendedPanel-0...> but was:<...id="org-apache-wicket-markup-html-header-testing-TestExtendedPanel-0" languange="javascript...>
        at junit.framework.Assert.assertEquals(Assert.java:81)
        at org.apache.wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:156)
        at org.apache.wicket.util.tester.WicketTester.assertResultPage(WicketTester.java:542)
        at org.apache.wicket.WicketTestCase.executeTest(WicketTestCase.java:84)
        at org.apache.wicket.markup.html.header.testing.HeaderTest.test_1(HeaderTest.java:43)

$ java -version
java version "1.6.0_07"
Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)


I have seen older references to this problem in the web, but (a) no clear solution and (b)
wonder why the problem is (still?) there?

Any hint?

Martin

-- 
----------- / http://herbert.the-little-red-haired-girl.org / -------------
=+= 
In my glass coffin I am waiting

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Building 1.3.6 from the source, test failures

Posted by Martin Dietze <di...@fh-wedel.de>.
On Tue, May 19, 2009, Martijn Dashorst wrote:

> http://lmgtfy.com/?q=wicket+java+6+fails+unit+tests
> 
> gives you:
> 
> https://issues.apache.org/jira/browse/WICKET-708
> 
> And in comment [1] Juergen says:
> 
> "This is due to java 1.6. The hashmap hash code implementation has
> changed which leads to a different internal sequence of values within
> the map. Since tag attributes are based on hashmap ..."

Oh, that explains it, thanks. Leaves the question whether it is
such a good idea to depend on the order of hash map entries in
the tests while of cause well knowing that it's probably not too
easy to come up with a good alternative approach :)

Cheers,

Martin

-- 
----------- / http://herbert.the-little-red-haired-girl.org / -------------
=+= 
This parrot is no more.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Building 1.3.6 from the source, test failures

Posted by Martijn Dashorst <ma...@gmail.com>.
http://lmgtfy.com/?q=wicket+java+6+fails+unit+tests

gives you:

https://issues.apache.org/jira/browse/WICKET-708

And in comment [1] Juergen says:

"This is due to java 1.6. The hashmap hash code implementation has
changed which leads to a different internal sequence of values within
the map. Since tag attributes are based on hashmap ..."

Martijn

[1] https://issues.apache.org/jira/browse/WICKET-708?focusedCommentId=12508898&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12508898

On Tue, May 19, 2009 at 10:07 AM, Martin Dietze <di...@fh-wedel.de> wrote:
> On Mon, May 18, 2009, Martijn Dashorst wrote:
>
> [quote order fixed]
>> On Mon, May 18, 2009 at 4:49 PM, Martin Dietze <di...@fh-wedel.de> wrote:
>
>> >  I just checked out wicket 1.3.6 from the svn, changed into the
>> > wicket-1.3.6 directory, ran `mvn package' and ran across these
>
>> Don't run the tests with java 6
>
> Thank you, the tests now do no longer fail. Just out of
> curiousity, wasn't Java 6 supposed to be downward compatible? I
> find this extremly confusing...
>
> Cheers,
>
> Martin
>
> --
> ----------- / http://herbert.the-little-red-haired-girl.org / -------------
> =+=
> * Free Speech Online!!! Support the Blue Ribbon Campaign! *
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Building 1.3.6 from the source, test failures

Posted by Martin Dietze <di...@fh-wedel.de>.
On Mon, May 18, 2009, Martijn Dashorst wrote:

[quote order fixed]
> On Mon, May 18, 2009 at 4:49 PM, Martin Dietze <di...@fh-wedel.de> wrote:

> > �I just checked out wicket 1.3.6 from the svn, changed into the
> > wicket-1.3.6 directory, ran `mvn package' and ran across these

> Don't run the tests with java 6

Thank you, the tests now do no longer fail. Just out of
curiousity, wasn't Java 6 supposed to be downward compatible? I
find this extremly confusing...

Cheers,

Martin

-- 
----------- / http://herbert.the-little-red-haired-girl.org / -------------
=+= 
* Free Speech Online!!! Support the Blue Ribbon Campaign! *

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: Building 1.3.6 from the source, test failures

Posted by Martijn Dashorst <ma...@gmail.com>.
Don't run the tests with java 6

Martijn

On Mon, May 18, 2009 at 4:49 PM, Martin Dietze <di...@fh-wedel.de> wrote:
> Hi,
>
>  I just checked out wicket 1.3.6 from the svn, changed into the
> wicket-1.3.6 directory, ran `mvn package' and ran across these
> test failures:
>
> Failed tests:
>  test_1(org.apache.wicket.markup.html.header.testing.HeaderTest)
>  testRenderHomePage_7(org.apache.wicket.markup.html.basic.SimplePageTest)
>  testHeaderContribution1(org.apache.wicket.ajax.AjaxRequestTargetTest)
>  testHeaderContribution3(org.apache.wicket.ajax.AjaxRequestTargetTest)
>  test_2(org.apache.wicket.markup.html.header.inheritance.InheritanceHeadTest)
>  testDomReadyOrder(org.apache.wicket.ajax.DomReadyOrderTest)
>  testDetachPageAjaxRequest(org.apache.wicket.ComponentTest)
>
> This is the test log for the first test:
>
> -------------------------------------------------------------------------------
> Test set: org.apache.wicket.markup.html.header.testing.HeaderTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.101 sec <<< FAILURE!
> test_1(org.apache.wicket.markup.html.header.testing.HeaderTest)  Time elapsed: 0.022 sec  <<< FAILURE!
> junit.framework.ComparisonFailure: org/apache/wicket/markup/html/header/testing/TestPage_ExpectedResult.html expected:<...languange="javascript" id="org-apache-wicket-mark
> up-html-header-testing-TestExtendedPanel-0...> but was:<...id="org-apache-wicket-markup-html-header-testing-TestExtendedPanel-0" languange="javascript...>
>        at junit.framework.Assert.assertEquals(Assert.java:81)
>        at org.apache.wicket.util.diff.DiffUtil.validatePage(DiffUtil.java:156)
>        at org.apache.wicket.util.tester.WicketTester.assertResultPage(WicketTester.java:542)
>        at org.apache.wicket.WicketTestCase.executeTest(WicketTestCase.java:84)
>        at org.apache.wicket.markup.html.header.testing.HeaderTest.test_1(HeaderTest.java:43)
>
> $ java -version
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Server VM (build 10.0-b23, mixed mode)
>
>
> I have seen older references to this problem in the web, but (a) no clear solution and (b)
> wonder why the problem is (still?) there?
>
> Any hint?
>
> Martin
>
> --
> ----------- / http://herbert.the-little-red-haired-girl.org / -------------
> =+=
> In my glass coffin I am waiting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.3.5 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org