Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Testing Infrastructure
Labels:

Assigned Teams:

Server Tooling & Methods
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Linked BF Score:
0
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

When we have a failure during concurrent fuzzing while applying the oplog it would be helpful to have the data files to check what operation caused the fassert.

Assignee:: Backlog - Server Tooling and Methods (STM) (Inactive)
Reporter:: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Participants:: Backlog - Server Tooling and Methods (STM), DO NOT USE - Backlog - Test Infrastructure Group (TIG), Steven Vannelli
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Aug 15 2016 06:46:21 PM UTC
Updated:: Dec 06 2022 04:19:10 AM UTC

Details

Description

Attachments

Forms

Activity

People

Dates