[SERVER-24719] Run the Validate hook on the 3.2 branch Created: 22/Jun/16  Updated: 22/Nov/16  Resolved: 25/Aug/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.2.10

Type: Improvement Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Done Votes: 1
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-24726 queryableBackupMode should ignore tem... Closed
depends on SERVER-25358 resmoke does not terminate mongod cle... Closed
Duplicate
Related
related to SERVER-25947 jsCore_v33_validate should set multiv... Closed
related to SERVER-22860 Port resmoke.py's ValidateCollections... Closed
Backwards Compatibility: Fully Compatible
Sprint: TIG 16 (06/24/16), TIG 17 (07/15/16), TIG 18 (08/05/16), TIG 2016-08-29
Participants:
Linked BF Score: 0

 Description   

We can run the validate hook on the 3.2 branch by starting a 3.3.6+ server on the same files.

This is a 3.2 only change



 Comments   
Comment by Githook User [ 25/Aug/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robertguo@me.com'}

Message: SERVER-24719 add jsCore_v33_validate to Windows

This reverts commit 827432f14aae0c6a65f70d58749bd0f72c7c6999.
Branch: v3.2
https://github.com/mongodb/mongo/commit/f4bb75a1af39f9b787690dfe59493e18bd7579bd

Comment by Robert Guo (Inactive) [ 15/Aug/16 ]

ramon.fernandez Still needs changes. I'll push it to 3.2.10

Comment by Githook User [ 28/Jul/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robert.guo@10gen.com'}

Message: SERVER-24719 remove jsCore_v33_validate from Windows
Branch: v3.2
https://github.com/mongodb/mongo/commit/827432f14aae0c6a65f70d58749bd0f72c7c6999

Comment by Githook User [ 27/Jul/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robertguo@me.com'}

Message: SERVER-24719 run index validation on v3.2
Branch: v3.2
https://github.com/mongodb/mongo/commit/4fa62d1e396647ed7e38cf62ec04efdcdf963497

Comment by Robert Guo (Inactive) [ 22/Jun/16 ]

copy of Max's comment for future reference.

What I would consider doing is downloading a 3.3 release (the most recent?) with the multiversion script and writing a special validation hook that stops the 3.2 mongod, starts the 3.3 mongod on the same dbpath (perhaps using --queryableBackupMode to avoid modifying the data files), and running db.collection.validate(true). If there's too much overhead from starting and stopping the mongod after every test, then we could do it after every N tests similar to what the CleanEveryN hook does now.

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