Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Catalog and Routing
Sprint:
CAR Team 2024-12-23, CAR Team 2025-01-06, CAR Team 2025-01-20
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

As we aim to progressively transition towards the core testing infrastructure to qualify the behavior of sharded clusters, we should stop creating new test files within jstests/sharding. The objective of this ticket is to create a new task that rejects the submission of an evergreen patch if it includes file creations under such a path.

depends on

SERVER-97544 The coverage guaranteed by JS core test suites is not on par with ShardingTest-based ones

Closed

SERVER-98315 Ensure that relevant noPassthrough test cases are executed against multiple Sharded Cluster Topologies

Backlog

SERVER-99356 Improve the coverage and isolation of JS Core test cases for add/removeShard

Backlog

is related to

SERVER-98670 Clean up single-variant evergreen task apperaing in multiple variant definitions

Needs Scheduling

related to

SERVER-100775 Ensure code coverage for un/sharded, non-timeseries clustered collections within the JS core framework

Backlog

SERVER-100776 Ensure code coverage for mongod nodes with maxed mirrored read settings within the JS core framework

Closed

(1 related to)

Assignee:: Paolo Polato
Reporter:: Paolo Polato
Participants:: Paolo Polato
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Nov 20 2024 03:23:32 PM UTC
Updated:: Feb 12 2025 10:40:42 AM UTC
Confidence Status Last Update:: 04/Dec/24 2:31 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates