[SERVER-82290] Improve logging on JSON parsing failures from log-message tests Created: 18/Oct/23  Updated: 31/Oct/23  Resolved: 31/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Adam Rayner Assignee: Adam Rayner
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Security 2023-10-30, Security 2023-11-13
Participants:
Linked BF Score: 12

 Description   

In jstests/noPassthrough/log-message.js, we cat and then manually parse out file contents to ensure that our log message is recorded properly with various encodings and escape characters.

If another process or test fails and corrupts the log file in some way, the parsing will fail, and the test will fail without any way to know what happened, if the parsed line was valid or not, etc.

We can add some extra log output for this manual parsing in the (unlikely) event that this happens in the future.



 Comments   
Comment by Githook User [ 20/Oct/23 ]

Author:

{'name': 'Adam Rayner', 'email': 'adam.rayner@mongodb.com', 'username': 'adamtron'}

Message: SERVER-82290 additional test logging around JSON parsing directly from log file
Branch: master
https://github.com/mongodb/mongo/commit/31033a63a5a34dd142672b477d8b5cfe28762f61

Generated at Thu Feb 08 06:48:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.