* the members of the element set of {@code multiset2} that are not contained in {@code
   * multiset1}, with repeated occurrences of the same element appearing consecutively.
   *
   * <p>Results are undefined if {@code multiset1} and {@code multiset2} are based on different
   * equivalence relations (as {@code HashMultiset} and {@code TreeMultiset} are).
   *
   * @since 14.0
   */

   * the members of the element set of {@code multiset2} that are not contained in {@code
   * multiset1}, with repeated occurrences of the same element appearing consecutively.
   *
   * <p>Results are undefined if {@code multiset1} and {@code multiset2} are based on different
   * equivalence relations (as {@code HashMultiset} and {@code TreeMultiset} are).
   *
   * @since 14.0
   */

 * detailed at {@link ImmutableCollection}.
 *
 * <p><b>Grouped iteration.</b> In all current implementations, duplicate elements always appear
 * consecutively when iterating. Elements iterate in order by the <i>first</i> appearance of that
 * element when the multiset was created.
 *
 * <p>See the Guava User Guide article on <a href=

     */
    public void incrementHeartbeatFailures() {
        this.heartbeatFailures++;
    }

    /**
     * Gets the number of consecutive heartbeat failures.
     *
     * @return the number of consecutive heartbeat failures
     */
    public int getHeartbeatFailures() {
        return heartbeatFailures;
    }

    /**

 * according to when the first occurrence of the element was added. When the multiset contains
 * multiple instances of an element, those instances are consecutive in the iteration order. If all
 * occurrences of an element are removed, after which that element is added to the multiset, the
 * element will appear at the end of the iteration.
 *

                // Expected
            }
        }

        // Still closed
        assertEquals(SimpleCircuitBreaker.State.CLOSED, circuitBreaker.getState());

        // Success resets consecutive failures
        circuitBreaker.call(() -> "success");

        SimpleCircuitBreaker.Statistics stats = circuitBreaker.getStatistics();
        assertEquals(0, stats.consecutiveFailures);

   * defer that to Range, since it's ContiguousSet.create() that's used to create the sets. However,
   * that gets messy here, and we already have null tests for Range.
   */

  /*
   * These generators also rely on consecutive integer inputs (not necessarily in order, but no
   * holes).
   */

  // SetCreationTester has some tests that pass in duplicates. Dedup them.

                return true;
            }

            // Check if transport is failed
            if (transport.isFailed()) {
                return true;
            }

            // Check for consecutive failures
            String key = getConnectionKey(transport);
            AtomicInteger failures = consecutiveFailures.get(key);
            if (failures != null && failures.get() >= MAX_CONSECUTIVE_FAILURES) {

                            currentDirective = new Directive(userAgent);
                            robotsTxt.addDirective(currentDirective);
                        }
                        // Add to current list - multiple consecutive User-agent lines
                        // form a group and subsequent rules apply to all of them
                        currentDirectiveList.add(currentDirective);
                        continue;
                    }

    }

    /**
     * Get failure count for a handle
     *
     * @param handle notification handle
     * @return number of consecutive failures
     */
    private int getFailureCount(ChangeNotificationHandle handle) {
        return failureCounts.getOrDefault(handle.getDirectoryPath(), 0);
    }

    /**