While working on the DevTools profiler, I've noticed that durations are sometimes incorrect. This seems to be vaguely related to high/low priority state updates. Need to track this down more so I'm filing an issue for myself.
</React.unstable_Profiler>,
      );
      
      expect(callback).toHaveBeenCalledTimes(3);
      callback.mockReset();
      renderer.unstable_flushSync(() => {
        instance.setState({
          count: 1,
        });
      });
      
      
      expect(callback).toHaveBeenCalledTimes(2);
      expect(callback.mock.calls[0][0]).toBe('middle');
      expect(callback.mock.calls[1][0]).toBe('outer');
    });
    it('decreases actual time but not base time when sCU prevents an update', () => {
      const callback = jest.fn();
      advanceTimeBy(5); 
      const renderer = ReactTestRenderer.create(
        <React.unstable_Profiler id="test" onRender={callback}>
          <AdvanceTime byAmount={10}>
            <AdvanceTime byAmount={10} shouldComponentUpdate={false} />
          </AdvanceTime>
        </React.unstable_Profiler>,
      );
      expect(callback).toHaveBeenCalledTimes(1);
      advanceTimeBy(30); 
      renderer.update(
        <React.unstable_Profiler id="test" onRender={callback}>