// Thread.interrupt can throw arbitrary exceptions due to the nio InterruptibleChannel API
        // This will make sure that tasks don't get stuck busy waiting.
        // Some of this is fixed in jdk11 (see https://bugs.openjdk.org/browse/JDK-8198692) but
        // not all.  See the test cases for examples on how this can happen.
        try {
          ((Thread) currentRunner).interrupt();
        } finally {

  }

  @J2ktIncompatible
  @GwtIncompatible // NullPointerTester
  public void testNulls() throws NoSuchMethodException {
    NullPointerTester tester = new NullPointerTester();
    // Necessary until JDK15:
    // https://bugs.openjdk.org/browse/JDK-8202469
    tester.ignore(Equivalence.class.getMethod("wrap", Object.class));

    tester.testAllPublicStaticMethods(Equivalence.class);

  }

  @J2ktIncompatible
  @GwtIncompatible // NullPointerTester
  public void testNulls() throws NoSuchMethodException {
    NullPointerTester tester = new NullPointerTester();
    // Necessary until JDK15:
    // https://bugs.openjdk.org/browse/JDK-8202469
    tester.ignore(Equivalence.class.getMethod("wrap", Object.class));

    tester.testAllPublicStaticMethods(Equivalence.class);

              <validateOnly>true</validateOnly>
              <sourceLevel>1.8</sourceLevel>
              <!--
                To avoid "java.io.IOException: User limit of inotify watches reached" under JDK10.
                Presumably we don't need inotify, since we don't intend to change files during the
                build?
                -->
              <extraJvmArgs>-Dgwt.watchFileChanges=false</extraJvmArgs>