[SERVER-32561] Asserts in rollback_drop_database.js are not correct for all storage engines Created: 05/Jan/18 Updated: 30/Oct/23 Resolved: 09/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.7.1 |
| Fix Version/s: | 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vesselina Ratcheva (Inactive) | Assignee: | Vesselina Ratcheva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2018-01-15 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
After the last collection is dropped, the test currently checks that there are zero collections in the database. Instead, it should simply check that previously existing collections are no longer in the database. This causes build failures on variants that use MMAPv1. |
| Comments |
| Comment by Githook User [ 09/Jan/18 ] |
|
Author: {'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb', 'email': 'vesselina.ratcheva@10gen.com'}Message: |