[SERVER-31854] After the first drop, assertSchemaMatch() should assert that subsequent drops succeed Created: 07/Nov/17  Updated: 30/Oct/23  Resolved: 02/Jan/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.6.3, 3.7.1

Type: Bug Priority: Major - P3
Reporter: Kyle Suarez Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-32273 assert_schema_match.js should assert ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Query 2018-01-15
Participants:
Linked BF Score: 0

 Description   

In jstests/libs/assert_schema_match.js, we run several drop collections but don't assert that they succeed. We have to assert that they succeed for the second drop and onwards, otherwise state from the previous validation will linger and interferes with future assertions.



 Comments   
Comment by Githook User [ 11/Jan/18 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-31854 After the first drop, assertSchemaMatch() should assert that subsequent drops succeed

(cherry picked from commit af1bfd9f4d47672e541c5c60e68c68e436a79fbf)
Branch: v3.6
https://github.com/mongodb/mongo/commit/3e8aefe5521091906dec637a41f48ab8bc3f67ce

Comment by Githook User [ 02/Jan/18 ]

Author:

{'name': 'Tess Avitabile', 'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com'}

Message: SERVER-31854 After the first drop, assertSchemaMatch() should assert that subsequent drops succeed
Branch: master
https://github.com/mongodb/mongo/commit/af1bfd9f4d47672e541c5c60e68c68e436a79fbf

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