Skip to content

Explicitly set the child process working directory if we run the plugin #694 #695

New issue

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

Merged
merged 2 commits into from
Aug 11, 2022

Conversation

sergeypospelov
Copy link
Member

@sergeypospelov sergeypospelov commented Aug 9, 2022

Description

  • We explicitly set the child process working directory as the project root
  • Also refactored services a bit

Fixes #694

Type of Change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual Scenario

To reproduce section from #694 succeeds.

Checklist (remove irrelevant options):

  • The change followed the style guidelines of the UTBot project
  • Self-review of the code is passed
  • The change contains enough commentaries, particularly in hard-to-understand areas
  • No new warnings
  • All tests pass locally with my changes

@sergeypospelov sergeypospelov changed the title Explicitly set the child process working directory if we run the plugin Explicitly set the child process working directory if we run the plugin #694 Aug 10, 2022
@sergeypospelov sergeypospelov force-pushed the sergey/explicitly_set_working_dir branch from 6a51e4b to d460e30 Compare August 11, 2022 09:00
@sergeypospelov sergeypospelov merged commit c38666c into main Aug 11, 2022
@sergeypospelov sergeypospelov deleted the sergey/explicitly_set_working_dir branch August 11, 2022 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

The child process working directory differs from the test runner working directory
2 participants