Skip to content

chore(project): split Desktop Nimbus UI into single-worker jobs - #17148

Draft
jaredlockhart wants to merge 3 commits into
mainfrom
17132
Draft

chore(project): split Desktop Nimbus UI into single-worker jobs#17148
jaredlockhart wants to merge 3 commits into
mainfrom
17132

Conversation

@jaredlockhart

Copy link
Copy Markdown
Collaborator

Because

  • Kinto allows one pending review per collection, so several xdist workers
    driving one Kinto instance contend for a single shared resource
  • --dist loadgroup only pins tests that declare a Kinto fixture directly, so
    tests that reach Kinto through the selenium fixture were never grouped

This commit

  • Runs integration-nimbus-ui as a matrix of four single-worker jobs, each with
    its own container stack and therefore its own Kinto
  • Removes the xdist_group tagging from the integration conftest, now that no
    job passes --dist loadgroup

Fixes #17132

Because

* Kinto allows one pending review per collection, so several xdist workers
  driving one Kinto instance contend for a single shared resource
* `--dist loadgroup` only pins tests that declare a Kinto fixture directly, so
  tests that reach Kinto through the `selenium` fixture were never grouped

This commit

* Runs `integration-nimbus-ui` as a matrix of four single-worker jobs, each with
  its own container stack and therefore its own Kinto
* Removes the `xdist_group` tagging from the integration conftest, now that no
  job passes `--dist loadgroup`

Fixes #17132
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Isolate integration test Kinto concurrency by splitting nimbus_ui into single-worker jobs

1 participant