`test.concurrent.only` does not work as expected

[mgwidmann]

🐛 Bug Report

When using test.concurrent.only and test.concurrent with two different tests, the test.concurrent test runs but reports as skipped. This behavior does not happen with test and test.only.

To Reproduce

Steps to reproduce the behavior:

In a test file with all test.concurrent, change one of them to test.concurrent.only and rerun test for that file.

Expected behavior

When run with regular test.only, the execution of the others are not performed and the test is marked as skipped. However, with test.concurrent.only, the test does run (only apparent via side effects like console.log) but the test is correctly marked as skipped. The test should not actually run like it does with test.only.

Link to repl or repo (highly encouraged)

Using test.only:
https://repl.it/repls/NativeHuskySweepsoftware#sum.test.js
In this repl you can see the console.log line does not appear for the skipped test.

Using test.concurrent.only:
https://repl.it/repls/WillingDazzlingCategory#sum.test.js
But in this version the console.log line does appear for the skipped test.

envinfo

N/A (used repl above for all testing)

Notes

I did not try this mixing test and test.concurrent.only but there could be an issue there as well.

[Mark1626]

I think this is related to #7997 .

https://github.com/facebook/jest/blob/c9c8dba4dd8de34269bdb971173659399bcbfd55/packages/jest-circus/src/legacy-code-todo-rewrite/jestAdapterInit.ts#L84-L90

[baruchiro]

Is it possible it is not skipping when it.concurrent.skip?

[iliubinskii]

Same problem here.

Note that if you use "it.concurrent.skip" then test marked with "skip" really does not run.
So, "it.concurrent.skip" really does not run.

However, if you use "it.concurrent.only" then other tests still run despite being marked as skipped.

Since this issue is marked as "Needs Repro" I have added reproduction repository:
https://github.com/ilyub/repro-jest-concurrent

[github-actions]

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.