Problem/Motivation

The webship-js suite runs more than 200 scenarios in one job. It takes about 26 minutes, and the drupal.org runners stop a job at 30 minutes whatever the job asks for. The 4.0.3 tag pipeline went red that way, with no failing test.

Proposed resolution

  • Run the suite in three parallel jobs (parallel: 3), each with its own Drupal site.
  • cucumber.js shares the feature files out between the jobs by scenario count. Outside a parallel job it runs every file, as before.
  • Drop the timeout: 60m that the runners ignore.

Remaining tasks

  • ✔ File the issue
  • ➖ Merge request with a green pipeline

User interface changes

N/A

API changes

N/A

Data model changes

N/A

AI-Generated: Yes

Issue fork uikit_admin-3627154

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:

About issue forks

Comments

rajab natshah created an issue. See original summary.

rajab natshah opened merge request !14

  • rajab natshah committed 50715e31 on 4.0.x 
    ci: #3627154 Run the webship-js suite in three parallel jobs to stay...
rajab natshah’s picture

rajab natshah
he/him
commented
Status: Active » Fixed

Merged into 4.0.x. The three test jobs ran in 8 to 10 minutes each, where the one job took 26.

AI-Generated: Yes

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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