Skip to content
Snippets Groups Projects

Refactor CI workflow to use run-tests.sh for speed, and always run performance tests

Open Refactor CI workflow to use run-tests.sh for speed, and always run performance tests
issue/drupal_cms-3524223:ci-parallel into 1.x
1 unresolved thread
Open Adam G-H requested to merge issue/drupal_cms-3524223:ci-parallel into 1.x
1 unresolved thread

Merge request reports

Members who can merge are allowed to add commits.

Merge request pipeline #496268 failed

Stage: test
Stage: deploy

Merge request pipeline failed for 29e65cb8

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
.gitlab-ci.yml
162 extends: .phpunit-base
163 parallel:
164 matrix:
165 *components
166 variables:
167 # Skip performance tests by default.
168 PHPUNIT_OPTIONS: '--exclude-group=OpenTelemetry $CI_PROJECT_DIR/$DIR'
169 174 rules:
170 175 # Don't test the `drupal_cms_analytics` recipe, because it is a metapackage.
171 176 - if: $DIR =~ /\/drupal_cms_analytics$/
172 177 when: never
173 - if: $PERFORMANCE_TEST == "1"
174 when: never
175 178 - when: on_success
176 179
177 test performance:
  • C
    catch @catch

    Performance tests should continue to run serially because there can be issues with performance tests and multiple chromedriver instances, and also with timings when tests run at the same time. Especially if/when things finally work with https://gander.tag1.io/?orgId=1&refresh=30s (which I couldn't get working for Drupal CMS when I tried last time.

  • Please register or sign in to reply
Please register or sign in to reply