DAOS-11363 test: Increase timeout for check_free_space for SCM at the…
… end of container/multiple_delete.py
After 50 iterations of container create, IOR run, container destroy, SCM free space isn’t fully recovered. However, this may be due to the aggregation taking a while. If we wait for a while before the final free space check, the space may be fully recovered.
Increase the timeout for check_free_space() to 180 sec, pass in the SCM initial value, and see if the test passes. (Default timeout is 30 sec)
Test-tag: multi_container_delete Skip-unit-tests: true Skip-fault-injection-test: true
Required-githooks: true Signed-off-by: Makito Kano [email protected]
Bug-tracker data: Ticket title is 'Apply threshold for SCM free space check in container/multiple_delete.py' Status is 'In Review' Errors are Title of PR is too long https://daosio.atlassian.net/browse/DAOS-11363
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9974/3/execution/node/145/log
Test stage checkpatch completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9974/4/execution/node/145/log
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9974/9/execution/node/675/log
Test stage Functional Hardware Large completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-9974/10/execution/node/324/log