[SERVER-35514] max_time_ms.js should not fail because interrupting JS execution caused a InternalError failure Created: 08/Jun/18  Updated: 29/Oct/23  Resolved: 12/Jun/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Improvement Priority: Major - P3
Reporter: Justin Seyster Assignee: Justin Seyster
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: Query 2018-06-18
Participants:
Linked BF Score: 7

 Comments   
Comment by Githook User [ 12/Jun/18 ]

Author:

{'username': 'jseyster', 'name': 'Justin Seyster', 'email': 'justin.seyster@mongodb.com'}

Message: SERVER-35514 Make max_time_ms.js even more robust.

There are rare cases where interrupting javascript execution on the
server with a stepdown or timeout causes an InternalError, which
causes some test commands that were expected to fail with
ExceededTimeLimit to instead fail with InternalError. For now, we just
accept InternalError as an acceptable failure when the command
executes java on the server (i.e., uses $where).

This change also includes the error in the failure message for some
assertions, which may help with diagnosis of other problems in the
future.
Branch: master
https://github.com/mongodb/mongo/commit/361ec85b0a73baac9033cf5fe646e1cb40dc8f26

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