[SERVER-30631] Run sharding tasks on larger Windows machines to increase resmoke.py concurrency Created: 12/Aug/17  Updated: 30/Oct/23  Resolved: 24/Aug/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.5.13

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Eddie Louie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2017-08-12 at 2.06.09 PM.png    
Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: TIG 2017-09-11
Participants:
Linked BF Score: 0

 Description   

The Evergreen tasks that run tests from the jstests/sharding/ directory are close to hitting the 6-hour Evergreen time limit. We should use the windows-64-vs2015-large distro on all of the Windows build variants when running sharding tasks like we already do for the Windows 2008R2 DEBUG builder in order to safely use a larger number of resmoke.py --jobs.

  • sharding
  • sharding_WT
  • sharding_auth
  • sharding_auth_audit_WT
  • sharding_csrs_continuous_config_stepdown_WT
  • sharding_WT_ese
  • sharding_last_stable_mongos_and_mixed_shards

$ rg -l 'jstests/sharding/' buildscripts/resmokeconfig/suites/
buildscripts/resmokeconfig/suites/sharding_auth.yml
buildscripts/resmokeconfig/suites/sharding.yml
buildscripts/resmokeconfig/suites/sharding_auth_audit.yml
buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
buildscripts/resmokeconfig/suites/sharding_ese.yml
buildscripts/resmokeconfig/suites/sharding_last_stable_mongos_and_mixed_shards.yml



 Comments   
Comment by Ramon Fernandez Marina [ 24/Aug/17 ]

Author:

{'username': u'elouie99', 'name': u'Eddie Louie', 'email': u'eddie.louie@mongodb.com'}

Message:SERVER-30631 Run sharding tasks on larger Windows machines to increase resmoke.py concurrency
Branch:master
https://github.com/mongodb/mongo/commit/cbb56bcd7d0d1f9d3ec503c2f815da56cd481d92

Generated at Thu Feb 08 04:24:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.