[SERVER-54572] Introduce assumes_standalone_mongod tag for jscore tests Created: 16/Feb/21  Updated: 29/Oct/23  Resolved: 22/Feb/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: Backlog
Fix Version/s: 4.9.0

Type: Improvement Priority: Minor - P4
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

The following jscore tests:

  • jstests/core/dbadmin.js
  • jstests/core/opcounters_write_cmd.js
  • jstests/core/read_after_optime.js
  • jstests/core/capped_update.js

only works with single standalone mongod. They don't work neither with replicaset nor with a sharded cluster.

All these tests needs to be excluded from a wide variety of suites, at least from all the replicaset and sharding passthrough suites. At the moment we are blacklisting explicitely every one of these tests in ~45 suites.

This can be easily avoided by tagging this test with the new tag assumes_standalone_mongod and use tag exclusions rules in all those suites.



 Comments   
Comment by Githook User [ 22/Feb/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-54572 Introduce assumes_standalone_mongod tag for jscore tests
Branch: master
https://github.com/mongodb/mongo/commit/cc4854a927905dcf32fd0968176a706dc37ed329

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