We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In sim, GetLaunchDirectory, GetOperatingDirectory, and GetDeployDirectory return correctly:
GetLaunchDirectory
GetOperatingDirectory
GetDeployDirectory
launch: c:\Path\To\Project operating: c:\Path\To\Project deploy: c:\Path\To\Project\src\main\deploy
In unit tests, they return directories in the build directory:
launch: c:\Path\To\Project\build\test-results\frcUserProgramTest\windowsx86-64\release operating: c:\Path\To\Project\build\test-results\frcUserProgramTest\windowsx86-64\release deploy: c:\Path\To\Project\build\test-results\frcUserProgramTest\windowsx86-64\release\src\main\deploy
Looks like gradle sets the working directory to \build\test-results\frcUserProgramTest\{platform}\{buildType}.
\build\test-results\frcUserProgramTest\{platform}\{buildType}
Setting the working directory to the 5th parent directory in unit tests appears to work as a workaround:
std::error_code ec; std::filesystem::current_path(std::filesystem::current_path().parent_path().parent_path().parent_path().parent_path().parent_path(), ec);
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In sim,
GetLaunchDirectory
,GetOperatingDirectory
, andGetDeployDirectory
return correctly:In unit tests, they return directories in the build directory:
Looks like gradle sets the working directory to
\build\test-results\frcUserProgramTest\{platform}\{buildType}
.Setting the working directory to the 5th parent directory in unit tests appears to work as a workaround:
The text was updated successfully, but these errors were encountered: