Skip to content

Commit

Permalink
E2E Tests: Lower workers from 100% to 50% (#97334)
Browse files Browse the repository at this point in the history
This means out of 16 cores, jest will use 8. Might be better, might be worse, but worth a try if CPU is capped at 100%.
  • Loading branch information
aidvu authored and timur987 committed Dec 13, 2024
1 parent 81351dc commit a403b33
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .teamcity/settings.kts
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ project {
// as supported (even though both TeamCity and chalk support that.)
param("env.FORCE_COLOR", "1")
param("env.NODE_OPTIONS", "--max-old-space-size=16384")
text("JEST_E2E_WORKERS", "100%", label = "Jest max workers", description = "Number or percent of cores to use when running E2E tests.", allowEmpty = true)
text("JEST_E2E_WORKERS", "50%", label = "Jest max workers", description = "Number or percent of cores to use when running E2E tests.", allowEmpty = true)
password("matticbot_oauth_token", "credentialsJSON:34cb38a5-9124-41c4-8497-74ed6289d751", display = ParameterDisplay.HIDDEN)
text("env.CHILD_CONCURRENCY", "15", label = "Yarn child concurrency", description = "How many packages yarn builds in parallel", allowEmpty = true)
text("docker_image", "registry.a8c.com/calypso/base:latest", label = "Docker image", description = "Default Docker image used to run builds", allowEmpty = true)
Expand Down

0 comments on commit a403b33

Please sign in to comment.