Skip to content

Poll comms: always process standard outputs on poll #6599

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

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

MetRonnie
Copy link
Member

@MetRonnie MetRonnie commented Feb 7, 2025

In case a task went through >1 state change since the last poll, always process the all outputs gleaned from the job poll info.

However this means that repeated polls will repeat the same outputs, so this PR also needs:

Also closes #6593

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.

@MetRonnie MetRonnie added the could be better Not exactly a bug, but not ideal. label Feb 7, 2025
@MetRonnie MetRonnie added this to the 8.5.0 milestone Feb 7, 2025
@MetRonnie MetRonnie self-assigned this Feb 7, 2025
@MetRonnie MetRonnie force-pushed the poll-comms branch 3 times, most recently from 5b00e12 to dd6c0c1 Compare February 11, 2025 11:39
@MetRonnie MetRonnie force-pushed the poll-comms branch 3 times, most recently from 152e791 to ab8166d Compare April 4, 2025 13:45
@MetRonnie MetRonnie linked an issue Apr 8, 2025 that may be closed by this pull request
In case a task went through >1 state change since the last poll, always process the all outputs gleaned from the job poll info
from typing_extensions import Literal


@dataclass
Copy link
Member

@oliver-sanders oliver-sanders Feb 11, 2025

Choose a reason for hiding this comment

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

If switching to dataclass please turn slots on to match the original implementation (or revert to plain class).

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, unfortunately slots cannot be used with default values in dataclasses until Python 3.10, so I have partially reverted and left a comment

'time_submit_exit', # submit (exit) time
'time_run', # run start time
'time_run_exit', # run exit time
'job_runner_call_no_lines', # line count in job runner call stdout
Copy link
Member Author

@MetRonnie MetRonnie Apr 10, 2025

Choose a reason for hiding this comment

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

job_runner_call_no_lines was unused

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
could be better Not exactly a bug, but not ideal.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent timings in job.status vs task_jobs DB table
2 participants