Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

chore(infrastructure): Run 2 parallel browsers by default instead of 3 #3500

Merged
merged 1 commit into from
Sep 2, 2018

Conversation

acdvorak
Copy link
Contributor

@acdvorak acdvorak commented Sep 2, 2018

Running 3 parallel browsers is a waste of resources.

npm run screenshot:test captures screenshots in 4 browsers, so it takes the same amount of time to finish whether it run 2 or 3 browsers in parallel.

By only consuming 2 parallels, we free up a VM for someone else to use.

As before, the --parallels=N CLI flag can be used to override the default.

Running 3 of 5 parallel browsers is a waste of resources. The tests finish in the same amount of time with 2 parallel browsers, and by only using 2, we free up an extra VM for somebody else to use.

As before, the `--parallels=N` CLI flag can be used to override the default.
@mdc-web-bot
Copy link
Collaborator

All 357 screenshot tests passed for commit 7f1e764 vs. master! 💯🎉

@acdvorak acdvorak merged commit 782cd67 into master Sep 2, 2018
@acdvorak acdvorak deleted the chore/infra/parallels branch September 2, 2018 23:50
adrianschmidt pushed a commit to Lundalogik/material-components-web that referenced this pull request Sep 25, 2018
material-components#3500)

Running 3 parallel browsers is a waste of resources.

`npm run screenshot:test` captures screenshots in 4 browsers, so it takes the same amount of time to finish whether it run 2 or 3 browsers in parallel.

By only consuming 2 parallels, we free up a VM for someone else to use.

As before, the `--parallels=N` CLI flag can be used to override the default.

(cherry picked from commit 782cd67)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants