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
The bounded-closure judgement belongs to rounds that complete and drain the old generation. An aborted round keeps the strict verdict, which is what makes a drain that closes connections it should not have visible. rt24 also judges its probe summary instead of its liveness, and its criterion text now matches what it asserts.
-c, --cases <list> Comma-separated case list, or 'all'.
172
172
available: precheck,baseline,rt01,rt02,rv9,gr0,
173
173
rt12,rt13,rt20,rt20b,rt21,rt22,rt23,
174
-
rt30,rt31 (PT-NR baselines)
174
+
rt24,rt30,rt31 (rt24 and the other
175
+
rt2x need a fault-injection build)
175
176
--fault <name> runtime fault injection (FF_FAULT); requires a
176
177
fault-injection build manifest. rt23 is the only
177
178
fault case that runs on the production form
@@ -992,7 +993,7 @@ case_rt24() {
992
993
say "=== case rt24 (abort, then HUP again: the surviving G_old drains a second time) ==="
993
994
local rc=0 hrc=0 conf out before after found=0 done=0 deadline fetch
994
995
local crit meas completions drain nworkers t0_line
995
-
crit="round 1 aborts (rx ownership flip failed, G_old untouched); round 2 completes with a bounded drain (<= 15000 ms), 6/6 FSM and workers back to $WORKERS"
996
+
crit="round 1 aborts (rx ownership flip failed, G_old untouched); round 2 completes with a bounded drain (<= 15000 ms), a T5 -> T0 transition, workers back to $WORKERS, and fresh_fail=0 with at most one closure per connection"
996
997
997
998
if [ "$FAULT"!="flip_fail_once" ];then
998
999
say "rt24: --fault=$FAULT does not match the case fault flip_fail_once"
0 commit comments