[Bug]: `test.concurrent.each` not executing tests concurrently

Version

v27.3.1

Steps to reproduce

import { setTimeout } from 'timers/promises';

test.concurrent.each([1, 2, 3, 4, 5])(
  'concurrency test',
  async () => {
    await setTimeout(1000);
    expect(true).toBe(true);
  },
);

 PASS  src/a.spec.ts (5.457 s)
  ✓ concurrency test (1004 ms)
  ✓ concurrency test (1001 ms)
  ✓ concurrency test (1002 ms)
  ✓ concurrency test (1002 ms)
  ✓ concurrency test (1000 ms)

Test Suites: 1 passed, 1 total
Tests:       5 passed, 5 total
Snapshots:   0 total
Time:        5.653 s, estimated 6 s

Expected behavior

I expect test run time to be around 1 second

Actual behavior

Based on the run time tests seem to be run in sync.

Additional context

No response

Environment

System:
    OS: Linux 4.19 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 4800H with Radeon Graphics
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
  npmPackages:
    jest: ^27.3.1 => 27.3.1

[Mark1626]

It seems to be in jest-circus after version v27.0.0.

It works fine for me with jest-jasmine2 in v27.0.0.

Can another person try this with jest-jasmine2, to confirm it’s only in jest-circus?

// jest.config.js
{
  "testRunner": "jest-jasmine2"
}

With jest-jasmine:

 PASS  ./each.test.js
  ✓ concurrency test (998 ms)
  ✓ concurrency test
  ✓ concurrency test
  ✓ concurrency test (1 ms)
  ✓ concurrency test

Test Suites: 1 passed, 1 total
Tests:       5 passed, 5 total
Snapshots:   0 total
Time:        1.279 s, estimated 6 s

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.