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.
expect(updateCall[4]).toBe(28); 
      expect(updateCall[5]).toBe(43); 
    });
    describe('with regard to interruptions', () => {
      it('should accumulate actual time after a scheduling interruptions', () => {
        const callback = jest.fn();
        const Yield = ({renderTime}) => {
          advanceTimeBy(renderTime);
          ReactTestRenderer.unstable_yield('Yield:' + renderTime);
          return null;
        };
        advanceTimeBy(5); 
        
        const renderer = ReactTestRenderer.create(
          <React.unstable_Profiler id="test" onRender={callback}>
            <Yield renderTime={2} />
            <Yield renderTime={3} />
          </React.unstable_Profiler>,
          {unstable_isAsync: true},
        );
        expect(renderer).toFlushThrough(['Yield:2']);
        expect(callback).toHaveBeenCalledTimes(0);
        
        expect(renderer).toFlushAll(['Yield:3']);
        
        expect(callback).toHaveBeenCalledTimes(1);
        const [call] = callback.mock.calls;
        expect(call[2]).toBe(5); 
        expect(call[3]).toBe(5); 
        expect(call[4]).toBe(5);