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

Mixologic created an issue. See original summary.

Mile23’s picture

Seems 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()?

  • 777a791 committed on 2845732-add-processor-count
    Issue #2845732: removes concurrency defaults and falls back on num cber...
  • b10ba25 committed on 2845732-add-processor-count
    Issue #2845732: adds a processor count function to the environment
    

  • 6e8e6a1 committed on 2845732-add-processor-count
    Issue #2845732: reupdates failing test
    
Mixologic’s picture

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

Mixologic’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.