-
Notifications
You must be signed in to change notification settings - Fork 11
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
Rose Stem Fixes #172
Rose Stem Fixes #172
Conversation
b86cdd2
to
9d66ff1
Compare
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.
Checked out locally, tests run and compared this behaviour on master. This works as detailed in the description. Thanks @wxtim.
Just to note that this is still the case: #170 (review) So, either:
This may be suitable for a different ticket. |
9d66ff1
to
8860884
Compare
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'm happy with the updated help. The comment about the absolute path causing error is only the case for non-svn sources and so the help update resolves that comment from me. Thanks @wxtim.
…Runner object update the help docs to match Rose 2019 fix broken test increase or decrease the verbosity of the logging.
4b5d0cb
to
39339e7
Compare
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.
Fixes the problem in my tests
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.
Thanks @wxtim
* Ensured that opts.source is not unset when opts is passed to the StemRunner object update the help docs to match Rose 2019 fix broken test increase or decrease the verbosity of the logging. * fix stuff * fixed opts.verbose
* Ensured that opts.source is not unset when opts is passed to the StemRunner object update the help docs to match Rose 2019 fix broken test increase or decrease the verbosity of the logging. * fix stuff * fixed opts.verbose
…mental_improvements_to_testing * 'master' of github.com:cylc/cylc-rose: Remove subprocess from tests (cylc#194) update stem - install interface (cylc#193) Update tests/unit/test_rose_stem_units.py response to review Update setup.cfg removed never used option Improve test coverage for Rose Stem reinstall changes to `rose-suite.conf` [tests] (cylc#178) Changed the rose stem functional tests to a more pytest-integration style. Bump rose dependency to `2.1.*` Bump dev version on master to next minor release (cylc#175) Fix changelog conflict with 1.1.x (cylc#186) Prepare release: 1.1.1 (cylc#183) Rose Stem Fixes (cylc#172) Don't pass rose variables with state ! or !! to Cylc. (cylc#171) Don't pass rose variables with state ! or !! to Cylc. (cylc#171) Bump cylc-flow dependency (cylc#173) functional tests only cleanup if succeeded
This is a small change with no associated Issue.
Summary of issue
At Rose 2019 the command
rose stem --source=X=$PWD
would set the variableconf_dir
to None by default, before passing the options to theStemRunner.process
method.At Rose 2 I had failed to do this and as a result attempts to calculate the
conf_dir
in Rose failed because there was noconf_dir
to reference.n.b. In the process of translating the Rose 2019 code I renamed
conf_dir
andsource
tosource
andstem_sources
respectively. I'm not completely happy with that decision, but I don't want to add a reversion to it to this PR.Additional things
~/cylc-run/rose-stem
#177Requirements check-list
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
.