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(childCall[2]).toBe(20); 
      expect(childCall[3]).toBe(20); 
      expect(childCall[4]).toBe(15); 
      expect(childCall[5]).toBe(35); 
      expect(parentCall[2]).toBe(30); 
      expect(parentCall[3]).toBe(30); 
      expect(parentCall[4]).toBe(5); 
      expect(parentCall[5]).toBe(35); 
    });
    it('tracks sibling Profilers separately', () => {
      const callback = jest.fn();
      advanceTimeBy(5); 
      ReactTestRenderer.create(
        <React.Fragment>
          <React.unstable_Profiler id="first" onRender={callback}>
            <AdvanceTime byAmount={20} />
          </React.unstable_Profiler>
          <React.unstable_Profiler id="second" onRender={callback}>
            <AdvanceTime byAmount={5} />
          </React.unstable_Profiler>
        </React.Fragment>,
      );
      expect(callback).toHaveBeenCalledTimes(2);
      const [firstCall, secondCall] = callback.mock.calls;
      expect(firstCall[0]).toBe('first');
      expect(secondCall[0]).toBe('second');
      
      expect(firstCall[2]).toBe(20); 
      expect(firstCall[3]).toBe(20); 
      expect(firstCall[4]).toBe(5);