Conversation
hjoliver
left a comment
hjoliver
left a comment
There was a problem hiding this comment.
Good.
This is on an upstream branch, please contribute!
Erm, what do you mean by this? Are you suggesting we don't just merge individual PRs to master as usual, to incrementally upgrade the troubleshooting section?
The branch this PR is on is a cylc/cylc-doc branch NOT an oliver-sanders/cylc-doc branch, that means you can push new commits to this PR. I.E. I have intended this PR to be collaborative. |
Roger that (well, I think we tend to allow pushes to each other's branch too, but I guess a central branch is more clearly for that purpose). |
|
Should add "Disk IO Error" (ran out of disk space)
|
|
Addressed feedback, fleshed this out a bit. I think there's enough here to make it worthwhile merging this now so changed the milestone. |
|
(rebased) |
oliver-sanders
force-pushed
the
troubleshooting
branch
from
d38d8c4 to
e3ed685
Compare
There was a problem hiding this comment.
Looks good. I was going to add a couple of things, but it might be better to get it in then I'll propose those additions.
For the record my other thoughts were:
- Did your script fail because you needed to
chmod? log/config/flow-processed.cylcshows you the effect of Jinja2 templating.log/config/01-start-01.cylcshows you the effect of Jinja2 and task parameter expansions.
|
For the record my other thoughts were:
Good idea.
Good idea, we could do with a general Jinja2 debugging section including
I'm not sure we expand task params, or maybe just in runtime? Can't remember. Good to raise awareness of the config log directory, explain the file numbers and names and why they are useful. |
I wasn't sure, so I checked - you're right, it's just the runtime.
|
hjoliver
left a comment
hjoliver
left a comment
There was a problem hiding this comment.
Definitely need this in 8.3.0
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| To find out why a task is not being run, use the ``cylc show`` command. | ||
| This will list the task's prerequisites and xtriggers. |
There was a problem hiding this comment.
Should mention cylc show currently only works on the task pool.
| This will list the task's prerequisites and xtriggers. | |
| This will list the task's prerequisites and xtriggers. | |
| Note, ``cylc show`` can only query active (``n=0``) tasks. | |
| Waiting tasks beyond ``n=0`` have no satisfied prerequisites. |
With a link to the meaning of "active tasks" - which has just been redefined by #660
There was a problem hiding this comment.
Added note to remove this on the "task matching" issue - cylc/cylc-flow#5827
There was a problem hiding this comment.
Update: cylc show now works via the datastore, on tasks in the n-window.
I've corrected this text as part of #798
|
@wxtim - do you want to (or have you) posted another issue for your additional points above? #638 (review) |
It's #725 |
|
Comments addressed bar a couple. |
Co-authored-by: Hilary James Oliver <hilary.j.oliver@gmail.com>
3 participants
The beginnings of a Cylc 8 troubleshooting section, mostly aimed at users as opposed to sys-admins.
This is on an upstream branch, please contribute!
Specific troubleshooting for platform setup issues (sys-admin targetted content) is probably better placed in
src/reference/config/writing-platform-configs.rst.Requirements check-list
CONTRIBUTING.mdand added my name as a Code Contributor.