[SERVER-40305] Add diagnostic logging to max_time_ms.js Created: 22/Mar/19  Updated: 29/Oct/23  Resolved: 25/Mar/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.0.8, 4.1.10, 3.6.18

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

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0, v3.6
Participants:
Linked BF Score: 18

 Description   

This will help us diagnose a scenario where a query that is expected not to time out does so. This has happened once in our testing infrastructure.



 Comments   
Comment by Githook User [ 08/Apr/20 ]

Author:

{'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}

Message: SERVER-40305 Add logging in max_time_ms.js

(cherry picked from commit 0fcfd17a40ad22973d03b51208ca03a66c010ec5)
(cherry picked from commit d803265a34cc40a374f2409381a1ecc75dfa0a02)
Branch: v3.6
https://github.com/mongodb/mongo/commit/2005f25eed7ed88fa698d9b800fe536bb0410ba4

Comment by Githook User [ 26/Mar/19 ]

Author:

{'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}

Message: SERVER-40305 Add logging in max_time_ms.js

(cherry picked from commit 0fcfd17a40ad22973d03b51208ca03a66c010ec5)
Branch: v4.0
https://github.com/mongodb/mongo/commit/d803265a34cc40a374f2409381a1ecc75dfa0a02

Comment by Githook User [ 25/Mar/19 ]

Author:

{'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}

Message: SERVER-40305 Add logging in max_time_ms.js
Branch: master
https://github.com/mongodb/mongo/commit/0fcfd17a40ad22973d03b51208ca03a66c010ec5

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