[SERVER-78107] Improve failure details for NTDI jstests Created: 14/Jun/23 Updated: 29/Oct/23 Resolved: 26/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathis Bessa | Assignee: | Mathis Bessa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Server Serverless 2023-06-26, Server Serverless 2023-07-10 | ||||
| Participants: | |||||
| Linked BF Score: | 162 | ||||
| Description |
|
We recently had a test failure which gave no information about the reason of the failure beside a the location in the code of the failure. For instance, we should favor the use of
over
An example of code can be found here. I think we should make similar changes to the `native_tenant_data_isolation*` existing tests we have.
|
| Comments |
| Comment by Githook User [ 26/Jun/23 ] |
|
Author: {'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}Message: |