[SERVER-38250] Fix assertion message creation in assert.docEq Created: 26/Nov/18  Updated: 29/Oct/23  Resolved: 27/Nov/18

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: tig-assertjs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-37868 Add multi shard passthrough for core_txn Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-12-03
Participants:

 Description   

SERVER-37868 refactored assert.docEq to use a helper method to compare documents. This inadvertently broke the assertion message thrown by this method, because it tries to log the sorted versions of the compared documents, which are only in scope within the helper, not where the assertion is created.



 Comments   
Comment by Githook User [ 27/Nov/18 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-38250 Fix assertion message creation in assert.docEq
Branch: master
https://github.com/mongodb/mongo/commit/48faa56d37f527694edfd9878f6c7d27edc5093f

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