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
When [scheduler][run hosts] are used to run scheduler on, validation errors occur post-detatch which makes the failure invisible.
[scheduler][run hosts]
E.G. when you run an invalid workflow:
$ cylc play <id> ... <id>: <server> PID=<pid>
It looks like it worked, but it didn't:
$ cylc cat-log <id> ... ERROR - Workflow shutting down - WorkflowConfigError: This workflow requires an initial cycle point.
This didn't use to be the case, the change was likely caused by recent startup reordering.
Note: #3896 will reduce the pressure on this, however, ideally we would fix this in the cylc play command properly.
cylc play
Pull requests welcome!
The text was updated successfully, but these errors were encountered:
I have reproduced this even without [scheduler][run hosts], so maybe higher priority?
#4836 is the culprit, however I'm struggling to figure out why just by looking at the code changes. Will try more in-depth debugging...
Sorry, something went wrong.
configure()
log_start()
MetRonnie
Successfully merging a pull request may close this issue.
When
[scheduler][run hosts]
are used to run scheduler on, validation errors occur post-detatch which makes the failure invisible.E.G. when you run an invalid workflow:
It looks like it worked, but it didn't:
This didn't use to be the case, the change was likely caused by recent startup reordering.
Note: #3896 will reduce the pressure on this, however, ideally we would fix this in the
cylc play
command properly.Pull requests welcome!
The text was updated successfully, but these errors were encountered: