[SERVER-37317] Make sleepmillis more conservative in slow transaction logging unit tests Created: 25/Sep/18  Updated: 29/Oct/23  Resolved: 19/Nov/18

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

Type: Task Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-36697 Use virtual clock for transactions me... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-12-03
Participants:
Linked BF Score: 34

 Description   

In the TransactionParticipant unit tests, we currently sleep a bit to trigger the logging of slow transactions. Currently these sleeps are a bit flaky because they are very close to the slowMs value. We should increase the sleeps and consider reducing the slowMs value used in the test. The following tests should be updated:

  • LogTransactionInfoAfterSlowCommit
  • LogTransactionInfoAfterSlowAbort
  • LogTransactionInfoAfterSlowStashedAbort


 Comments   
Comment by Githook User [ 19/Nov/18 ]

Author:

{'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}

Message: SERVER-37317 Make sleeps more conservative in transactions metrics unit tests
Branch: v4.0
https://github.com/mongodb/mongo/commit/d90fd0c5a5bd4bf7f5a2a5f6775082ee0213bbcc

Comment by William Schultz (Inactive) [ 15/Oct/18 ]

This should be fixed in 4.1 by SERVER-36697, but we can still do it on 4.0, unless we end up backporting SERVER-36697.

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