[SERVER-38398] Investigate sync_tail_test after StringMap change Created: 04/Dec/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Henrik Edin Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Sprint: Dev Tools 2018-12-31, Dev Tools 2019-01-14
Participants:

 Description   

Commit https://github.com/mongodb/mongo/commit/279fba2819e281053b19507e06b862b852d4e85f removed the MultiApplyAssignsOperationsToWriterThreadsBasedOnNamespaceHash test because with the new StringMap implementation the internal hash produced is not deterministic between runs. See the corresponding change in sync_tail.cpp

Perhaps there's a way to re-write this test to not loose test coverage.
For more details, see the discussion in: https://mongodbcr.appspot.com/243700002/


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