* 2. Tests on hardcoded datasets include non-finite values for chains starting with scale(10);
   * 3. Tests on a mechanically generated dataset for chains starting with percentiles();
   * 4. Tests of illegal usages of the API.
   */

  /*
   * Covering every combination would lead to an explosion in the number of tests. So we cover only:
   * - median with compute taking a double-collection and with computeInPlace;

   * 2. Tests on hardcoded datasets include non-finite values for chains starting with scale(10);
   * 3. Tests on a mechanically generated dataset for chains starting with percentiles();
   * 4. Tests of illegal usages of the API.
   */

  /*
   * Covering every combination would lead to an explosion in the number of tests. So we cover only:
   * - median with compute taking a double-collection and with computeInPlace;

* A pod’s Quality of Service Class is now available in its Status.
* Upgrade cAdvisor library to v0.25.0. Notable changes include,
  - Container filesystem usage tracking disabled for device mapper due to excessive
    IOPS.
  - Ignore `.mount` cgroups, fixing disappearing stats.
* A new field `terminationMessagePolicy` has been added to containers that allows

  <mime-type type="application/vnd.oma.dd2+xml">
    <glob pattern="*.dd2"/>
  </mime-type>
  <mime-type type="application/vnd.oma.drm.risd+xml"/>
  <mime-type type="application/vnd.oma.group-usage-list+xml"/>
  <mime-type type="application/vnd.oma.poc.detailed-progress-report+xml"/>
  <mime-type type="application/vnd.oma.poc.final-report+xml"/>
  <mime-type type="application/vnd.oma.poc.groups+xml"/>

   * of Java 20, it always throws an exception, and as of Java 26, the method does not even exist.
   * For now, we continue using it to clean up under older JDKs.
   *
   * Our usages should at least be *relatively* safe: Typically, threads started by a test are dying
   * at the end of the test, so there is no object state put at risk by stopping the threads

   * of Java 20, it always throws an exception, and as of Java 26, the method does not even exist.
   * For now, we continue using it to clean up under older JDKs.
   *
   * Our usages should at least be *relatively* safe: Typically, threads started by a test are dying
   * at the end of the test, so there is no object state put at risk by stopping the threads

 * com.google.common.collect.Ordering} (otherwise).
 *
 * <h3>Relationship to {@code Ordering}</h3>
 *
 * <p>In light of the significant enhancements to {@code Comparator} in Java 8, the overwhelming
 * majority of usages of {@code Ordering} can be written using only built-in JDK APIs. This class is
 * intended to "fill the gap" and provide those features of {@code Ordering} not already provided by
 * the JDK.
 *
 * @since 21.0

    }

    @Test
    void testReadModifiedPoms(@TempDir Path tempDir) throws Exception {
        // TODO a similar test should be created to test the dependency management (basically all usages
        // of DefaultModelBuilder.getCache() are affected by MNG-6530

        FileUtils.copyDirectoryStructure(new File("src/test/resources/projects/grandchild-check"), tempDir.toFile());

pkg syscall (freebsd-arm64), type Rusage struct, Msgrcv int64
pkg syscall (freebsd-arm64), type Rusage struct, Msgsnd int64
pkg syscall (freebsd-arm64), type Rusage struct, Nivcsw int64
pkg syscall (freebsd-arm64), type Rusage struct, Nsignals int64
pkg syscall (freebsd-arm64), type Rusage struct, Nswap int64
pkg syscall (freebsd-arm64), type Rusage struct, Nvcsw int64
pkg syscall (freebsd-arm64), type Rusage struct, Oublock int64

pkg syscall (darwin-arm64), type Rusage struct, Msgrcv int64
pkg syscall (darwin-arm64), type Rusage struct, Msgsnd int64
pkg syscall (darwin-arm64), type Rusage struct, Nivcsw int64
pkg syscall (darwin-arm64), type Rusage struct, Nsignals int64
pkg syscall (darwin-arm64), type Rusage struct, Nswap int64
pkg syscall (darwin-arm64), type Rusage struct, Nvcsw int64
pkg syscall (darwin-arm64), type Rusage struct, Oublock int64