fix: Update EventManager
and task::run_on_core
to ignore spurious wakeups if they happen
#340
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.
Description
notified
flag toSubscriberData
which is set / cleared appropriately and used as predicate tocv.wait(...)
notified
bool used inrun_on_core
to ensure thecv.wait(...)
uses it as the predicate, ensuring the blocking run on core does not return earlyMotivation and Context
Spurious wakeups can happen (see c++ docs on condition variable wait and associated methods). On ESP this can happen for instance if you enable light sleep and have some time-dependent wakeups.
Even though the methods changed in this PR use
wait(...)
instead ofwait_for(...)
orwait_until(...)
, these changes were applied to ensure better adherence to programming guidelines and recommendations from the c++ reference / standard.How has this been tested?
event_manger/example
on esp32s3task/example
on esp32s3Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Event Manager example output snippet:
Task example output snippet:
Types of changes
Checklist:
Software
.github/workflows/build.yml
file to add my new test to the automated cloud build github action.