[SERVER-60640] sharding_update_v1_oplog_jscore_passthrough identical to sharding_jscore_passthrough Created: 12/Oct/21 Updated: 27/Oct/23 Resolved: 01/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Query Execution |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | QE 2021-11-15, QE 2021-11-29, QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-02-07, QE 2022-02-21, QE 2022-01-24 | ||||||||
| Participants: | |||||||||
| Description |
|
It looks like the v1_oplog version of the sharding jscore passthrough task got redefined in There is a separate sharding_update_v1_oplog_jscore_passthrough.yml but it isn't used anywhere. |
| Comments |
| Comment by Mihai Andrei [ 01/Jul/22 ] |
|
This suite has been deleted; going to close as gone away |
| Comment by Kyle Suarez [ 02/Mar/22 ] |
|
This ticket got lost on the backlog; flagging for retriage. |
| Comment by Kyle Suarez [ 22/Oct/21 ] |
|
ethan.zhang to close this ticket (or otherwise handle it) once his other work goes in. |
| Comment by Rushan Chen [ 14/Oct/21 ] |
|
ethan.zhang Related to what you are working on. Please close as needed. |