You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Tests have shown that the Bronx-23 pp.started FRE 2025 workflows have a repeatable problem.
fre pp wrapper runs the fre pp tools in order: checkout, configure-yaml, install, run, trigger
When the Cylc scheduler is not yet started, the run step starts it. The run step is essentially cylc play, which exits 0 before the Cylc scheduler is up and ready to respond to cylc trigger.
To Reproduce
Any fre pp wrapper usage where the Cylc scheduler is not yet running will cause it.
Expected behavior fre pp run itself should wait until the Cylc scheduler is actually up before exiting with success.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
…cheduler
- check to see if the scheduler is already up; if so exit right away with success
- otherwise, sleep 30 seconds, then confirm the scheduler is actually up
- if not, error
30 seconds was chosen based on hand-testing and might have to be adjusted later
Describe the bug
Tests have shown that the Bronx-23 pp.started FRE 2025 workflows have a repeatable problem.
fre pp wrapper
runs thefre pp
tools in order: checkout, configure-yaml, install, run, triggerWhen the Cylc scheduler is not yet started, the
run
step starts it. The run step is essentiallycylc play
, which exits 0 before the Cylc scheduler is up and ready to respond tocylc trigger
.To Reproduce
Any
fre pp wrapper
usage where the Cylc scheduler is not yet running will cause it.Expected behavior
fre pp run
itself should wait until the Cylc scheduler is actually up before exiting with success.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: