Description
When running multiple flutter test commands parallely via flutterTest() method for sharded tests, the cli throws the below error
Waiting for another flutter command to release the startup lock...
If the same flutter test command is ran for sharded tests without using flutterTest() method but via Process.start, the flutter command runs the sharded tests successfully.
**Expected Behavior**
When executing the `flutter test` command via `Process.start` for the shared tests, it runs without failure.
`flutterTest()` method also uses `Process.start` internally & it should run without locking `flutter` command on the sharded tests.
```dart
Process.start(
'flutter',
"--total-shards 2 --shard-index 1 '${testDirectory.path}/example_a[1]_test.dart'"
.split(' '),
);
Process.start(
'flutter',
"--total-shards 2 --shard-index 2 '${testDirectory.path}/example_a[2]_test.dart'"
.split(' '),
);
Screenshots
Additional Context
Please find the test case to reproduce the issue here:
Description When running multiple
flutter test
commands parallely viaflutterTest()
method for sharded tests, thecli
throws the below errorIf the same
flutter test
command is ran for sharded tests without usingflutterTest()
method but viaProcess.start
, theflutter
command runs the sharded tests successfully.Steps To Reproduce
flutterTest( arguments: "--total-shards 2 --shard-index 1 '${testDirectory.path}/example_a[2]_test.dart'" .split(' '), workingDirectory: tempDirectory.path, );
Screenshots
Additional Context Please find the test case to reproduce the issue here: