[SERVER-63429] Create a `patch_only` test suite that runs runs a no Config pass-through hook Created: 08/Feb/22  Updated: 06/Dec/22  Resolved: 28/Sep/22

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

Type: New Feature Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Fix Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-63427 Create a pass-through python hook tha... Closed
is depended on by SERVER-63598 Umbrella ticket for minimal POC for o... Closed
Assigned Teams:
Sharding NYC
Sprint: Sharding 2022-02-21
Participants:
Story Points: 3

 Description   

This is a continuation of SERVER-63427 and is blocked by it. Add a new test suite in evergreen.yml with `patch_only` tag. Right now we have 2 suites with this tag to be used as example.

Write a pass-through suite definition that glues all of it together. Use `sharding_hello_failures_gen` and `buildscripts/resmokeconfig/suites/sharding_hello_failures.yml` as examples. The goal is to observe that the ShardingTest is started with augmented constructor that doesn't run a separate Config server.

The goal is to be able to run such a suite as a patch build manually and observe the output. Most tests are expected to fail because starting a ShardingTest without config server should not work.


Generated at Thu Feb 08 05:57:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.