[SERVER-18799] Reduce flakiness of max_time_ms.js Created: 03/Jun/15  Updated: 19/Sep/15  Resolved: 03/Jun/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.1.3
Fix Version/s: 3.1.4

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

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 4
Participants:
Linked BF Score: 15

 Description   

max_time_ms.js has been failing periodically expecting to time out on a getMore. The theory is that this happens because the timeout is measured using an approximation of the current time, which can become inaccurate under high CPU load. We should only allow the core suites to use as many jobs as there are cores available, and increase the delta between the sleep in the $where clause of the query, and the timeout specified. These will hopefully both reduce the frequency with which this failure occurs.

We would need to improve our timing logic in the server to make sure the test never sporadically fails. That work should happen in a separate ticket, if no such ticket already exists.



 Comments   
Comment by Githook User [ 03/Jun/15 ]

Author:

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

Message: SERVER-18799: Improve reliability of max_time_ms.js

Tweak the timeouts in the getMore section of the test, and cap the
number of jobs resmoke.py uses in evergreen at the number of available
cores on the machine.
Branch: master
https://github.com/mongodb/mongo/commit/cc59f160a2f10e69419bb17d4561950fa6fd78f8

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