[SERVER-34771] secondary_reads_timestamp_visibility.js should log the read concern level when asserting on counts Created: 01/May/18 Updated: 29/Oct/23 Resolved: 07/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Storage NYC 2018-05-07 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In secondary_reads_timestamp_visibility.js we have loops like the following:
We should update the assertion message to mention the read concern level being used for that find; otherwise it makes it difficult to determine what's failing. |
| Comments |
| Comment by Githook User [ 07/May/18 ] |
|
Author: {'email': 'louis.williams@mongodb.com', 'name': 'Louis Williams', 'username': 'louiswilliams'}Message: |
| Comment by Kyle Suarez [ 01/May/18 ] |
|
Sent to the Storage Team backlog because this test was introduced as part of |