tree 3349ef77fb46b8c961fde7ac533ef7fddfc302d6
parent d58de22faba77291e6c3dc6dda34adeb00a1c5fe
author Jacob MacDonald <jakemac@google.com> 1580322775 -0800
committer GitHub <noreply@github.com> 1580322775 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJeMc/XCRBK7hj4Ov3rIwAAdHIIAJRDzHVjV6iJF0z249DRGg7H
 ojPYM+/1L+anQyA1DjwcQmoSoTlJ7Lxetnuq4NRxMcXKSNGIw78HCgsb0taHgsya
 YzEI5a6Fq/dRcPHlWsxz6E9VMHU6FiNzHa8PmGPJuwny2Bdilc6w9jl8fX/2WNVE
 b6XQMKeVjMYYX7Xr71+A3RUNwcsidwNbYWpT3RIUVf/lrIUsE5W6LGFJz+Zx7e5T
 6HPHNDBboSXwnE1CjbYSUMceejwC4FlIo6hJ0vl5w5c/5ToCH9NlcfX58bSWvlur
 P0tiAh3+SCu5R+Vemd+UK05viXZL5DqCRIaQGimzts9M6ZAIoofVRKJQuQ6nN7o=
 =8mJ4
 -----END PGP SIGNATURE-----
 

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`.