This feature is meant to warn about sync priority updates that block paint (e.g. set state in layout effect) but it appears to also warn for transition priority updates. We should fix this.
const randomSample = createUserTimingEntry({
      dur: 100,
      tdur: 200,
      ph: 'X',
      cat: 'disabled-by-default-devtools.timeline',
      name: 'RunTask',
      args: {},
    });
    await expect(async () => preprocessData([randomSample])).rejects.toThrow();
  });
  it('should throw given a timeline without an explicit profiler version mark nor any other React marks', async () => {
    const cpuProfilerSample = creactCpuProfilerSample();
    await expect(
      async () => await preprocessData([cpuProfilerSample]),
    ).rejects.toThrow(
      'Please provide profiling data from an React application',
    );
  });
  it('should throw given a timeline with React scheduling marks, but without an explicit profiler version mark', async () => {
    const cpuProfilerSample = creactCpuProfilerSample();
    const scheduleRenderSample = createUserTimingEntry({
      cat: 'blink.user_timing',
      name: '--schedule-render-512-',
    });
    const samples = [cpuProfilerSample, scheduleRenderSample];
    await expect(async () => await preprocessData(samples)).rejects.toThrow(
      'This version of profiling data is not supported',
    );
  });
  it('should return empty data given a timeline with no React scheduling profiling marks', async () => {