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.
<AdvanceTime byAmount={10}>
            <AdvanceTime byAmount={10} shouldComponentUpdate={false} />
          </AdvanceTime>
        </React.unstable_Profiler>,
      );
      expect(callback).toHaveBeenCalledTimes(2);
      const [mountCall, updateCall] = callback.mock.calls;
      expect(mountCall[1]).toBe('mount');
      expect(mountCall[2]).toBe(20); 
      expect(mountCall[3]).toBe(20); 
      expect(mountCall[4]).toBe(5); 
      expect(mountCall[5]).toBe(25); 
      expect(updateCall[1]).toBe('update');
      expect(updateCall[2]).toBe(10); 
      expect(updateCall[3]).toBe(20); 
      expect(updateCall[4]).toBe(55); 
      expect(updateCall[5]).toBe(65); 
    });
    it('includes time spent in render phase lifecycles', () => {
      class WithLifecycles extends React.Component {
        state = {};
        static getDerivedStateFromProps() {
          advanceTimeBy(3);
          return null;
        }
        shouldComponentUpdate() {
          advanceTimeBy(7);
          return true;
        }
        render() {