-
Notifications
You must be signed in to change notification settings - Fork 94
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
Fix.all xtriggers on an itask are the same #5791
Merged
oliver-sanders
merged 4 commits into
cylc:8.2.x
from
wxtim:fix.all_xtriggers_on_an_itask_are_the_same
Nov 2, 2023
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
fix a bug where if multiple clock triggers are set for a task only one was being satisfied. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,67 @@ | ||
# THIS FILE IS PART OF THE CYLC WORKFLOW ENGINE. | ||
# Copyright (C) NIWA & British Crown (Met Office) & Contributors. | ||
# | ||
# This program is free software: you can redistribute it and/or modify | ||
# it under the terms of the GNU General Public License as published by | ||
# the Free Software Foundation, either version 3 of the License, or | ||
# (at your option) any later version. | ||
# | ||
# This program is distributed in the hope that it will be useful, | ||
# but WITHOUT ANY WARRANTY; without even the implied warranty of | ||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | ||
# GNU General Public License for more details. | ||
# | ||
# You should have received a copy of the GNU General Public License | ||
# along with this program. If not, see <http://www.gnu.org/licenses/>. | ||
"""Tests for the behaviour of xtrigger manager. | ||
""" | ||
|
||
|
||
async def test_2_xtriggers(flow, start, scheduler, monkeypatch): | ||
"""Test that if an itask has 2 wall_clock triggers with different | ||
offsets that xtrigger manager gets both of them. | ||
|
||
https://github.com/cylc/cylc-flow/issues/5783 | ||
|
||
n.b. Clock 3 exists to check the memoization path is followed, | ||
and causing this test to give greater coverage. | ||
""" | ||
task_point = 1588636800 # 2020-05-05 | ||
ten_years_ahead = 1904169600 # 2030-05-05 | ||
monkeypatch.setattr( | ||
'cylc.flow.xtriggers.wall_clock.time', | ||
lambda: ten_years_ahead - 1 | ||
) | ||
id_ = flow({ | ||
'scheduler': { | ||
'allow implicit tasks': True | ||
}, | ||
'scheduling': { | ||
'initial cycle point': '2020-05-05', | ||
'xtriggers': { | ||
'clock_1': 'wall_clock()', | ||
'clock_2': 'wall_clock(offset=P10Y)', | ||
'clock_3': 'wall_clock(offset=P10Y)', | ||
}, | ||
'graph': { | ||
'R1': '@clock_1 & @clock_2 & @clock_3 => foo' | ||
} | ||
} | ||
}) | ||
schd = scheduler(id_) | ||
async with start(schd): | ||
foo_proxy = schd.pool.get_tasks()[0] | ||
clock_1_ctx = schd.xtrigger_mgr.get_xtrig_ctx(foo_proxy, 'clock_1') | ||
clock_2_ctx = schd.xtrigger_mgr.get_xtrig_ctx(foo_proxy, 'clock_2') | ||
clock_3_ctx = schd.xtrigger_mgr.get_xtrig_ctx(foo_proxy, 'clock_2') | ||
|
||
assert clock_1_ctx.func_kwargs['trigger_time'] == task_point | ||
assert clock_2_ctx.func_kwargs['trigger_time'] == ten_years_ahead | ||
assert clock_3_ctx.func_kwargs['trigger_time'] == ten_years_ahead | ||
|
||
schd.xtrigger_mgr.call_xtriggers_async(foo_proxy) | ||
assert foo_proxy.state.xtriggers == { | ||
'clock_1': True, | ||
'clock_2': False, | ||
'clock_3': False, | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could avoid this line by just storing
None
in theclock_trigger_times
dict?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, although I've never tried using
None
as a dictionary key before, and was somewhat surprised by it as a thing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit more complex in practice - because if
offset_str
is inself.clock_trigger_times
it makes the following logic invalid and you have to write a separate loop caching the conversion ofP0Y
into seconds since epoch. I ended up with this diff:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
None
is hashable so can be used as a dict keyThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. TIL - still doesn't deal with the other problem.
Removed the plain wrong comment about using None as a dictionary key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what you mean by this. What I am suggesting is:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too late - Oliver's merged it! - And yes, I had misunderstood.