-
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
Exit immediately if no rose suite.conf #267
Exit immediately if no rose suite.conf #267
Conversation
have a rose-suite.conf
Tests are in a bit of a mess at the moment. Disregarding the 3.7 job failing on installation, there are 8 tests failing on the 3.8 job (but 5 of those are failing on master) Edit: never mind, I get 8 failures on master locally. Not sure why only 5 on GH Actions Edit edit: or sometimes 7 failures... |
(taking a look at the rose-stem flakeyness, they did pass on the last branch) |
This should stabilise the rose-stem tests: #268 |
The reinstall tests are broken because the interface has changed from sync to async in cylc-flow. |
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.
LGTM, are we happy to merge?
Will run tests locally... |
I get the same fails on master as on this branch. |
Make pre-configure act like post install.
Because pre-configure uses Cylc global config in the process of getting
ROSE_ORIG_HOST
it creates an instance of the global config object with the default items if it is called before the global config is otherwise instantiated, such as when loading and parsing a global config file.Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).Tests are includedChange in code covered by existing tests.Don't want to advertise that this was possible before.CHANGES.md
entry included if this is a change that can affect usersCylc-Doc pull request opened if required at cylc/cylc-doc/pull/XXXX.If this is a bug fix, PR should be raised against the relevant?.?.x
branch.