* Unsafe on modern JVMs (if perhaps not quite as fast as VarHandle?). However, I'm not sure
       * exactly what we've benchmarked, and we certainly haven't benchmarked as far back as JDK 8.
       * (We also haven't benchmarked under Android. We continue to use UnsafeAtomicHelper there so
       * that we don't change the performance there, for better or for worse.) Fortunately, JVM

available CPUs. Not including hyper-threading.
If you want to explicitly specify the number of JVMs you can do so on the command
line:

----------------------------
./gradlew test -Dtests.jvms=8
----------------------------

Or in `~/.gradle/gradle.properties`:

----------------------------
systemProp.tests.jvms=8
----------------------------

     * Compares cipher suites names like "TLS_RSA_WITH_NULL_MD5" and "SSL_RSA_WITH_NULL_MD5",
     * ignoring the "TLS_" or "SSL_" prefix which is not consistent across platforms. In particular
     * some IBM JVMs use the "SSL_" prefix everywhere whereas Oracle JVMs mix "TLS_" and "SSL_".
     */
    internal val ORDER_BY_NAME =
      object : Comparator<String> {
        override fun compare(
          a: String,
          b: String,
        ): Int {

        return "Unknown";
    }

    /**
     * Gets the instance ID for this Fess instance.
     * Combines scheduler.target.name (if configured), hostname, and PID
     * to ensure uniqueness across multiple JVMs on the same host.
     *
     * @return The instance ID.
     */
    public String getInstanceId() {
        final String targetName = ComponentUtil.getFessConfig().getSchedulerTargetName();

            test.setWorkingDir(project.file(project.getBuildDir() + "/testrun/" + test.getName()));
            test.setMaxParallelForks(Integer.parseInt(System.getProperty("tests.jvms", BuildParams.getDefaultParallel().toString())));

            test.exclude("**/*$*.class");

            test.jvmArgs(
                "-Xmx" + System.getProperty("tests.heap.size", "512m"),

 *  Fix: The previous release would crash when running on Robolectric. We didn't anticipate
    running our Android artifact on the JVM platform!


## Version 5.0.0-alpha.15

_2025-05-28_

**This release introduces separate JVM and Android artifacts.** Until now, we've distributed OkHttp
as a JVM library that _detects_ Android capabilities at runtime, but that doesn't offer

              files=".*[/\\]platforms[/\\]jvm[/\\]language-jvm[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]jvm[/\\]language-jvm[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]tasks[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-jvm",
    "path": "platforms/jvm/testing-jvm",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "testing-jvm-infrastructure",
    "path": "platforms/jvm/testing-jvm-infrastructure",
    "unitTests": true,
    "functionalTests": false,

            <option value="$PROJECT_DIR$/platforms/jvm/jvm-compiler-worker" />
            <option value="$PROJECT_DIR$/platforms/jvm/jvm-services" />
            <option value="$PROJECT_DIR$/platforms/jvm/language-groovy" />
            <option value="$PROJECT_DIR$/platforms/jvm/language-java" />
            <option value="$PROJECT_DIR$/platforms/jvm/language-jvm" />
            <option value="$PROJECT_DIR$/platforms/jvm/normalization-java" />

import org.opensearch.action.admin.cluster.health.ClusterHealthResponse;
import org.opensearch.monitor.jvm.JvmStats;
import org.opensearch.monitor.jvm.JvmStats.BufferPool;
import org.opensearch.monitor.jvm.JvmStats.Classes;
import org.opensearch.monitor.jvm.JvmStats.GarbageCollectors;
import org.opensearch.monitor.jvm.JvmStats.Mem;
import org.opensearch.monitor.jvm.JvmStats.Threads;
import org.opensearch.monitor.os.OsProbe;