Skip to content

Conversation

@oliver-sanders
Copy link
Member

@oliver-sanders oliver-sanders commented Oct 21, 2025

  • task events mgr: address possibly undefined variable warning
  • job log retrieval: configurable success condition
    • Presently, job log retrieval is considered successful when the
      job.out file appears, and additionally the job.err file if the job
      failed.
    • This commit adds a new configuration to allow additional files to be
      specified.
    • This will help with a MO platform where the job epilogue file is
      written asynchronously, so may only appear some time after the job.out
      file.

Check List

  • I have read CONTRIBUTING.md and added my name as a Code Contributor.
  • Contains logically grouped changes (else tidy your branch by rebase).
  • Does not contain off-topic changes (use other PRs for other changes).
  • Applied any dependency changes to both setup.cfg (and conda-environment.yml if present).
  • Tests are included (or explain why tests are not needed).
  • Changelog entry included if this is a change that can affect users
  • Cylc-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.

@oliver-sanders oliver-sanders added this to the 8.7.0 milestone Oct 21, 2025
@oliver-sanders oliver-sanders self-assigned this Oct 21, 2025
return

try:
host = get_host_from_platform(platform, bad_hosts=self.bad_hosts)
Copy link
Member Author

@oliver-sanders oliver-sanders Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split this try block into two so tools like mypy can tell that platform cannot be undefined.

(see the before part of the diff)

@oliver-sanders oliver-sanders force-pushed the job-log-retrieval.configurable-success-condition branch from 37103d6 to 5aae063 Compare October 21, 2025 15:34
@oliver-sanders oliver-sanders changed the title Job log retrieval.configurable success condition job log retrieval: configurable success condition Oct 21, 2025
@oliver-sanders oliver-sanders force-pushed the job-log-retrieval.configurable-success-condition branch from 5aae063 to 41c1e9d Compare October 22, 2025 09:26
@oliver-sanders oliver-sanders marked this pull request as draft October 23, 2025 16:22
@oliver-sanders
Copy link
Member Author

oliver-sanders commented Oct 23, 2025

Converted to draft as a newly added feature (#6933) needs to be updated in response to this....

... done

@oliver-sanders oliver-sanders force-pushed the job-log-retrieval.configurable-success-condition branch from 41c1e9d to 47ce08f Compare October 30, 2025 14:12
Comment on lines +589 to +597
job_log_present = all(
(Path(local_log_dir) / file).exists()
for file in [
# the files which are used to indicate that job log retrieval
# has completed
'job.out',
*platform['retrieve job log expected files'],
]
)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ChrisPaulBennett

With this PR, the condition we use to determine whether job log retrieval has completed can also take into account these configured files. The cylc cat-log logic should also respect this.

@oliver-sanders oliver-sanders marked this pull request as ready for review October 30, 2025 14:14
* Presently, job log retrieval is considered successful when the
  `job.out` file appears, and additionally the `job.err` file if the job
  failed.
* This commit adds a new configuration to allow additional files to be
  specified.
* This will help with a MO platform where the job epilogue file is
  written asynchronously, so may only appear some time after the `job.out`
  file.
@oliver-sanders oliver-sanders force-pushed the job-log-retrieval.configurable-success-condition branch from 47ce08f to 0766817 Compare October 30, 2025 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants