Jim Harris 84ab68c1a3 test/scheduler: add a for_each_reactor shutdown test ... The scheduler test app is ideal for testing that the reactors properly flush any existing for_each_reactor operations during the shutdown process. This is because it has no SPDK subsystems, so the reactors stop immediately after the application is signaled to terminate. So start a for_each_reactor operation when the application starts, and then keep starting another one once the previous one completes. This serves as a regression test for issue #2206. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I69825b50ad6f3c059da11241f58a8319199e88d5 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9929 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Xiaodong Liu <xiaodong.liu@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>		2021-10-21 14:47:15 +00:00
..
.gitignore	test/scheduler: application to test behaviour of schedulers	2021-01-22 18:31:25 +00:00
Makefile	scheduler: create public API and subsystem for scheduler/governor	2021-09-07 07:33:03 +00:00
scheduler_plugin.py	test/scheduler: application to test behaviour of schedulers	2021-01-22 18:31:25 +00:00
scheduler.c	test/scheduler: add a for_each_reactor shutdown test	2021-10-21 14:47:15 +00:00
scheduler.sh	autotest: Use rpc_cmd() for rpc plugin-based tests	2021-04-02 08:22:42 +00:00