[SERVER-32654] Revisit skipped tests for mobile SE to include standalone portions Created: 11/Jan/18  Updated: 06/Dec/22  Resolved: 29/Jun/18

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

Type: Improvement Priority: Major - P3
Reporter: Sulabh Mahajan Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

Mobile SE variants in evergreen skip tests that require replication or sharding. Some of these tests can also run standalone. These tests should be revisited to run the standalone portions with mobile SE.



 Comments   
Comment by Max Hirschhorn [ 29/Jun/18 ]

ian.whalen, the following was the comment I had left on the code review for SERVER-32505. I attempted to explicitly the the tests in order to ease the burden of the Storage team doing the audit themselves.

I think it's worth noting that all of the following tests run against a standalone mongod in addition to running against a replica set and/or sharded cluster. We may want to revisit at a later point changing them to use conditional logic within the JavaScript test in order to still be able to run the relevant parts.

// Skip the rest of this test if running with the "mobile" storage engine.
if (jsTest.options().storageEngine === 'mobile') {
    jsTest.log('Skipping the rest of this test because storageEngine is "mobile"');
    return;
}

  • jstests/aggregation/bugs/server7781.js
  • jstests/aggregation/sources/addFields/use_cases.js
  • jstests/aggregation/sources/collStats/shard_host_info.js
  • jstests/aggregation/sources/facet/use_cases.js
  • jstests/aggregation/sources/lookup/lookup.js
  • jstests/auth/authentication_restrictions.js
  • jstests/auth/authentication_restrictions_role.js
  • jstests/auth/copyauth.js
  • jstests/auth/resource_pattern_matching.js

There's also some additional tests in SERVER-32507 from the jstests/noPassthrough/ directory which would need to be audited as well.

Unfortunately, the changes from SERVER-32052 and SERVER-33882 have caused many more tests in these directories to be tagged with "requires_sharding" because we chose an approach which made tests no longer runnable in a sharded cluster if the storage engine doesn't support running as a replica set (e.g. mobile and non-journaling). I had advised the Sharding team of a different approach in this comment on SERVER-33950 because we still haven't actually done SERVER-32531. I don't think it is appropriate for the Storage team to do significantly more work on this ticket just because we weren't diligent about how we tagged tests. I'll accept this ticket being closed as "Won't fix".

Comment by Ian Whalen (Inactive) [ 28/Jun/18 ]

max.hirschhorn: We think this came about as a part of a discussion with you. We're worried about this taking a lot of time and not returning much value. Are you thinking of some specific functionality that Mobile supports for which we're going to lose coverage?

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