[SERVER-21962] Add testing hook for detecting anomalous log entries to resmoke.py Created: 19/Dec/15  Updated: 06/Dec/22  Resolved: 30/Oct/18

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

Type: Task Priority: Major - P3
Reporter: Kamran K. Assignee: [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-21930 Restart oplog query if oplog entries ... Closed
is related to SERVER-21867 WiredTiger oplog cursor can return re... Closed
is related to SERVER-25852 Automatically demangle stack traces i... Closed
Assigned Teams:
Decision Automation Group
Backport Requested:
v3.2
Sprint: TIG 2016-08-29, TIG 2017-01-02
Participants:

 Description   

It'd be helpful if resmoke.py could fail a test if it detected an anomalous log entry.

For example, as part of the fix for SERVER-21867 on the client side (SERVER-21930), we've added non-fatal warnings when detecting oplog ordering issues from the sync source. The presence of these warnings should cause a test to fail, even if the situation is handled gracefully by replication.


Generated at Thu Feb 08 03:58:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.