[SERVER-22595] Reactivate rollback4.js Created: 12/Feb/16  Updated: 18/Nov/16  Resolved: 12/Feb/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.4, 3.3.2

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding 10 (02/19/16)
Participants:

 Description   

It was disabled by accident.



 Comments   
Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22595 Reactivate rollback4.js
Branch: v3.2
https://github.com/mongodb/mongo/commit/b4f8f3a699646ff9f5edfa72ead35f0685f2a561

Comment by Githook User [ 12/Feb/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-22595 Reactivate rollback4.js
Branch: master
https://github.com/mongodb/mongo/commit/9432e72adf826bd1912ae21e874e3852856736f2

Comment by Charlie Swanson [ 12/Feb/16 ]

Note that this test may not work on ephemeral storage engines, see jstests/replication/rollback5.js.

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