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
In this test run https://github.com/restatedev/restate/actions/runs/13764395844/job/38488506837?pr=2873#step:11:434, the test KillInvocation is stuck. From the looks of the sys_invocation table, we are not properly killing all recursive calls. It seems as if one child is still running while the direct parent and the startCallTree are completed. Since the final verification call runs on the same VO as the recursive call, the test is stuck.
slinkydeveloper
changed the title
KillingInvocation seems to not properly work with service protocol v5
KillingInvocation seems to not properly work with Killed invocation status
Mar 11, 2025
In this test run https://github.com/restatedev/restate/actions/runs/13764395844/job/38488506837?pr=2873#step:11:434, the test
KillInvocation
is stuck. From the looks of the sys_invocation table, we are not properly killing all recursive calls. It seems as if one child is still running while the direct parent and thestartCallTree
are completed. Since the final verification call runs on the same VO as the recursive call, the test is stuck.The text was updated successfully, but these errors were encountered: