You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible that during an agent-agent communication we don't properly catch all possible errors. Failing to catch these errors can result if the PolykeyAgent crashing randomly. We need to create a test to check for these conditions so we can prevent any problems.
There should never be a condition where the failure of an agent causes an connected agent to crash.
There should never be a condition where general operation of a PolykeyAgent causes it to crash.
We need to create tests where we do random agent-agent interactions and then force the crash of either the client or agent node. We need to make sure either of these agents don't crash unexpectedly. given the randomness of the test and how expensive starting agents are, it's unlikely to catch these errors very often but just having these tests covers our bases. These tests should be using fast-check to allow randomness of the testing.
tegefaulkes
changed the title
Make sure that any agent-agent GRPC call that is being made catches any connection errors if they can be handled. We want to prevent connection errors crashing the agent. 1-2 hours
Create tests for PolykeyAgent stability during random agent-agent interactions
Sep 21, 2022
I think such chaos testing is best done in Polykey-CLI because that encompasses the entire system and would be more illustrative of potential problems including memory leaks, resource leaks... etc.
Specification
It's possible that during an agent-agent communication we don't properly catch all possible errors. Failing to catch these errors can result if the
PolykeyAgent
crashing randomly. We need to create a test to check for these conditions so we can prevent any problems.PolykeyAgent
causes it to crash.We need to create tests where we do random agent-agent interactions and then force the crash of either the client or agent node. We need to make sure either of these agents don't crash unexpectedly. given the randomness of the test and how expensive starting agents are, it's unlikely to catch these errors very often but just having these tests covers our bases. These tests should be using
fast-check
to allow randomness of the testing.Additional context
Tasks
The text was updated successfully, but these errors were encountered: