[SERVER-34185] Failure of data consistency checks run by resmoke.py no longer halt test execution Created: 28/Mar/18  Updated: 29/Oct/23  Resolved: 29/Mar/18

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

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-33665 Tests run by hooks should be TestCase... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: TIG 2018-04-09
Participants:

 Description   

The changes from SERVER-33665 made it so all hooks that run a static JavaScript file raise a resmokelib.errors.TestFailure exception if they fail. This means that when running with --continueOnFailure, another test will run against a MongoDB deployment that's already gotten into an inconsistent state will cause a cascade of failures. We should go back to raising a resmokelib.errors.StopExecution exception or perhaps raise a resmokelib.errors.ServerFailure exception in order to halt resmoke.py's test execution regardless of the --continueOnFailure setting.



 Comments   
Comment by Githook User [ 29/Mar/18 ]

Author:

{'email': 'max.hirschhorn@mongodb.com', 'name': 'Max Hirschhorn', 'username': 'visemet'}

Message: SERVER-34185 Introduce DataConsistencyHook for raising ServerFailures.
Branch: master
https://github.com/mongodb/mongo/commit/b0f022596c6b80e5d2d331f8fe3172c28954c027

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