[SERVER-57040] Add a test-only command to trigger a tripwire assertion Created: 18/May/21  Updated: 29/Oct/23  Resolved: 06/Aug/21

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

Type: Task Priority: Major - P3
Reporter: Kyle Suarez Assignee: Raunak Chowdhury (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes CDRIVER-4120 Tests inspecting failpoint error mess... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-06-28, Query Execution 2021-07-12, Query Execution 2021-07-26, QE 2021-08-09, QE 2021-08-23
Participants:

 Description   

This would be helpful for our test infrastructure, which ideally would catch legit tripwire assertions being triggered. If we had a dependable way to trigger one, we could test that our testing infrastructure reliably catches them.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 06/Aug/21 ]

Author:

{'name': 'Raunak Chowdhury', 'email': 'raunak.chowdhury@mongodb.com', 'username': 'raunakchowdhury'}

Message: SERVER-57040 Add a test-only tripwire assert (tassert) to the failCommand failpoint
Branch: master
https://github.com/mongodb/mongo/commit/8d1608f0747d8c7d3769076b114aa56bd1e815f6

Comment by Billy Donahue [ 01/Jul/21 ]

I don't know if we want tassert to change the error messages. I consider tassert to be invisible to the caller.
Maybe it's a piece of metadata delivered in the response but not part of the error message?

Comment by Ian Boros [ 18/May/21 ]

We may also want this ticket to include adding the word "tassert" or some other string to the error message produced by a tassert() failure.

Generated at Thu Feb 08 05:40:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.