Murdock results

✔️ PASSED

bef6232 tests/event_periodic_callback: add test for oneshot event

Artifacts

• Documentation preview

I'm not too familiar with the details of the different event queue APIs, but the naming event_periodic_callback_onshot() sounds confusing. I would expect to be an event either periodic or oneshot :P

I'm not too familiar with the details of the different event queue APIs, but the naming event_periodic_callback_onshot() sounds confusing. I would expect to be an event either periodic or oneshot :P

I would not expect a periodic event to count but somehow it does looks a bit going a egg-laying-wool-milk-pig attempt to events which are not events but tasks that are parsed by workers named event threads

I think the naming of and the actual implementation is quiet fitting

I agree that this is confusing, we can do much better simply by not trying to stack too much on top of each other - see #21219