[SERVER-72437] Clear in memory logs before each test case in txn_commit_optimizations_for_read_only_shards.js Created: 29/Dec/22  Updated: 29/Oct/23  Resolved: 28/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Jason Zhang Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-06-26, Sharding NYC 2023-07-10
Participants:
Linked BF Score: 6
Story Points: 2

 Description   

Essentially with the usage of internal transactions in new features, the server will output more transaction related logs that break the current test expecations.

Clearing the in memory logs before each test case should give us a fresh set of logs to look at per test run.



 Comments   
Comment by Githook User [ 03/Jul/23 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-72437 Clear in memory logs before each test case in txn_commit_optimizations_for_read_only_shards.js
Branch: EVG-17874-taskgen-test
https://github.com/mongodb/mongo/commit/355daa6771213df9151aadc6d40285447afea0de

Comment by Githook User [ 27/Jun/23 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-72437 Clear in memory logs before each test case in txn_commit_optimizations_for_read_only_shards.js
Branch: master
https://github.com/mongodb/mongo/commit/355daa6771213df9151aadc6d40285447afea0de

Comment by Adi Zaimi [ 18/Apr/23 ]

One possibility to fix the test is to assert by some measure other than scanning the log file (for instance a counter that distinguishes internal transactions vs non-internal ones).

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