[SERVER-85458] fix expected secure allocation count in secureAllocBytesCount test in secure_allocator_test.cpp Created: 19/Jan/24  Updated: 07/Feb/24  Resolved: 26/Jan/24

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

Type: Bug Priority: Major - P3
Reporter: Niaz Pavel Assignee: Niaz Pavel
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.3
Steps To Reproduce:

secure_allocator_test failed on enterprise-rhel-82-arm64-grpc.

Sprint: Security 2024-01-22, Security 2024-02-05
Participants:
Linked BF Score: 38

 Description   

SERVER-74289 added statistics for secure allocation. secure_allator_test.cpp added a test which compares secure allocation paged bytes with the expected bytes. The expected byte count for a platform or a test case is wrong. One of the tests is failing on enterprise-rhel-82-arm64-grpc. 



 Comments   
Comment by Niaz Pavel [ 26/Jan/24 ]

It introduces a page allocation at the start of the secure allocation byte count test, so that we can predict where the new allocation page for the test allocations should start.

Comment by Githook User [ 25/Jan/24 ]

Author:

{'name': 'Niaz Pavel', 'email': 'niaz.pavel@mongodb.com', 'username': 'niazpavelatmongo'}

Message: SERVER-85458 fix expected secure allocation count in secureAllocBytesCount test in secure_allocator_test.cpp

GitOrigin-RevId: 1f950ae202015d0da854de995fdd34b088594d1f
Branch: master
https://github.com/mongodb/mongo/commit/5abb98c9a959f4d68791c0c52ac7166b20f44b31

Comment by Niaz Pavel [ 24/Jan/24 ]

https://github.com/10gen/mongo/pull/18204

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