Neels Hofmeyr d28aa0c2f1 fsm_dealloc_test: no need for ST_DESTROYING ... A separate ST_DESTROYING state originally helped with certain deallocation scenarios. But now that fsm.c avoids re-entering osmo_fsm_inst_term() twice and gracefully handles FSM instance deallocations for termination cascades, it is actually just as safe without a separate ST_DESTROYING state. ST_DESTROYING was used to flag deallocation and prevent entering osmo_fsm_inst_term() twice, which works only in a very limited range of scenarios. Remove ST_DESTROYING from fsm_dealloc_test.c to show that all tested scenarios still clean up gracefully. Change-Id: I05354e6cad9b82ba474fa50ffd41d481b3c697b4		2019-04-11 05:36:36 +00:00
..
fsm_dealloc_test.c	fsm_dealloc_test: no need for ST_DESTROYING	2019-04-11 05:36:36 +00:00
fsm_dealloc_test.err	fsm_dealloc_test: no need for ST_DESTROYING	2019-04-11 05:36:36 +00:00
fsm_test.c	log: fsm: allow logging the timeout on state change	2019-02-26 20:57:58 +00:00
fsm_test.err	log: fsm: allow logging the timeout on state change	2019-02-26 20:57:58 +00:00
fsm_test.ok	osmo_fsm_inst_state_chg(): set T also for zero timeout	2019-01-29 10:25:26 +00:00