Shared loading and running pool (#1161)
Change the behavior of the concurrency setting so that loading and running don't have separate pools. * The loading and running of a test are now done with the same resource, and the concurrency setting uniformly affects each. With `-j1` only a single test will ever be loaded at a time. * Previously the loading pool was 2x larger than the actual concurrency setting which could cause flaky tests due to tests being loaded while other tests were running, even with `-j1`.
Showing
- pkgs/test/test/runner/browser/compact_reporter_test.dart 1 addition, 1 deletionpkgs/test/test/runner/browser/compact_reporter_test.dart
- pkgs/test/test/runner/configuration/platform_test.dart 2 additions, 2 deletionspkgs/test/test/runner/configuration/platform_test.dart
- pkgs/test/test/runner/engine_test.dart 55 additions, 0 deletionspkgs/test/test/runner/engine_test.dart
- pkgs/test/test/utils.dart 5 additions, 0 deletionspkgs/test/test/utils.dart
- pkgs/test_core/CHANGELOG.md 8 additions, 0 deletionspkgs/test_core/CHANGELOG.md
- pkgs/test_core/lib/src/runner/engine.dart 19 additions, 31 deletionspkgs/test_core/lib/src/runner/engine.dart
Loading
Please register or sign in to comment