I couldn’t find a way to detect if the “-server” switch would be supported
without actually running the jvm, and then searching the value of a system
property (like: System.getProperty("java.vm.name")) for the text: “server”.
Seems nasty.
FWIW, the following docs suggest the “-server” mode is the default now on
non-32 bit jvms:
(http://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html - same doc
info for other os flavors)
-server
Selects the Java HotSpot Server VM. The 64-bit version of the JDK supports only
the Server VM, so in that case the option is implicit.
I guess I'm trying to make the case that just removing the “-server” arg is
acceptable. :)
Dan
> On Jan 5, 2016, at 11:03 AM, [email protected] wrote:
>
> From: Peter <[email protected] <mailto:[email protected]>>
> Subject: Re: Test Failures on ARM, maybe I'm missing setup?
> Date: January 4, 2016 at 9:46:52 PM EST
> To: "[email protected] <mailto:[email protected]>"
> <[email protected] <mailto:[email protected]>>
>
>
> Is there a way we can detect the platform, we use server for testing as jit
> optimisations are more agressive and more likely to highlight problems or
> bugs?
>
> Peter.
>
> Sent from my Samsung device.
>
> Include original message
> ---- Original message ----
> From: Dan Rollo <[email protected] <mailto:[email protected]>>
> Sent: 05/01/2016 08:20:52 am
> To: [email protected] <mailto:[email protected]>
> Subject: Re: Test Failures on ARM, maybe I'm missing setup?
>
> Thanks Greg, and Peter. I was able to apply the “remove -server” fix to
> qaDefaults.properties, and the test ran fine on a Pi. I’ve attached a patch
> with these fixes against trunk. If there is a better way to submit such a
> patch, please point me in the right direction ( - dare I ask about git? :) .
>
> Dan
