[SERVER-83192] Always include zero cpuNanos in profiler Created: 13/Nov/23  Updated: 28/Dec/23  Resolved: 28/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0, 7.0.6

Type: Bug Priority: Minor - P4
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2, v7.1, v7.0
Sprint: Execution Team 2023-11-27, Execution Team 2023-12-11
Participants:
Linked BF Score: 28

 Description   

In some tests, we check that cpuNanos is present in the profiler output. It is sometimes possible for the observed cpuNanos to be non-positive, which can result in certain tests to fail.

We should just always report cpuNanos (on Linux), even if the value is zero.



 Comments   
Comment by Githook User [ 26/Dec/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-83192 Always report zero cpuNanos

(cherry picked from commit 6d8817557e1ecd0d032277eeb5df453bbb4cee6b)

GitOrigin-RevId: a3385950305d997e8b50e8aee1cf9ae128fa73c6
Branch: v7.0
https://github.com/mongodb/mongo/commit/b95fabe4f8110e4d39408cad4d0750b147ca878c

Comment by Milena Ivanova [ 06/Dec/23 ]

Requested backport to 7.0 in connection to BF-30937

Comment by Githook User [ 20/Nov/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-83192 Always report zero cpuNanos
Branch: master
https://github.com/mongodb/mongo/commit/6d8817557e1ecd0d032277eeb5df453bbb4cee6b

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