Skip to content
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

Make sure tune_cpu gets started #176

Merged
merged 1 commit into from
Sep 25, 2024
Merged

Conversation

vmcj
Copy link
Member

@vmcj vmcj commented Sep 17, 2024

In the past we could (and did) fail somewhere in the playbook which would result in not handling this notified handler. This also meant that we would not copy the file again on the next run, so didn't kick the handler and also didn't hit the handler on the next run.

The disadvantage here is we might hit other handlers more often if next roles want to hit the same handler.

@vmcj vmcj requested a review from Kevinjil September 17, 2024 11:38
In the past we could (and did) fail somewhere in the playbook which
would result in not handling this notified handler. This also meant that
we would not copy the file again on the next run, so didn't kick the
handler and also didn't hit the handler on the next run.

The disadvantage here is we might hit other handlers more often if next
roles want to hit the same handler.
@vmcj vmcj merged commit 0b0ee14 into DOMjudge:main Sep 25, 2024
3 checks passed
@vmcj vmcj deleted the turboboost_starting branch September 25, 2024 15:52
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.

3 participants