-
Notifications
You must be signed in to change notification settings - Fork 57
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
BUG: Stop looking for environment file if already running in AML #432
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be achieved simpler, please see my comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I edited the PR title for consistency, I hope that's ok.
Currently, if the user specifies a relative path as
--conda_env
, it will be found by the first process which will then start training, and change the cwd to 'outputs'. This means that spawned processes can't find the relative conda_env path. This PR enables spawned processes to still find the conda env path