On Mon, Sep 30, 2019 at 4:09 PM Thorsten Schöning <tschoen...@am-soft.de>
wrote:

> Guten Tag Martin Grigorov,
> am Montag, 30. September 2019 um 13:25 schrieben Sie:
>
> > Does it always break the same way ?
>
> Yes.
>
> > Can you build 8.7.0-SNAPSHOT, i.e. current HEAD of wicket-8.x branch ?
>
> No, exactly the same error.
>
> > I
> > just built it locally without any issues. Same Java version but on Linux,
> > Maven 3.6.2.
>
> I've used Maven 3.6.0, but updating to 3.6.2 doesn't change a thing.
> What does make the project succeed is ignoring one of the tests:
>
> >         @Ignore// broken in Wicket 8.0. Needs debugging!
> >         @Test
> >         public void shouldNotMonitorJamonAdminPageItSelf()
> >         {
> >                 wicketTester.startPage(JamonAdminPage.class);
> >                 assertEquals(0,
> MonitorFactory.getMonitor("JamonAdminPage", "ms.").getHits(), 0);
> >                 FormTester formTester =
> wicketTester.newFormTester("adminPanel:adminForm");
> >                 formTester.setValue("monitorLabel", "J");
> >
>  wicketTester.executeAjaxEvent("adminPanel:adminForm:monitorLabel",
> "keyup");
> >                 assertEquals(0,
> MonitorFactory.getMonitor("JamonAdminPage", "ms.").getHits(), 0);
> >         }
>
>
> https://github.com/wicketstuff/core/blob/master/jamon-parent/jamon/src/test/java/org/wicketstuff/jamon/request/cycle/JamonMonitoredRequestCycleTest.java#L72
>
> There are other tests in that file ignored the same way already. so
> how to proceed from here, creating an issue? Any ideas on how to debug
> this further?
>

It will be good to find what in your environment causes the problem.
Maybe it is some environment variable, or your system locale, or something
else.
For me this test passes. It must pass at Maxim's machine as well because he
built the release.
Could someone else with Windows run the test and report ?


>
> My guess is that there's really some System.exit triggered somewhere.
> I don't see any clue that the JVM is crashing becuase of memory errors
> or exceptions.
>

If there is JVM crash then there must be a hs_errPID.txt file in the Maven
process working folder. It will give you more information what went wrong.


>
> Mit freundlichen Grüßen,
>
> Thorsten Schöning
>
> --
> Thorsten Schöning       E-Mail: thorsten.schoen...@am-soft.de
> AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
>
> Telefon...........05151-  9468- 55
> Fax...............05151-  9468- 88
> Mobil..............0178-8 9468- 04
>
> AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
>
>

Reply via email to