Neverlord on neverlord
Fix edge case on the SPSC buffe… Fix error propagation in fused … Improve coverage of from_resour… (compare)
gtest_discover_testsin the cmake file, which implicitly calls ctest with
--gtest_list_tests. Using same example as in : https://github.com/actor-framework/actor-framework/blob/master/examples/testing/ping_pong.cpp. Is CAF tests not discoverable this way ? The error related to
caf::pec::not_an_optionwhich difficult to track down
high_priorityflag, everything works as expected
CAF_MAINotherwise does for you. Here's our setup for the I/O module tests: https://github.com/actor-framework/actor-framework/blob/master/libcaf_io/test/io-test.cpp.
request()..await()and then set the behavior later by calling
init_global_meta_objectsif you write a custom
main, cf. https://github.com/actor-framework/actor-framework/blob/master/libcaf_core/caf/init_global_meta_objects.hpp#L61).
a.home_system().node() != b.home_system().node(), but then realized these both return the same
node_id. I then tried
a.node() != b.node(), which works as expected. Is this a bug, or am I just misunderstanding? I am still on CAF 0.17.6.
This might help: https://www.cafcademy.com/articles/monitoring-and-linking
If "nothing happens": are you just doing regular shutdown? Links only tear down other actors in case of an error.