[SERVER-75181] Make resmoke write to working directory Created: 23/Mar/23 Updated: 16/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Trevor Guidry | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Correctness
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Currently resmoke writes to the /data directory. Specifically /data/db but maybe other locations also. |
| Comments |
| Comment by Trevor Guidry [ 25/Jul/23 ] |
|
steve.gross@mongodb.com I think it is low priority because this was triggered by the linked BF which we closed as gone away. However this is a reasonable thing for people to expect resmoke to be able to do so it makes sense to keep it as a request. |
| Comment by Trevor Guidry [ 24/Jul/23 ] |
|
steve.gross@mongodb.com There were failures associated with the linked PR that made it not work.
The following might be slightly wrong but is what I remember: When setting resmoke to the current directory in evergreen using an absolute path the mongo shell complained because the path was over 100 characters. This is maybe something we can fix but I could not find where the code was for this when I looked last.
So one of these two things need to be fixed before this ticket is done. |