import org.jspecify.annotations.Nullable;
import org.junit.Ignore;

/** Support class added to a suite as part of {@link FeatureSpecificTestSuiteBuilderTest}. */
/*
 * @Ignore affects the Android test runner (and only the Android test runner): It respects JUnit 4
 * annotations even on JUnit 3 tests.
 *
 * TODO(b/225350400): Remove @Ignore, which doesn't seem like it should be necessary and probably
 * soon won't be.
 */

import org.junit.Ignore;

/**
 * Tester for {@link SortedSetMultimap#get(Object)}.
 *
 * @author Louis Wasserman
 */
@GwtCompatible
@Ignore("test runners must not instantiate and run this directly, only via suites we build")
// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")
public class SortedSetMultimapGetTester<K, V>

import java.util.Locale;

/**
 * This class is emulated in GWT.
 *
 * @author Hayward Chan
 */
@GwtCompatible
final class Platform {

  /** Format the template with args, only supports the placeholder {@code %s}. */
  static String format(String template, Object... args) {
    return String.format(Locale.ROOT, template, args);
  }

  /** See {@link ListListIteratorTester} */

  *** getStackTraceElement(...);
  *** getStackTraceDepth(...);
}

# FinalizableReferenceQueue calls this reflectively
# Proguard is intelligent enough to spot the use of reflection onto this, so we
# only need to keep the names, and allow it to be stripped out if
# FinalizableReferenceQueue is unused.
-keepnames class com.google.common.base.internal.Finalizer {
  *** startFinalizer(...);
}

        ImmutableMap.of(
            3, ValueDifferenceImpl.create("c", "f"), 5, ValueDifferenceImpl.create("e", "g")),
        diff1.entriesDiffering());
    assertEquals(
        "not equal: only on left={2=b, 4=d}: only on right={6=z}: "
            + "value differences={3=(c, f), 5=(e, g)}",
        diff1.toString());

    MapDifference<Integer, String> diff2 = Maps.difference(right, left);
    assertFalse(diff2.areEqual());

     * either on the class-path or on the module-path. The project needs to make a choice
     * (possibly using heuristic rules), then add the dependency in only one of the paths
     * identified by {@link PathType}.
     *
     * @return file paths to place on the different tool options
     */
    @Nonnull
    Map<PathType, List<Path>> getDispatchedPaths();

    /**

name: Flaking Test
description: Report flaky tests or jobs in Kubernetes CI
labels: kind/flake
body:
  - type: textarea
    id: jobs
    attributes:
      label: Which jobs are flaking?
      description: |
        Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Kubernetes CI.
        Links to go.k8s.io/triage and/or links to specific failures in spyglass are appreciated.

import java.util.Queue;
import org.junit.Ignore;

/**
 * Base class for queue collection tests.
 *
 * @author Jared Levy
 */
@GwtCompatible
@Ignore("test runners must not instantiate and run this directly, only via suites we build")
// @Ignore affects the Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
@SuppressWarnings("JUnit4ClassUsedInJUnit3")

 -----
 2016-05-29
 -----

Maven Compat

 Maven2 classes maintained as compatibility layer for plugins that need to keep Maven2 compatibility.

 Plugins should avoid these classes and be updated to use only Maven3 dependencies (and require Maven3): see
 {{{https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies} Plugin migration to Maven3 dependencies}}

import assertk.assertions.hasMessage
import assertk.assertions.isNotNull
import java.io.IOException
import org.junit.Test
import org.junit.runner.RunWith
import org.junit.runners.JUnit4

/**
 * Android test running with only stubs.
 */
@RunWith(JUnit4::class)
class NonRobolectricOkHttpClientTest : BaseOkHttpClientUnitTest() {
  @Test
  override fun testPublicSuffixDb() {
    assertFailure { super.testPublicSuffixDb() }.all {