Commit 5d49965b authored by Michal Berger's avatar Michal Berger Committed by Tomasz Zawadzki
Browse files

test/scheduler: Ignore failures while removing dummy cgroups 



Upon removal, there's a small chance that new threads would jump into
these cgroups AFTER we read the list of PIDs to migrate. In such a
case, there may be some processes left preventing us from finally
removing the cgroup. Since we can't fully control that without
continuously reading the list, simply ignore it.

Fixes issue #2298

Signed-off-by: default avatarMichal Berger <michalx.berger@intel.com>
Change-Id: I0d50b975742a8b15edd25c6b4e51ab337b017eaa
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10872


Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <smatsumoto@nvidia.com>
Reviewed-by: default avatarKonrad Sztyber <konrad.sztyber@intel.com>
Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
parent d0969027

test/scheduler/isolate_cores.sh

+2 −2
Original line number Diff line number Diff line
@@ -7,8 +7,8 @@ restore_cgroups() { 
	xtrace_disable

	kill_in_cgroup "/cpuset/spdk"

	remove_cgroup "/cpuset/spdk"

	remove_cgroup "/cpuset/all"

	remove_cpuset_cgroup

	remove_cgroup "/cpuset/all" || true

	remove_cpuset_cgroup || true

	xtrace_restore

}