[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: |
|
||||
| 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: |
| Comment by Githook User [ 27/Jun/23 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |
| 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). |