Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Currently, a configurable option on the simpletest assessment plugin is 'DCI_Concurrency'. The issue is that this gets written into the derived build.yml file, which makes it difficult to re-run that build.yml exactly on another environment that might not have 40 cores to work with.
So, we need a reliable way to determine the number of available cores and not allow the concurrency setting to be above that, regardless of how its configured.
Comments
Comment #2
Mile23Seems like this should be a core issue against run-tests.sh to set an upper limit on concurrency based on resources.
Maybe with sys_getloadavg()?
Comment #5
MixologicThis passed tests n whatnot, so Im going to push it to production and start removing the concurrency value from pift so that if I run this different sized machines we can leverage it better.
Comment #6
Mixologic