Problem/Motivation

The nightwatch job runs with four concurrency (and not many total jobs) and we can get away with a smaller CPU request, this will allow other smaller jobs to co-exist on the same machine.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3469070

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

catch created an issue. See original summary.

catch’s picture

Status: Active » Needs review
catch’s picture

Set it to 16 which is also the number of the maximum possible browser instances. With 12 I got one timeout which might have been a fluke or too low CPU, but let's try 16 and see how it goes rather than introducing even more random test failures.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community

Seems straight forward and don't imagine it broke unit tests.

  • nod_ committed e4280812 on 10.3.x
    Issue #3469070 by catch, smustgrave: Reduce CPU request for Nightwatch...

  • nod_ committed 2d8df6ac on 10.4.x
    Issue #3469070 by catch, smustgrave: Reduce CPU request for Nightwatch...

  • nod_ committed 13cbf867 on 11.0.x
    Issue #3469070 by catch, smustgrave: Reduce CPU request for Nightwatch...

  • nod_ committed 2258a66b on 11.x
    Issue #3469070 by catch, smustgrave: Reduce CPU request for Nightwatch...
nod_’s picture

Version: 11.x-dev » 10.3.x-dev
Status: Reviewed & tested by the community » Fixed

Committed and pushed 2258a66bdc to 11.x and 13cbf867d2 to 11.0.x and 2d8df6ac4c to 10.4.x and e4280812f3 to 10.3.x. Thanks!

Status: Fixed » Closed (fixed)

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