[Bug] Duration in reportData is incorrect when merging reports in sharding mode

[carlipprice]

Describe the bug Duration always calculated by earliest start time and the end time of the latest start. If shard 1 starts first and run much longer than 2 and 3, then calculated duration would be wrong https://github.com/cenfun/monocart-reporter/blob/d65bdb88fbe2c91e8b9c903284914f23c5bff784/tests/example/example.spec.js#L158-L172

To Reproduce

• Version: 2.9.7
• Node Version: 18
• Have you tried the latest version (including node), and does the issue still exist? yes
• Steps to reproduce the actual behavior:
  1. Start tests in sharding mode

     # start up shard
     # node 1
     npx playwright test --shard=1/3 # starts at 00:00:01 and ends at 00:00:06
     # node 2
     npx playwright test --shard=2/3 # starts at 00:00:08 and ends at 00:00:16
     # node 3
     npx playwright test --shard=3/3 # starts at 00:00:02 and ends at 00:00:24

  2. copy all output .zip to a node to perform merge

     npx monocart merge 'path-to/shard*/*.zip'
     # reportData.duration shows 15s instead of 23s

Expected behavior Sharding test duration should be calculated by earliest start and latest end.

Make a minimal reproduction

• Provide the minimal, reproducible code and options of the bug.

  test('@util getDuration', () => {
  let ranges = [
      {
          start: 1,
          end: 6
      },
      {
          start: 8,
          end: 16
      },
      {
          start: 2,
          end: 24
      }
  ];
  expect(Util.getDuration(ranges)).toBe(23);
  });

[cenfun]

Thanks, it should be fixed in monocart-reporter@2.9.8

[carlipprice]

@cenfun It works on 2.9.8! Thanks for the quick response and fix.